J2EE server stopped during deployment of SPS 11

Hi,
We are using EP 7.0 on Win 2003 32 bit, Oracle 10G platform. The java version is j2sdk1.4.2_12.
Recently I applied SPS 10 on the system successfully but when I try to upgrade it to SPS 11 the J2EE server is stopped it happened during the deployment phase of sap.com\ADSSAP. The deployment is stuck at this phase and shows message u201CRestarting J2EE engine finishedu201D.
When I check from MMC I found that server0 is stopped and exit code is -11113, type is J2EE server. The part of developer trace is as follows.
[Thr 4260] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 4260] JLaunchRequestQueueInit: create pipe listener thread
[Thr 2800] WaitSyncSemThread: Thread 2800 started as semaphore monitor thread.
[Thr 5364] JLaunchRequestFunc: Thread 5364 started as listener thread for np messages.
[Thr 4260] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 4260] CPIC (version=700.2006.09.13)
[Thr 4260] [Node: server0] java home is set by profile parameter
     Java Home: C:\j2sdk1.4.2_12
[Thr 4260] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\EPP\JC01\exe\jvmx.jar
I searched the no of notes and still not able to find out the solution for this. I also changed the below parameters using configtool.bat.
-Xms2048m
-XX:NewSize=320m
-XX:MaxNewSize=320m
-XX:MaxPermSize=512m
-XX:PermSize=512m
Please suggest the solution for it.
Thanks & Regards,
Rajesh

Hi,
We are using EP 7.0 on Win 2003 32 bit, Oracle 10G platform. The java version is j2sdk1.4.2_12.
Recently I applied SPS 10 on the system successfully but when I try to upgrade it to SPS 11 the J2EE server is stopped it happened during the deployment phase of sap.com\ADSSAP. The deployment is stuck at this phase and shows message u201CRestarting J2EE engine finishedu201D.
When I check from MMC I found that server0 is stopped and exit code is -11113, type is J2EE server. The part of developer trace is as follows.
[Thr 4260] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 4260] JLaunchRequestQueueInit: create pipe listener thread
[Thr 2800] WaitSyncSemThread: Thread 2800 started as semaphore monitor thread.
[Thr 5364] JLaunchRequestFunc: Thread 5364 started as listener thread for np messages.
[Thr 4260] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 4260] CPIC (version=700.2006.09.13)
[Thr 4260] [Node: server0] java home is set by profile parameter
     Java Home: C:\j2sdk1.4.2_12
[Thr 4260] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\EPP\JC01\exe\jvmx.jar
I searched the no of notes and still not able to find out the solution for this. I also changed the below parameters using configtool.bat.
-Xms2048m
-XX:NewSize=320m
-XX:MaxNewSize=320m
-XX:MaxPermSize=512m
-XX:PermSize=512m
Please suggest the solution for it.
Thanks & Regards,
Rajesh

