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

Similar Messages

  • 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

  • WDRuntimeException: Failed to create J2EE cluster node in SLD

    Hello,
    I am getting the below error, but to my knowledge I have everything set up properly.  Let me briefly outline the logistics (I am running everything LOCALLY (will move to remote later)):
    WAS 6.4 <b>SP12</b>
    Set up JCo and tests fine
    Set up Visual Administrator / SLD Data Supplier / HTTP and CIM configured and seem to test fine
    Created SLD and it tests OK
    Created Technical Landscape
    I have noticed that in SP12, in the SLD config I actually have a NEW category called "<b>System Landscape</b>" above my "Technical Landscape" link.  I have not seen this option in previous versions SP9 or SP11.  Is it mandatory to configure this?
    Also, I created a model for Adaptive RFC and found the function I needed successfully.
    Anyway, here is the error when trying to deploy...
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
    Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create J2EE cluster node in SLD for 'J2E.SystemHome.bc347792': com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND: No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="J2E.SystemHome.bc347792"
    Any help will be appreciated!

    I figured it out for those that may have a similar problem.
    Although I had created and tested my JCo's properly and they were working fine, somehow, and I still don't know why, they went RED in the JCo Maintainence screen. 
    I had to "create" again and it works fine now.

  • 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

  • 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

  • How many server nodes can you create per instance

    Hi,
    Very often the bottle neck in a java installation (NW04s) is the heap size. In order to increase the heap you simple create new server nodes.
    My question is:
    How many server nodes can you create per instance?
    Is there an upper limit before you have to create a new dialog instance (with a web dispatcher)?
    I can imagine that when you create a new server node you also have to increase the heap and max therad of the dispatcher. Is there any upper limit of the heap size of the dispatcher node ?

    Rasmus , I think you laid out a real good scenario for every one to contribute
    I may be very late but just updating this forum for benefit of everyone who visits this.
    In addition to all the points above one must also consider following things if one decides to add more server nodes to one dispatcher
    1.Garbage collection time
    2.Dispatcher would keep on sending request to node S2 if it is not completely bad and there by impacting all the servernode       so  you might end up restartiing the entire cluster.
    3,Debugging also becomes diffculy as you are not sure on which server node you are within the cluster.
    4.If you have something like F5 which does hear beat monitoring even one server node goes bad F5 will not report anything.
    So in my view one server node per dispatcher is an ideal configuration.
    Over All Dispatcher does not consume more resouces (Disk Space + CPU + memory ) at the same time it will give you maintenance flexibility.
    Nothing is right or wrong ,all these things are based on how your infrastructure set up is.
    Cheers !!
    Manish Jain

  • Java DC wrapped in J2EE Server Comp Library DC

    Hi Experts
    I have jxl.jar file, I imported this jar file in a Java DC and declared jxl.jar as public part. I created a Webdynpro DC and used the public part in it. I have created an application, component and a view in it using some classes of jxl.jar. I created a new J2EE Server Component Library DC and used the public part of jxl.jar in it again. Built the J2EE Server Component Library DC. Once done I got a .sda file. I deployed it in server. Once this is done, I have added the J2EE Server Component Library DC in my Webdynpro DC's Library Reference. Once I added this, i built it and deployed it. I got deployment finished with Warnings. Please see the exception below and Please advice.
    Exception from NWDS Deployment Screen
    "java.rmi.RemoteException: Error occurred while starting application wrigley.com/signauth/ui and wait. Reason: Clusterwide exception: server ID 6840450:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application wrigley.com/signauthui for startup. Reason=Clusterwide exception: Failed to start dependent library ''signauth/libraryimpl'' of application ''wrigley.com/signauthui''. Status of dependent component:  STATUS_MISSING. Hint: Is the component deployed correctly on the engine?"
    Names of the DCs used
    Webdynpro DC - signauth/ui
    J2EE Server Component DC - signauth/libraryimpl
    Java External Library DC - signauth/library
    FYI. I have created J2EE Server Component DC's name with more number of characters. Hope this shouldn't create issue. If this is also an issue, please let me know. I will reduce it and try.
    Thank you
    Best Regards
    Ramamoorthy D

    Hi Experts
    Kindly help me out in getting a solution for this problem.
    Thank you.
    Best Regards
    Ramamoorthy D

  • 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,

  • 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

  • Is it possible to create a two node cluster with SQL server 2012 STD on node1 and SQL Server 2008 ENT on node2 on a Windows server 2012?

    Hi All,
    Is it possible to create a two node cluster with SQL server 2012 STD on node1 and SQL Server 2008 ENT on node2 on a Windows server 2012?
    aa

    I think you are confused with the way cluster is installed. Installing SQL on cluster is a two step process. On first node you create a new SQL cluster and on second node you need "AddNode" action.
    Same edition media has to be used in above two operation.
    you can install two separate instances with one enterprise and one standard.
    Balmukund Lakhani
    Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
    This posting is provided "AS IS" with no warranties, and confers no rights.
    My Blog |
    Team Blog | @Twitter
    | Facebook
    Author: SQL Server 2012 AlwaysOn -
    Paperback, Kindle

  • Creating XI Roles for CMS and NWDI on seperate J2EE server

    We are going through the "How to Transport XI Content Using CMS" Guide.  We are runnning CMS and NWDI on a seperate J2EE server.
    It's not clear from the guide what we need to do on the J2EE side in terms of the user and roles.  The guide mostly details setting up CMS/NWDI on the same box as XI.  So we created the XIDIRUSER and XIREPUSER on the seperate J2EE server.  We add these users to the SAP_CMS_ADMISTRATOR role/group. 
    Questions -
    - Do we need to create any XI specific profiles/roles on the server - or is that applicable only to CMS running on the XI box?
    - Are there any things that we need to keep in mind that is not in the guide when we are setting this up.
    If you have a similar landscape (with CMS and NWDI) on a seperate server, I would like to know how you set this up.
    Thanks for your help.
    Jay Malla
    SAP XI Consultant
    Licensed To Code

    any progress?
    on your environment, have U installed DEV, CONS, PRD?
    i will be trying to set DEV and PRD, so i am not clear from guide weather it is possible or not.
    and do i register J2EE on JDI BOX to SLD on same box?
    or only register J2EE on JDI box to centeral SLD box via data supplier on J2EE engine on JDI box
    so here are some questions i am not clear;
    1. JDI server should be registered to SLD on same JDI BOX? or centeral SLD we are currently using?
    or both?
    2. according to Guide, they provide to make a domain or track DEV,CONS,PRD, but we will have DEV,PRD. so is it possible to configure CMS?
    thanks in advance

  • 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)

  • J2EE server not running. 503 service unavailable

    Hi ,
    J2EE Server is not starting. Rest all are running in mmc console.The contents of the file std_server0.out is as below.
    stdout/stderr redirect
    node name : server0
    pid : 584
    system name : J2E
    system nr. : 00
    started at : Tue Feb 15 10:12:46 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 iaik/security/md/SHA a
    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 87289.311 is starting...
    Loading: LogManager ... 1656 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 282 ms.
    Loading: ThreadManager ... 1360 ms.
    Loading: IpVerificationManager ... 47 ms.
    Loading: ClassLoaderManager ... 31 ms.
    Loading: ClusterManager ... 1047 ms.
    Loading: LockingManager ... 719 ms.
    Loading: ConfigurationManager ... 2093 ms.
    Loading: LicensingManager ... 125 ms.
    Loading: ServiceManager ...
    0.000: [GC 0.000: [ParNew: 43517K->2681K(65280K), 0.1899077 secs] 43517K->2681K(502528K), 0.1900163 secs]
    Loading services.:
    Service memory started. (125 ms).
    Service cross started. (125 ms).
    Service jmx_notification started. (110 ms).
    Service trex.service started. (140 ms).
    Service file started. (47 ms).
    Service runtimeinfo started. (0 ms).
    Service timeout started. (188 ms).
    Service userstore started. (16 ms).
    7.557: [GC 7.557: [ParNew: 46201K->4641K(65280K), 0.0511883 secs] 46201K->4641K(502528K), 0.0513121 secs]
    Service tcsecvsi~service started. (953 ms).
    Service tcsecwssec~service started. (1016 ms).
    Service p4 started. (578 ms).
    Service classpath_resolver started. (32 ms).
    Service deploy started. (5922 ms).
    14.157: [GC 14.157: [ParNew: 48161K->7636K(65280K), 0.0653829 secs] 48161K->7636K(502528K), 0.0655197 secs]
    Service apptracing started. (390 ms).
    Service log_configurator started. (11172 ms).
    Service locking started. (0 ms).
    Service http started. (563 ms).
    Service naming started. (765 ms).
    Service failover started. (94 ms).
    Service appclient started. (250 ms).
    Service ts started. (234 ms).
    Service javamail started. (282 ms).
    Service jmsconnector started. (282 ms).
    Service licensing started. (47 ms).
    Service connector started. (547 ms).
    Service configuration started. (250 ms).
    Service webservices started. (1234 ms).
    19.873: [GC 19.873: [ParNew: 51143K->8276K(65280K), 0.0746933 secs] 51143K->8276K(502528K), 0.0748063 secs]
    25.284: [GC 25.284: [ParNew: 51796K->8763K(65280K), 0.0613457 secs] 51796K->8763K(502528K), 0.0614361 secs]
    Service dbpool started. (6796 ms).
    Timed out services:
    Service ssl.
    Service tc.monitoring.logviewer.
    Service keystore.
    Service shell.
    Service prtbridge.
    Service webdynpro.
    Service com.sap.security.core.ume.service.
    Service pmi.
    Service tcsecsaml~service.
    Service sld.
    Service com.sap.portal.prt.sapj2ee.
    Service jms_provider.
    Service basicadmin.
    Service classload.
    Service adminadapter.
    Service telnet.
    Service servlet_jsp.
    Service ejb.
    Service dsr.
    Service monitor.
    Service tcsecdestinations~service.
    Service tcsecsecurestorage~service.
    Service security.
    Service applocking.
    Service jmx.
    Service DQE.
    Service tceCATTPingservice.
    Service rfcengine.
    ServiceManager started for 315217 ms.
    Framework started for 323623 ms.
    SAP J2EE Engine Version 6.40 PatchLevel 87289.311 is running!
    PatchLevel 87289.311 November 18, 2004 20:31 GMT
    608.267: [GC 608.268: [ParNew: 52274K->10357K(65280K), 0.1024975 secs] 52274K->10357K(502528K), 0.1026132 secs]
    Excluding compile: iaik.security.md.SHA::a
    The Developer Trace of J2EE Server is as below.
    trc file: "D:\usr\sap\J2E\JC00\work\dev_server0", trc level: 1, release: "640"
    node name : ID3718450
    pid : 3964
    system name : J2E
    system nr. : 00
    started at : Tue Feb 15 10:12:46 2005
    arguments :
    arg[00] : D:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    arg[01] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC00_igtehydsapweb
    arg[02] : -DSAPINFO=J2E_00_server
    arg[03] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC00_igtehydsapweb
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties]
    -> ms host : igtehydsapweb
    -> ms port : 3601
    -> OS libs : D:\usr\sap\J2E\JC00\j2ee\os_libs
    -> Admin URL :
    -> run mode : NORMAL
    -> run action : NONE
    -> enabled : yes
    Used property files
    -> files [00] : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host : igtehydsapweb
    -> ms port : 3601
    -> os libs : D:\usr\sap\J2E\JC00\j2ee\os_libs
    -> admin URL :
    -> run mode : NORMAL
    -> run action : NONE
    -> enabled : yes
    Bootstrap nodes
    -> [00] bootstrap : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID3718400 : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID3718450 : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID3718400 : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] ID3718450 : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    [Thr 4256] Tue Feb 15 10:12:46 2005
    [Thr 4256] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 4256] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 3328] JLaunchRequestFunc: Thread 3328 started as listener thread for np messages.
    [Thr 1800] WaitSyncSemThread: Thread 1800 started as semaphore monitor thread.
    [Thr 4256] Tue Feb 15 10:12:47 2005
    [Thr 4256] INFO: Invalid property value [JLaunchParameters/]
    [Thr 4256] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx512M [jstartxx.c 2282]
    [Thr 4256] [Node: server0] java home is set by profile parameter
    Java Home: D:\j2sdk1.4.2_07
    JStartupIReadSection: read node properties [ID3718450]
    -> node name : server0
    -> node type : server
    -> java path : D:\j2sdk1.4.2_07
    -> 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=D:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=D:/usr/sap/J2E/SYS/global/
    -> java vm version : 1.4.2_07-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 : D:\usr\sap\J2E\JC00\j2ee\cluster\server0
    -> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path : D:\usr\sap\J2E\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 : D:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> shutdown class : com.sap.engine.boot.Start
    -> parameters :
    -> debuggable : no
    -> debug mode : no
    -> debug port : 50021
    -> shutdown timeout: 120000
    [Thr 4256] JLaunchISetDebugMode: set debug mode [no]
    [Thr 1784] JLaunchIStartFunc: Thread 1784 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack : 262144 Bytes
    -> arg[ 0]: exit
    -> arg[ 1]: abort
    -> arg[ 2]: -Denv.class.path=D:\j2sdk1.4.2_07\%JAVA_HOME%\lib;
    -> 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]: -Djco.jarm=1
    -> arg[ 9]: -Dsun.io.useCanonCaches=false
    -> arg[ 10]: -Djava.awt.headless=true
    -> arg[ 11]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 12]: -verbose:gc
    -> arg[ 13]: -XX:+PrintGCDetails
    -> arg[ 14]: -XX:+PrintGCTimeStamps
    -> arg[ 15]: -XX:+UseParNewGC
    -> arg[ 16]: -XX:MaxNewSize=85M
    -> arg[ 17]: -XX:NewSize=85M
    -> arg[ 18]: -XX:+DisableExplicitGC
    -> arg[ 19]: -XX:MaxPermSize=192M
    -> arg[ 20]: -XX:PermSize=192M
    -> arg[ 21]: -XX:SurvivorRatio=2
    -> arg[ 22]: -XX:TargetSurvivorRatio=90
    -> arg[ 23]: -Drdbms.driverLocation=D:/sapdb/programs/runtime/jar/sapdbc.jar
    -> arg[ 24]: -Dsys.global.dir=D:/usr/sap/J2E/SYS/global/
    -> arg[ 25]: -Dsys.global.dir=D:\usr\sap\J2E\SYS\global
    -> arg[ 26]: -Dapplication.home=D:\usr\sap\J2E\JC00\j2ee\os_libs
    -> arg[ 27]: -Djava.class.path=D:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=D:\j2sdk1.4.2_07\jre\bin\server;D:\j2sdk1.4.2_07\jre\bin;D:\j2sdk1.4.2_07\bin;D:\usr\sap\J2E\JC00\j2ee\os_libs;D:\usr\sap\Python\.;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;D:\j2sdk1.4.2_07\bin;;D:\usr\sap\J2E\SCS01\exe;D:\usr\sap\J2E\JC00\exe;D:\usr\sap\J2E\SYS\exe\run
    -> arg[ 29]: -Dmemory.manager=512M
    -> arg[ 30]: -Xmx512M
    -> arg[ 31]: -Xms512M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=3964
    -> arg[ 35]: -Djstartup.ownHardwareId=W0450436801
    -> arg[ 36]: -Djstartup.whoami=server
    -> arg[ 37]: -Djstartup.debuggable=no
    -> arg[ 38]: -DSAPINFO=J2E_00_server
    -> arg[ 39]: -DSAPSTARTUP=1
    -> arg[ 40]: -DSAPSYSTEM=00
    -> arg[ 41]: -DSAPSYSTEMNAME=J2E
    -> arg[ 42]: -DSAPMYNAME=igtehydsapweb_J2E_00
    -> arg[ 43]: -DSAPDBHOST=
    -> arg[ 44]: -Dj2ee.dbhost=igtehydsapweb
    [Thr 1784] Tue Feb 15 10:12:48 2005
    [Thr 1784] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 3104] Tue Feb 15 10:12:56 2005
    [Thr 3104] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 3104] JLaunchISetClusterId: set cluster id 3718450
    [Thr 3104] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 3104] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 3104] Tue Feb 15 10:18:15 2005
    [Thr 3104] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
    please do the needful.
    regards,
    sreeram

    Hi Sreeram,
    The reasons for this issue can be numerous and most of them will be present in the default trace in
    /usr/sap/<SID>/JC<instance-nr>/j2ee/cluster/server<0..N>/log
    It would be best to report an OSS message and let the support find the problem for you.
    Best Regards: Iavor

Maybe you are looking for