J2EE server node crashes / .hotspot_compiler

Hi,
I'm trying to install a NW AS Java + usage type DI 7.0 SR3 on W2K3 R2 x64 SP2 with MS SQL Server 2005 and Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_18-b06, mixed mode). During sapinst the server node was shut down by the program but doesn't come up anymore. It crashes constantly and is directly beeing restarted.
A look in std_server0.out gave me the following insight (example, added lf):
Login :33.902: [ParNew 218352K->59053K(966656K), 0.0923355 secs]
39.132: [ParNew 222893K->62535K(966656K), 0.1131081 secs]
44.103: [ParNew 226375K->65891K(966656K), 0.0794097 secs]
### Excluding compile:  com.sap.engine.services.
webservices.jaxrpc.encoding.TypeMappingImpl::initializeRelations
48.296: [ParNew 229731K->66972K(966656K), 0.0845196 secs]
### Excluding compile:  com.sap.engine.services.
webservices.jaxrpc.encoding.InstanceBuilder::readElement
52.107: [ParNew 230812K->71757K(966656K), 0.0862884 secs]
### Excluding compile:  com.sap.engine.services.
webservices.jaxrpc.encoding.GeneratedComplexType::_loadInto
56.691: [ParNew 235597K->75601K(966656K), 0.0875517 secs]
An unrecoverable stack overflow has occurred.
# An unexpected error has been detected by HotSpot Virtual Machine:
#  EXCEPTION_STACK_OVERFLOW (0xc00000fd) at pc=0x00000000080e3dd6, pid=4460, tid=5532
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.4.2_18-b06 mixed mode)
# Problematic frame:
# V  [jvm.dll+0xe3dd6]
# An error report file with more information is saved as hs_err_pid4460.log
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
stdout/stderr redirect
node name   : server0
pid         : 3924
system name : DID
system nr.  : 00
started at  : Wed Sep 24 12:27:17 2008
As you can see the VM crashes. A look in the corresponding log-file (hs_err_pid4460.log) gave me the following insight (added lf):
Current CompileTask:
opto:1295  !   com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendMessage(
Lcom/sap/engine/core/cluster/impl6/ms/MSMessageObjectImpl;
Lcom/sap/engine/core/cluster/impl6/ms/MSRegistrable;
[BIIZ)Lcom/sap/engine/frame/cluster/message/MessageAnswer; (1477 bytes)
It seems that the CompileTask for the Hotspot VM always crashes when trying to compile the MSRawConnection class natively (reproducable). Sun describes a workaround for this type of problem, http://java.sun.com/javase/6/webnotes/trouble/TSG-VM/html/gbyzo.html#gbyzd . The workaround is to place a .hotspot_compiler file in the working directory of the application with an exclusion of the method. This will advice the VM whenever it decides to natively compile a certain bit of code first to check this file for exclusions. If the method identified by the VM to be compiled is exluded in this file, the compilation will be skipped. Therefore it would have been worth a try to exclude the above mentioned method sendMessage of class MSRawConnection for hotspot compilation. But when I do a quick search for .hotspot_compiler in my sap folder I find four of them, it seems SAP is already making heavy use of this "workaround" instead of reporting a bug. These files are located under:
D:\usr\sap\DID\JC00\j2ee\cluster
D:\usr\sap\DID\JC00\SDM\program
D:\usr\sap\DID\JC00\j2ee\cluster\dispatcher
D:\usr\sap\DID\JC00\j2ee\cluster\server0
They all contain the same exclusions, listed here (added lf):
## This file contains a list of methods which are going to be excluded from JIT compilation on server start
## The format of the file is as follows
## exclude package/subpackage1/subpackage2/../subpackageN/<Class_name> <method_to_exclude>
## Each line of the file describes only one method
## <method_to_exclude> is method name that will not be compiled with JIT
## package/subpackage1/subpackage2/../subpackageN/<Class_name>
is the name of the class with the packages containing <method_to_exclude>
## Example:
## exclude com/sap/engine/boot/Start main
## will not compile with JIT the main method of com.sap.engine.boot.Start class
## To enter a list of methods to exclude from JIT compilation write them after this line
exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
I thought the D:\usr\sap\DID\JC00\j2ee\cluster\server0\.hotspot_compiler file must be the right file, but however to be sure (test) I added the following line to all four files after having shutdown the instance:
exclude com/sap/engine/core/cluster/impl6/ms/MSRawConnection sendMessage
When I start the engine again, the content of every file gets overwritten by the original content, therefore lacking my new line. So it seems to me that the content is somehow hardcoded or contained in the db. If it is in the db, is it possible to change the content via config tool? It also seems that this jdk is a beta version since it reports itself with the version string 1.4.2_18-b06. This is the one officially delivered by Sun on the [SAP download page|http://java.sun.com/j2se/1.4.2/SAPsite/download.html], as mentioned in [SAP Note 941595|https://websmp130.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=941595]. Can you please provide me a solution to add an exclusion to the .hotspot_compiler file or workaround for the above mentioned problem. As a last option I will deinstall the system and reinstall it with another jdk (e.g. J2SE v 1.4.2_17 x64 SDK), but first I want to try to exclude the method/class from compilation. Thanks for your help!
Best regards,
Fabian

Hi,
You can tell the VM which file to load as compiler exclusion list. Therefore I copied .hotspot_compiler to .ext_hotspot_compiler and added my line
exclude com/sap/engine/core/cluster/impl6/ms/MSRawConnection sendMessage
then I went to config tool and added under cluster data -> myinstance -> myservernode under tab General the Java parameter
-XX:CompileCommandFile=D:/usr/sap/DID/JC00/j2ee/cluster/server0/.ext_hotspot_compiler
The J2EE node is now starting up without problems.
Best regards,
Fabian

Similar Messages

  • Central CCMS Alert for Java instance server node crash

    Hi,
    Is it possible to trigger an alert of an Java system server node crash using central CCMS alerts.
    J2EE instance CCMS alert does show some MTEs, however they do not trigger alerts. I got this info from below link
    http://help.sap.com/saphelp_nwce711/helpdata/en/46/11aaf352da14dce10000000a155369/frameset.htm
    Any idea how to trigger the alert for server node crash.
    I understand that server node crash should be investigated for permanent fix, however we need this as a proactive measure to know the crash if they happen.
    Thanks
    Imtiaz

    Hi Imtiaz,
    Do you see any error on the view>status auto-reaction? Have you been able to assign an auto-reaction to this MTE?
    Cheers,
    Maurício

  • The problem is occurred with J2ee server node which is disabled it from MMC

    Dear SAP Consultants,
    The problem is occurred with J2ee server node which is disabled J2ee server node from MMS Console and the abap work process is working fine but the dispatcher is yellow status and I can login to the abap system but Iu2019m not able to start the j2ee from Tcode u201CSmicmu201D as well
    The system parameters are:
    BI 7.0 System as ABAP & JAVA add on, windows 2003 on Oracle database, 24 GB Ram
    Paging files: Driveu201D Os system: minimum: 1525, maximum: 3048
    Driveu201DEu201D application: minimum: 70855, maximum: 70855
    I can see the log files as follow:
    From dev_disp:
    Sun Jun 21 13:10:28 2009
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 2892
      argv[0] = E:\usr\sap\BWD\DVEBMGS00\exe\jcontrol.EXE
      argv[1] = E:\usr\sap\BWD\DVEBMGS00\exe\jcontrol.EXE
      argv[2] = pf=E:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS00_cai-bwdev
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=64990
      argv[5] = -DSAPSYSTEM=00
      argv[6] = -DSAPSYSTEMNAME=BWD
      argv[7] = -DSAPMYNAME=cai-bwdev_BWD_00
      argv[8] = -DSAPPROFILE=E:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS00_cai-bwdev
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    DpJ2eeLogin: j2ee state = CONNECTED
    Sun Jun 21 13:10:29 2009
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
    ERROR => NiIRead: SiRecv failed for hdl 6 / sock 1032
        (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:1362) [nixxi.cpp    4424]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=2892)
    ERROR => DpProcKill: kill failed [dpntdisp.c   371]
    DpIJ2eeShutdown: j2ee state = SHUTDOWN
    Sun Jun 21 13:10:48 2009
    DpEnvCheckJ2ee: switch off j2ee start flag
    From dev_jcontrol :
    [Thr 2124] Sun Jun 21 13:10:29 2009
    [Thr 2124] *** ERROR => invalid return code of process [bootstrap] (exitcode = 66) [jstartxx.c   1642]
    [Thr 2124] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = 66)
    [Thr 2124] JControlCloseProgram: started (exitcode = 66)
    [Thr 2124] JControlCloseProgram: good bye... (exitcode = 66)
    From dev_bootstrap :
    JHVM_BuildArgumentList: main method arguments of node [bootstrap]
    -> arg[  0]: com.sap.engine.bootstrap.Bootstrap
    -> arg[  1]: ./bootstrap
    -> arg[  2]: ID0072573
    -> arg[  3]: -XX:NewSize=57M
    -> arg[  4]: -XX:MaxNewSize=57M
    -> arg[  5]: -Xms256M
    -> arg[  6]: -Xmx256M
    -> arg[  7]: -XX:+DisableExplicitGC
    -> arg[  8]: -verbose:gc
    -> arg[  9]: -Djava.security.policy=.java.policy
    -> arg[ 10]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 11]: -Djco.jarm=1
    [Thr 5216] JLaunchIExitJava: exit hook is called (rc = 66)
    [Thr 5216] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 5216] JLaunchCloseProgram: good bye (exitcode = 66)
    From server.0.log :
    #1.5 #001E4F208703008A0001C7470000092000046A4414D60A1F#1242740546634#/System/Server##com.sap.caf.eu.gp.schedule.impl.ScheduleWorker#J2EE_GUEST#0##n/a##27772ea0447811deb9bf001e4f208703#SAPEngine_Application_Thread[impl:3]_25##0#0#Error#1#com.sap.caf.eu.gp.schedule.impl.ScheduleWorker#Plain###ERROR_ACQUIRE_CONNECTION
    com.sap.caf.eu.gp.base.exception.EngineException: ERROR_ACQUIRE_CONNECTION
         at com.sap.caf.eu.gp.base.db.ConnectionPoolJ2EE.getConnection(ConnectionPoolJ2EE.java:92)
         at com.sap.caf.eu.gp.schedule.impl.ScheduleDbImpl.getScheduleToProcess(ScheduleDbImpl.java:1936)
         at com.sap.caf.eu.gp.schedule.impl.ScheduleService.getScheduleToProcess(ScheduleService.java:432)
         at com.sap.caf.eu.gp.schedule.impl.ScheduleWorker.work(ScheduleWorker.java:77)
         at com.sap.caf.eu.gp.schedule.impl.ScheduleWorker.run(ScheduleWorker.java:63)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: com.sap.sql.log.OpenSQLException: Error while accessing secure store: File "
    cai-bwdev
    sapmnt
    BWD
    SYS
    global
    security
    data
    SecStore.properties" does not exist although it should..
         at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:59)
         at com.sap.caf.eu.gp.base.db.ConnectionPoolJ2EE.getConnection(ConnectionPoolJ2EE.java:89)
         ... 8 more
    Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: com.sap.sql.log.OpenSQLException: Error while accessing secure store: File "
    cai-bwdev
    sapmnt
    BWD
    SYS
    global
    security
    data
    SecStore.properties" does not exist although it should..
         at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:193)
         at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:338)
         at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:267)
         at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:51)
         ... 9 more
    Caused by: com.sap.sql.log.OpenSQLException: Error while accessing secure store: File "
    cai-bwdev
    sapmnt
    BWD
    SYS
    global
    security
    data
    SecStore.properties" does not exist although it should..
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:145)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:226)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:197)
         at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:117)
         ... 12 more
    Caused by: com.sap.security.core.server.secstorefs.FileMissingException: File "
    cai-bwdev
    sapmnt
    BWD
    SYS
    global
    security
    data
    SecStore.properties" does not exist although it should.
         at com.sap.security.core.server.secstorefs.StorageHandler.openExistingStore(StorageHandler.java:372)
         at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:1946)
         at com.sap.sql.connect.OpenSQLConnectInfo.getStore(OpenSQLConnectInfo.java:802)
         at com.sap.sql.connect.OpenSQLConnectInfo.lookup(OpenSQLConnectInfo.java:783)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:209)
         ... 14 more
    Please advice with the right solution,
    Regards,
    Ahmed

    thanks

  • Creating j2ee server node

    hi everyone,
    can any one tell me how to create j2ee server node.
    What happens basically by creating one.
    -Naveen.

    Dear Naveen,
    A  node represents a logical view of an external communication system in the SAP System,
    This will help you
    http://help.sap.com/saphelp_webas620/helpdata/en/2b/d9263f4b8a11d1894c0000e8323c4f/frameset.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/73a16f1d-0e01-0010-95a6-a4f66ca1a65e
    Regards
    Agasthuri Doss

  • Batch restart of j2ee server nodes

    Hello all,
    Is it possible (maybe with jcmon) to schedule a single server node restart within a j2ee cluster ?
    I would like to restart just one out of 4 server nodes on which ther are sometimes memory issues and where there are dedicated jobs running
    thanks and regards,
    MIchele

    Hi Donna
    If you are on unix/linux then you can pass options to jcmon over a pipe. This will restart the server1 node:
    echo "20\n5\n2\ny\n0\n0\n" | jcmon pf=SID_DVEBMGS00_host
    20\n5\n2\ny\n0\n0\n decodes like this:
    20 -> goto local administration menu
    5 -> restart process
    2 -> restart server node 1 (change this to your server node number)
    y -> yes i want to restart it
    0 -> exit local admin menu
    0 -> exit jcmon
    This command can be included into a script and scheduled in cron.
    Best regards, Michael

  • Restarting J2EE server nodes from Developer Studio Vs SAP Management Consol

    Hi,
    What makes the difference between restarting server nodes from Dev Studio and SAP Management console.
    Please let me know if any documents related to this.
    Thanks

    Thanks for your quick reply.
    I observed that options for restarting services from Dev Studio are disabled.
    Could you please let me know where we need to configure to enable these options when right click on server instances.
    Thanks

  • When should i consider to add multiple j2ee server node?

    are there best practice about configuration for this?
    such as : any recommendation provided are helpful for me!
    thanks a lot!

    Hi,
    Please see this link
    adding additional j2ee node
    Best Regards
    Imran

  • JDBC Adapter: J2EE server crashes while sending large messages

    We want to use the following scenario to transfer data from a MS SQL Server to SAP BW via XI:
    JDBC Sender Adapter – XI – SAP ABAP Proxy.
    All works fine with a small amount of data. But if the select statement delivers too many record sets and the size of the transformed XML payload is greater then 50 MB the J2EE server crashes. A complete restart is necessary. It seems to be am memory problem.
    Here are the entries from our log files:
    dev_server0
    [Thr 6151] Mon Jul 24 12:46:57 2006
    [Thr 6151] JLaunchIExitJava: exit hook is called (rc=666)
    [Thr 6151] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 940893 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 6151] SigISetIgnoreAction : SIG_IGN for signal 17
    [Thr 6151] JLaunchCloseProgram: good bye (exitcode=666)
    std_server0.out
    FATAL: Caught OutOfMemoryError! Node will exit with exit code 666java.lang.OutOfMemoryError
    Is this a general problem of the XI or a specific one of our configuration? Is it possible to transfer such large messages via XI? If not, is there a workaround for such scenarios?
    (Memory heap size of the J2EE server is 1024 MB.)

    > Hi Gil,
    >
    > i had nearly the same problems some times in praxis
    > and the mapping was the reason. Just change your
    > interface determination temporary, delete the mapping
    > and test again to find out if the mapping is the
    > reason.
    >
    > Regards,
    > Udo
    I have changed my interface determination so that no message mapping is used. The J2EE server still crashes.
    > Hi Gil,
    > This does sounds like a memory problem especially
    > when it comes to 50M message with a minimum XI sys
    > requierments...
    > To be sure you can check on the RWB for the
    > componnent monitoring at the JDBC adapters and look
    > for your adapter
    > look at the status of the adapter and the trace
    > there...
    Hi Nimrod
    In case of such an error I have no entries in channel monitor. So I can't see anything there. I have also no entries in message monitor of the RWB in this case. So I don't get any information with standard XI tools.
    > My reccomendation to you is to set the poll intervall
    > to a shorter period,this way you'll make sure you get
    > less records...I hope you have remembered to add  a
    > status/flag column on the table to be set after
    > selection so no duplicate records will be taken on
    > the second pools.
    >
    The problem is that the source of my data is not a simple SQL statement but a stored procedure. So I don't know exactly how many records will be delivered. A update command is not possible.

  • How to create one more server node for SAP J2EE server?

    Hi,
    Can any one please suggest how to create one more server node for SAP J2EE server? I am using WAS700.
    Thanks and Regards,
    Smriti.

    Hai,
          Login into the Configtool(C:\usr\sap\SID\DVEBMGS<inst no>\j2ee\configtool) if ABAP+JAVA stack or C:\usr\sap\SID\JC<inst no>\j2ee\configtool) if JAVA stack
    click on the instance and and select the addserver button on the top to create a servernode for J2EE server.
    Thanks and Regards,

  • ORA-12514 on R12 EBS Apps server when 1 DB RAC node crashed/down

    Just now Production 11.2.0.2 RAC DB on windows 2008 server Node1 crashed. While on Node 2 all services are up and running including database. But from EBS R12.1.2 application server when connecting as username/password from sql*plus is throwing ORA-12514 error.
    While It is connecting if I give username/password@TNSNAME but not without @TNSNAME. Due to this none of the application services are starting.
    Please help/advise. Thank you.
    Following is the tnsnames.ora,
    # This file is automatically generated by AutoConfig.  It will be read and
    # overwritten.  If you were instructed to edit this file, or if you are not
    # able to use the settings created by AutoConfig, refer to Metalink Note
    # 387859.1 for assistance.
    #$Header: NetServiceHandler.java 120.19.12010000.6 2010/03/09 08:11:36 jmajumde ship $
    ORCL=
            (DESCRIPTION=
                    (ADDRESS=(PROTOCOL=tcp)(HOST=orcldbscan)(PORT=1521))
                (CONNECT_DATA=
                    (SERVICE_NAME=ORCL)
                    (INSTANCE_NAME=ORCL1)
    ORCL1=
            (DESCRIPTION=
                    (ADDRESS=(PROTOCOL=tcp)(HOST=orcldbscan)(PORT=1521))
                (CONNECT_DATA=
                    (SERVICE_NAME=ORCL)
                    (INSTANCE_NAME=ORCL1)
    ORCL1_FO=
            (DESCRIPTION=
                    (ADDRESS=(PROTOCOL=tcp)(HOST=orcldbscan)(PORT=1521))
                (CONNECT_DATA=
                    (SERVICE_NAME=ORCL)
                    (INSTANCE_NAME=ORCL1)
    ORCL_FO=
            (DESCRIPTION=
                    (ADDRESS=(PROTOCOL=tcp)(HOST=orcldbscan)(PORT=1521))
                (CONNECT_DATA=
                    (SERVICE_NAME=ORCL)
                    (INSTANCE_NAME=ORCL1)
    ORCL1=
            (DESCRIPTION=
                    (ADDRESS=(PROTOCOL=tcp)(HOST=orcldbscan)(PORT=1521))
                (CONNECT_DATA=
                    (SERVICE_NAME=ORCL)
                    (INSTANCE_NAME=ORCL1)
    ORCL1_FO=
            (DESCRIPTION=
                    (ADDRESS=(PROTOCOL=tcp)(HOST=orcldbscan)(PORT=1521))
                (CONNECT_DATA=
                    (SERVICE_NAME=ORCL)
                    (INSTANCE_NAME=ORCL1)
    ORCL2=
            (DESCRIPTION=
                    (ADDRESS=(PROTOCOL=tcp)(HOST=orcldb2-vip.sa.company.net)(PORT=1521))
                (CONNECT_DATA=
                    (SERVICE_NAME=ORCL)
                    (INSTANCE_NAME=ORCL2)
    ORCL2_FO=
            (DESCRIPTION=
                    (ADDRESS=(PROTOCOL=tcp)(HOST=orcldb2-vip.sa.company.net)(PORT=1521))
                (CONNECT_DATA=
                    (SERVICE_NAME=ORCL)
                    (INSTANCE_NAME=ORCL2)
    ORCL_BALANCE=
            (DESCRIPTION=
                (ADDRESS_LIST=
                    (LOAD_BALANCE=YES)
                    (FAILOVER=YES)
                    (ADDRESS=(PROTOCOL=tcp)(HOST=orcldb1-vip.sa.company.net)(PORT=1521))
                    (ADDRESS=(PROTOCOL=tcp)(HOST=orcldb2-vip.sa.company.net)(PORT=1521))
                (CONNECT_DATA=
                    (SERVICE_NAME=ORCL)
    FNDFS_orclAPPL=
            (DESCRIPTION=
                    (ADDRESS=(PROTOCOL=tcp)(HOST=orclAPPL.sa.company.net)(PORT=1626))
                (CONNECT_DATA=
                    (SID=FNDFS)
    FNDFS_orclAPPL.sa.company.net=
            (DESCRIPTION=
                    (ADDRESS=(PROTOCOL=tcp)(HOST=orclAPPL.sa.company.net)(PORT=1626))
                (CONNECT_DATA=
                    (SID=FNDFS)
    FNDFS_ORCL_orclAPPL=
            (DESCRIPTION=
                    (ADDRESS=(PROTOCOL=tcp)(HOST=orclAPPL.sa.company.net)(PORT=1626))
                (CONNECT_DATA=
                    (SID=FNDFS)
    FNDFS_ORCL_orclAPPL.sa.company.net=
            (DESCRIPTION=
                    (ADDRESS=(PROTOCOL=tcp)(HOST=orclAPPL.sa.company.net)(PORT=1626))
                (CONNECT_DATA=
                    (SID=FNDFS)
    FNDSM_orclAPPL_ORCL=
            (DESCRIPTION=
                    (ADDRESS=(PROTOCOL=tcp)(HOST=orclAPPL.sa.company.net)(PORT=1626))
                (CONNECT_DATA=
                    (SID=FNDSM)
    FNDSM_orclAPPL.sa.company.net_ORCL=
            (DESCRIPTION=
                    (ADDRESS=(PROTOCOL=tcp)(HOST=orclAPPL.sa.company.net)(PORT=1626))
                (CONNECT_DATA=
                    (SID=FNDSM)
    FNDFS_APPLTOP_orclappl=
            (DESCRIPTION=
                (ADDRESS_LIST=
                    (ADDRESS=(PROTOCOL=tcp)(HOST=orclAPPL.sa.company.net)(PORT=1626))
                (CONNECT_DATA=
                    (SID=FNDFS)
    IFILE=E:\ORACLE\ORCL\INST\APPS\ORCL_orclappl\ora\10.1.2\network\admin\ORCL_orclappl_ifile.ora

    A database/OS crash shouldn't have such impact on your configuration. Please review the following docs and verify your setup.
    Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release 12 (Doc ID 823587.1)
    Configuring and Managing E-Business Application Tier for RAC (Doc ID 1311528.1)
    Thanks,
    Hussein

  • Server node creation in J2EE

    Hi,
       I want to create a new server node (server1)with existing server0 in J2EE engine .Please tell me the procedure .
    Thanks

    Hello,
    Olivier is right, all info is in the SAP online help :
    [http://help.sap.com/erp2005_ehp_04/helpdata/EN/68/dcde416fb3c417e10000000a155106/content.htm|http://help.sap.com/erp2005_ehp_04/helpdata/EN/68/dcde416fb3c417e10000000a155106/content.htm]
    Proper J2EE and portal setup means a good preparation not only adding server nodes.
    Also make sure that you have enough space in your J2EE instance directory, this is often forgotten.
    [http://help.sap.com/erp2005_ehp_04/helpdata/EN/ef/61ca70718e4992befe589d9fb9d37b/content.htm|http://help.sap.com/erp2005_ehp_04/helpdata/EN/ef/61ca70718e4992befe589d9fb9d37b/content.htm]
    For the rest have a look on the SAP Market place for SAP Notes concerning J2EE tuning, especially SAP Notes related to J2EE memory parameters for your OS.
    There exist a lot of interesting SAP Notes on this topic.
    Success.
    Wim

  • J2EE Server unable to start

    Hi,
    first of all, i'm really new to SAP NW. Today I started installing the Sneak Preview of SAP NetWeaver 2004 7.0 SP9
    JavaStack on my Virtual Machine (Windows2003Server, J2SE 1.4.2.09) and it worked fine.
    After installation I started the SAP Management Console and tried to start my first and only instance J2E.
    In J2E i got 3 instances, the DB, Instance 0 and Instance 1.
    After start:
    DB is working (blue)
    Instance 0 is working (green)
    Instance 1 failed while starting (turned from yellow to red)
      Process List shows:
      jcontrol.EXE | J2EE Server | License check failed
      igswd.EXE | IGS Watchdog | Running
    Problem:
    I don't know why the License check failed!
    I downloaded the Software about mid of february, its been about 3 month ago and I ran the install for the first time
    today. What might be the problem? I searched the SDN-History for similar problems, but i did not find an adequate
    answer. I checked dev_jcontrol and the "license check failed" entry is in the file. So I'm wondering why my license
    check fails, although I'm installing the software for the first time!
    An info i got from the start.htm is:
    The license of this Trial Version is for evaluation purposes only and does not allow commercial use.
    The license is valid for 90 days and cannot be extended (View license). If the license has expired, the
    entry license check failed will appear in the trace file <INST_DRIVE>:\usr\sap\J2E\JC01\work\dev_jcontrol,
    if the instance name remains unchanged during the installation process. Please refer to SAP Developer
    Network for more information about commercially available editions of SAP Web Application Server and SAP NetWeaver Developer Studio.
    May one find some more information in that file?
    I realised that a package is missing, but read in the forum, that this is not a obligatory package (?)
    JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
    trc file: "D:\usr\sap\J2E\JC01\work\dev_jcontrol", trc level: 1, release: "700"
    node name   : jcontrol
    pid         : 2644
    system name : J2E
    system nr.  : 01
    started at  : Wed May 07 13:28:11 2008
    arguments       :
           arg[00] : D:\usr\sap\J2E\JC01\exe\jcontrol.EXE
           arg[01] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
    [Thr 1352] Wed May 07 13:28:11 2008
    [Thr 1352] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]
    [Thr 1352] *** WARNING => INFO: Unknown property [instance.en.host=sope75] [jstartxx.c   841]
    [Thr 1352] *** WARNING => INFO: Unknown property [instance.box.number=J2EJC01sope75] [jstartxx.c   841]
    [Thr 1352] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties;D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties]
    -> ms host    : sope75
    -> ms port    : 3900
    -> OS libs    : D:\usr\sap\J2E\JC01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> files [01] : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
    Instance properties
    -> ms host    : sope75
    -> ms port    : 3900
    -> os libs    : D:\usr\sap\J2E\JC01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap_ID18439050 : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID18439000 : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> [02] bootstrap            : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID18439050           : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> [01] ID18439000           : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> [02] sdm                  : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
    [Thr 1352] [Node: bootstrap] java home is set by profile parameter
         Java Home: C:\Programme\Java\j2sdk1.4.2_09
    [Thr 1352] Wed May 07 13:28:19 2008
    [Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
    JStartupIReadSection: read node properties [bootstrap]
    -> node name          : bootstrap
    -> node type          : bootstrap
    -> node execute       : yes
    -> java path          : C:\Programme\Java\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          : 512M
    -> root path          : D:\usr\sap\J2E\JC01\j2ee\cluster
    -> class path         : .\bootstrap\launcher.jar
    -> OS libs path       : D:\usr\sap\J2E\JC01\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     : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
    -> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0184390
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 60000
    -> shutdown timeout   : 120000
    [Thr 1352] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
    [Thr 1352] [Node: bootstrap] java home is set by profile parameter
         Java Home: C:\Programme\Java\j2sdk1.4.2_09
    [Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
    JStartupIReadSection: read node properties [bootstrap]
    -> node name          : bootstrap
    -> node type          : bootstrap
    -> node execute       : yes
    -> java path          : C:\Programme\Java\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          : 512M
    -> root path          : D:\usr\sap\J2E\JC01\j2ee\cluster
    -> class path         : .\bootstrap\launcher.jar
    -> OS libs path       : D:\usr\sap\J2E\JC01\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     : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
    -> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0184390
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 60000
    -> shutdown timeout   : 120000
    JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
    -> arg[02] = -DSAPINFO=J2E_01_bootstrap
    -> arg[03] = -nodeId=-1
    -> arg[04] = -file=D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
    -> arg[06] = -nodeName=bootstrap
    -> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_bootstrap.out
    -> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_bootstrap.out
    -> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_bootstrap
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
    -> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
    [Thr 1352] Wed May 07 13:30:12 2008
    [Thr 1352] JControlExecuteBootstrap: read instance values after global bootstrap
    [Thr 1352] *** WARNING => INFO: Unknown property [instance.box.number=J2EJC01sope75] [jstartxx.c   841]
    [Thr 1352] *** WARNING => INFO: Unknown property [instance.en.host=sope75] [jstartxx.c   841]
    [Thr 1352] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]
    [Thr 1352] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties;D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties]
    -> ms host    : sope75
    -> ms port    : 3900
    -> OS libs    : D:\usr\sap\J2E\JC01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : normal
    -> run action : NONE
    -> enabled    : yes
    [Thr 1352] JControlExecuteBootstrap: enumerate the nodes after global bootstrap
    Used property files
    -> files [00] : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> files [01] : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
    Instance properties
    -> ms host    : sope75
    -> ms port    : 3900
    -> os libs    : D:\usr\sap\J2E\JC01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : normal
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID18439000 : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID18439050 : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID18439000           : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> [01] ID18439050           : D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> [02] sdm                  : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
    [Thr 1352] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID18439000]
    [Thr 1352] [Node: dispatcher bootstrap] java home is set by profile parameter
         Java Home: C:\Programme\Java\j2sdk1.4.2_09
    [Thr 1352] Wed May 07 13:30:16 2008
    [Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
    JStartupIReadSection: read node properties [bootstrap_ID18439000]
    -> node name          : dispatcher bootstrap
    -> node type          : bootstrap
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\Programme\Java\j2sdk1.4.2_09
    -> java parameters    : -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          : 256M
    -> root path          : D:\usr\sap\J2E\JC01\j2ee\cluster
    -> class path         : .\bootstrap\launcher.jar
    -> OS libs path       : D:\usr\sap\J2E\JC01\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     : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
    -> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID018439000
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 60000
    -> shutdown timeout   : 120000
    JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
    -> arg[02] = -DSAPINFO=J2E_01_bootstrap
    -> arg[03] = -nodeId=-1
    -> arg[04] = -file=D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
    -> arg[06] = -nodeName=bootstrap_ID18439000
    -> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_bootstrap_ID18439000.out
    -> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_bootstrap_ID18439000.out
    -> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_bootstrap_ID18439000
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
    -> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
    [Thr 1352] Wed May 07 13:31:04 2008
    [Thr 1352] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID18439050]
    [Thr 1352] [Node: server0 bootstrap] java home is set by profile parameter
         Java Home: C:\Programme\Java\j2sdk1.4.2_09
    [Thr 1352] Wed May 07 13:31:06 2008
    [Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
    JStartupIReadSection: read node properties [bootstrap_ID18439050]
    -> node name          : server0 bootstrap
    -> node type          : bootstrap
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\Programme\Java\j2sdk1.4.2_09
    -> java parameters    : -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          : 256M
    -> root path          : D:\usr\sap\J2E\JC01\j2ee\cluster
    -> class path         : .\bootstrap\launcher.jar
    -> OS libs path       : D:\usr\sap\J2E\JC01\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     : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
    -> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID018439050
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 60000
    -> shutdown timeout   : 120000
    JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
    -> arg[02] = -DSAPINFO=J2E_01_bootstrap
    -> arg[03] = -nodeId=-1
    -> arg[04] = -file=D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
    -> arg[06] = -nodeName=bootstrap_ID18439050
    -> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_bootstrap_ID18439050.out
    -> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_bootstrap_ID18439050.out
    -> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_bootstrap_ID18439050
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
    -> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
    [Thr 1352] Wed May 07 13:33:15 2008
    [Thr 1352] JControlIBuildProcessList: Maximum error count is set to 4
    [Thr 1308] JControlRequestFunc: Thread 1308 started as listener thread for np messages.
    [Thr 1352] [Node: dispatcher] java home is set by profile parameter
         Java Home: C:\Programme\Java\j2sdk1.4.2_09
    [Thr 1352] Wed May 07 13:33:17 2008
    [Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID18439000]
    -> node name          : dispatcher
    -> node type          : dispatcher
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\Programme\Java\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 -verbose:gc  -verbose:gc -XX:NewSize=28m -XX:MaxNewSize=28m -XX:+DisableExplicitGC
    -> 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
    -> init heap size     : 170M
    -> root path          : D:\usr\sap\J2E\JC01\j2ee\cluster\dispatcher
    -> class path         : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : D:\usr\sap\J2E\JC01\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     : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 60000
    -> shutdown timeout   : 120000
    [Thr 1352] [Node: server0] java home is set by profile parameter
         Java Home: C:\Programme\Java\j2sdk1.4.2_09
    [Thr 1352] Wed May 07 13:33:18 2008
    [Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID18439050]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\Programme\Java\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 -verbose:gc -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -XX:NewSize=145m -XX:MaxNewSize=145m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:+DisableExplicitGC -XX:+UseParNewGC -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
    -> 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          : 874M
    -> init heap size     : 874M
    -> root path          : D:\usr\sap\J2E\JC01\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : D:\usr\sap\J2E\JC01\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     : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
    -> parameters         :
    -> debuggable         : yes
    -> debug mode         : yes
    -> debug port         : 50121
    -> shutdown timeout   : 120000
    [Thr 1352] INFO: Invalid property value [Debbugable=yes]
    [Thr 1352] [Node: SDM] java home is set by profile parameter
         Java Home: C:\Programme\Java\j2sdk1.4.2_09
    [Thr 1352] Wed May 07 13:33:19 2008
    [Thr 1352] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar
    JStartupIReadSection: read node properties [sdm]
    -> node name          : SDM
    -> node type          : sdm
    -> node execute       : yes
    -> java path          : C:\Programme\Java\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          : 256M
    -> root path          : D:\usr\sap\J2E\JC01\SDM\program
    -> class path         : D:\usr\sap\J2E\JC01\SDM\program\bin\SDM.jar
    -> OS libs path       : D:\usr\sap\J2E\JC01\j2ee\os_libs
    -> main class         : SDMInternal
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
    -> shutdown class     : com.sap.sdm.jstartup.shutdown.InternalShutDown
    -> parameters         : server sdmhome=D:\usr\sap\J2E\JC01\SDM\program
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 60000
    -> shutdown timeout   : 120000
    [Thr 1352] JControlMSConnect: attached to message server (sope75/3900)
    JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
    -> arg[02] = -DSAPINFO=J2E_01_dispatcher
    -> arg[03] = -nodeId=0
    -> arg[04] = -file=D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
    -> arg[06] = -nodeName=ID18439000
    -> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_dispatcher.out
    -> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_dispatcher.out
    -> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_dispatcher
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
    -> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
    [Thr 3376] JControlMSMessageFunc: Thread 3376 started as listener thread for ms messages.
    [Thr 1352] JControlICheckProcessList: process dispatcher started (PID:724)
    JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
    -> arg[02] = -DSAPINFO=J2E_01_server
    -> arg[03] = -nodeId=1
    -> arg[04] = -file=D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
    -> arg[06] = -nodeName=ID18439050
    -> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_server0.out
    -> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_server0.out
    -> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_server0
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = -debugMode=yes
    -> arg[12] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
    -> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
    [Thr 1352] JControlICheckProcessList: process server0 started (PID:2276)
    JControlStartJLaunch: program = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\J2E\JC01\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
    -> arg[02] = -DSAPINFO=J2E_01_sdm
    -> arg[03] = -nodeId=2
    -> arg[04] = -file=D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_2644
    -> arg[06] = -nodeName=sdm
    -> arg[07] = -jvmOutFile=D:\usr\sap\J2E\JC01\work\jvm_sdm.out
    -> arg[08] = -stdOutFile=D:\usr\sap\J2E\JC01\work\std_sdm.out
    -> arg[09] = -locOutFile=D:\usr\sap\J2E\JC01\work\dev_sdm
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_sope75
    -> lib path = PATH=C:\Programme\Java\j2sdk1.4.2_09\jre\bin\server;C:\Programme\Java\j2sdk1.4.2_09\jre\bin;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\Programme\Java\j2sdk1.4.2_09\bin;D:\usr\sap\J2E\JC01\j2ee\os_libs;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;c:\orabase\1020\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;c:\prgramme\sharepoint portal server\bin;C:\Programme\Gemeinsame Dateien\Microsoft Shared\web server extensions\60\BIN;C:\Programme\Microsoft SQL Server\80\Tools\Binn\;c:\Programme\Java\jdk1.5.0_13\bin;D:\usr\sap\J2E\SYS\exe\uc\NTI386
    [Thr 1352] JControlICheckProcessList: process SDM started (PID:3312)
    [Thr 1352] JControlMSSendLogon: delete SDM logon information (rc=0)
    [Thr 3376] Wed May 07 13:33:47 2008
    [Thr 3376] JControlIEnableProcesses: disable processes of type (Exclude:0) [SDM Server]
    [Thr 3376] JControlIDisableProcess: disable process SDM
    [Thr 3376] JControlIProcessSoftKill: soft kill of process SDM (pid:3312)
    [Thr 1352] Wed May 07 13:33:52 2008
    [Thr 1352] JControlICheckProcessList: process SDM (pid:3312) died (STOPPING)
    [Thr 1352] JControlIResetProcess: reset process SDM
    [Thr 1352] Wed May 07 14:20:27 2008
    [Thr 1352] JControlICheckProcessList: process dispatcher (pid:724) died (RUN-FLAG)
    [Thr 1352] JControlIResetProcess: reset process dispatcher
    *[Thr 1352] JControlICheckProcessList: license check failed*
    *[Thr 1352] JControlMainLoop: license check failed -> shutdown the instance*
    [Thr 1352] JControlProcessMessage: received <shutdown without restart> command
    [Thr 1352] JControlIStopInstance: shutting down (command: 0)
    [Thr 1352] JControlIProcessSoftKill: soft kill of process server0 (pid:2276)
    [Thr 1352] Wed May 07 14:22:33 2008
    [Thr 1352] *** ERROR => Can't terminate process (pid = 2276,handle = 00000678,err = 5) [jstartnt.c   690]
    [Thr 1352] *** ERROR => Critical error, can't terminate process server0 (pid:2276) (rc=-2) [jcntrxxi.c   407]
    [Thr 1352] JControlICheckProcessList: process server0 (pid:2276) died (STOPPING)
    [Thr 1352] JControlIResetProcess: reset process server0
    [Thr 1352] JControlCloseProgram: started (exitcode = 0)
    [Thr 3376] JControlMSMessageFunc: shutdown -> terminate message listener
    [Thr 3376] JControlMSMessageFunc: leave listener thread
    [Thr 1352] Wed May 07 14:22:34 2008
    [Thr 1352] JControlCloseProgram: good bye... (exitcode = -11111)
    Regards
    RandomStudent
    Edited by: RandomStudent on May 7, 2008 4:45 PM
    Edited by: RandomStudent on May 7, 2008 4:47 PM

    Hello Vijith, thanks for your answer.
    Installed a Sneak Preview of SAP NetWeaver 7.1 CE on Monday(5th May), but it failed.
    Deinstalled the 7.1 CE Software on Tuesday (6th May).
    Installed Sneak Preview of SAP Netweaver (2004s) 7.0 SP9 on Wednesday (7th May) and it was installed correctly, but i got the problem with the license check.
    So the Options are:
    Change the date on OS before starting the Software
    or
    Deinstalling the Software and installing SAP Netweaver (2004s) 7.0 SP9 SR 3 (which i downloaded this night). But i think i have to get the registry clean then. Are there Tools to clean the registry from all SAP entries?

  • GRC AC 5.3 Logging strategy in multi server nodes

    Hello Experts,
    We have GRC AC 5.3 SP6 and 5.2 10 landscapes and PRD system are running with multiple server nodes. SAP recomends to use SAP Logger instead of Java Logger in multi server environment, but i am not able to find out complete documentation on this.
    Can someone please give pointers on configuring GRC logging in NWA - which all Categories needs to be defined,etc,etc.
    And after this configuration, will we be able to see the logs of scheduled jobs with same details as shown in GRC --> Background Job -> View Logs.
    Thanks
    Davinder

    Hello Harleen,
    Thanks for your time. Here are my observations
    1. When we have created categories and then deinfed Logging and Tracing (with Severity level ALL) in NWA - these entries have also been reflected in Visual Administrator -> Log Configuration.
    2. We will have to restart SAP system after changing logging strategy from Java Logger to SAP Logger.
    3. After this change and restart, only upcoming new jobs scheduled/run will be displayed in NWA, jobs ran in the past will never be displayed in NWA.
    Severe Problems faced when checking logs through NWA:
    1. Logs through NWA are not at all readble as one entry is displayed in one row, whereas checking logs in RAR - VIew Logs was very convenient (similar to reading a text file).
    Is it possible to customize the display format of log files in NWA to something like text files,etc?
    2. When we try to donwload the logs from NWA, server produces huge dumps files of size in GBs (hpfa files which are memory dumps) - and before this download is completed - server crashes after around 15 minutes of starting log downloads - no free space availbale as everything has been taken by these memroy dumps (around 7GB).
    Any further pointers on handling GRC AC logs (multiple server nodes) in NWA would be highly appreciated.
    Thanks
    Davinder

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

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

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

  • NW2004sSP7_Preview J2EE Server error

    Hi,
    I am not able to start the J2ee server after install.
    Here is the trace file from the server.
    trc file: "C:\usr\sap\J2E\JC01\work\dev_server0", trc level: 1, release: "700"
    node name   : ID14203250
    pid         : 5668
    system name : J2E
    system nr.  : 01
    started at  : Sun May 14 14:24:29 2006
    arguments       :
           arg[00] : C:\usr\sap\J2E\JC01\exe\jlaunch.exe
           arg[01] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC01_TWCALA203437
           arg[02] : -DSAPINFO=J2E_01_server
           arg[03] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC01_TWCALA203437
    [Thr 5004] Sun May 14 14:24:29 2006
    [Thr 5004] *** WARNING => INFO: Unknown property [instance.box.number=J2EJC01twcala203437] [jstartxx.c   841]
    [Thr 5004] *** WARNING => INFO: Unknown property [instance.en.host=TWCALA203437] [jstartxx.c   841]
    [Thr 5004] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]
    [Thr 5004] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties]
    -> ms host    : TWCALA203437
    -> ms port    : 3900
    -> OS libs    : C:\usr\sap\J2E\JC01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : normal
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : C:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : TWCALA203437
    -> ms port    : 3900
    -> os libs    : C:\usr\sap\J2E\JC01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : normal
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : C:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID14203200 : C:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID14203250 : C:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID14203200           : C:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    -> [01] ID14203250           : C:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties
    [Thr 5004] Sun May 14 14:24:30 2006
    [Thr 5004] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 5004] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 4616] JLaunchRequestFunc: Thread 4616 started as listener thread for np messages.
    [Thr 5672] WaitSyncSemThread: Thread 5672 started as semaphore monitor thread.
    [Thr 5004] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 5004] CPIC (version=700.2005.12.02)
    [Thr 5004] JStartupIReadSection: debug mode is specified by program arguments
    [Thr 5004] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_09
    [Thr 5004] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\J2E\JC01\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID14203250]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> 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 -verbose:gc -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -XX:NewSize=170m -XX:MaxNewSize=170m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:DisableExplicitGC -XX:UseParNewGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
    -> 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          : 1023M
    -> init heap size     : 1023M
    -> root path          : C:\usr\sap\J2E\JC01\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : C:\usr\sap\J2E\JC01\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     : C:\usr\sap\J2E\JC01\exe\jstartup.jar;C:\usr\sap\J2E\JC01\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : yes
    -> debug mode         : yes
    -> debug port         : 50121
    -> shutdown timeout   : 120000
    [Thr 5004] JLaunchISetDebugMode: set debug mode [yes]
    [Thr 5696] JLaunchIStartFunc: Thread 5696 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 262144 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Denv.class.path=.;C:\Program Files\QuickTime\QTSystem\QTJava.zip;C:\j2sdk1.4.2_09\jre\lib;C:\Program Files\SAP\JDT\eclipse\plugins\org.apache.ant_1.5.3
    -> arg[  4]: -Djava.security.policy=./java.policy
    -> arg[  5]: -Djava.security.egd=file:/dev/urandom
    -> arg[  6]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  7]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  8]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  9]: -Djco.jarm=1
    -> arg[ 10]: -verbose:gc
    -> arg[ 11]: -Djava.awt.headless=true
    -> arg[ 12]: -Dsun.io.useCanonCaches=false
    -> arg[ 13]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 14]: -XX:NewSize=170m
    -> arg[ 15]: -XX:MaxNewSize=170m
    -> arg[ 16]: -XX:MaxPermSize=192m
    -> arg[ 17]: -XX:PermSize=192m
    -> arg[ 18]: -XX:+DisableExplicitGC
    -> arg[ 19]: -XX:+UseParNewGC
    -> arg[ 20]: -XX:+PrintGCDetails
    -> arg[ 21]: -XX:+PrintGCTimeStamps
    -> arg[ 22]: -XX:SurvivorRatio=2
    -> arg[ 23]: -XX:TargetSurvivorRatio=90
    -> arg[ 24]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 25]: -verbose:gc
    -> arg[ 26]: -Dsys.global.dir=C:\usr\sap\J2E\SYS\global
    -> arg[ 27]: -Dapplication.home=C:\usr\sap\J2E\JC01\exe
    -> arg[ 28]: -Djava.class.path=C:\usr\sap\J2E\JC01\exe\jstartup.jar;C:\usr\sap\J2E\JC01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 29]: -Djava.library.path=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;C:\j2sdk1.4.2_09\bin;C:\usr\sap\J2E\JC01\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\Program Files\ThinkPad\Utilities;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\QuickTime\QTSystem\;C:\j2sdk1.4.2_09\bin;C:\Program Files\Intel\Wireless\Bin\;C:\usr\sap\J2E\SYS\exe\uc\NTI386
    -> arg[ 30]: -Xdebug
    -> arg[ 31]: -Xnoagent
    -> arg[ 32]: -Djava.compiler=NONE
    -> arg[ 33]: -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=50121
    -> arg[ 34]: -Dmemory.manager=1023M
    -> arg[ 35]: -Xmx1023M
    -> arg[ 36]: -Xms1023M
    -> arg[ 37]: -DLoadBalanceRestricted=no
    -> arg[ 38]: -Djstartup.mode=JCONTROL
    -> arg[ 39]: -Djstartup.ownProcessId=5668
    -> arg[ 40]: -Djstartup.ownHardwareId=K0385668384
    -> arg[ 41]: -Djstartup.whoami=server
    -> arg[ 42]: -Djstartup.debuggable=yes
    -> arg[ 43]: -DSAPINFO=J2E_01_server
    -> arg[ 44]: -DSAPSTARTUP=1
    -> arg[ 45]: -DSAPSYSTEM=01
    -> arg[ 46]: -DSAPSYSTEMNAME=J2E
    -> arg[ 47]: -DSAPMYNAME=TWCALA203437_J2E_01
    -> arg[ 48]: -DSAPDBHOST=TWCALA203437
    -> arg[ 49]: -Dj2ee.dbhost=TWCALA203437
    Error occurred during initialization of VM
    Could not reserve enough space for object heap
    [Thr 5696] JLaunchIAbortJava: abort hook is called
    [Thr 5696] JLaunchCloseProgram: good bye (exitcode = -2)

    Hi,
    I have the same problem: the J2EE services do not start after installation,
    and reducing the heap size did not help!
    I have 3GB of RAM.
    This is my trace (please note the error code "exitcode = -11113"
    - what does it mean?):
    node name   : ID19941450
    pid         : 4944
    system name : X11
    system nr.  : 01
    started at  : Fri Jun 30 11:12:14 2006
    arguments       :
           arg[00] : C:\usr\sap\X11\DVEBMGS01\exe\jlaunch.exe
           arg[01] : pf=C:\usr\sap\X11\SYS\profile\X11_DVEBMGS01_testxi
           arg[02] : -DSAPINFO=X11_01_server
           arg[03] : pf=C:\usr\sap\X11\SYS\profile\X11_DVEBMGS01_testxi
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=1058
           arg[06] : -DSAPSYSTEM=01
           arg[07] : -DSAPSYSTEMNAME=X11
           arg[08] : -DSAPMYNAME=testxi_X11_01
           arg[09] : -DSAPPROFILE=C:\usr\sap\X11\SYS\profile\X11_DVEBMGS01_testxi
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 4948] Fri Jun 30 11:12:14 2006
    [Thr 4948] *** WARNING => INFO: Unknown property [instance.box.number=X11DVEBMGS01testxi] [jstartxx.c   841]
    [Thr 4948] *** WARNING => INFO: Unknown property [instance.en.host=testxi] [jstartxx.c   841]
    [Thr 4948] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]
    [Thr 4948] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [C:\usr\sap\X11\DVEBMGS01\j2ee\cluster\instance.properties]
    -> ms host    : testxi
    -> ms port    : 3900
    -> OS libs    : C:\usr\sap\X11\DVEBMGS01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : C:\usr\sap\X11\DVEBMGS01\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : testxi
    -> ms port    : 3900
    -> os libs    : C:\usr\sap\X11\DVEBMGS01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : C:\usr\sap\X11\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID19941400 : C:\usr\sap\X11\DVEBMGS01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID19941450 : C:\usr\sap\X11\DVEBMGS01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID19941400           : C:\usr\sap\X11\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] ID19941450           : C:\usr\sap\X11\DVEBMGS01\j2ee\cluster\instance.properties
    [Thr 4948] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 4948] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 4952] JLaunchRequestFunc: Thread 4952 started as listener thread for np messages.
    [Thr 4960] WaitSyncSemThread: Thread 4960 started as semaphore monitor thread.
    [Thr 4948] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 4948] CPIC (version=700.2005.12.02)
    [Thr 4948] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_12
    [Thr 4948] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\X11\DVEBMGS01\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID19941450]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\j2sdk1.4.2_12
    -> 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 -Dorg.xml.sax.driver=com.sap.engine.lib.xml.parser.SAXParser -Djco.jarm=1 -Dsun.io.useCanonCaches=false -XX:NewSize=170m -XX:MaxNewSize=170m -XX:MaxPermSize=256m -Djava.awt.headless=true -XX:PermSize=256m -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc -XX:DisableExplicitGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:UseParNewGC -Drdbms.driverLocation=C:/sapdb/programs/runtime/jar/sapdbc.jar
    -> java vm version    : 1.4.2_12-b03
    -> 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          : C:\usr\sap\X11\DVEBMGS01\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : C:\usr\sap\X11\DVEBMGS01\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     : C:\usr\sap\X11\DVEBMGS01\exe\jstartup.jar;C:\usr\sap\X11\DVEBMGS01\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50121
    -> shutdown timeout   : 120000
    [Thr 4948] JLaunchISetDebugMode: set debug mode [no]
    [Thr 4492] JLaunchIStartFunc: Thread 4492 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 262144 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -Dorg.xml.sax.driver=com.sap.engine.lib.xml.parser.SAXParser
    -> arg[  9]: -Djco.jarm=1
    -> arg[ 10]: -Dsun.io.useCanonCaches=false
    -> arg[ 11]: -XX:NewSize=170m
    -> arg[ 12]: -XX:MaxNewSize=170m
    -> arg[ 13]: -XX:MaxPermSize=256m
    -> arg[ 14]: -Djava.awt.headless=true
    -> arg[ 15]: -XX:PermSize=256m
    -> arg[ 16]: -XX:SurvivorRatio=2
    -> arg[ 17]: -XX:TargetSurvivorRatio=90
    -> arg[ 18]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 19]: -verbose:gc
    -> arg[ 20]: -XX:+DisableExplicitGC
    -> arg[ 21]: -XX:+PrintGCDetails
    -> arg[ 22]: -XX:+PrintGCTimeStamps
    -> arg[ 23]: -XX:+UseParNewGC
    -> arg[ 24]: -Drdbms.driverLocation=C:/sapdb/programs/runtime/jar/sapdbc.jar
    -> arg[ 25]: -Dsys.global.dir=C:\usr\sap\X11\SYS\global
    -> arg[ 26]: -Dapplication.home=C:\usr\sap\X11\DVEBMGS01\exe
    -> arg[ 27]: -Djava.class.path=C:\usr\sap\X11\DVEBMGS01\exe\jstartup.jar;C:\usr\sap\X11\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;C:\j2sdk1.4.2_12\bin;C:\usr\sap\X11\DVEBMGS01\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\usr\sap\X11\SYS\exe\uc\NTI386
    -> arg[ 29]: -Dmemory.manager=512M
    -> arg[ 30]: -Xmx512M
    -> arg[ 31]: -Xms512M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=4944
    -> arg[ 35]: -Djstartup.ownHardwareId=B0489370142
    -> arg[ 36]: -Djstartup.whoami=server
    -> arg[ 37]: -Djstartup.debuggable=no
    -> arg[ 38]: -DSAPINFO=X11_01_server
    -> arg[ 39]: -DSAPSTART=1
    -> arg[ 40]: -DCONNECT_PORT=1058
    -> arg[ 41]: -DSAPSYSTEM=01
    -> arg[ 42]: -DSAPSYSTEMNAME=X11
    -> arg[ 43]: -DSAPMYNAME=testxi_X11_01
    -> arg[ 44]: -DSAPPROFILE=C:\usr\sap\X11\SYS\profile\X11_DVEBMGS01_testxi
    -> arg[ 45]: -DFRFC_FALLBACK=ON
    -> arg[ 46]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 47]: -DSAPSTARTUP=1
    -> arg[ 48]: -DSAPSYSTEM=01
    -> arg[ 49]: -DSAPSYSTEMNAME=X11
    -> arg[ 50]: -DSAPMYNAME=testxi_X11_01
    -> arg[ 51]: -DSAPDBHOST=testxi
    -> arg[ 52]: -Dj2ee.dbhost=testxi
    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
    [Thr 4492] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 5028] Fri Jun 30 11:12:16 2006
    [Thr 5028] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 5028] Fri Jun 30 11:12:17 2006
    [Thr 5028] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 5028] JLaunchISetClusterId: set cluster id 19941450
    [Thr 5028] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 5028] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    Fri Jun 30 11:12:20 2006
    0.000: [GC 0.000: [ParNew: 87039K->2301K(130560K), 0.0361967 secs] 87039K->2301K(480768K), 0.0365311 secs]
    Fri Jun 30 11:12:30 2006
    10.462: [GC 10.462: [ParNew: 89341K->6046K(130560K), 0.0395094 secs] 89341K->6046K(480768K), 0.0396748 secs]
    Fri Jun 30 11:12:37 2006
    17.296: [GC 17.296: [ParNew: 93086K->12485K(130560K), 0.0808105 secs] 93086K->12485K(480768K), 0.0809729 secs]
    Fri Jun 30 11:12:46 2006
    26.032: [GC 26.032: [ParNew: 99524K->15336K(130560K), 0.0757925 secs] 99524K->15336K(480768K), 0.0759567 secs]
    [Thr 5372] Fri Jun 30 11:12:51 2006
    [Thr 5372] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 5372] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
    [Thr 5000] Fri Jun 30 11:12:52 2006
    [Thr 5000] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 5000] JLaunchCloseProgram: good bye (exitcode = -11113)

Maybe you are looking for