Similar Messages

  • J2EE Server stops with error code -1113

    Hi all
    My J2EE server stops after applying support stack 9 for SRM. It was working fine after applying stack 8 but after applying 9 and I restarted the server it stops and its not coming up. The log below of stdserver0_out file shows some security issues. Please review the log and let me know what can I do to fix this issue.
    Thanks in advance.
    stdout/stderr redirect
    node name   : server0
    pid         : 6340
    system name : SRT
    system nr.  : 00
    started at  : Wed Jul 18 22:14:59 2007
    [Thr 4600] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    SAP J2EE Engine Version 7.00   PatchLevel 108458.44 is starting...
    Loading: LogManager ... 407 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 156 ms.
    Loading: ThreadManager ... 16 ms.
    Loading: IpVerificationManager ... 15 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 125 ms.
    Loading: LockingManager ... 62 ms.
    Loading: ConfigurationManager ... 1719 ms.
    Loading: LicensingManager ... 16 ms.
    Loading: CacheManager ... 109 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service memory started. (15 ms).
      Service trex.service started. (78 ms).
      Service userstore started. (16 ms).
      Service cross started. (0 ms).
      Service file started. (140 ms).
      Service timeout started. (78 ms).
      Service jmx_notification started. (16 ms).
      Service runtimeinfo started. (125 ms).
      Service p4 started. (172 ms).
      Service classpath_resolver started. (16 ms).
      Service log_configurator started. (3469 ms).
      Service locking started. (0 ms).
      Service naming started. (281 ms).
      Service failover started. (78 ms).
      Service javamail started. (125 ms).
      Service appclient started. (110 ms).
      Service http started. (437 ms).
      Service ts started. (141 ms).
      Service jmsconnector started. (141 ms).
      Service licensing started. (15 ms).
      Service connector started. (250 ms).
      Service iiop started. (187 ms).
      Service webservices started. (469 ms).
      Service deploy started. (4187 ms).
      Service MigrationService started. (31 ms).
      Service bimmrdeployer started. (15 ms).
      Service configuration started. (31 ms).
      Service dbpool started. (859 ms).
      Service com.sap.security.core.ume.service started. (1031 ms).
    Jul 18, 2007 10:15:12... ...xt.<init>(UserContextSpi, Properties) [SAPEngine_System_Thread[impl:5]_9] Fatal: Can not instantiate UserContext with given properties.
      service security ================= ERROR =================
    Core service security failed. J2EE Engine cannot be started.
    com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:181)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
         at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:405)
         at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:84)
         at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:58)
         at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
         ... 5 more

    Hi
    Are you using LAC (Live Auction Cockpit ) ?
    <u>Try the following SAP OSS Notes -></u>
    Note 726805 - How to switch LiveAuction 2.0 to pt to different backend svr
    Note 903441 - System Copy of SAP Web AS 6.40 and 7.00 J2EE with LAC-WPS
    Note 718383 - NetWeaver: Supported UME Data Sources and Change Options
    Note 888921 Ability to override protocol,host & port for Live Auction
    Note 888922 Recommendations - Reverse Proxy and Live Auction Server
    Note 676706 SSO configuration: Live Auction 1.0 with Enterprise Portal
    Note 686437 Added ability to override protocol, host, and port
    Incase nothing works, try re-starting the J2EE Server. Else raise a Customer OSS message with SAP as well.
    Do let me know.
    Regards
    - Atul

  • SAP Netweaver 7.0 - J2EE Server Stopped exitcode -2

    Hi All,
    I am trying to Install SAP Netweaver 7.0 Preview software on to my system I have successfully done that . But when i am trying to start J2E ( i.e J2EE Server Name ) - the J2ee Server present is getting stopped saying Java VM has crashed .
    Can you please suggest what needs to be done . My system confguration is 2GB Ram , 120 GB hard drive .
    Thanks in Advance .
    Regards
    Rk

    Hi
    Note 723909
    Anytime the j2ee engine dies unexpectedly you must check the following log files in the work directory, std_server0.out and dev_server0. The dev_server0 will usually provide the exit code with a small description and the std_server0.out will provide the runtime details. In the std_server0.out search for "OutOfMemory" as this is one of the most common issues. Try to find the section of the std_server0.out that appears just before you see the restart occurring (before managers are restarting). Please provide any exception information you find there and the details just before the exception such as garbage collection data
    [J2EE Start-Up Issues u2013 Troubleshooting Guide|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e09e4a5e-8280-2a10-ca98-a59dd47d396d]
    Regards
    Uday

  • J2EE server stops while stopping irj application

    Hi
    We are getting Problem while trying to stop irj application before applying Patch 2 SP2 in EP 6.0. The server stops and displays message connection Lost in admin tool.
    Pl help me to solve the Problem.
    Regards
    Atul

    it stops every time if i make some changes. it is eclipse or bea-plugin which thinks the server has to be restarted/redeployed and so the server will be stopped (that's what i think)
    i could now "resolve" the problem with deactivating the builders on the utility-project where my beans are located.
    Properties/project/builders:
    [X] Java Builder
    [ ] Faceted Project Validation Builder
    [ ] Validation
    [ ] Web Logic J2EE Library Framework Validator
    this is a quite adventurous solution! if i restart the workbench with the configuration above, eclipse will migrate the project and "Web Logic J2EE ... Validator" is active again and doubled. This looks like so and it is still working:
    [X] Java Builder
    [ ] Faceted Project Validation Builder
    [ ] Validation
    [ ] Web Logic J2EE Library Framework Validator
    [X] Web Logic J2EE Library Framework Validator

  • J2ee Server stopped with exit code = -2

    Hi,
    We have an Xi system on Windows 2000 server. and when starting the SAP on the system SAP instance is up and running but in the java instance it shows that the J2ee server status is stopped with exit code= -2. And the jcontrol.exe is showing some processes are running.
    this is the information that i got from the trace file.
    trc file: "D:\usr\sap\SMD\J90\work\dev_SMDAgent", trc level: 1, release: "640"
    node name   : smdagent
    pid         : 4832
    system name : SMD
    system nr.  : 90
    started at  : Sun Jun 17 16:13:08 2007
    arguments   :
        arg[00] : D:\usr\sap\SMD\J90/exe\jlaunch.exe
        arg[01] : pf=D:\usr\sap\SMD\J90/profile\SMD_J90_localhost
        arg[02] : -DSAPINFO=SMD_90_server
        arg[03] : pf=D:\usr\sap\SMD\J90/profile\SMD_J90_localhost
    [Thr 4580] Sun Jun 17 16:13:08 2007
    [Thr 4580] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 4580] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 4716] JLaunchRequestFunc: Thread 4716 started as listener thread for np messages.
    [Thr 4828] WaitSyncSemThread: Thread 4828 started as semaphore monitor thread.
    [Thr 4580] NiInit2: NI already initialized; param 'maxHandles' ignored
    [Thr 4580] [Node: SMDAgent] java home is set by profile parameter
         Java Home: D:\java\j2sdk1.4.2_08
    [Thr 4580] JLaunchISetDebugMode: set debug mode [no]
    [Thr 4844] JLaunchIStartFunc: Thread 4844 started as Java VM thread.
    [Thr 4844] *** ERROR => DlLoadLib: LoadLibrary(jvm.dll) Error 126 [dlnt.c       237]
    [Thr 4844]         Error 126 = "The specified module could not be found."
    [Thr 4844] *** ERROR => Can't load VM shared library (jvm.dll) (rc=-2) [jhvmxx.c     1434]
    [Thr 4844] *** ERROR => Cannot load DLL for Java VM [jlnchxxi.c   561]
    [Thr 4580] Sun Jun 17 16:13:10 2007
    [Thr 4580] JLaunchCloseProgram: good bye (exitcode=-2)
    Please Help !
    Thanks,
    Swaroop.

    Thank you for the help. We are looking into it.
    I would like to know the difference between the batch user and background user.And batch process and background process?
    I appreciate your help.
    Thanks,
    Swaroop.

  • J2ee server stopped netweaver linux

    Hi,
    i've installed the netweaver linux java and abap vmware trial
    installation was succesfull
    i could start the all processes but not the server process, this one stopps automatically with the following answer:
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 1614998432] Thu Jan 31 13:46:01 2008
    [Thr 1614998432] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 1614998432] Thu Jan 31 13:46:02 2008
    [Thr 1614998432] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1614998432] JLaunchISetClusterId: set cluster id 428727050
    [Thr 1614998432] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 1614998432] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 1634806688] Thu Jan 31 13:46:52 2008
    [Thr 1634806688] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 1634806688] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 1634806688] SigISetIgnoreAction : SIG_IGN for signal 17
    [Thr 1634806688] JLaunchCloseProgram: good bye (exitcode = -11113)
    Could someone tell me whats the problem?
    I've 3GB RAM in the VMWare, 2GB SWAP Space, 11 GB Free hdd Space, so there should be enough space for the server.
    I hope someone could give me a hint.
    Thanks.

    Hello Friends,
               I am also facing similar error. Please help me out from this.
    Thanks in advance
    Here with attaching dev_disp log trace
    Tue Feb 05 11:25:57 2008
    kernel runs with dp version 224(ext=109) (@(#) DPLIB-INT-VERSION-224)
    length of sys_adm_ext is 360 bytes
    SWITCH TRC-HIDE on ***
    ***LOG Q00=> DpSapEnvInit, DPStart (00 544) [dpxxdisp.c   1239]
    Tue Feb 05 11:25:58 2008
         shared lib "dw_xml.dll" version 95 successfully loaded
         shared lib "dw_xtc.dll" version 95 successfully loaded
         shared lib "dw_stl.dll" version 95 successfully loaded
         shared lib "dw_gui.dll" version 95 successfully loaded
         shared lib "dw_mdm.dll" version 95 successfully loaded
    rdisp/softcancel_sequence :  -> 0,5,-1
    use internal message server connection to port 3900
    Tue Feb 05 11:26:03 2008
    WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds
    Tue Feb 05 11:26:04 2008
    ***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  5355]
    MtxInit: 30000 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
    DpIPCInit2: start server >INLD50044432A_NSP_00                    <
    DpShMCreate: sizeof(wp_adm)          6328     (904)
    DpShMCreate: sizeof(tm_adm)          3605136     (17936)
    DpShMCreate: sizeof(wp_ca_adm)          1200     (60)
    DpShMCreate: sizeof(appc_ca_adm)     1200     (60)
    DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528040/528048
    DpShMCreate: sizeof(comm_adm)          528048     (1048)
    DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    DpShMCreate: sizeof(slock_adm)          0     (96)
    DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    DpShMCreate: sizeof(file_adm)          0     (72)
    DpShMCreate: sizeof(vmc_adm)          0     (1280)
    DpShMCreate: sizeof(wall_adm)          (22440/34344/56/100)
    DpShMCreate: sizeof(gw_adm)     48
    DpShMCreate: SHM_DP_ADM_KEY          (addr: 04E60040, size: 4205552)
    DpShMCreate: allocated sys_adm at 04E60040
    DpShMCreate: allocated wp_adm at 04E61A28
    DpShMCreate: allocated tm_adm_list at 04E632E0
    DpShMCreate: allocated tm_adm at 04E63310
    DpShMCreate: allocated wp_ca_adm at 051D35A0
    DpShMCreate: allocated appc_ca_adm at 051D3A50
    DpShMCreate: allocated comm_adm at 051D3F00
    DpShMCreate: system runs without slock table
    DpShMCreate: system runs without file table
    DpShMCreate: allocated vmc_adm_list at 05254DB0
    DpShMCreate: allocated gw_adm at 05254DF0
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated ca_info at 05254E20
    DpShMCreate: allocated wall_adm at 05254E28
    MBUF state OFF
    DpCommInitTable: init table for 500 entries
    EmInit: MmSetImplementation( 2 ).
    MM global diagnostic options set: 0
    <ES> client 0 initializing ....
    <ES> InitFreeList
    <ES> block size is 1024 kByte.
    Using implementation view
    <EsNT> Memory Reset disabled as NT default
    <ES> 127 blocks reserved for free list.
    ES initialized.
    Tue Feb 05 11:26:05 2008
    rdisp/http_min_wait_dia_wp : 1 -> 1
    ***LOG Q0K=> DpMsAttach, mscon ( INLD50044432A) [dpxxdisp.c   11663]
    Tue Feb 05 11:26:06 2008
    DpStartStopMsg: send start message (myname is >INLD50044432A_NSP_00                    <)
    DpStartStopMsg: start msg sent
    CCMS: alert/MONI_SEGM_SIZE = 0   monitoring and alerting switched off.
    DpMsgAdmin: Set release to 7000, patchlevel 0
    MBUF state PREPARED
    MBUF component UP
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
    DpMsgAdmin: Set patchno for this platform to 95
    Release check o.K.
    Tue Feb 05 11:26:46 2008
    ERROR => W0 (pid 2248) died [dpxxdisp.c   14318]
    ERROR => W1 (pid 3040) died [dpxxdisp.c   14318]
    ERROR => W2 (pid 804) died [dpxxdisp.c   14318]
    my types changed after wp death/restart 0x9f --> 0x9e
    ERROR => W3 (pid 2312) died [dpxxdisp.c   14318]
    my types changed after wp death/restart 0x9e --> 0x9c
    ERROR => W4 (pid 1196) died [dpxxdisp.c   14318]
    my types changed after wp death/restart 0x9c --> 0x98
    ERROR => W5 (pid 1744) died [dpxxdisp.c   14318]
    my types changed after wp death/restart 0x98 --> 0x90
    ERROR => W6 (pid 3580) died [dpxxdisp.c   14318]
    my types changed after wp death/restart 0x90 --> 0x80
    DP_FATAL_ERROR => DpWPCheck: no more work processes
    DISPATCHER EMERGENCY SHUTDOWN ***
    Rgds,
    Dinesh

  • Error while starting NW server and j2ee server is getting stopped.

    Hi,
    I am working in NW04s. It contains ABAP sp5 and java sp9 versions. The server was working find till ten days back. After the gap of ten days, when i started to work on this SAP system, i was not able to start the j2ee server. During the startup of the server itself, j2ee server is getting stopped and dispatcher also. Following is the error bunch I got in trace. If any one has any idea about this, please reply this soon.
    [EXCEPTION]
    #1#com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed
    Connect_PM  TYPE=A ASHOST=garden SYSNR=00 GWHOST=garden GWSERV=sapgw00 PCS=1
    LOCATION    CPIC (TCP/IP) on local host with Unicode
    ERROR       connection to partner '15.70.176.191:sapgw00' broken
    TIME        Mon Nov 13 12:45:30 2006
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -6
    MODULE      nixxi.cpp
    LINE        4207
    DETAIL      NiIRead
    SYSTEM CALL recv
    ERRNO       10054
    ERRNO TEXT  WSAECONNRESET: Connection reset by peer
    COUNTER     4
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    #1.5#000E7FFD8B5D001D00000011000008540004221BAAB8047C#1163402130490#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_54##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#

    > ceException: Connect to SAP gateway failed
    > Connect_PM  TYPE=A ASHOST=garden SYSNR=00
    > GWHOST=garden GWSERV=sapgw00 PCS=1
    >
    > LOCATION    CPIC (TCP/IP) on local host with Unicode
    > ERROR       connection to partner
    > '15.70.176.191:sapgw00' broken
    You can ping this machine from your portal-nodes and you can connect to the port "sapgw00" (should be 3300) ?
    > ##0#0#Fatal#1#/System/Server#Plain###Critical
    > shutdown was invoked. Reason is: Core service
    > com.sap.security.core.ume.service failed. J2EE Engine
    > cannot be started.#
    This is the reason why your j2ee-server stops - the portal can't connect to the ume. What did you configured as the ume - the portal database, a ldap-server or a r3-system ?
    Regards
    Norman

  • Ruleset webservice: error during deployment EAR file on the java server

    Hi,
    I want to create a webservices for a ruleset which i have created with the rules composer (NWDS).
    During this proces, the following problem occurs: after creating a ruleset and the EAR file with the Web Service Generation Tool, i wanted to deploy this file on the java server for creating a webservices. During deployment, I get the following warning with no results:
    <h5>
                S U M M A R Y
    ~~~~~~~~~~~~~~~~~~~
    Successfully deployed:           0
    Deployed with warnings:           1
    Failed deployments:                0
    ~~~~~~~~~~~~~~~~~~~
    1. File:C:\Documents and Settings\Martin Gerritsen\Desktop\Webservices\DeclaratieCheckRulesetEAR.ear
         Name:DeclaratieCheckRulesetEAR
         Vendor:sap.com
         Location:localhost
         Version:2008.03.12.12.02.09
         Deploy status:Warning
         Version:NEW
         Description:
              1. Warning occurred on server 1573750 during deploy sap.com/DeclaratieCheckRulesetEAR : Web Class Existence Test: The servlet "GenericWS" must implement "javax.servlet.Servlet"., file: DeclaratieCheckRulesetWEB.war#WEB-INF/web.xml, column 0, line 0, severity: warning
              2. Exception has been returned while the [sap.com/DeclaratieCheckRulesetEAR] was starting. Warning/Exception :[
    ][[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: [server ID 1573750:[ERROR CODE DPL.DS.5035] Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
               -> [ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
         The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.
         The registered containers in this moment were [CTCContainer, MDRContainer, com.sap.security.ume, developmentserver, SCA Composites Container, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, BRMS_Content_Archive, JMSConnector, MigrationContainer, Galaxy_Content_Archive, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
         Possible reasons :
         1.Empty or incorrect application, which is not recognized by registered containers.
         2.An AS Java service, which is providing a container, is stopped or not deployed.
         3.The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about deployed components in the application deployment info].
    server ID 1573750:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
         at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:871)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:848)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:575)
         at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:489)
         at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:169)
         at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:134)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:286)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:555)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:197)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:358)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3421)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3407)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3297)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3269)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:105)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:78)
         at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:91)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:61)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:862)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:810)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:640)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:359)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:248)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:897)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:355)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:971)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
         The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.
         The registered containers in this moment were [CTCContainer, MDRContainer, com.sap.security.ume, developmentserver, SCA Composites Container, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, BRMS_Content_Archive, JMSConnector, MigrationContainer, Galaxy_Content_Archive, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
         Possible reasons :
         1.Empty or incorrect application, which is not recognized by registered containers.
         2.An AS Java service, which is providing a container, is stopped or not deployed.
         3.The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about deployed components in the application deployment info].
         at com.sap.engine.services.deploy.server.utils.ValidateUtils.missingDCinDIValidator(ValidateUtils.java:80)
         at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:158)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyLocal(StartTransaction.java:477)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:433)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:193)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:591)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:202)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:367)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.regularStartApplicationLocalAndWait(DeployServiceImpl.java:3218)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:3210)
         at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:863)
         ... 36 more
    Result
    Status:Warning
    </h5>
    Development Infrastructure:
    - development configuration: local development
    - development configuration: saptest (SAP NetWeaver CE 7.1 EHP1)
    Before I created the EAR file with the Web Service Generation Tool, I have carried out the following steps:
    - Created a ruleset (including two rules and one decision table) (development configuration: saptest)
    - Build and deploy the ruleset on the java server...
    - Created a dummy web module (development configuration: local development)
    - Added 3 dependencies (references) to the dummy web module:
    - References 1: enginee.jee5.facade (no selection on design time, deploy time or runtime)
    - References 2: tc/bl/logging/api (selection on design time, deploy time and runtime)
    - References 3: tc/brms/ facade (selection on design time, deploy time and runtime)
    - Dummy web module -> sync used DC's
    - Build dummy web module
    After that I started the Web Service Generation Tool and created the EAR file....
    1) NWDS -> window -> show view -> others -> deploy view -> deploy view
    2) Added the EAR file to External Deployable Archives
    3) deployed the file to the java server... then the warning occurs...
    How can I resolve this error?
    <h5>Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start...</h5>
    And...
    <h5>[ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
         The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.</h5>
    Can somebody help me with this problem?
    Kind regards,
    Martin Gerritsen

    Hello Martin Gerritsen,
    This is Arti from the PM team.
    It seems to me that the brms facade has not yet started in your application server. You can check whether it has started or not by doing the following -
    You need to access the JavaEE Applications running on your AS. To do this -
    1. Open the nwa portal
    2. Navigate to Operations Management > Systems > Start & Stop > Java EE Applications
    3. Search for the brms related applications available on the server.
    In case the applications have not yet been started, please try to manually start them. If you still have problem in starting the BRMS facade please contact me.
    I will send across to you a fresh set of SCAs which you can deploy into your server to resolve this issue.
    Regards,
    Arti

  • Error while deploying BPEL Process(Error during deployment: Deployment Fail

    Hi,
    when i try to deploying 11.1.1.3 - bpel project with thirdpartyparty adapter from jdeveloper to weblogic server, I got the following error.
    [04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
    [04:53:50 PM] HTTP error code returned [500]
    [04:53:50 PM] Error message from server:
    Error during deployment: Deployment Failed: [JCABinding] [TPASOAProject.Service1/1.0]Unable to complete load due to: Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    : Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    [04:53:50 PM] Check server log for more details.
    [04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
    [04:53:50 PM] #### Deployment incomplete. ####
    [04:53:50 PM] Error deploying archive file:/C:/JDeveloper/mywork/Application16/TPASOAProject/deploy/sca_TPASOAProject_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
    Please, any one can tell solution for this.
    Thanks In advance
    Amar.
    Edited by: 897448 on Dec 13, 2011 8:48 PM

    Hi,
    when i try to deploying 11.1.1.3 - bpel project with thirdpartyparty adapter from jdeveloper to weblogic server, I got the following error.
    [04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
    [04:53:50 PM] HTTP error code returned [500]
    [04:53:50 PM] Error message from server:
    Error during deployment: Deployment Failed: [JCABinding] [TPASOAProject.Service1/1.0]Unable to complete load due to: Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    : Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    [04:53:50 PM] Check server log for more details.
    [04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
    [04:53:50 PM] #### Deployment incomplete. ####
    [04:53:50 PM] Error deploying archive file:/C:/JDeveloper/mywork/Application16/TPASOAProject/deploy/sca_TPASOAProject_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
    Please, any one can tell solution for this.
    Thanks In advance
    Amar.
    Edited by: 897448 on Dec 13, 2011 8:48 PM

  • Org.xml.sax.SAXParseException during deploying project in SOA 11G

    Hello,
    I was migrating a project from SOA 10G to SOA 11G (11.1.1.3). I had to make a few changes in the project such as:
    1) Put concrete wsdl's
    2) Put "<bpelx:exec import="oracle.soa.common.util.Base64Decoder"/>" in the bpel file
    3) Change the database adapters to have "toplink" as the persistence provider as when I migrated the file , it changed it to Eclipse
    4) Fill in the port and location in the reference portion of the composite.xml
    At the end of all these changes , my project compiled properly , but when I tried to deploy it , I am getting this error:
    [09:57:27 AM] Error deploying archive sca_MIA_ModuleInvToGP_rev1.0.jar to partition "default" on server soa_server1 [sv-soafm-dev1.infinera.com:8001]
    [09:57:27 AM] HTTP error code returned [500]
    [09:57:27 AM] Error message from server:
    Error during deployment: org.xml.sax.SAXParseException: <Line 26, Column 68>: XML-20221: (Fatal Error) Invalid char in text.: <Line 26, Column 68>: XML-20221: (Fatal Error) Invalid char in text..
    [09:57:27 AM] Check server log for more details.
    I am unable to know where this particular error is coming from , and do not know how to resolve this. Does any one have any idea on what could be the possible reason for this?
    Seems to be a problem with some XML file , but I dont know which file to check.
    Any help is welcome.
    Thanks
    Manan Sanghvi

    In the session.xml schema it is a choice between driver-class/url and datasource, so you need to remove the driver-class tag as you are using a datasource.
    <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
    <datasource>jdbc/AlfaDS</datasource>
    replalce with,
    <datasource>jdbc/AlfaDS</datasource>

  • Port error while deploying a dictonary project to j2ee server

    Hello,
    I created a dictonary project in sap netweaver developer studio 7.1.The j2ee server and the database (both on a remote server) are running and configured.
    When i try to deploy it i get the following errors
    [#3]: DC API is trying to connect to '<server name>:50004' [INFO: Jan 31, 2008 9:28:26 PM /userOut/daView_category (eclipse.UserOutLocation) [Thread[main,6,main]] ]
    om.sap.ide.eclipse.deployer.api.APIException: ConnectionException,cause=[ERROR CODE DPL.DCAPI.1144] NamingException.Cannot get initial context.
    Reason: Exception during getInitialContext operation. Cannot establish connection to the remote server.
    The error is guess is the port number.My server is configured on port 50000 and here it is showing 50004.If i am correct then how do i configure my applications port number?
    I searched  and saw some messages like open \usr\SAP\<SID>\SYS\profile ,edit the port and similar solutions.Where is this "\usr\SAP\<SID>\SYS\profile " location?My server is on a remote machine.How do i configure my client to pick up the correct port ?
    Thank you in advance.
    Thanks and Regards
    Siri

    the issue got solved..the error was not about the port..on restarting the server i was able to deploy my project..

  • Sun J2EE SDK 1.3_01, java.lang.ClassCastException thrown during deployment

    I encountered a bug while using the deploytool to deploy
    an EAR file to the Sun J2EE 1.3_01 server.
    I submitted a bug report to Sun via the Sun Java Developer Connection.
    (Sorry, it has not been assigned a BugID yet)
    Question:
    Does anybody know if the web container in Sun's
    J2EE 1.3_01 server supports access to local enterprise beans?
    Screenshots of the bug are available at
    http://sync4j.sourceforge.net/deploymentbug/
    Full details below....
    -Sean
    category: j2ee
    subcategory: deployment
    release: 1.3_01
    hardware: x86
    OSversion: windows_2000
    synopsis: java.lang.ClassCastException thrown during deployment of Session bean
    java -version
    java version "1.3.1_01"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_01)
    Java HotSpot(TM) Client VM (build 1.3.1_01, mixed mode)
    C:\j2sdkee1.3\bin>j2ee -version
    Java 2 Enterprise Edition version 1.3_01, build 1.3_01-b01
    I built a EJB 2.0 compliant stateful session bean.
    The session bean has a remote interface (ISyncRemote),
    a remote home interface (ISyncHomeRemote),
    a local interface (ISyncLocal),
    and a local home interface (ISyncHomeLocal).
    I built an HTTP Servlet that is supposed to access
    the Stateful Session Bean using ISyncHomeLocal and
    ISyncLocal
    I run "deploytool.bat" in GUI mode to perform the deployment.
    During deployment, the deploytool GUI displays a message
    box which states:
    "There was a deployment error.
    java.rmi.ServerException: RemoteException occurred in server thread;
    nested exception is:
    java.rmi.RemoteException: An error was encountered while loading
    a web component.
    Please refer to
    <J2EE_HOME>/logs/<machine-name>/j2ee//j2ee/error.log
    for more information. Please verify your Application with the
    Verifier tool."
    The "error.log" file did not contain any useful information.
    I ran the J2EE "verifier.bat" tool to verify that my EAR archive is OK.
    The Sun J2EE server output this error string:
    "java.lang.ClassCastException:
    com.sun.enterprise.deployment.EjbExternalDescriptor"
    Here is the full output from the Sun J2EE server:
    C:\j2sdkee1.3\bin>j2ee -verbose
    J2EE server listen port: 1050
    Naming service started:1050
    Binding DataSource, name = jdbc/EstoreDB, url =
    jdbc:cloudscape:rmi:CloudscapeDB;create=true
    Binding DataSource, name = jdbc/Cloudscape, url =
    jdbc:cloudscape:rmi:CloudscapeDB;create=true
    Binding DataSource, name = jdbc/DB1, url =
    jdbc:cloudscape:rmi:CloudscapeDB;create=true
    Binding DataSource, name = jdbc/DB2, url =
    jdbc:cloudscape:rmi:CloudscapeDB;create=true
    Binding DataSource, name = jdbc/InventoryDB, url =
    jdbc:cloudscape:rmi:CloudscapeDB;create=true
    Binding DataSource, name = jdbc/XACloudscape, url = jdbc/XACloudscape__xa
    Binding DataSource, name = jdbc/XACloudscape__xa, dataSource =
    COM.cloudscape.core.RemoteXaDataSourc
    e@245536
    Starting JMS service...
    Initialization complete - waiting for client requests
    Binding: < JMS Destination : jms/Queue , javax.jms.Queue >
    Binding: < JMS Destination : jms/Topic , javax.jms.Topic >
    Binding: < JMS Cnx Factory : TopicConnectionFactory , Topic , No properties >
    Binding: < JMS Cnx Factory : jms/TopicConnectionFactory , Topic , No properties
    >
    Binding: < JMS Cnx Factory : QueueConnectionFactory , Queue , No properties >
    Binding: < JMS Cnx Factory : jms/QueueConnectionFactory , Queue , No properties
    >
    Starting web service at port: 8000
    Starting secure web service at port: 7000
    J2EE SDK/1.3
    Starting web service at port: 9191
    J2EE SDK/1.3
    J2EE server startup complete.
    Compiling c:\j2sdkee1.3\repository\rbi\gnrtrTMP\Sync4j Server enterprise
    application\sync4j\server\s
    yncbean\SyncBean_LocalHomeImpl.java ....
    Compiling c:\j2sdkee1.3\repository\rbi\gnrtrTMP\Sync4j Server enterprise
    application\sync4j\server\s
    yncbean\SyncBean_EJBLocalObjectImpl.java ....
    Compiling c:\j2sdkee1.3\repository\rbi\gnrtrTMP\Sync4j Server enterprise
    application\sync4j\server\s
    yncbean\SyncBean_RemoteHomeImpl.java ....
    Compiling c:\j2sdkee1.3\repository\rbi\gnrtrTMP\Sync4j Server enterprise
    application\sync4j\server\s
    yncbean\SyncBean_EJBObjectImpl.java ....
    rmic sync4j.server.syncbean.SyncBean_RemoteHomeImpl...
    rmic sync4j.server.syncbean.SyncBean_EJBObjectImpl...
    c:\j2sdkee1.3\repository\rbi\applications\Sync4j Server enterprise
    application1004172068449Server.ja
    r
    Binding name:`java:comp/env/ejb/ISyncHomeRemote`
    Binding name:`java:comp/env/ejb/ISyncHomeLocal`
    java.lang.ClassCastException:
    com.sun.enterprise.deployment.EjbExternalDescriptor
    at com.sun.enterprise.deployment.EjbReferenceDescriptor.getValue
    (EjbReferenceDescriptor.java
    :202)
    at com.sun.enterprise.naming.NamingManagerImpl.bindObjects
    (NamingManagerImpl.java:394)
    at com.sun.web.server.WebService.addContext(WebService.java:148)
    at com.sun.web.server.ServletDeployerImpl.loadWebComponents
    (ServletDeployerImpl.java:214)
    at
    com.sun.enterprise.tools.deployment.backend.JarInstallerImpl.deployWebComponent
    s
    (JarInsta
    llerImpl.java:791)
    at
    com.sun.enterprise.tools.deployment.backend.JarInstallerImpl.deployApplication
    (JarInstall
    erImpl.java:219)
    at
    org.omg.stub.com.sun.enterprise.tools.deployment.backend._JarInstallerImpl_Tie.
    invoke(Un
    known Source)
    at com.sun.corba.ee.internal.corba.ServerDelegate.dispatch
    (ServerDelegate.java:355)
    at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:273)
    at com.sun.corba.ee.internal.iiop.RequestProcessor.process
    (RequestProcessor.java:84)
    at com.sun.corba.ee.internal.orbutil.ThreadPool$PooledThread.run
    (ThreadPool.java:99)
    Does the Sun J2EE server implementation support the invocation
    of Session EJB's via a Local interface?
    Does the Sun J2EE server implementation allow a Servlet to invoke
    Session EJB's via the bean's Local interface?
    While researching this issue, I read the J2EE 1.3 final specification.
    The spec says:
    "The EJB container is required to access to local enterprise beans.
    We recommend that the web container also support access to local
    enterprise beans."
    Does the web container in Sun's J2EE server support access to local enterprise beans?

    I'm pretty much sure that you cannot access a
    local Session bean from outside the EJB container.Please read the J2EE 1.3 specification before posting messages about EJB and J2EE.
    According to the J2EE 1.3 specification:
    "The EJB container is required to support access to local enterprise beans. We recommend that the web container also support access to local enterprise beans.
    No support is provided for access to local enterprise beans from the application client container or the applet container."
    If you use local interfaces for your session bean,
    than your client must be local too. A local client is
    a client that is collocated in the same JVM with the
    session/entity that provides the local view and which
    can be tightly coupled to the bean.My client is running in the same JVM as my EJB. The client is a servlet. The servlet is running in the same JVM as the EJB.
    For what its worth, the error that I observed occurs during deployment. I haven't figured out why deployment is failing.

  • J2EE server does not start during installation

    Hi,
    I am installing WebAS JAVA 640 (NW04 SR1) on a Windows 2003/MSSQL server. I am using JAVA SDK 1.4.2_9. The installation stops at step 24/25 whereby the installer waits for the J2EE engine to start. After making 3 attempts to start the J2EE server, the installation process just hangs and I have to Cancel the installation.
    BTW, I am specifying a heap size of 1024 MB and using the "Database Only" option as UME data store during installation.
    Having checked the trace and log files, it seems the UME service fails to start, throws an exception and the message "the start of a core service failed, Web AS will not start".
    According to the information available  <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/20/361941edd5ef23e10000000a155106/content.htm">here</a>, I have checked the settings and it seems that option 2, <b>"User or group data is missing"</b> is causing the problem since database content of UME is missing. I have tried selecting entries from table UME_STRINGS but this table is empty.
    Now, the same link says that I should login to UME web application as SAP* but the problem is that without the J2EE engine starting up, I cannot login and create missing users/groups.
    Any ideas???
    Regards
    Shehryar

    Thanks to all who replied. I have actually tried all options suggested like waiting for retries until the box appears, trying to manually start the server, and reducing heap size. None worked for me. For your information, I have a 2.4 GHz machine with 4GB RAM so I think heap size should not be an issue. I checked SAP Note regarding heap size issues in Win 2003 but that does not seem to apply in my case since my system does not behave abnormally with JVM settings.
    Thanks again and I'll give it another shot.
    Regards
    Shehryar

  • Deploying a jar file into J2EE server

    Hello,
    I need to deploy a few jar files I need in my jsp pages I deploy into EP 6.  I'm using SAP Web AS 6.40.  I tried to copy them into F:\usr\sap\DEP\JC00\j2ee\cluster\server1\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\lib folder but after restarting J2EE server, I still have an error for each import I'm doing for the classes contained in my jar files.
    I also tried to pu them in PORTALINF/lib folder of my project but it doesn't work.
    Does anyone have an idea ?
    Thank you !

    Hi Olivier,
    you could try the following approach:
    1. Package your JAR files as J2EE Engine libraries and deploy them on it as described here: <a href="http://help.sap.com/saphelp_nw04/helpdata/en/9f/2ade3fc6c6ec06e10000000a1550b0/frameset.htm">Working with J2EE Libraries</a>.
    2. Set reference to this library from the application that use them. Depending on your application, refer to the appropriate documentation:
    -- reference from a J2EE app -> see <a href="http://help.sap.com/saphelp_nw04/helpdata/en/15/d5d93fe80fed06e10000000a1550b0/frameset.htm">Referencing Libraries in Applications</a>
    -- reference from a portal app -> see <a href="http://help.sap.com/saphelp_nw04/helpdata/en/02/788540ae1dbb4de10000000a1550b0/frameset.htm">Referencing Elements</a>
    Hope that helps!

  • J2ee server has suddenly stopped running with exit code -11113

    Hi,
    Have installed WAS 6.40 portal and TREX on same machine.
    j2ee server has suddenly stopped with exit code -1331.sdm and dispatcher are working fine.
    Please help..!
    here is the default trace file
    #1.5#000C29352CBB001400000149000008C400042E8904DE861B#1177065933781#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#sap.com/irj#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#Guest#192####59a32750edc011dbbdea000c29352cbb#Thread[ThreadPool.Worker7,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Pull packages failed - java.io.IOException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri:  Connection refused: connect
         at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:194)
         at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
         at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
         at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
         at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#000C29352CBB00E600000000000008C400042E89108312C3#1177066129093#com.tssap.dtr.server.deltav.nameres.impl.SecureStoreNameServerConfig#sap.com/tcdtrenterpriseapp#com.tssap.dtr.server.deltav.nameres.impl.SecureStoreNameServerConfig#Guest#192####b885af50ef2c11dbcb71000c29352cbb#Thread[Scheduler_com.tssap.dtr.server.deltav.nameres.ProcessNameReservationsTask\#176_workerThread\#0,1,Scheduler_com.tssap.dtr.server.deltav.nameres.ProcessNameReservationsTask\#176]##0#0#Warning#1#/dtr/nameres#Java###error while retrieving data from secure-store
    [EXCEPTION]
    #1#com.sap.security.core.server.securestorage.exception.ObjectRetrievalException: Could not find clientID sapcomtcdtrenterpriseapp
         at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.getClientsStorageLocation(RemoteSecureStorageClientContextImpl.java:231)
         at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.retrieveObject(RemoteSecureStorageClientContextImpl.java:724)
         at com.tssap.dtr.server.deltav.nameres.impl.SecureStoreNameServerConfig.loadConfiguration(SecureStoreNameServerConfig.java:54)
         at com.tssap.dtr.server.deltav.nameres.impl.NameReservationManager.loadNameServerConfiguration(NameReservationManager.java:162)
         at com.tssap.dtr.server.deltav.nameres.impl.NameReservationManager.processQueue(NameReservationManager.java:231)
         at com.tssap.dtr.server.deltav.nameres.ProcessNameReservationsTask._run(ProcessNameReservationsTask.java:35)
         at com.tssap.dtr.pvc.basics.transaction.AbstractSessionBoundTask.run(AbstractSessionBoundTask.java:37)
         at com.tssap.dtr.pvc.util.scheduler.Invocation$Worker.run(Invocation.java:130)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#000C29352CBB00140000014A000008C400042E8916B567FD#1177066233031#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#sap.com/irj#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#Guest#192####59a32750edc011dbbdea000c29352cbb#Thread[ThreadPool.Worker7,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Cannot contact ICE server - com.sapportals.wcm.WcmException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri:  Connection refused: connect
         at com.sapportals.wcm.util.http.slim.SlimRequester.doPerform(SlimRequester.java:608)
         at com.sapportals.wcm.util.http.slim.SlimRequester.perform(SlimRequester.java:257)
         at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:164)
         at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
         at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
         at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
         at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#000C29352CBB00140000014B000008C400042E8916B570EB#1177066233031#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#sap.com/irj#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#Guest#192####59a32750edc011dbbdea000c29352cbb#Thread[ThreadPool.Worker7,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Pull packages failed - java.io.IOException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri:  Connection refused: connect
         at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:194)
         at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
         at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
         at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
         at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#000C29352CBB000D0000001F000008C400042E8919E67A90#1177066286578#com.sap.portal.jsp#sap.com/irj#com.sap.portal.jsp#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_38##0#0#Warning#1#/System/Server#Java###null
    [EXCEPTION]
    #1#java.lang.NullPointerException
         at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
         at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
         at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
         at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    #1.5#000C29352CBB000D00000020000008C400042E8919E696EC#1177066286578#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_38##0#0#Error#1#/System/Server#Java###Exception ID:06:51_20/04/07_0132_8358550
    [EXCEPTION]
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
    Component : UserManagement.UserManagementMain
    Component class : com.xyz.usermanagement.core.UserManagementMain
    User : ncarste
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
         at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
         at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.prt.component.PortalComponentException: Original exception:
         at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:51)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
         ... 36 more
    Caused by: java.lang.NullPointerException
         at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
         at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
         ... 41 more
    #1.5#000C29352CBB00180000000F000008C400042E891F950BA4#1177066381890#com.sap.portal.jsp#sap.com/irj#com.sap.portal.jsp#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_34##0#0#Warning#1#/System/Server#Java###null
    [EXCEPTION]
    #1#java.lang.NullPointerException
         at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
         at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
         at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
         at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    #1.5#000C29352CBB001800000010000008C400042E891F951BEF#1177066381890#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#/System/Server#Java###Exception ID:06:53_20/04/07_0133_8358550
    [EXCEPTION]
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
    Component : UserManagement.UserManagementMain
    Component class : com.xyz.usermanagement.core.UserManagementMain
    User : ncarste
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
         at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
         at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.prt.component.PortalComponentException: Original exception:
         at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:51)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
         ... 36 more
    Caused by: java.lang.NullPointerException
         at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
         at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
         ... 41 more
    #1.5#000C29352CBB001100000198000008C400042E892504640C#1177066473062#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#sap.com/irj#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#Guest#192####a71f1491edbf11dba7d1000c29352cbb#Thread[ThreadPool.Worker8,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Cannot contact ICE server - com.sapportals.wcm.WcmException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri:  Connection refused: connect
         at com.sapportals.wcm.util.http.slim.SlimRequester.doPerform(SlimRequester.java:608)
         at com.sapportals.wcm.util.http.slim.SlimRequester.perform(SlimRequester.java:257)
         at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:164)
         at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
         at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
         at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
         at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#000C29352CBB001100000199000008C400042E892504642F#1177066473062#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#sap.com/irj#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#Guest#192####a71f1491edbf11dba7d1000c29352cbb#Thread[ThreadPool.Worker8,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Pull packages failed - java.io.IOException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri:  Connection refused: connect
         at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:194)
         at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
         at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
         at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
         at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#000C29352CBB00110000019A000008C400042E89289DD7BB#1177066533437#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#sap.com/irj#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#Guest#192####a71f1491edbf11dba7d1000c29352cbb#Thread[ThreadPool.Worker8,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Cannot contact ICE server - com.sapportals.wcm.WcmException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri:  Connection refused: connect
         at com.sapportals.wcm.util.http.slim.SlimRequester.doPerform(SlimRequester.java:608)
         at com.sapportals.wcm.util.http.slim.SlimRequester.perform(SlimRequester.java:257)
         at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:164)
         at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
         at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
         at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
         at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#000C29352CBB00110000019B000008C400042E89289DDB04#1177066533437#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#sap.com/irj#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#Guest#192####a71f1491edbf11dba7d1000c29352cbb#Thread[ThreadPool.Worker8,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Pull packages failed - java.io.IOException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri:  Connection refused: connect
         at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:194)
         at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
         at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
         at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
         at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#000C29352CBB003000000028000008C400042E892CEAA96A#1177066605437#com.sap.portal.jsp#sap.com/irj#com.sap.portal.jsp#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_6##0#0#Warning#1#/System/Server#Java###null
    [EXCEPTION]
    #1#java.lang.NullPointerException
         at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
         at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
         at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
         at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    #1.5#000C29352CBB003000000029000008C400042E892CEAC648#1177066605562#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_6##0#0#Error#1#/System/Server#Java###Exception ID:06:56_20/04/07_0134_8358550
    [EXCEPTION]
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
    Component : UserManagement.UserManagementMain
    Component class : com.xyz.usermanagement.core.UserManagementMain
    User : ncarste
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
         at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
         at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.prt.component.PortalComponentException: Original exception:
         at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:51)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
         ... 36 more
    Caused by: java.lang.NullPointerException
         at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
         at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
         ... 41 more
    #1.5#000C29352CBB001A00000028000008C400042E8934452A55#1177066728921#com.sap.portal.jsp#sap.com/irj#com.sap.portal.jsp#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_1##0#0#Warning#1#/System/Server#Java###null
    [EXCEPTION]
    #1#java.lang.NullPointerException
         at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:119)
         at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
         at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
         at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    #1.5#000C29352CBB001A00000029000008C400042E8934453D75#1177066728921#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_1##0#0#Error#1#/System/Server#Java###Exception ID:06:58_20/04/07_0135_8358550
    [EXCEPTION]
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
    Component : UserManagement.UserManagementMain
    Component class : com.xyz.usermanagement.core.UserManagementMain
    User : ncarste
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
         at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
         at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.prt.component.PortalComponentException: Original exception:
         at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:51)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
         ... 36 more
    Caused by: java.lang.NullPointerException
         at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:119)
         at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
         ... 41 more
    Thanks
    Rocky

    Hi Rocky,
    1)Goto configtool directory and run confgitool.sh
    <drive:\>\usr\sap\sid\JC<InstanceNumber>\J2EE\configtool\configtool.sh
    2)Under Clustre Data -> Global Server Configuration -> Services -> com.sap.security.cor.ume.services
    3)Now find the parameter - ume.persistence.data_source_configuration
    And change to default value (The default - dataSourceConfiguration_database_only.xml)
    4)Click on set and then apply the setting. Then restart the server.
    Hope it will be helpful.
    Thanks & regards
    Arun Singh

