J2EE startup - Service timeouts

Hello all,
Does anyone of you have experienced the problem during Java AS startup, many services do not start due to service timeouts. Ultimately the engine does not startup??
In the std_server.out log file, there are lot of services waiting to start and subsequently there are service timeouts, later thread dumps are being logged!
I am on Linux Platform..
Any solution, suggestions, idea will be appreciated..
Thanks
Vasu

hello,
In the meantime, i managed to find out that the timeouts could occur due to outOfMemory errors, long running gC and mainly due to DB connect timeout. In my case it so happened that there was a timeout while connecting to DB, there was no connection returned from DB...
Perhaps this might be helpful incase you come accross such problems.
Thanks and Regards
vasu

Similar Messages

  • Timeout error at J2EE Web Service client

    i have a .NET web service. a J2EE web service client deployed on Websphere application server 5.1 is invoking it. some services on .NET end take a long time to return a value. in such cases, the following error occurs on J2EE end. please suggest a solution.
    faultCode: Server.generalException
    faultString: java.net.SocketTimeoutException: Read timed out
    faultActor: null
    faultDetail:
    java.net.SocketTimeoutException: Read timed out
    at com.ibm.ws.webservices.engine.WebServicesFault.makeFault(WebServicesFault.java:150)
    at com.ibm.ws.webservices.engine.transport.http.HTTPSender.invoke(HTTPSender.java:200)
    at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:212)
    at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:255)
    at com.ibm.ws.webservices.engine.client.Connection.invokeEngine(Connection.java:685)
    at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:611)
    at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:441)
    at com.ibm.ws.webservices.engine.client.Stub$Invoke.invoke(Stub.java:662)

    Hi, am also getting time out .. excepiton in client
    i added the following code inside stub class constructer...
    System.out.println("GET TIME OUT ::::"+super.getTimeout());
    super.setTimeout(77777);
    System.out.println("GET TIME OUT AFTER SET::"+super.getTimeout());
    compilation success. However am getting runtime exception after the sop.
    GET TIME OUT ::::0
    javax.xml.rpc.ServiceException: WSWS5014E: Error instantiating generated Stub class.
    can you please tell me how u solved the issue.
    Thanks
    Bogi

  • J2ee Add-in - Error on J2ee startup

    Hi
    We are installing SAP WEBAS NW04 on AIX 5.2 server/Oracle 9.2.0.4 database.
    We finished ABAP installation and continue to install Java Add-in but we got some errors bellow when J2ee re-started:
    SAP J2EE Engine Version 6.30   PatchLevel 66061.37 is starting...
    Loading: LogManager ... 1776 ms.
    Loading: PoolManager ... 31 ms.
    Loading: ApplicationThreadManager ... 677 ms.
    Loading: ThreadManager ... 109 ms.
    Loading: IpVerificationManager ... 18 ms.
    Loading: ClassLoaderManager ... 25 ms.
    Loading: ClusterManager ... My Library Path is: /usr/java14_64/jre/bin:/usr/java
    14_64/jre/bin/classic:/usr/java14_64/jre/bin:/usr/sap/NWP/DVEBMGS50/j2ee/os_libs
    :/usr/sap/NWP/SYS/exe/run:/usr/sap/NWP/SYS/exe/runU:/usr/lib:/usr/sap/NWP/DVEBMG
    S50/j2ee/os_libs:/usr/sap/NWP/DVEBMGS50/j2ee/os_libs:/usr/lib:/lib:/usr/sap/NWP/
    SYS/exe/run:/usr/sap/NWP/SYS/exe/runU
    1558 ms.
    Loading: LockingManager ... My Library Path is: /usr/java14_64/jre/bin:/usr/java
    14_64/jre/bin/classic:/usr/java14_64/jre/bin:/usr/sap/NWP/DVEBMGS50/j2ee/os_libs
    :/usr/sap/NWP/SYS/exe/run:/usr/sap/NWP/SYS/exe/runU:/usr/lib:/usr/sap/NWP/DVEBMG
    S50/j2ee/os_libs:/usr/sap/NWP/DVEBMGS50/j2ee/os_libs:/usr/lib:/lib:/usr/sap/NWP/
    SYS/exe/run:/usr/sap/NWP/SYS/exe/runU
    169 ms.
    Loading: ConfigurationManager ... 4420 ms.
    1. log generation timestamp : 2004_09_27_at_20_29_13
    SAP J2EE Engine Version 6.30   PatchLevel 66061.37 is starting...
    Loading: LogManager ... 1776 ms.
    Loading: PoolManager ... 31 ms.
    Loading: ApplicationThreadManager ... 677 ms.
    Loading: ThreadManager ... 109 ms.
    Loading: IpVerificationManager ... 18 ms.
    Loading: ClassLoaderManager ... 25 ms.
    Loading: ClusterManager ... My Library Path is: /usr/java14_64/jre/bin:/usr/java
    14_64/jre/bin/classic:/usr/java14_64/jre/bin:/usr/sap/NWP/DVEBMGS50/j2ee/os_libs
    :/usr/sap/NWP/SYS/exe/run:/usr/sap/NWP/SYS/exe/runU:/usr/lib:/usr/sap/NWP/DVEBMG
    S50/j2ee/os_libs:/usr/sap/NWP/DVEBMGS50/j2ee/os_libs:/usr/lib:/lib:/usr/sap/NWP/
    SYS/exe/run:/usr/sap/NWP/SYS/exe/runU
    1558 ms.
    Loading: LockingManager ... My Library Path is: /usr/java14_64/jre/bin:/usr/java
    14_64/jre/bin/classic:/usr/java14_64/jre/bin:/usr/sap/NWP/DVEBMGS50/j2ee/os_libs
    :/usr/sap/NWP/SYS/exe/run:/usr/sap/NWP/SYS/exe/runU:/usr/lib:/usr/sap/NWP/DVEBMG
    S50/j2ee/os_libs:/usr/sap/NWP/DVEBMGS50/j2ee/os_libs:/usr/lib:/lib:/usr/sap/NWP/
    SYS/exe/run:/usr/sap/NWP/SYS/exe/runU
    169 ms.
    Loading: ConfigurationManager ... 4420 ms.
    Loading: LicensingManager ... 358 ms.
    Loading: ServiceManager ...
    Loading services:
      service memory started. (26 ms)
      service cross started. (68 ms)
      service runtimeinfo started. (43 ms)
      service jmx_notification started. (172 ms)
      service file started. (91 ms)
      service timeout started. (35 ms)
      service userstore started. (7 ms)
      service failover started. (599 ms)
      service tcsecwssec~service started. (633 ms)
      service deploy started. (583 ms)
      service p4 started. (896 ms)
      service classpath_resolver started. (3 ms)
      service log_configurator started. (4116 ms)
      service locking started. (18 ms)
      service http started. (583 ms)
      service naming started. (1643 ms)
      service appclient started. (111 ms)
      service jmsconnector started. (106 ms)
      service connector started. (141 ms)
      service ts started. (199 ms)
      service configuration started. (56 ms)
      service licensing started. (218 ms)
      service javamail started. (757 ms)
      service webservices started. (829 ms)
      service dbpool started. (1741 ms)
    Unable to instantiate class: com.sap.security.core.imp.RoleFactorycom.sap.secur
    ity.core.persistence.datasource.PersistenceException: com.sap.engine.lib.xml.par
    ser.ParserException: > expected to close DTD: (http://localhost/dataSourceConfig
    uration.dtd, row:1, col:2)
    Unable to initialize class: com.sap.security.core.imp.RoleFactorycom.sap.securi
    ty.api.UMRuntimeException:  Unable to instantiate class: com.sap.security.core.i
    mp.RoleFactorycom.sap.security.core.persistence.datasource.PersistenceException:
    com.sap.engine.lib.xml.parser.ParserException: > expected to close DTD: (http:/
    /localhost/dataSourceConfiguration.dtd, row:1, col:2)
      service com.sap.security.core.ume.service ================= ERROR ============
    =====
      CORE SERVICE ERROR! com.sap.security.core.ume.service
    com.sap.security.api.UMRuntimeException:  Unable to initialize class: com.sap.se
    curity.core.imp.RoleFactorycom.sap.security.api.UMRuntimeException:  Unable to i
    nstantiate class: com.sap.security.core.imp.RoleFactorycom.sap.security.core.per
    sistence.datasource.PersistenceException: com.sap.engine.lib.xml.parser.ParserEx
    ception: > expected to close DTD: (http://localhost/dataSourceConfiguration.dtd,
    row:1, col:2)
            at com.sap.security.api.UMFactory.initializeClass(UMFactory.java:991)
            at com.sap.security.api.UMFactory.getRoleFactory(UMFactory.java:513)
            at com.sap.security.core.role.imp.PermissionRoles.createDefaultRoles(Per
    missionRoles.java:334)
            at com.sap.security.core.role.imp.PermissionRoles.createDefaultRoles(Per
    missionRoles.java:317)
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMESer
    viceFrame.java:290)
            at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAd
    aptor.java:31)
            at com.sap.engine.core.service630.container.ServiceRunner.startApplicati
    onServiceFrame(ServiceRunner.java:144)
            at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRun
    ner.java:107)
            at com.sap.engine.core.thread.impl4.SingleThread.execute(SingleThread.ja
    va:86)
            at com.sap.engine.core.thread.impl4.SingleThread.run(SingleThread.java:1
    40)
    Nested Exception:
    com.sap.security.api.UMRuntimeException:  Unable to instantiate class: com.sap.s
    ecurity.core.imp.RoleFactorycom.sap.security.core.persistence.datasource.Persist
    enceException: com.sap.engine.lib.xml.parser.ParserException: > expected to clos
    e DTD: (http://localhost/dataSourceConfiguration.dtd, row:1, col:2)
            at com.sap.security.api.UMFactory.instantiateClass(UMFactory.java:1018)
            at com.sap.security.api.UMFactory.initializeClass(UMFactory.java:984)
            at com.sap.security.api.UMFactory.getRoleFactory(UMFactory.java:513)
            at com.sap.security.core.role.imp.PermissionRoles.createDefaultRoles(Per
    missionRoles.java:334)
            at com.sap.security.core.role.imp.PermissionRoles.createDefaultRoles(Per
    missionRoles.java:317)
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMESer
    viceFrame.java:290)
            at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAd
    aptor.java:31)
            at com.sap.engine.core.service630.container.ServiceRunner.startApplicati
    onServiceFrame(ServiceRunner.java:144)
            at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRun
    ner.java:107)
            at com.sap.engine.core.thread.impl4.SingleThread.execute(SingleThread.ja
    va:86)
            at com.sap.engine.core.thread.impl4.SingleThread.run(SingleThread.java:1
    40)
    Nested Exception:
    com.sap.security.core.persistence.datasource.PersistenceException: com.sap.engin
    e.lib.xml.parser.ParserException: > expected to close DTD: (http://localhost/dat
    aSourceConfiguration.dtd, row:1, col:2)
            at com.sap.security.core.persistence.datasource.imp.Configuration.refres
    h(Configuration.java:245)
            at com.sap.security.core.persistence.datasource.imp.Configuration.(RoleFactory.java:97)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
    orAccessorImpl.java:79)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
    onstructorAccessorImpl.java:43)
            at java.lang.reflect.Constructor.newInstance(Constructor.java(Compiled C
    ode))
            at java.lang.Class.newInstance3(Class.java:364)
            at java.lang.Class.newInstance(Class.java:302)
            at com.sap.security.api.UMFactory.instantiateClass(UMFactory.java:1012)
            at com.sap.security.api.UMFactory.initializeClass(UMFactory.java:984)
            at com.sap.security.api.UMFactory.getRoleFactory(UMFactory.java:513)
            at com.sap.security.core.role.imp.PermissionRoles.createDefaultRoles(Per
    missionRoles.java:334)
            at com.sap.security.core.role.imp.PermissionRoles.createDefaultRoles(Per
    missionRoles.java:317)
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMESer
    viceFrame.java:290)
            at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAd
    aptor.java:31)
            at com.sap.engine.core.service630.container.ServiceRunner.startApplicati
    onServiceFrame(ServiceRunner.java:144)
            at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRun
    ner.java:107)
            at com.sap.engine.core.thread.impl4.SingleThread.execute(SingleThread.ja
    va:86)
            at com.sap.engine.core.thread.impl4.SingleThread.run(SingleThread.java:1
    40)
            at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:144)
            at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl
    .java:145)
            at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
            at com.sap.security.core.persistence.datasource.imp.Configuration.refres
    h(Configuration.java:233)
            at com.sap.security.core.persistence.datasource.imp.Configuration.(RoleFactory.java:97)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
    orAccessorImpl.java:79)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
    onstructorAccessorImpl.java:43)
            at java.lang.reflect.Constructor.newInstance(Constructor.java(Compiled C
    ode))
            at java.lang.Class.newInstance3(Class.java:364)
            at java.lang.Class.newInstance(Class.java:302)
            at com.sap.security.api.UMFactory.instantiateClass(UMFactory.java:1012)
            at com.sap.security.api.UMFactory.initializeClass(UMFactory.java:984)
            at com.sap.security.api.UMFactory.getRoleFactory(UMFactory.java:513)
            at com.sap.security.core.role.imp.PermissionRoles.createDefaultRoles(Per
    missionRoles.java:334)
            at com.sap.security.core.role.imp.PermissionRoles.createDefaultRoles(Per
    missionRoles.java:317)
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMESer
    viceFrame.java:290)
            at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAd
    aptor.java:31)
            at com.sap.engine.core.service630.container.ServiceRunner.startApplicati
    onServiceFrame(ServiceRunner.java:144)
            at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRun
    ner.java:107)
            at com.sap.engine.core.thread.impl4.SingleThread.execute(SingleThread.ja
    va:86)
            at com.sap.engine.core.thread.impl4.SingleThread.run(SingleThread.java:1
    40)
    We already updated kernel to patch level 30 , re-created SAPJSF user on client 000 and 550 (our installation client informed
    during installation - for this re-creation, we used function module ****). we didn´t apply any support packages on this
    environment as for XI installation , we saw on documentation that we need a SAP WEBAS SP0 as a pre-requisite (Is this
    correct??).
    After those problems, we can´t continue as J2ee server and dispatcher must be running to finished all deploy files.
    Looking on /usr/sap/NWP/DV*/work directory , dev_jcontrol has this error:
    Tue Sep 28 16:10:45 2004
    JControlICheckProcessList: process server0 (pid:3301512) died (RUN-FLAG)
    JControlIResetProcess: not running -> increase error count (3)
    JStartupStartJLaunch: program = /usr/sap/NWP/DVEBMGS50/j2ee/os_libs/jlaunch
    -> arg[00] = /usr/sap/NWP/DVEBMGS50/j2ee/os_libs/jlaunch
    -> arg[01] = pf=/usr/sap/NWP/SYS/profile/NWP_DVEBMGS50_scxx024cto
    -> arg[02] = -file=/usr/sap/NWP/DVEBMGS50/j2ee/cluster/instance.properties
    -> arg[03] = -syncSem=262223
    -> arg[04] = -nodeName=ID508154250
    -> arg[05] = -nodeId=1
    -> arg[06] = -jvmOutFile=/usr/sap/NWP/DVEBMGS50/work/jvm_server0.out
    -> arg[07] = -jvmOutMode=append
    -> arg[08] = -stdOutFile=/usr/sap/NWP/DVEBMGS50/work/std_server0.out
    -> arg[09] = -stdOutMode=append
    -> arg[10] = -traceMode=append
    -> arg[11] = -locOutFile=/usr/sap/NWP/DVEBMGS50/work/dev_server0
    -> arg[12] = -mode=JCONTROL
    -> arg[13] = pf=/usr/sap/NWP/SYS/profile/NWP_DVEBMGS50_scxx024cto
    -> arg[14] = -DSAPSTART=1
    -> arg[15] = -DCONNECT_PORT=53806
    -> arg[16] = -DLISTEN_PORT=53807
    -> arg[17] = -DSAPSYSTEM=50
    -> arg[18] = -DSAPSYSTEMNAME=NWP
    -> arg[19] = -DSAPMYNAME=scxx024cto_NWP_50
    -> arg[20] = -DSAPPROFILE=/usr/sap/NWP/SYS/profile/NWP_DVEBMGS50_scxx024cto
    -> arg[21] = -DFRFC_FALLBACK=ON
    -> arg[22] = -DFRFC_FALLBACK_HOST=localhost
    -> lib path = LIBPATH=/usr/java14_64/jre/bin:/usr/java14_64/jre/bin/classic:/usr
    /java14_64/jre/bin:/usr/sap/NWP/DVEBMGS50/j2ee/os_libs:/usr/sap/NWP/SYS/exe/run:
    /usr/sap/NWP/SYS/exe/runU:/usr/lib:/usr/sap/NWP/DVEBMGS50/j2ee/os_libs:/usr/sap/
    NWP/DVEBMGS50/j2ee/os_libs:/usr/lib:/lib:/usr/sap/NWP/SYS/exe/run:/usr/sap/NWP/S
    YS/exe/runU
    -> exe path = PATH=/usr/java14_64/bin:/usr/sap/NWP/DVEBMGS50/j2ee/os_libs:/oracl
    e/NWP/920_64/bin:/usr/java14_64/bin:/home/nwpadm:/usr/sap/NWP/SYS/exe/runU:/usr/
    sap/NWP/SYS/exe/run:/usr/bin:/etc:/usr/sbin:/usr/ucb:/home/nwpadm/bin:/usr/bin/X
    11:/sbin:.
    JStartupICreateProcess: fork process (pid 3301514)
    JControlICheckProcessList: process server0 started (PID:3301514)
    Tue Sep 28 16:11:15 2004
    JControlICheckProcessList: process server0 (pid:3301514) died (RUN-FLAG)
    JControlIResetProcess: not running -> increase error count (4)
    Can anybody help us?????
    Thanks a lot!
    Daniela Godoi

    Hi Vamsi,
        check this thread:
    http://help.sap.com/saphelp_nw04/helpdata/en/20/361941edd5ef23e10000000a155106/frameset.htm
    Regards, Suresh KB

  • How to determine 640/J2EE Startup Framework Binary Patch Level?

    Hi All,
    We are running BI ABAP with Java Add-in on WAS 640/SUSE/Oracle.
    In the ABAP world, there are many options for determining the current kernel patch level.  Disp+work -v, SYSTEM->STATUS, etc..
    How do I determine the patch level of the J2EE startup framework (ie: jlaunch, jcontrol, etc..)?  If I run these commands with '-version', I get a patch level of 0. From System Information, the Cluster Kernel Version is 6.40 PatchLevel 105424.313. 
    What I am trying to determine is if I have the binaries that map to the latest applied SP (18).  Do I need to download J2EERTOS18.SAR and apply the bits or has that already been done?  Or is the current patch level for the bits fro the J2EERTOS14.SAR file?  Etc...
    Any tips/suggestions?
    Thanks much,
    Greg

    Hi
    You can check the patch number like this;
    D:\usr\sap\FT0\SYS\exe\uc\NTI386>jlaunch -version
    Failed to reserve 1610612736 (0x60000000) bytes before loading DLLs (error 8).
    jlaunch information
    kernel release                700
    kernel make variant           700_REL
    compiled on                   NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10
    compilation mode              UNICODE
    compile time                  Jan 23 2008 20:42:28
    update level                  0
    patch number                  128                         <<< Here is the patch number>>
    source id                     0.144
    While regarding which file(s) to apply, please notice that the files you are not talking like
    J2EERTOS16_1, is part of the J2EE support package stack, which can be applied with JSPM.
    Regarding the kernel, you can alway refer to note 19466, and downlaod the lastest kernel from:
    http://service.sap.com/swdc
       Support Packages and Patches ->
       Entry by Application Group "
       SAP NetWeaver and complementary products"
       SAP NETWEAVER" SAP NETWEAVER 7.0"
       Entry by Component"
       Application Server Java
       ===> SAP KERNEL 7.00 64-BIT UNICODE
    Regards,
    Thunder

  • J2ee startup problems

    Hi all!
    we tried to configure a connection between EP 6.0 SP13 and our CRM - System after the configuration in the portal we restartet the engine and following errors occure:
    jcontrol.exe - some processes running
    Developer Trace:
    Thr 4352] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 5552] Mon Sep 05 16:27:03 2005
    [Thr 5552] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 5552] JLaunchISetClusterId: set cluster id 1165550
    [Thr 5552] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 5552] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 4288] Mon Sep 05 16:27:17 2005
    [Thr 4288] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 2208] JLaunchIExitJava: exit hook is called (rc=-11113)
    [Thr 2208] JLaunchCloseProgram: good bye (exitcode=-11113)
    dev_jcontrol:
    trc file: "F:\usr\sap\UEP\JC00\work\dev_jcontrol", trc level: 1, release: "640"
    node name   : jcontrol
    pid         : 4696
    system name : UEP
    system nr.  : 00
    started at  : Mon Sep 05 16:25:47 2005
    arguments   :
        arg[00] : F:\usr\sap\UEP\JC00\j2ee\os_libs\jcontrol.exe
        arg[01] : pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    [Thr 4104] Mon Sep 05 16:25:47 2005
    [Thr 4104] INFO: Unknown property [box.number=UEPJC00uep]
    [Thr 4104] INFO: Unknown property [system.id=0]
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties;F:\usr\sap\UEP\JC00\SDM\program\config\sdm_jstartup.properties]
    -> ms host    : uep
    -> ms port    : 3601
    -> OS libs    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> files [01] : F:\usr\sap\UEP\JC00\SDM\program\config\sdm_jstartup.properties
    Instance properties
    -> ms host    : uep
    -> ms port    : 3601
    -> os libs    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID1165500  : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID1165550  : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID1165500            : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> [01] ID1165550            : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> [02] sdm                  : F:\usr\sap\UEP\JC00\SDM\program\config\sdm_jstartup.properties
    [Thr 4104] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
    [Thr 4104] [Node: bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_09
    JStartupIReadSection: read node properties [bootstrap]
    -> node name       : bootstrap
    -> node type       : bootstrap
    -> node execute   : yes
    -> java path       : C:\j2sdk1.4.2_09
    -> java parameters : -Djco.jarm=1 -Djco.jarm=1
    -> java vm version : 1.4.2_09-b05
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 128M
    -> root path       : F:\usr\sap\UEP\JC00\j2ee\cluster
    -> class path      : .\bootstrap\launcher.jar
    -> OS libs path    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.offline.OfflineToolStart
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : F:\usr\sap\UEP\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0011655
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_bootstrap
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=bootstrap
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_bootstrap.out
    -> arg[08] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_bootstrap.out
    -> arg[09] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_bootstrap
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] Mon Sep 05 16:25:50 2005
    [Thr 4104] JControlExecuteBootstrap: read instance values after global bootstrap
    [Thr 4104] INFO: Unknown property [box.number=UEPJC00uep]
    [Thr 4104] INFO: Unknown property [system.id=0]
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties;F:\usr\sap\UEP\JC00\SDM\program\config\sdm_jstartup.properties]
    -> ms host    : uep
    -> ms port    : 3601
    -> OS libs    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    [Thr 4104] JControlExecuteBootstrap: enumerate the nodes after global bootstrap
    Used property files
    -> files [00] : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> files [01] : F:\usr\sap\UEP\JC00\SDM\program\config\sdm_jstartup.properties
    Instance properties
    -> ms host    : uep
    -> ms port    : 3601
    -> os libs    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID1165500  : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID1165550  : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID1165500            : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> [01] ID1165550            : F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> [02] sdm                  : F:\usr\sap\UEP\JC00\SDM\program\config\sdm_jstartup.properties
    [Thr 4104] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID1165500]
    [Thr 4104] INFO: Unknown property [JLaunchParameters=]
    [Thr 4104] [Node: dispatcher bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_09
    JStartupIReadSection: read node properties [bootstrap_ID1165500]
    -> node name       : dispatcher bootstrap
    -> node type       : bootstrap
    -> node execute   : yes
    -> java path       : C:\j2sdk1.4.2_09
    -> java parameters : -Djco.jarm=1 -Djco.jarm=1
    -> java vm version : 1.4.2_09-b05
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 170M
    -> root path       : F:\usr\sap\UEP\JC00\j2ee\cluster
    -> class path      : .\bootstrap\launcher.jar
    -> OS libs path    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.offline.OfflineToolStart
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : F:\usr\sap\UEP\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID001165500
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_bootstrap
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=bootstrap_ID1165500
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_bootstrap_ID1165500.out
    -> arg[08] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_bootstrap_ID1165500.out
    -> arg[09] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_bootstrap_ID1165500
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] Mon Sep 05 16:25:53 2005
    [Thr 4104] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID1165550]
    [Thr 4104] INFO: Unknown property [JLaunchParameters=]
    [Thr 4104] [Node: server0 bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_09
    JStartupIReadSection: read node properties [bootstrap_ID1165550]
    -> node name       : server0 bootstrap
    -> node type       : bootstrap
    -> node execute   : yes
    -> java path       : C:\j2sdk1.4.2_09
    -> java parameters : -Djco.jarm=1 -Djco.jarm=1
    -> java vm version : 1.4.2_09-b05
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 1024M
    -> root path       : F:\usr\sap\UEP\JC00\j2ee\cluster
    -> class path      : .\bootstrap\launcher.jar
    -> OS libs path    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.offline.OfflineToolStart
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : F:\usr\sap\UEP\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID001165550
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_bootstrap
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=bootstrap_ID1165550
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_bootstrap_ID1165550.out
    -> arg[08] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_bootstrap_ID1165550.out
    -> arg[09] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_bootstrap_ID1165550
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] Mon Sep 05 16:25:56 2005
    [Thr 4104] JControlIBuildProcessList: Maximum error count is set to 4
    [Thr 4104] INFO: Unknown property [JLaunchParameters=]
    [Thr 3900] JControlRequestFunc: Thread 3900 started as listener thread for np messages.
    [Thr 4104] [Node: dispatcher] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_09
    JStartupIReadSection: read node properties [ID1165500]
    -> node name       : dispatcher
    -> node type       : dispatcher
    -> node execute   : yes
    -> java path       : C:\j2sdk1.4.2_09
    -> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Djco.jarm=1 -XX:NewSize=28m -XX:MaxNewSize=28m -XX:+DisableExplicitGC -Drdbms.driverLocation=F:/oracle/uep/920/jdbc/lib/classes12.jar -Dsys.global.dir=F:/usr/sap/UEP/SYS/global/
    -> java vm version : 1.4.2_09-b05
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 170M
    -> root path       : F:\usr\sap\UEP\JC00\j2ee\cluster\dispatcher
    -> class path      : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
    -> OS libs path    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.boot.Start
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : F:\usr\sap\UEP\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      :
    -> debuggable      : no
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    [Thr 4104] INFO: Unknown property [JLaunchParameters=]
    [Thr 4104] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx512M [jstartxx.c   2300]
    [Thr 4104] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_09
    JStartupIReadSection: read node properties [ID1165550]
    -> node name       : server0
    -> node type       : server
    -> node execute   : yes
    -> java path       : C:\j2sdk1.4.2_09
    -> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:UseParNewGC -XX:MaxNewSize=85M -XX:NewSize=85M -XX:DisableExplicitGC -XX:MaxPermSize=192M -XX:PermSize=192M -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Drdbms.driverLocation=F:/oracle/uep/920/jdbc/lib/classes12.jar -Dsys.global.dir=F:/usr/sap/UEP/SYS/global/
    -> java vm version : 1.4.2_09-b05
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 512M
    -> init heap size  : 512M
    -> root path       : F:\usr\sap\UEP\JC00\j2ee\cluster\server0
    -> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> main class      : com.sap.engine.boot.Start
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : F:\usr\sap\UEP\JC00\j2ee\os_libs\jstartup.jar
    -> parameters      :
    -> debuggable      : no
    -> debug mode      : no
    -> debug port      : 50021
    -> shutdown timeout: 120000
    [Thr 4104] [Node: SDM] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_09
    JStartupIReadSection: read node properties [sdm]
    -> node name       : SDM
    -> node type       : sdm
    -> node execute   : yes
    -> java path       : C:\j2sdk1.4.2_09
    -> java parameters :
    -> java vm version : 1.4.2_09-b05
    -> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type    : server
    -> java vm cpu     : x86
    -> heap size       : 128M
    -> root path       : F:\usr\sap\UEP\JC00\SDM\program
    -> class path      : F:\usr\sap\UEP\JC00\SDM\program\bin\SDM.jar
    -> OS libs path    : F:\usr\sap\UEP\JC00\j2ee\os_libs
    -> main class      : SDMInternal
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : F:\usr\sap\UEP\JC00\j2ee\os_libs\jstartup.jar
    -> shutdown class  : com.sap.sdm.jstartup.shutdown.InternalShutDown
    -> parameters      : server sdmhome=F:\usr\sap/UEP/JC00/SDM/program
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    [Thr 4104] JControlMSConnect: attached to message server (uep/3601)
    [Thr 2896] JControlMSMessageFunc: Thread 2896 started as listener thread for ms messages.
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_dispatcher
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID1165500
    -> arg[05] = -nodeId=0
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_dispatcher.out
    -> arg[08] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_dispatcher.out
    -> arg[09] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_dispatcher
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] JControlICheckProcessList: process dispatcher started (PID:5596)
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_server
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID1165550
    -> arg[05] = -nodeId=1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_server0.out
    -> arg[08] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_server0.out
    -> arg[09] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_server0
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] JControlICheckProcessList: process server0 started (PID:4700)
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_sdm
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\SDM\program\config\sdm_jstartup.properties
    -> arg[04] = -nodeName=sdm
    -> arg[05] = -nodeId=2
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_sdm.out
    -> arg[08] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_sdm.out
    -> arg[09] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_sdm
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] JControlICheckProcessList: process SDM started (PID:5272)
    [Thr 4104] Mon Sep 05 16:26:21 2005
    [Thr 4104] JControlICheckProcessList: process server0 (pid:4700) died (RUN-FLAG)
    [Thr 4104] JControlIResetProcess: reset process server0
    [Thr 4104] JControlIResetProcess: [server0] not running -> increase error count (1)
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_server
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID1165550
    -> arg[05] = -nodeId=1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_server0.out
    -> arg[08] = -jvmOutMode=append
    -> arg[09] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_server0.out
    -> arg[10] = -stdOutMode=append
    -> arg[11] = -traceMode=append
    -> arg[12] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_server0
    -> arg[13] = -mode=JCONTROL
    -> arg[14] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] JControlICheckProcessList: process server0 started (PID:3440)
    [Thr 4104] Mon Sep 05 16:26:41 2005
    [Thr 4104] JControlICheckProcessList: process server0 (pid:3440) died (RUN-FLAG)
    [Thr 4104] JControlIResetProcess: reset process server0
    [Thr 4104] JControlIResetProcess: [server0] not running -> increase error count (2)
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_server
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID1165550
    -> arg[05] = -nodeId=1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_server0.out
    -> arg[08] = -jvmOutMode=append
    -> arg[09] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_server0.out
    -> arg[10] = -stdOutMode=append
    -> arg[11] = -traceMode=append
    -> arg[12] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_server0
    -> arg[13] = -mode=JCONTROL
    -> arg[14] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] JControlICheckProcessList: process server0 started (PID:3280)
    [Thr 4104] Mon Sep 05 16:27:01 2005
    [Thr 4104] JControlICheckProcessList: process server0 (pid:3280) died (RUN-FLAG)
    [Thr 4104] JControlIResetProcess: reset process server0
    [Thr 4104] JControlIResetProcess: [server0] not running -> increase error count (3)
    JStartupStartJLaunch: program = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = F:\usr\sap\UEP\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> arg[02] = -DSAPINFO=UEP_00_server
    -> arg[03] = -file=F:\usr\sap\UEP\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=ID1165550
    -> arg[05] = -nodeId=1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_4696
    -> arg[07] = -jvmOutFile=F:\usr\sap\UEP\JC00\work\jvm_server0.out
    -> arg[08] = -jvmOutMode=append
    -> arg[09] = -stdOutFile=F:\usr\sap\UEP\JC00\work\std_server0.out
    -> arg[10] = -stdOutMode=append
    -> arg[11] = -traceMode=append
    -> arg[12] = -locOutFile=F:\usr\sap\UEP\JC00\work\dev_server0
    -> arg[13] = -mode=JCONTROL
    -> arg[14] = pf=F:\usr\sap\UEP\SYS\profile\UEP_JC00_uep
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\JC00\j2ee\os_libs;F:\usr\sap\Python\.;F:\oracle\uep\920\jre\1.4.2\bin\client;F:\oracle\uep\920\jre\1.4.2\bin;F:\oracle\uep\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\j2sdk1.4.2_09\bin;F:\usr\sap\UEP\SCS01\exe;F:\usr\sap\UEP\JC00\exe;F:\usr\sap\UEP\SYS\exe\run
    [Thr 4104] JControlICheckProcessList: process server0 started (PID:3436)
    [Thr 4104] Mon Sep 05 16:27:21 2005
    [Thr 4104] JControlICheckProcessList: process server0 (pid:3436) died (RUN-FLAG)
    [Thr 4104] JControlIResetProcess: reset process server0
    [Thr 4104] JControlIResetProcess: [server0] not running -> increase error count (4)
    std_server0.out
    stdout/stderr redirect
    node name   : server0
    pid         : 4696
    system name : UEP
    system nr.  : 00
    started at  : Mon Sep 05 16:25:56 2005
    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
    SAP J2EE Engine Version 6.40   PatchLevel 95420.313 is starting...
    Loading: LogManager ... 516 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 78 ms.
    Loading: ThreadManager ... 31 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 15 ms.
    Loading: ClusterManager ... 657 ms.
    Loading: LockingManager ... 109 ms.
    Loading: ConfigurationManager ... 2000 ms.
    Loading: LicensingManager ... 31 ms.
    Loading: ServiceManager ...
    0.000: [GC 0.000: [ParNew: 43519K->3351K(65280K), 0.0312769 secs] 43519K->3351K(502528K), 0.0313265 secs]
    Loading services.:
      Service memory started. (16 ms).
      Service cross started. (15 ms).
      Service jmx_notification started. (234 ms).
      Service trex.service started. (156 ms).
      Service runtimeinfo started. (15 ms).
      Service file started. (31 ms).
      Service tcsecwssec~service started. (625 ms).
      Service timeout started. (672 ms).
      Service userstore started. (0 ms).
      Service p4 started. (937 ms).
      Service classpath_resolver started. (0 ms).
    5.469: [GC 5.469: [ParNew: 46871K->7055K(65280K), 0.0510631 secs] 46871K->7055K(502528K), 0.0511160 secs]
      Service log_configurator started. (4078 ms).
      Service locking started. (16 ms).
      Service http started. (375 ms).
      Service naming started. (437 ms).
      Service failover started. (266 ms).
      Service appclient started. (281 ms).
      Service jmsconnector started. (297 ms).
      Service javamail started. (438 ms).
      Service ts started. (359 ms).
      Service licensing started. (16 ms).
      Service connector started. (375 ms).
    9.002: [GC 9.002: [ParNew: 50575K->8716K(65280K), 0.1193652 secs] 50575K->8716K(502528K), 0.1194184 secs]
      Service webservices started. (1469 ms).
      Service deploy started. (7484 ms).
      Service configuration started. (63 ms).
      Service apptracing started. (94 ms).
    12.418: [GC 12.418: [ParNew: 52236K->11128K(65280K), 0.0434016 secs] 52236K->11128K(502528K), 0.0434532 secs]
      Service dbpool started. (1484 ms).
    Sep 5, 2005 4:26:20 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_25] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "'mshost' missing". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      TimeZoneMapping=
      snc_qop=
      client=300
      abap_debug=
      snc_myname=
      gwserv=
      snc_partnername=
      ashost=194.127.167.74
      group=
      r3name=UME
      snc_mode=0
      gwhost=
      sysnr=00
      msserv=
      poolmaxsize=10
      snc_lib=
      passwd=********
      poolmaxwait=
      trace=
      receiverid_guest=master
      mshost=
      user=SAPJSF_UEP
      lang=EN
      receiverid=master
    Sep 5, 2005 4:26:20 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_25] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: 'mshost' missing
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:573)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:207)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:140)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: 'mshost' missing
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:1719)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:1951)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:283)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:570)
         ... 6 more
    com.sap.engine.frame.ServiceException: 'mshost' missing
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:573)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:207)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:140)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: 'mshost' missing
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:1719)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:1951)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:283)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:570)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Sep 5, 2005 4:26:20 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_25] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 4696
    system name : UEP
    system nr.  : 00
    started at  : Mon Sep 05 16:26:21 2005
    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
    SAP J2EE Engine Version 6.40   PatchLevel 95420.313 is starting...
    Loading: LogManager ... 516 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 78 ms.
    Loading: ThreadManager ... 16 ms.
    Loading: IpVerificationManager ... 31 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 234 ms.
    Loading: LockingManager ... 63 ms.
    Loading: ConfigurationManager ... 1375 ms.
    Loading: LicensingManager ... 32 ms.
    Loading: ServiceManager ...
    0.000: [GC 0.000: [ParNew: 43520K->2968K(65280K), 0.0208138 secs] 43520K->2968K(502528K), 0.0208688 secs]
    Loading services.:
      Service memory started. (94 ms).
      Service cross started. (172 ms).
      Service runtimeinfo started. (94 ms).
      Service file started. (172 ms).
      Service trex.service started. (172 ms).
      Service timeout started. (218 ms).
      Service userstore started. (125 ms).
      Service jmx_notification started. (156 ms).
      Service tcsecwssec~service started. (407 ms).
      Service p4 started. (172 ms).
      Service classpath_resolver started. (0 ms).
    3.397: [GC 3.397: [ParNew: 46488K->6596K(65280K), 0.0343611 secs] 46488K->6596K(502528K), 0.0344101 secs]
      Service log_configurator started. (3390 ms).
      Service locking started. (0 ms).
      Service naming started. (312 ms).
      Service failover started. (93 ms).
      Service appclient started. (172 ms).
      Service jmsconnector started. (203 ms).
      Service http started. (656 ms).
      Service javamail started. (344 ms).
      Service ts started. (281 ms).
      Service licensing started. (0 ms).
      Service connector started. (312 ms).
    6.312: [GC 6.312: [ParNew: 50113K->8624K(65280K), 0.0386024 secs] 50113K->8624K(502528K), 0.0386580 secs]
      Service webservices started. (813 ms).
      Service deploy started. (6532 ms).
      Service configuration started. (47 ms).
      Service apptracing started. (79 ms).
    9.241: [GC 9.241: [ParNew: 52143K->11000K(65280K), 0.0363859 secs] 52143K->11000K(502528K), 0.0364380 secs]
      Service dbpool started. (1359 ms).
    Sep 5, 2005 4:26:37 PM          com.sap.security.core.persistence [Session Reader for cluster node 1165500] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "'mshost' missing". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      TimeZoneMapping=
      snc_qop=
      client=300
      abap_debug=
      snc_myname=
      gwserv=
      snc_partnername=
      ashost=194.127.167.74
      group=
      r3name=UME
      snc_mode=0
      gwhost=
      sysnr=00
      msserv=
      poolmaxsize=10
      snc_lib=
      passwd=********
      poolmaxwait=
      trace=
      receiverid_guest=master
      mshost=
      user=SAPJSF_UEP
      lang=EN
      receiverid=master
    Sep 5, 2005 4:26:37 PM          com.sap.security.core.persistence [Session Reader for cluster node 1165500] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: 'mshost' missing
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:573)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:207)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:140)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: 'mshost' missing
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:1719)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:1951)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:283)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:570)
         ... 6 more
    com.sap.engine.frame.ServiceException: 'mshost' missing
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:573)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:207)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:140)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: 'mshost' missing
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:1719)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:1951)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:283)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:570)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Sep 5, 2005 4:26:37 PM              com.sap.engine.core.Framework [Session Reader for cluster node 1165500] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 4696
    system name : UEP
    system nr.  : 00
    started at  : Mon Sep 05 16:26:41 2005
    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
    SAP J2EE Engine Version 6.40   PatchLevel 95420.313 is starting...
    Loading: LogManager ... 531 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 94 ms.
    Loading: ThreadManager ... 16 ms.
    Loading: IpVerificationManager ... 15 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 235 ms.
    Loading: LockingManager ... 125 ms.
    Loading: ConfigurationManager ... 1171 ms.
    Loading: LicensingManager ... 16 ms.
    Loading: ServiceManager ...
    0.000: [GC 0.000: [ParNew: 43505K->3079K(65280K), 0.0218877 secs] 43505K->3079K(502528K), 0.0219387 secs]
    Loading services.:
      Service memory started. (31 ms).
      Service jmx_notification started. (47 ms).
      Service cross started. (47 ms).
      Service runtimeinfo started. (31 ms).
      Service trex.service started. (125 ms).
      Service userstore started. (15 ms).
      Service file started. (109 ms).
      Service timeout started. (141 ms).
      Service p4 started. (250 ms).
      Service classpath_resolver started. (31 ms).
      Service tcsecwssec~service started. (343 ms).
    3.557: [GC 3.557: [ParNew: 46599K->6971K(65280K), 0.0362422 secs] 46599K->6971K(502528K), 0.0362937 secs]
      Service log_configurator started. (3297 ms).
      Service locking started. (0 ms).
      Service http started. (344 ms).
      Service naming started. (391 ms).
      Service appclient started. (218 ms).
      Service jmsconnector started. (250 ms).
      Service javamail started. (297 ms).
      Service ts started. (219 ms).
      Service failover started. (297 ms).
      Service licensing started. (15 ms).
      Service connector started. (422 ms).
      Service webservices started. (640 ms).
    6.372: [GC 6.372: [ParNew: 50462K->8734K(65280K), 0.0393979 secs] 50462K->8734K(502528K), 0.0394531 secs]
      Service deploy started. (7015 ms).
      Service configuration started. (32 ms).
      Service apptracing started. (125 ms).
    9.659: [GC 9.659: [ParNew: 52254K->11326K(65280K), 0.0405210 secs] 52254K->11326K(502528K), 0.0405719 secs]
      Service dbpool started. (1469 ms).
    Sep 5, 2005 4:26:58 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_11] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "'mshost' missing". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      TimeZoneMapping=
      snc_qop=
      client=300
      abap_debug=
      snc_myname=
      gwserv=
      snc_partnername=
      ashost=194.127.167.74
      group=
      r3name=UME
      snc_mode=0
      gwhost=
      sysnr=00
      msserv=
      poolmaxsize=10
      snc_lib=
      passwd=********
      poolmaxwait=
      trace=
      receiverid_guest=master
      mshost=
      user=SAPJSF_UEP
      lang=EN
      receiverid=master
    Sep 5, 2005 4:26:58 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_11] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: 'mshost' missing
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:573)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:207)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleT

    Here's a list of all the parameters but I think you need this one ume.r3.connection.master.msserv=
    ume.r3.connection.master.abap_debug=
    ume.r3.connection.master.ashost=
    ume.r3.connection.master.client=
    ume.r3.connection.master.group=
    ume.r3.connection.master.gwhost=
    ume.r3.connection.master.gwserv=
    ume.r3.connection.master.lang=
    ume.r3.connection.master.msghost=
    ume.r3.connection.master.msserv=
    ume.r3.connection.master.poolmaxsize=10
    ume.r3.connection.master.poolmaxwait=
    ume.r3.connection.master.r3name=
    ume.r3.connection.master.receiverid=master
    ume.r3.connection.master.receiverid_guest=master
    ume.r3.connection.master.snc_lib=
    ume.r3.connection.master.snc_mode=
    ume.r3.connection.master.snc_myname=
    ume.r3.connection.master.snc_partnername=
    ume.r3.connection.master.snc_qop=
    ume.r3.connection.master.sysnr=
    ume.r3.connection.master.trace=
    ume.r3.connection.master.user=
    ume.r3.connection.master.TimeZoneMapping=
    ume.r3.connection.master.abap_debug=
    ume.r3.connection.master.ashost=
    ume.r3.connection.master.client=
    ume.r3.connection.master.group=
    ume.r3.connection.master.gwhost=
    ume.r3.connection.master.gwserv=
    ume.r3.connection.master.lang=
    ume.r3.connection.master.msghost=
    ume.r3.connection.master.msserv=
    ume.r3.connection.master.poolmaxsize=10
    ume.r3.connection.master.poolmaxwait=
    ume.r3.connection.master.r3name=
    ume.r3.connection.master.receiverid=master
    ume.r3.connection.master.receiverid_guest=master
    ume.r3.connection.master.snc_lib=
    ume.r3.connection.master.snc_mode=
    ume.r3.connection.master.snc_myname=
    ume.r3.connection.master.snc_partnername=
    ume.r3.connection.master.snc_qop=
    ume.r3.connection.master.sysnr=
    ume.r3.connection.master.trace=
    ume.r3.connection.master.user=

  • J2ee startup problem

    hi,
    After installation of NW2004's I restarted the system for post installation then I found server0 is not working...see the logs
    dev_server0:
    Thr 4256] Thu May  8 17:53:04 2008
    [Thr 4256] ***LOG Q0I=> NiPConnect: connect (79: Connection refused) [nixxi.cpp 2460]
    [Thr 4256] *** ERROR => NiPConnect: SiConnect failed for hdl 6 / sock 9
        (SI_ECONN_REFUSE/79; I4; ST; 127.0.0.1:3300) [nixxi.cpp    2460]
    [Thr 4256] *** ERROR => GwIConnect: GwConnect to localhost / sapgw00 failed (rc=NIECONN_REFUSED) [gwxx_mt.c    296]
    [Thr 4256] ***LOG S0T=> GwIConnect, GwConnect (-0010) [gwxx_mt.c    297]
    [Thr 4256] ***LOG S0R=> GwIConnect, GwConnect () [gwxx_mt.c    299]
    [Thr 4256] ***LOG S0S=> GwIConnect, GwConnect (sapgw00) [gwxx_mt.c    301]
    [Thr 4256] ***LOG S90=> SAP_STINIT3, GwIConnect ( 236) [r3cpic_mt.c  2006]
    [Thr 4256]
    [Thr 4256] *  LOCATION    CPIC (TCP/IP) on local host with Unicode
    [Thr 4256] *  ERROR       partner '127.0.0.1:sapgw00' not reached
    [Thr 4256] *
    TIME        Thu May  8 17:53:04 2008
    [Thr 4256] *  RELEASE     700
    [Thr 4256] *  COMPONENT   NI (network interface)
    [Thr 4256] *  VERSION     38
    [Thr 4256] *  RC          -10
    [Thr 4256] *  MODULE      nixxi.cpp
    [Thr 4256] *  LINE        2460
    [Thr 4256] *  DETAIL      NiPConnect
    [Thr 4256] *  SYSTEM CALL connect
    [Thr 4256] *  ERRNO       79
    [Thr 4256] *  ERRNO TEXT  Connection refused
    [Thr 4256] *  COUNTER     84
    [Thr 4256] *
    [Thr 4256] *****************************************************************************
    dev_jcontrol:
    [Thr  1] Sat May 10 13:40:35 2008
    [Thr  1] ***LOG Q0I=> NiPConnect: connect (79: Connection refused) [nixxi.cpp 2460]
    [Thr  1] *** ERROR => NiPConnect: SiConnect failed for hdl 2 / sock 11
        (SI_ECONN_REFUSE/79; I4; ST; :3901) [nixxi.cpp    2460]
    [Thr  1] *** ERROR => MsIAttachEx: NiBufConnect to GGBDV/3901 failed (rc=NIECONN_REFUSED) [msxxi_mt.c   652]
    [Thr  1] *** ERROR => Can't attach to message server (hostname/3901) [rc = -100]-> terminate [jcntrms_mt.c 374]
    [Thr  1] JControlCloseProgram: started (exitcode = -100)
    [Thr  1] *** ERROR => MsIModState: not_attached [msxxi_mt.c   3838]
    [Thr  1] *** ERROR => Can't modify message server state (state = 7, rc = -3) [jcntrms_mt.c 841]
    [Thr  1] JControlCloseProgram: good bye... (exitcode = -100)
    dev_ms:
    trc file: "dev_ms", trc level: 1, release: "700"
    [Thr  1] Sat May 10 13:16:54 2008
    [Thr  1] MsSOsPrivInit: Run priority adjusted to 12
    [Thr  1] MsSSetTrcLog: trc logging active, max size = 20971520 bytes
    systemid   324 (IBM iSeries with OS400)
    relno      7000
    patchlevel 0
    patchno    116
    intno      20050900
    make:      multithreaded, Unicode, 64 bit, optimized
    pid        475
    [Thr  1] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 475) [msxxserv_mt. 1824]
    [Thr  1] SigISetDefaultAction : default handling for signal 20
    [Thr  1] load acl file = /usr/sap/GBI/SYS/global/ms_acl_info
    [Thr  1] MsGetOwnIpAddr: my host addresses are :
    [Thr  1]   1 :  (HOSTNAME)
    [Thr  1]   2 : [127.0.0.1] LOOPBACK (LOCALHOST)
    [Thr  1] MsHttpInit: full qualified hostname
    [Thr  1] HTTP logging is switch off
    [Thr  1] set HTTP state to LISTEN
    [Thr  1] MsHttpOwnDomain: own domain[1]
    [Thr  1] ms/icf_info_server : deleted
    [Thr  1] *** I listen to port sapmsSID(3600) ***
    [Thr  1] *** I listen to internal port 3900 (3900) ***
    [Thr  1] *** HTTP port 8100 state LISTEN ***
    [Thr  1] CUSTOMER KEY: >Y0799187842<
    [Thr  1] Sat May 10 13:18:17 2008
    [Thr  1] MsHttpReadUrl2: H-1 url = /sap/public/icf_info/logon_groups (403 Forbidden)
    [Thr  1] Sat May 10 13:18:23 2008
    [Thr  1] MsHttpReadUrl2: H-1 url = /sap/public/icf_info/urlprefix (403 Forbidden)
    [Thr  1] Sat May 10 13:47:18 2008
    [Thr  1] MsHttpReadUrl2: H-1 url = /sap/public/icf_info/logon_groups (403 Forbidden)
    give me your suggestion

    HI,
    STD_SERVEO:
    stdout/stderr redirect
    node name   : server0
    pid         : 7753
    system name : SID
    system nr.  : 00
    started at  : Thu May  8 08:01:48 2008
    [Thr  1] Thu May  8 08:01:51 2008
    [Thr  1] MtxInit: -2 0 0
    GC: initial heap(KB) 1048576; maximum heap(KB) 4194304; virtual machine identifier CC9D260C1B003900;  heap identifier CC9D260C1B003900.
    GC 1: starting collection, reason  external thread attached.
    GC 1: collection starting 05/08/08 08:01:55
    GC 1: live objects 3550; collected objects 1654; collected(KB) 145.
    GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
    GC 1: current heap(KB) 5556; current threshold(KB) 1048576.
    GC 1: collect (milliseconds) 57.
    GC 1: current cycle allocation(KB) 864; previous cycle allocation(KB) 4185.
    GC 1: total weak references 0; cleared weak references 0.
    GC 1: total final references 6; cleared final references 0.
    GC 1: total phantom references 0; cleared phantom references 0.
    GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 1: collection ending 05/08/08 08:01:56
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Loading: LogManager ... 2339 ms.
    Loading: PoolManager ... 15 ms.
    Loading: ApplicationThreadManager ... 338 ms.
    Loading: ThreadManager ... 87 ms.
    Loading: IpVerificationManager ... 53 ms.
    Loading: ClassLoaderManager ... 116 ms.
    Loading: ClusterManager ... 1461 ms.
    Loading: LockingManager ... 744 ms.
    Loading: ConfigurationManager ... 11296 ms.
    Loading: LicensingManager ... 82 ms.
    Loading: CacheManager ... 805 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service cafeuodi~mnuacc started. (87 ms).
      Service DQE started. (440 ms).
      Service runtimeinfo started. (137 ms).
      Service cross started. (351 ms).
      Service timeout started. (333 ms).
      Service cafeucc~api started. (480 ms).
      Service memory started. (427 ms).
      Service userstore started. (4 ms).
      Service jmx_notification started. (196 ms).
      Service trex.service started. (1513 ms).
      Service file started. (1756 ms).
      Service p4 started. (1453 ms).
      Service classpath_resolver started. (62 ms).
      Service log_configurator started. (19040 ms).
      Service locking started. (7 ms).
      Service http started. (820 ms).
      Service naming started. (1393 ms).
      Service failover started. (151 ms).
      Service javamail started. (350 ms).
      Service appclient started. (304 ms).
      Service jmsconnector started. (464 ms).
      Service ts started. (457 ms).
      Service licensing started. (33 ms).
      Service connector started. (1071 ms).
      Service iiop started. (1319 ms).
      Service webservices started. (3808 ms).
      Service deploy started. (29721 ms).
      Service MigrationService started. (163 ms).
      Service bimmrdeployer started. (79 ms).
      Service configuration started. (175 ms).
      Service dbpool started. (8671 ms).
      Service cafeugpmailcf started. (500 ms).
      Service com.sap.security.core.ume.service started. (7927 ms).
      Service security started. (3006 ms).
      Service shell started. (236 ms).
      Service applocking started. (455 ms).
      Service tceCATTPingservice started. (37 ms).
      Service telnet started. (259 ms).
      Service classload started. (1208 ms).
      Service webdynpro started. (511 ms).
      Service dsr started. (1009 ms).
      Service keystore started. (2174 ms).
      Service developmentserver started. (1797 ms).
      Service ssl started. (52 ms).
      Service jmx started. (1357 ms).
      Service cafummetadata~imp started. (2227 ms).
      Service ejb started. (3294 ms).
      Service tcsecsecurestorage~service started. (830 ms).
      Service rfcengine started. (832 ms).
      Service cafeugp~model started. (197 ms).
      Service CUL started. (1771 ms).
      Service tceujwfuiwizsvc started. (14 ms).
      Service cafumrelgroups~imp started. (2829 ms).
      Service cafeuer~service started. (415 ms).
      Service basicadmin started. (2980 ms).
      Service servlet_jsp started. (6096 ms).
      Service prtbridge started. (2911 ms).
      Service com.adobe~DataManagerService started. (3094 ms).
      Service com.adobe~LicenseService started. (493 ms).
      Service tcsecwssec~service started. (3116 ms).
      Service com.adobe~DocumentServicesBinaries2 started. (620 ms).
      Service apptracing started. (2852 ms).
      Service com.adobe~FontManagerService started. (498 ms).
      Service com.adobe~DocumentServicesLicenseSupportService started. (387 ms).
      Service com.adobe~PDFManipulation started. (284 ms).
      Service adminadapter started. (980 ms).
      Service com.sap.portal.pcd.gl started. (39 ms).
      Service com.adobe~DocumentServicesConfiguration started. (2104 ms).
      Service tcsecdestinations~service started. (5500 ms).
      Service tc.monitoring.logviewer started. (6134 ms).
      Service com.adobe~XMLFormService started. (819 ms).
      Service pmi started. (165 ms).
      Service com.adobe~TrustManagerService started. (317 ms).
      Service com.adobe~DocumentServicesDestProtoService started. (231 ms).
      Service cafruntimeconnectivity~impl started. (62893 ms).
      Service tcsecvsi~service started. (976 ms).
      Service sld started. (6967 ms).
      Service monitor started. (2806 ms).
      Service com.sap.portal.prt.sapj2ee started. (147 ms).
      Service jms_provider started. (9062 ms).
    ServiceManager started for 79016 ms.
    Framework started for 96848 ms.
    GC 2: starting collection, threshold allocation reached.
    GC 2: collection starting 05/08/08 08:03:51
    GC 2: live objects 745472; collected objects 5156091; collected(KB) 928487.
    GC 2: queued for finalization 0; total soft references 8468; cleared soft references 0.
    GC 2: current heap(KB) 1142708; current threshold(KB) 1048576.
    GC 2: collect (milliseconds) 3028.
    GC 2: current cycle allocation(KB) 7441; previous cycle allocation(KB) 1048599.
    GC 2: total weak references 2607; cleared weak references 4.
    GC 2: total final references 19258; cleared final references 17233.
    GC 2: total phantom references 0; cleared phantom references 0.
    GC 2: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 2: collection ending 05/08/08 08:03:54
    SAP J2EE Engine Version 7.00   PatchLevel is running!
    PatchLevel September 11, 2006 16:35 GMT
    >
    Login :GC 3: starting collection, threshold allocation reached.
    GC 3: collection starting 05/08/08 08:06:15
    GC 3: collected class [Lcom/sap/engine/core/configuration/impl/utilities/ConfigurationPath;.
    GC 3: collected class sun/reflect/GeneratedMethodAccessor3630385287.
    GC 3: live objects 1665790; collected objects 7135030; collected(KB) 951876.
    GC 3: queued for finalization 0; total soft references 11565; cleared soft references 0.
    GC 3: current heap(KB) 1534552; current threshold(KB) 1048576.
    GC 3: collect (milliseconds) 3812.
    GC 3: current cycle allocation(KB) 21947; previous cycle allocation(KB) 1048593.
    GC 3: total weak references 11335; cleared weak references 76.
    GC 3: total final references 22258; cleared final references 19091.
    GC 3: total phantom references 0; cleared phantom references 0.
    GC 3: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 3: collection ending 05/08/08 08:06:18
    GC 4: starting collection, threshold allocation reached.
    GC 4: collection starting 05/08/08 08:08:59
    GC 4: collected class com/sap/engine/admin/model/monitoring/j2eeimpl/Messages.
    GC 4: live objects 2586327; collected objects 6257242; collected(KB) 965514.
    GC 4: queued for finalization 0; total soft references 12760; cleared soft references 0.
    GC 4: current heap(KB) 1701500; current threshold(KB) 1048576.
    GC 4: collect (milliseconds) 5253.
    GC 4: current cycle allocation(KB) 14367; previous cycle allocation(KB) 1048589.
    GC 4: total weak references 15920; cleared weak references 177.
    GC 4: total final references 19978; cleared final references 16017.
    GC 4: total phantom references 0; cleared phantom references 0.
    GC 4: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 4: collection ending 05/08/08 08:09:05
    GC 5: starting collection, threshold allocation reached.
    GC 5: collection starting 05/08/08 08:11:03
    GC 5: live objects 3284648; collected objects 7007268; collected(KB) 917356.
    GC 5: queued for finalization 0; total soft references 16766; cleared soft references 0.
    GC 5: current heap(KB) 1899328; current threshold(KB) 1048576.
    GC 5: collect (milliseconds) 4109.
    GC 5: current cycle allocation(KB) 30464; previous cycle allocation(KB) 1048598.
    GC 5: total weak references 17038; cleared weak references 132.
    GC 5: total final references 42750; cleared final references 38720.
    GC 5: total phantom references 0; cleared phantom references 0.
    GC 5: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 5: collection ending 05/08/08 08:11:07
    GC 6: starting collection, threshold allocation reached.
    GC 6: collection starting 05/08/08 08:14:03
    GC 6: live objects 4470495; collected objects 6575918; collected(KB) 979951.
    GC 6: queued for finalization 0; total soft references 34096; cleared soft references 0.
    GC 6: current heap(KB) 2095156; current threshold(KB) 1048576.
    GC 6: collect (milliseconds) 7546.
    GC 6: current cycle allocation(KB) 110101; previous cycle allocation(KB) 1048623.
    GC 6: total weak references 42891; cleared weak references 48.
    GC 6: total final references 35776; cleared final references 26485.
    GC 6: total phantom references 0; cleared phantom references 0.
    GC 6: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 6: collection ending 05/08/08 08:14:11
    GC 7: starting collection, threshold allocation reached.
    GC 7: collection starting 05/08/08 08:15:43
    GC 7: live objects 4922324; collected objects 7424152; collected(KB) 1034175.
    GC 7: queued for finalization 0; total soft references 36030; cleared soft references 0.
    GC 7: current heap(KB) 2196632; current threshold(KB) 1048576.
    GC 7: collect (milliseconds) 6246.
    GC 7: current cycle allocation(KB) 43733; previous cycle allocation(KB) 1048605.
    GC 7: total weak references 43181; cleared weak references 20.
    GC 7: total final references 17977; cleared final references 8153.
    GC 7: total phantom references 0; cleared phantom references 0.
    GC 7: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 7: collection ending 05/08/08 08:15:50
    GC 8: starting collection, threshold allocation reached.
    GC 8: collection starting 05/08/08 09:12:27
    GC 8: live objects 5349555; collected objects 8155508; collected(KB) 994872.
    GC 8: queued for finalization 0; total soft references 38217; cleared soft references 0.
    GC 8: current heap(KB) 2274232; current threshold(KB) 1048576.
    GC 8: collect (milliseconds) 7318.
    GC 8: current cycle allocation(KB) 220; previous cycle allocation(KB) 1048585.
    GC 8: total weak references 43778; cleared weak references 744.
    GC 8: total final references 31202; cleared final references 21696.
    GC 8: total phantom references 0; cleared phantom references 0.
    GC 8: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 8: collection ending 05/08/08 09:12:34
    GC 9: starting collection, threshold allocation reached.
    GC 9: collection starting 05/08/08 12:38:34
    GC 9: live objects 5680591; collected objects 11334758; collected(KB) 1014649.
    GC 9: queued for finalization 0; total soft references 39096; cleared soft references 3371.
    GC 9: current heap(KB) 2580764; current threshold(KB) 1048576.
    GC 9: collect (milliseconds) 50888.
    GC 9: current cycle allocation(KB) 5858; previous cycle allocation(KB) 1048591.
    GC 9: total weak references 43169; cleared weak references 5333.
    GC 9: total final references 61932; cleared final references 56885.
    GC 9: total phantom references 0; cleared phantom references 0.
    GC 9: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 9: collection ending 05/08/08 12:39:25
    GC 10: starting collection, threshold allocation reached.
    GC 10: collection starting 05/08/08 16:04:37
    GC 10: collected class sun/reflect/GeneratedConstructorAccessor3962137197.
    GC 10: collected class sun/reflect/GeneratedConstructorAccessor1177669627.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor1221400578.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor1175886476.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor842495978.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor2995163628.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor3935118260.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor3903475589.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor3820744598.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor902021387.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor3636210140.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor3041006465.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor2736528823.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor2741816805.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor3446856562.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor1063262256.
    GC 10: collected class sun/reflect/GeneratedSerializationConstructorAccessor2292015554.
    GC 10: collected class sun/reflect/GeneratedMethodAccessor3099279424.
    GC 10: live objects 5604892; collected objects 11760953; collected(KB) 1053812.
    GC 10: queued for finalization 0; total soft references 36473; cleared soft references 535.
    GC 10: current heap(KB) 2589776; current threshold(KB) 1048576.
    GC 10: collect (milliseconds) 11701.
    GC 10: current cycle allocation(KB) 2425; previous cycle allocation(KB) 1048581.
    GC 10: total weak references 38374; cleared weak references 910.
    GC 10: total final references 57639; cleared final references 53234.
    GC 10: total phantom references 0; cleared phantom references 0.
    GC 10: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 10: collection ending 05/08/08 16:04:49
    SAP J2EE Engine Version 7.00   PatchLevel is shutting down!  PatchLevel September 11, 2006 16:35 GMT
    Stopping services.
      Service com.sap.portal.prt.sapj2ee stopped. (287 ms)
      Service com.adobe~DocumentServicesLicenseSupportService stopped. (1567 ms)
      Service com.adobe~LicenseService stopped. (37 ms)
      Service com.adobe~XMLFormService stopped. (77 ms)
      Service com.adobe~FontManagerService stopped. (162 ms)
      Service com.adobe~PDFManipulation stopped. (165 ms)
      Service com.adobe~TrustManagerService stopped. (73 ms)
      Service com.adobe~DocumentServicesDestProtoService stopped. (52 ms)
      Service com.adobe~DocumentServicesBinaries2 stopped. (66 ms)
      Service com.adobe~DataManagerService stopped. (99 ms)
      Service iiop stopped. (1313 ms)
      Service cafumrelgroups~imp stopped. (27 ms)
      Service cafummetadata~imp stopped. (25 ms)
      Service cafeuer~service stopped. (4 ms)
      Service applocking stopped. (112 ms)
      Service licensing stopped. (10 ms)
      Service ts stopped. (57 ms)
      Service telnet stopped. (6 ms)
      Service com.adobe~DocumentServicesConfiguration stopped. (3 ms)
      Service tcsecwssec~service stopped. (50 ms)
      Service sld stopped. (29 ms)
      Service tcsecvsi~service stopped. (118 ms)
      Service pmi stopped. (176 ms)
      Service tcsecdestinations~service stopped. (4 ms)
      Service tceujwfuiwizsvc stopped. (10 ms)
      Service cafeugp~model stopped. (628 ms)
      Service tcsecsecurestorage~service stopped. (0 ms)
      Service ssl stopped. (6 ms)
      Service keystore stopped. (120 ms)
      Service classload stopped. (12 ms)
      Service jms_provider stopped. (161 ms)
      Service developmentserver stopped. (29 ms)
    GC 11: starting collection, threshold allocation reached.
    GC 11: collection starting 05/08/08 17:52:55

  • JAX-RPC vs OC4J J2Ee web service

    Hi,
    Currently we use Oracle10G 10.0.3 developer preview edition. we deployed same web service on both JAX-RPC platfrom and OC4J J2EE web service platfrom (RPC encoding style). We found that old platform seems to perform better than JAx-RPC platfrom with regard to serialization and de-serialzation. We also did the test on Doc/literal style in JAX-RPC platfrom and its performance is not as good as the one deployed on old platform. We understand JAX-RPC is new implementation and Oracle10.0.3 is under developer preview edition and so it may not be optimized. We have following questions
    1. Is this a known issue in JAX-RPC platform?
    2. Is there anyway to optimize JAX-RPC web service? Like using different XMl parser (instead of Oracle XML parser)
    3. When is the final release of 10.0.3 expected?
    4. Will Oracle be supporting old web service platfrom (OC4J J2EE web service platform)? If so how long?
    Thanks and regards
    __Hari

    Hi,
    Currently we use Oracle10G 10.0.3 developer preview edition. we deployed same web service on both JAX-RPC platfrom and OC4J J2EE web service platfrom (RPC encoding style). We found that old platform seems to perform better than JAx-RPC platfrom with regard to serialization and de-serialzation. We also did the test on Doc/literal style in JAX-RPC platfrom and its performance is not as good as the one deployed on old platform. We understand JAX-RPC is new implementation and Oracle10.0.3 is under developer preview edition and so it may not be optimized. We have following questions
    1. Is this a known issue in JAX-RPC platform?
    2. Is there anyway to optimize JAX-RPC web service? Like using different XMl parser (instead of Oracle XML parser)
    3. When is the final release of 10.0.3 expected?
    4. Will Oracle be supporting old web service platfrom (OC4J J2EE web service platform)? If so how long?
    Thanks and regards
    __Hari

  • Error while returning complex data type in a J2EE web service

    Hello,
    I am implementing J2EE web service which returns array of custom class object.
    I have implemented serializable interface to custom class, and also to session bean.
    But it gives the following error:
    Serializing object [Lcom.ltitl.j2ee.ejb.classes.ProjectDetails;@2a2289 fails. Nested message: XML Serialization Error. Object of Class [com.ltitl.j2ee.ejb.classes.ProjectDetails] does not have property [ObjId] of type [java.lang.Integer]. Check if the right object is passed to the serialization routine..
    As error stated about some property ObjId..I tried including such property in my class. But now it gave exception while deploying stating that ObjId already defined.
    Also I want to return multiple arrays of complex custom classes. i tried using vectors but didnt work. What is the method to return arrays of complex custom classes.
    Please help..
    Abhijeet

    Trying to create a web service that returns a Collection doesn't seem to be possible in Netweaver. The reason for this is that languages other than Java have difficulty in mapping Collections, amongst others, to their own native equivalents.
    There is a discussion on the subject here you may find useful:
    http://forum.capescience.com/showthreaded.php?Cat=&Board=webservices&Number=147&page=0&view=collapsed&sb=5&o=&vc=1
    The short answer is to use object Arrays instead, or a custom class that contains an array of each type of object you would expect to find in your Vector
    Hope this helps
    Steve

  • NullPointerException in Create J2EE Web Service Wizard

    I created an EJB2.1 session bean that has a method which returns an user defined class and also throws user defined exception. I tried to use the Create J2EE Web Service and chose to use RPC/Encoded scheme.
    The WSDL and java-wsdl mapping files were generated, but I got the following messages and exception. The webservices.xml and oracle-webservices.xml were not generated and wizard did not finish. Any ideas why would this happen?
    Web Service Log :
    Generating WSDL and mapping file
    Generating deployment descriptors
    ERROR: [failed to localize] Unable to find member message in jax-rpc mapping metadata for the exception whose wsdl message is: {http://mypackage/}MyException
    Exception dialog :
    java.lang.NullPointerException
         at oracle.j2ee.ws.tools.wsa.Util.createDeploymentDescriptors(Util.java:482)
         at oracle.j2ee.ws.tools.wsa.Util.createDeploymentDescriptors(Util.java:759)
         at oracle.jdeveloper.webservices.model.Generator.generateDDFiles(Generator.java:734)
         at oracle.jdeveloper.webservices.model.java.BaseJavaGenerator.doGeneration(BaseJavaGenerator.java:173)
         at oracle.jdeveloper.webservices.model.Generator.generateImpl(Generator.java:447)
         at oracle.jdeveloper.webservices.model.Generator.generate(Generator.java:295)
         at oracle.jdeveloper.webservices.model.WebService.saveEditImpl(WebService.java:3971)
         at oracle.jdeveloper.webservices.model.WebService.mav$saveEditImpl(WebService.java)
         at oracle.jdeveloper.webservices.model.WebService$1.run(WebService.java:3817)
         at oracle.jdeveloper.webservices.model.GeneratorUI$GeneratorAction.run(GeneratorUI.java:446)
         at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
         at java.lang.Thread.run(Thread.java:595)

    Specifically, this happens only when there is an exception thrown from the session bean method.

  • How to create stub for C++ client to invoke a  j2ee web service

    Hi All,
    I have developed a j2ee web service which is deployed in Tomcat. I have to call this service from C++ client. I have followed "Axis C++ Client User's Guide" to create stub for my service. I am running WSDL2Ws tool with command
    D:\axisserver\axis-c-win\wsdls>java -cp %AXISCLASSPATH_C%; org.apache.axis.wsdl.wsdl2ws.WSDL2Ws Calculator.wsdl -lc++ -sclient. While running this WSDL2Ws tool , it is giving error.
    Exception Stack is as follows.
    Exception in thread "main" java.lang.NoSuchMethodError
    at org.apache.axis.wsdl.wsdl2ws.info.Type.<init>(Unknown Source)
    at org.apache.axis.wsdl.wsdl2ws.info.TypeMap.getType(Unknown Source)
    at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.createParameterInfo(Unknown Source)
    at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.addRPCStyleInputMessageToMethodInfo(Unknown Source)
    at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.setMethodInfo(Unknown Source)
    at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.getServiceInfo(Unknown Source)
    at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.generateWrappers(Unknown Source)
    at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.main(Unknown Source)
    Anybody can suggest me what i missed...
    Thanks in advance...

    Hi all,
    I have solved this issue. I had JDK1.3 by default. So it was giving error. When i use java from jdk1.4, it created stubs for web service. Java version was the problem. Now it is working fine.
    Thanks....

  • Webdynpro application automatic start after j2ee startup

    Hi ,
    Is there a way to automatically start any specific webdynpro applications after j2ee startup
    Oren

    I guess you can write batch file for that.
    Example
    suppose you have a bat file which starts J2EE engine, startJ2EE.
    You can write a new bat file with following commands.
    startJ2EE.bat
    explorer http://<server>:<port>/webdynpro/<URL as application>
    Let me know if you need more help
    Ashutosh

  • J2EE Web services and JAX-RPC

    Hello..
    While working with J2EE web services using JDeveloper and OC4J, I noticed that it really doesn't confirm to Sun's JAX-RPC standard. The Web Service interface class does not extend the "Remote" and all methods don't throw "RemoteException" as mandated by JAX-RPC standard.
    I have few questions:
    (1) Are the OC4J J2EE web services completey different from JAX-RPC based web services.??
    (2) Does Oracle have any implementation of JAX-RPC??
    (3) Is Sun the only one promoting and implementing the JAX-RPC standard? Or are there other players?
    thanks...

    (1) Are the OC4J J2EE web services completey different from JAX-RPC based web services.??
    OC4J J2EE Web Services originate from Oracle/Apache SOAP with several differences:
    a. A model where each type of implementation gets a specific servlet (e.g. one for EJB's, one for PL/SQL, one for stateless and stateful Java classes. Architecturally, you can see the picture here:
    http://otn.oracle.com/docs/products/ias/doc_library/903doc_otn/generic.903/b10004/orawebservices.htm#1024808
    (scroll down a half page for the picture)
    b. The packaging of the Web services rather than using the Apache SOAP registration mechanism uses something closer to JSR 109 (also known as Web Services for J2EE, part of J2EE 1.4 with JAX-RPC, SAAJ [SOAP API forAttachments in Java] and JAXP [Java API for XML Parsing]), where the Web service is packaged as an ordinary ear file for deployment.
    Oracle built this implementation by extrapolating from the JAX-RPC documentation that was available last year before it was a final specification in an effort to release a production quality Web services implementation that was aligned with JAX-RPC. It has been through two releases - Oracle9iAS 9.02 and Oracle9iAS 9.0.3 and is now being evolved to JAX-RPC as we move to J2EE 1.4.
    (2) Does Oracle have any implementation of JAX-RPC??
    We are planning to release a JAX-RPC implementation in the new year (I don't have specific dates yet) on OC4J. The production implementation of this will be as seamless a migration as possible from the existing implementation. Oracle9i JDeveloper will also add support for JAX-RPC as a 3rd option in its list of choices available. You can get a sense of how such a migration would work by running the Web services wizard in JDev for Apache SOAP and then, in a separate project, running it for Oracle9iAS J2EE Web Services - imagine there being another option for JAX-RPC. The work to migrate should be as simple as running a wizard or command line utility (known as the Web Services Assembler tool in Oracle9iAS).
    (3) Is Sun the only one promoting and implementing the JAX-RPC standard? Or are there other players?
    Pretty much every one in the Java side of industry will be implementing JAX-RPC. The important time to note is when J2EE 1.4 is released ... sometime in the new year ... I believe around March but may be mistaken. Part of J2EE 1.4 is required support for JAX-RPC, SAAJ, Web Services for J2EE etc etc. This will standardize the implementation of Web services. Oracle, like others in the industry, supports the standard protocols, (SOAP), interfaces (WSDL) and registries (UDDI) - what J2EE 1.4 does is standardize the packaging, deployment and implementation (the wrappers generated by the tooling).
    My guess is that around JavaOne (June 2003) there will be a rash of announcements from J2EE vendors announcing support of JAX-RPC and J2EE 1.4 (or early implementations) as we will be in the same race that happened in 2001/2002 when J2EE 1.3 was the spec to announce implementations around.
    Mike.

  • Dump Core on Service Timeout

    Hello,
    is there a way to configure Tuxedo such that it dumps a core on a service
    timeout?
    Once in a blue moon we experienc a service timeout on a large production
    system. Unfortunately we would need to turn on a massive amount of logging
    to determine where exactly the process gets stuck. It would be so much
    simpler if the affected process would core when it is killed.
    What signal is the BBL sending?
    Could we change the signal handler for that signal (without causing other
    problems)?
    Thanks...
    Roger

    Hi Roger,
    By default the signal sent by BBL is SIGKILL. However, if environment
    variable "TM_SVCTIMEOUT_SIGTERM" is set for BBL, it will try to send SIGTERM
    first. So you can catch SIGTERM in your server and then issue an abort()
    which will generate a core file.
    Regards,
    -Hunter
    "Roger Fischer" <[email protected]> wrote in message
    news:[email protected]..
    Hello,
    is there a way to configure Tuxedo such that it dumps a core on a service
    timeout?
    Once in a blue moon we experienc a service timeout on a large production
    system. Unfortunately we would need to turn on a massive amount of logging
    to determine where exactly the process gets stuck. It would be so much
    simpler if the affected process would core when it is killed.
    What signal is the BBL sending?
    Could we change the signal handler for that signal (without causing other
    problems)?
    Thanks...
    Roger

  • Deploy a J2EE Web Services App in CE 7.1 SP1 SDN Preview

    Hi,
    I am new to SAP CE 7.1 SP1 (SDN Preview). I have a SAP J2EE (web services) application developed for SAP Netweaver 7.0.
    How to deply the application in CE 7.1 SP1.
    thanks in advance,
    Nagarjuna.

    Hi Nagarjuna,
    the easiest way will be to use the Deployment perspective in NWDS. Just choose Window > Open Perspective > Other > Deployment.
    If you have the application packages in a deployable archive (EAR, SCA, SDA, ...) in the file system, right-click External Deployable Archive and select Add. You can also choose archives to be deployed from the workspace.
    If your application cannot be deployed or doesn't run properly, you might have to make some changes to it in order to port it from NW 7.0 to 71.
    Other methods of deployment:
    - There's a program called JSPM which is aimed primarily at non-development, admin users (the guys running the production system).
    - There's a command-line deployment tool - have a look at <Install drive>\usr\sap\CE1\J00\j2ee\deployment\scripts.
    Cheers,
    Thorsten

  • J2EE startup framework and J2EE

    I have changed some Java VM parameters.
    To make above change effective, I have to re-start the J2EE instance.
    But my co-worker  (who left my company)  wrote in his document
    " For the SAP J2EE startup framework, it's NOT sufficient to re-satrt the J2EE
    instance"  to activate above change.
    I did some research on J2EE startup framework. I think it is no longer used in NW7.0
    Could you help me
    -- how do I know a system has SAP J2EE startup framework (I believe it is a concept  prior to 7.0 version).
        Our system is NW7.0.
    --  If it is a J2EE stratup framework, how do I activate above change?
    Thanks a million!

    Hello Christy
    SAP Netweaver 7.0 still has J2EE Startup and Control framework.
    When you change a property normally the tool prompts that a restart is required. Normally you get a description of what kind of restart is needed. "A cluster restart is needed" for example meaning you have to stop/start your J2EE cluster.
    If you are working on a dual stack you can stop/start through transaction SMICM under menu item Administration --> J2EE Cluster --> Send Hard Shutdown --> With Restart. That will hard restart your J2EE cluster and your parameter change (done in configtool I assume) will be activated once the J2EE cluster has restarted.
    If you are working on a single stack SAP system you can stop/start using command prompt stopsap JC<instance number> or through the SAP Management Console.
    You can check the activate VM parameters through the http://<hostname>:<j2ee port>:/index.html page under system information --> VM parameters for the node for which you have made a change.
    Kind regards
    Tom

Maybe you are looking for