Maybe you are looking for

  • How manage timeout Session using java SDK?

    Hi everyone ! I'm working with BO 4.1 and the Java SDK. I'm refreshing and exporting webi reports in my code. But it happens, sometimes, the report takes longer to refresh (when calling "setPrompts") and the session is over (timeout like when you're

  • Lenovo g550 cursor moving Please help

    Im struggling on here really....lol.... Im having trouble with my G550.......when im typing ....if im not watching the screen when typing, I find the cursor has moved into the middle of another word after pressing the space bar......also, after press

  • Photoshop CS4 in Windows 7 bug runing batch actions

    I been using Photoshop CS4 in Vista with no problems, but now my problem is when I installed windows 7 and opened 60 photos and apply an action and try to do other things while PS is working in the batch, when I try to change to other window I get ba

  • 4.2 - Checkbox : When onClick registered for, MRU not firing (demo incl)

    *** Hopefully this isn't a rehash, I've searched around but haven't found information on it. *** I have a wizard created tabular report with a Checkbox (Y/NULL) column. The wizard also created the MRU and MRD. In the page header, I've added the follo

  • 5800 display remains blank despite using the lock/...

    With firmware v20.0.012 on a German, blue 5800 RM-356 I have this problem which was not in the v11 FW.  I did a successful, legal update with NSU v1.4.98 and restored my settings with PC Suite 7.1.18.  The theme is a standard Nokia one.  The fault is