J2ee  - Restarting specific server process

hi,
We have Central instance with 3 j2ee server processes running. One of the server process has issues, needs restart . I tried with SMICM and JCMON to restart only a specific server process. I could not try all options in production instance. Is it possible to restart only affected server process instead of entire j2ee server.?
This is needed as users may be using other 2 server processes anytime.
Visual admin does not show, this server process as it has issues.
Thanks,
Raj

Hi Raj,
You could restart a server process with JCMON.
Choose local instance and then choose restart a process and enter the id of the server node that you want to restart.
Regards,
Ventsi Tsachev

Similar Messages

  • Directing requests to a particular server process

    Hi
    If I have two Server process connected to a single Java dispacther how can I force my web dynpro application to be run from one or the other .
    I am aware that the J2EE Engine uses cookies to register a request with a particular server process and thus by which dedicate all requests with specific cookie information to specific server processes.
    Is there a way to provide dispatcher+server instance details in a URL and thus forcing a particular server process to service this request.
    Regards
    Pran

    Hi,
    Sorry to say but all servers which are member of same RD Farm name are expected to have access of all application installed. We cannot control which specific server in a RD Farm a user is directed to. Still we can configure RemoteApp under RDSH server and assign
    the user to connect to the specific RemoteApp by assigning RemoteApp User Assignment.
    By this way, suppose we install WordPad as RemoteApp on RDSH server 1 and Notepad as RemoteApp on RDSH server 2 then provide the access to the specific user to access that RemoteApp under user assignment and don’t allow under other App so that specific user
    can only access the assigned RemoteApp.
    Anyway for redirection of server is managed by RDCB and there are different ways now to handle such as DNS RR, NLB, Hardware Load balancer or Dedicated Farm redirection and it depends on you what you prefer for your environment.
    More detail.
    Introducing RemoteApp User Assignment
    http://blogs.msdn.com/b/rds/archive/2009/06/12/introducing-remoteapp-user-assignment.aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Error calling a webservice from one server process of the cluster

    Hi ,
    I have a servlet which on startup makes a call to a webservice. I deploy this webapp on the cluster.
    The cluster has two instances each instance having one server process.
    So when the server restarts one server process on one instance calls the web service the other process on other instance fails with a 503 response code.
    When I tried to reproduce the same problem using two server processes on the same instance both processes are able to call the webservice properly.
    I am slightly confused as to how different the second scenario is from first one as both are individual server process and may or may not run on same instance.
    Can anyone tell me the real cause.
    Rgds
    Shashank

    Hi Rajat,
    This is how the default trace looks
    FATAL: Application Servlet failed to notify devices.
    Caught java.rmi.RemoteException: Service call exception; nested exception is:
         com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (503) Service Unavailable. The requested URL was:"http://<<server>>:50000/ManagementService/ManagementService?style=document"
         at com.om.mws.standaloneproxy.ManagementServiceBindingStub.notifyDevice(ManagementServiceBindingStub.java:1289)
         at com.om.mws.standaloneproxy.ManagementServiceBindingStub.notifyDevice(ManagementServiceBindingStub.java:1298)
         at com.om.ApplicationServlet$NotifyDevices.run(ApplicationServlet.java:86)
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (503) Service Unavailable. The requested URL was:"http://<<server>>:50000/ManagementService/ManagementService?style=document"
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:980)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1430)
         at com.om.mws.standaloneproxy.ManagementServiceBindingStub.notifyDevice(ManagementServiceBindingStub.java:1282)
         ... 2 more
    java.lang.NoSuchMethodError
    at java.lang.Thread.destroy(Thread.java:779)
         at com.omApplicationServlet$NotifyDevices.run(ApplicationServlet.java:92)
    Rgds
    Shashank

  • J2EE Server Process is restarted automatically?

    Hi,
    On one of our systems we have seen that one J2EE server process was taking up nearly 100% CPU, after a few hours suddenly the process seemed to restart itself. I am guessing that maybe JControl Framework restarted it since it was chewing up so much CPU, but can't find any documentation regarding if JControl can do this and if it logs anything to say it did an automatic restart. Can anyone clear this up?
    Thanks in advance,
    Simon

    Hi Simon
    Look at sap note 742395 might help u.
    regards,
    kaushal

  • Restarting App server and Process Scheduler

    Hi all,
    Can any body send me the document on how to Restart App server and Process Scheduler.
    Thanks In Advance
    Karthik

    Use the psadmin utility under $PS_HOME/appserv.
    https://peoplebooks.uta.edu/PSOL/pt846books/eng/psbooks/tsvt/chapter.htm?File=tsvt/htm/tsvt03.htm%23H3005
    Nicolas.

  • Do we need to restart admin server evertime we restart slapd process

    Hi all !
    For system stability Do we need to restart admin server evertime we restart slapd process ?
    -

    Recently i had some core dump file on my /var/core directory which is actually filling out the filesystem.
    When i send core dump file to sun support they told there is a bug in Directory server BUG ID 4992815.
    But to fix the core dump every time need to restart slapd process i need to restart the admin server.
    It seems strange to me ...but if its how i can fix the dump then i need to follow thier instruction...
    Just curious whether other people also following the same ...
    Thank you for your response....

  • DTR server and J2EE restart

    Our J2EE server is not starting due to following error :
    Severe error in network I/O of centralserver. Please restart DTR server application. If the problem occurs again, please refer to SAP note 774339 for more details on how to analyse the error condition
    we want to restart DTR server.
    since J2ee engine is not started, we are not able to logon to Visual Admin.
    can anyone tell me about any other way to restart the DTR server.
    or
    else how to start j2ee engine for above error.
    appropriate points will be awarded.
    thanks and regards,
    Aditya Deshpande

    Double post: DTR server problem
    Please continue in the other thread.

  • JCO_SYSTEM_FAILURE   and J2EE restart

    Hi All,
    We are currently encountering an issue with IDOC to HTTPS scenario that we we are working on. There are several RFC that are being performed in the mapping to retrieve information from R/3. The mapping has been tested sufficently with data from R/3 DEV system without any issues.
    We have the scenario tested in DEV, and its works fine. But when we test the same onjects connected to REL r/3 system, we are noticing that the messages always get stuck in the outbound queue with the status as "transaction executing". After a while the below message is logged:
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
      <SAP:P1>Bean SMPP_CALL_JAVA_RUNTIME3 not found on host albbir1, ProgId=AI_RUNTIME_BIR: P</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>&quot;SYSTEM FAILURE&quot; during JCo call. Bean SMPP_CALL_JAVA_RUNTIME3 not found on host albbir1, ProgId=AI_RUNTIME_BIR: P</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
      There seems to be an issue with RFC communication, but we can't seem to find the problem. This above error is logged a number of time, after which the J2ee server process will either restart or stop. We have been manually restarting the J2ee server and the cancelling the message with errors.
    We have tested the TCP RFC Destination AI_RUNTIME_JCOSERVER, it works fine, before the mesages get stuck.

    Hi Harleen,
    This kind of issue occurs for many cases.
    First of all, if there is a server restart(in specific the java stack) and during that time, if any synchronous interface was in execution it would fail with this error.
    Since, it is a HTTP adapter at the receiver side, it can also occur if the connection is down at the receiver side.
    Because of an untimed restart of a server node/cluster, async interfaces could also fail with this error.
    As of now to clear that issue, you can save the payload and delete the blocked message from the queue and check if other messages are getting processeed on not.
    Check if the connections to target system are working fine.
    Regards,
    Younus

  • Server Process  is not running in the  WAS  JAVA

    Hi,
    The WAS JAVA  have the resources Netweaver7.0 and java is j2sdk1.4.2_13 version Operating system is Windows2003 and database server is SQLserver2005.
    Previously it was running properly Now it giving the following Error.
    Any one of you please give me suggestions how to solve it .
    Devolper trace for the jcontol.exe process is as follows
    trc file: "D:\usr\sap\NW2\JC02\work\dev_jcontrol", trc level: 1, release: "700"
    node name   : jcontrol
    pid         : 4516
    system name : NW2
    system nr.  : 02
    started at  : Mon Mar 24 17:07:20 2008
    arguments       :
           arg[00] : D:\usr\sap\NW2\JC02\exe\jcontrol.EXE
           arg[01] : pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    [Thr 4512] Mon Mar 24 17:07:20 2008
    [Thr 4512] *** WARNING => INFO: Unknown property [instance.box.number=NW2JC02mmsr17] [jstartxx.c   841]
    [Thr 4512] *** WARNING => INFO: Unknown property [instance.en.host=mmsr17] [jstartxx.c   841]
    [Thr 4512] *** WARNING => INFO: Unknown property [instance.en.port=3203] [jstartxx.c   841]
    [Thr 4512] *** WARNING => INFO: Unknown property [instance.system.id=2] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties;D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties]
    -> ms host    : mmsr17
    -> ms port    : 3903
    -> OS libs    : D:\usr\sap\NW2\JC02\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> files [01] : D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
    Instance properties
    -> ms host    : mmsr17
    -> ms port    : 3903
    -> os libs    : D:\usr\sap\NW2\JC02\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID28653700 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID28653750 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID28653700           : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> [01] ID28653750           : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> [02] sdm                  : D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
    [Thr 4512] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
    [Thr 4512] [Node: bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_13
    [Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
    JStartupIReadSection: read node properties [bootstrap]
    -> node name          : bootstrap
    -> node type          : bootstrap
    -> node execute       : yes
    -> java path          : C:\j2sdk1.4.2_13
    -> java parameters    : -Djco.jarm=1
    -> java vm version    : 1.4.2_13-b06
    -> 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\NW2\JC02\j2ee\cluster
    -> class path         : .\bootstrap\launcher.jar
    -> OS libs path       : D:\usr\sap\NW2\JC02\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\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
    -> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0286537
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 60000
    -> shutdown timeout   : 120000
    JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> arg[02] = -DSAPINFO=NW2_02_bootstrap
    -> arg[03] = -nodeId=-1
    -> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
    -> arg[06] = -nodeName=bootstrap
    -> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_bootstrap.out
    -> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_bootstrap.out
    -> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_bootstrap
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    [Thr 4512] Mon Mar 24 17:07:20 2008
    [Thr 4512] JControlExecuteBootstrap: read instance values after global bootstrap
    [Thr 4512] *** WARNING => INFO: Unknown property [instance.box.number=NW2JC02mmsr17] [jstartxx.c   841]
    [Thr 4512] *** WARNING => INFO: Unknown property [instance.en.host=mmsr17] [jstartxx.c   841]
    [Thr 4512] *** WARNING => INFO: Unknown property [instance.en.port=3203] [jstartxx.c   841]
    [Thr 4512] *** WARNING => INFO: Unknown property [instance.system.id=2] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties;D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties]
    -> ms host    : mmsr17
    -> ms port    : 3903
    -> OS libs    : D:\usr\sap\NW2\JC02\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    [Thr 4512] JControlExecuteBootstrap: enumerate the nodes after global bootstrap
    Used property files
    -> files [00] : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> files [01] : D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
    Instance properties
    -> ms host    : mmsr17
    -> ms port    : 3903
    -> os libs    : D:\usr\sap\NW2\JC02\j2ee\os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID28653700 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID28653750 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID28653700           : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> [01] ID28653750           : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> [02] sdm                  : D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
    [Thr 4512] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID28653700]
    [Thr 4512] [Node: dispatcher bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_13
    [Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
    JStartupIReadSection: read node properties [bootstrap_ID28653700]
    -> node name          : dispatcher bootstrap
    -> node type          : bootstrap
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\j2sdk1.4.2_13
    -> java parameters    : -Djco.jarm=1
    -> java vm version    : 1.4.2_13-b06
    -> 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\NW2\JC02\j2ee\cluster
    -> class path         : .\bootstrap\launcher.jar
    -> OS libs path       : D:\usr\sap\NW2\JC02\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\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
    -> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID028653700
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 60000
    -> shutdown timeout   : 120000
    JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> arg[02] = -DSAPINFO=NW2_02_bootstrap
    -> arg[03] = -nodeId=-1
    -> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
    -> arg[06] = -nodeName=bootstrap_ID28653700
    -> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_bootstrap_ID28653700.out
    -> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_bootstrap_ID28653700.out
    -> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_bootstrap_ID28653700
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    [Thr 4512] Mon Mar 24 17:07:20 2008
    [Thr 4512] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID28653750]
    [Thr 4512] [Node: server0 bootstrap] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_13
    [Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
    JStartupIReadSection: read node properties [bootstrap_ID28653750]
    -> node name          : server0 bootstrap
    -> node type          : bootstrap
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\j2sdk1.4.2_13
    -> java parameters    : -Djco.jarm=1
    -> java vm version    : 1.4.2_13-b06
    -> 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\NW2\JC02\j2ee\cluster
    -> class path         : .\bootstrap\launcher.jar
    -> OS libs path       : D:\usr\sap\NW2\JC02\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\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
    -> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID028653750
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 60000
    -> shutdown timeout   : 120000
    JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> arg[02] = -DSAPINFO=NW2_02_bootstrap
    -> arg[03] = -nodeId=-1
    -> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
    -> arg[06] = -nodeName=bootstrap_ID28653750
    -> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_bootstrap_ID28653750.out
    -> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_bootstrap_ID28653750.out
    -> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_bootstrap_ID28653750
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    [Thr 4512] Mon Mar 24 17:07:20 2008
    [Thr 4512] JControlIBuildProcessList: Maximum error count is set to 4
    [Thr 5144] JControlRequestFunc: Thread 5144 started as listener thread for np messages.
    [Thr 4512] [Node: dispatcher] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_13
    [Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID28653700]
    -> node name          : dispatcher
    -> node type          : dispatcher
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\j2sdk1.4.2_13
    -> 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 -XX:NewSize=57m -XX:MaxNewSize=57m -XX:NewRatio=3 -XX:DisableExplicitGC -verbose:gc -XX:UseConcMarkSweepGC
    -> java vm version    : 1.4.2_13-b06
    -> 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\NW2\JC02\j2ee\cluster\dispatcher
    -> class path         : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : D:\usr\sap\NW2\JC02\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\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 60000
    -> shutdown timeout   : 120000
    [Thr 4512] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_13
    [Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID28653750]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\j2sdk1.4.2_13
    -> 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 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> java vm version    : 1.4.2_13-b06
    -> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : x86
    -> heap size          : 1024M
    -> init heap size     : 1024M
    -> root path          : D:\usr\sap\NW2\JC02\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : D:\usr\sap\NW2\JC02\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\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
    -> parameters         :
    -> debuggable         : yes
    -> debug mode         : yes
    -> debug port         : 50221
    -> shutdown timeout   : 120000
    [Thr 4512] INFO: Invalid property value [Debbugable=yes]
    [Thr 4512] [Node: SDM] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_13
    [Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
    JStartupIReadSection: read node properties [sdm]
    -> node name          : SDM
    -> node type          : sdm
    -> node execute       : yes
    -> java path          : C:\j2sdk1.4.2_13
    -> java parameters    :
    -> java vm version    : 1.4.2_13-b06
    -> 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\NW2\JC02\SDM\program
    -> class path         : D:\usr\sap\NW2\JC02\SDM\program\bin\SDM.jar
    -> OS libs path       : D:\usr\sap\NW2\JC02\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\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
    -> shutdown class     : com.sap.sdm.jstartup.shutdown.InternalShutDown
    -> parameters         : server sdmhome=D:\usr\sap\NW2\JC02\SDM\program
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 60000
    -> shutdown timeout   : 120000
    [Thr 4512] JControlMSConnect: attached to message server (mmsr17/3903)
    [Thr 5340] JControlMSMessageFunc: Thread 5340 started as listener thread for ms messages.
    JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> arg[02] = -DSAPINFO=NW2_02_dispatcher
    -> arg[03] = -nodeId=0
    -> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
    -> arg[06] = -nodeName=ID28653700
    -> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_dispatcher.out
    -> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_dispatcher.out
    -> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_dispatcher
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    [Thr 4512] JControlICheckProcessList: process dispatcher started (PID:5444)
    JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> arg[02] = -DSAPINFO=NW2_02_server
    -> arg[03] = -nodeId=1
    -> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
    -> arg[06] = -nodeName=ID28653750
    -> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
    -> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
    -> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = -debugMode=yes
    -> arg[12] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    [Thr 4512] JControlICheckProcessList: process server0 started (PID:4684)
    JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> arg[02] = -DSAPINFO=NW2_02_sdm
    -> arg[03] = -nodeId=2
    -> arg[04] = -file=D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
    -> arg[06] = -nodeName=sdm
    -> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_sdm.out
    -> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_sdm.out
    -> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_sdm
    -> arg[10] = -mode=JCONTROL
    -> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    [Thr 4512] JControlICheckProcessList: process SDM started (PID:5472)
    [Thr 4512] JControlMSSendLogon: delete SDM logon information (rc=0)
    [Thr 4512] Mon Mar 24 17:07:20 2008
    [Thr 4512] JControlMSSendLogon: insert SDM logon information (port=50218; rc=0)
    [Thr 4512] Mon Mar 24 17:07:20 2008
    [Thr 4512] JControlICheckProcessList: process server0 (pid:4684) died (RUN-FLAG)
    [Thr 4512] JControlIResetProcess: reset process server0
    [Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (1)
    [Thr 4512] JControlICheckProcessList: running flight recorder:
         C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856249 -bz D:\usr\sap\NW2\SYS\global
    JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> arg[02] = -DSAPINFO=NW2_02_server
    -> arg[03] = -nodeId=1
    -> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
    -> arg[06] = -nodeName=ID28653750
    -> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
    -> arg[08] = -jvmOutMode=append
    -> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
    -> arg[10] = -stdOutMode=append
    -> arg[11] = -traceMode=append
    -> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
    -> arg[13] = -mode=JCONTROL
    -> arg[14] = -debugMode=yes
    -> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    [Thr 4512] JControlICheckProcessList: process server0 started (PID:3944)
    [Thr 4512] Mon Mar 24 17:07:20 2008
    [Thr 4512] JControlICheckProcessList: process server0 (pid:3944) died (RUN-FLAG)
    [Thr 4512] JControlIResetProcess: reset process server0
    [Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (2)
    [Thr 4512] JControlICheckProcessList: running flight recorder:
         C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856314 -bz D:\usr\sap\NW2\SYS\global
    JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> arg[02] = -DSAPINFO=NW2_02_server
    -> arg[03] = -nodeId=1
    -> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
    -> arg[06] = -nodeName=ID28653750
    -> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
    -> arg[08] = -jvmOutMode=append
    -> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
    -> arg[10] = -stdOutMode=append
    -> arg[11] = -traceMode=append
    -> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
    -> arg[13] = -mode=JCONTROL
    -> arg[14] = -debugMode=yes
    -> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    [Thr 4512] Mon Mar 24 17:07:20 2008
    [Thr 4512] JControlICheckProcessList: process server0 started (PID:4308)
    [Thr 4512]  Mon Mar 24 17:07:20 2008
    [Thr 4512] JControlICheckProcessList: process server0 (pid:4308) died (RUN-FLAG)
    [Thr 4512] JControlIResetProcess: reset process server0
    [Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (3)
    [Thr 4512] JControlICheckProcessList: running flight recorder:
         C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856350 -bz D:\usr\sap\NW2\SYS\global
    JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> arg[02] = -DSAPINFO=NW2_02_server
    -> arg[03] = -nodeId=1
    -> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
    -> arg[06] = -nodeName=ID28653750
    -> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
    -> arg[08] = -jvmOutMode=append
    -> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
    -> arg[10] = -stdOutMode=append
    -> arg[11] = -traceMode=append
    -> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
    -> arg[13] = -mode=JCONTROL
    -> arg[14] = -debugMode=yes
    -> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    [Thr 4512] JControlICheckProcessList: process server0 started (PID:2616)
    [Thr 4512] Mon Mar 24 17:07:20 2008
    [Thr 4512] JControlICheckProcessList: process server0 (pid:2616) died (RUN-FLAG)
    [Thr 4512] JControlIResetProcess: reset process server0
    [Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (4)
    [Thr 4512] JControlICheckProcessList: running flight recorder:
         C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856405 -bz D:\usr\sap\NW2\SYS\global
    [Thr 5144] Mon Mar 24 17:07:20 2008
    [Thr 5144] JControlRequestFunc: receive command:10, argument:1 from pid:0
    [Thr 5144] JControlIDumpStackTrace: dump stacktrace for server0
    [Thr 5144] *** ERROR => Can't send command for stack dump (rc=-3) [jcntrxxi.c   1403]
    [Thr 5144] Mon Mar 24 17:07:20 2008
    [Thr 5144] JControlRequestFunc: receive command:19, argument:1 from pid:0
    [Thr 5144] JControlITraceIncrement: increment trace level for server0
    [Thr 5144] *** ERROR => Can't send command for trace level increment (rc=-3) [jcntrxxi.c   1434]
    [Thr 5144] Mon Mar 24 17:07:20 2008
    [Thr 5144] JControlRequestFunc: receive command:4, argument:1 from pid:0
    [Thr 5144] JControlIEnableProcess: enable process server0
    JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> arg[02] = -DSAPINFO=NW2_02_server
    -> arg[03] = -nodeId=1
    -> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
    -> arg[06] = -nodeName=ID28653750
    -> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
    -> arg[08] = -jvmOutMode=append
    -> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
    -> arg[10] = -stdOutMode=append
    -> arg[11] = -traceMode=append
    -> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
    -> arg[13] = -mode=JCONTROL
    -> arg[14] = -debugMode=yes
    -> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    [Thr 4512] JControlICheckProcessList: process server0 started (PID:3556)
    [Thr 4512] Mon Mar 24 17:07:20 2008
    [Thr 4512] JControlICheckProcessList: process server0 (pid:3556) died (RUN-FLAG)
    [Thr 4512] JControlIResetProcess: reset process server0
    [Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (5)
    [Thr 4512] JControlICheckProcessList: running flight recorder:
         C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856490 -bz D:\usr\sap\NW2\SYS\global
    [Thr 5144] Mon Mar 24 17:07:20 2008
    [Thr 5144] JControlRequestFunc: receive command:4, argument:1 from pid:0
    [Thr 5144] JControlIEnableProcess: enable process server0
    JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> arg[02] = -DSAPINFO=NW2_02_server
    -> arg[03] = -nodeId=1
    -> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
    -> arg[06] = -nodeName=ID28653750
    -> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
    -> arg[08] = -jvmOutMode=append
    -> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
    -> arg[10] = -stdOutMode=append
    -> arg[11] = -traceMode=append
    -> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
    -> arg[13] = -mode=JCONTROL
    -> arg[14] = -debugMode=yes
    -> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    [Thr 4512] JControlICheckProcessList: process server0 started (PID:2872)
    [Thr 4512] Mon Mar 24 17:07:20 2008
    [Thr 4512] JControlICheckProcessList: process server0 (pid:2872) died (RUN-FLAG)
    [Thr 4512] JControlIResetProcess: reset process server0
    [Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (6)
    [Thr 4512] JControlICheckProcessList: running flight recorder:
         C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189858000 -bz D:\usr\sap\NW2\SYS\global
    [Thr 5144] Mon Mar 24 17:07:20 2008
    [Thr 5144] JControlRequestFunc: receive command:10, argument:1 from pid:0
    [Thr 5144] JControlIDumpStackTrace: dump stacktrace for server0
    [Thr 5144] *** ERROR => Can't send command for stack dump (rc=-3) [jcntrxxi.c   1403]
    [Thr 5144] Mon Mar 24 17:07:20 2008
    [Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
    [Thr 5144] JControlIDisableDebugging: disable debugging server0
    [Thr 5144] JControlIEnableProcess: restart process server0
    [Thr 5144] Mon Mar 24 17:07:20 2008
    [Thr 5144] JControlRequestFunc: receive command:4, argument:1 from pid:0
    [Thr 5144] JControlIEnableProcess: enable process server0
    JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> arg[02] = -DSAPINFO=NW2_02_server
    -> arg[03] = -nodeId=1
    -> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
    -> arg[06] = -nodeName=ID28653750
    -> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
    -> arg[08] = -jvmOutMode=append
    -> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
    -> arg[10] = -stdOutMode=append
    -> arg[11] = -traceMode=append
    -> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
    -> arg[13] = -mode=JCONTROL
    -> arg[14] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    [Thr 4512] JControlICheckProcessList: process server0 started (PID:4836)
    [Thr 5144] Mon Mar 24 17:07:20 2008
    [Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
    [Thr 5144] JControlIDisableDebugging: disable debugging server0
    [Thr 5144] JControlIEnableProcess: restart process server0
    [Thr 5144] JControlIProcessSoftKill: soft kill of process server0 (pid:4836)
    [Thr 5144] Mon Mar 24 17:07:20 2008
    [Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
    [Thr 5144] JControlIDisableDebugging: disable debugging server0
    [Thr 5144] JControlIEnableProcess: restart process server0
    [Thr 5144] Mon Mar 24 17:07:20 2008
    [Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
    [Thr 5144] JControlIDisableDebugging: disable debugging server0
    [Thr 5144] JControlIEnableProcess: restart process server0
    [Thr 4512] Mon Mar 24 17:07:20 2008
    [Thr 4512] JControlICheckProcessList: process server0 (pid:4836) died (STOPPING)
    [Thr 4512] JControlIResetProcess: reset process server0
    JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> arg[02] = -DSAPINFO=NW2_02_server
    -> arg[03] = -nodeId=1
    -> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
    -> arg[06] = -nodeName=ID28653750
    -> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
    -> arg[08] = -jvmOutMode=append
    -> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
    -> arg[10] = -stdOutMode=append
    -> arg[11] = -traceMode=append
    -> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
    -> arg[13] = -mode=JCONTROL
    -> arg[14] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    [Thr 4512] JControlICheckProcessList: process server0 started (PID:5428)
    [Thr 4512] Mon Mar 24 17:07:20 2008
    [Thr 4512] JControlICheckProcessList: process server0 (pid:5428) died (RUN-FLAG)
    [Thr 4512] JControlIResetProcess: reset process server0
    [Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (7)
    [Thr 4512] JControlICheckProcessList: running flight recorder:
         C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189860005 -bz D:\usr\sap\NW2\SYS\global
    [Thr 5144] Mon Mar 24 17:07:20 2008
    [Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
    [Thr 5144] JControlIDisableDebugging: disable debugging server0
    [Thr 5144] JControlIEnableProcess: restart process server0
    [Thr 5144] Mon Mar 24 17:07:20 2008
    [Thr 5144] JControlRequestFunc: receive command:4, argument:1 from pid:0
    [Thr 5144] JControlIEnableProcess: enable process server0
    JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> arg[02] = -DSAPINFO=NW2_02_server
    -> arg[03] = -nodeId=1
    -> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
    -> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
    -> arg[06] = -nodeName=ID28653750
    -> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
    -> arg[08] = -jvmOutMode=append
    -> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
    -> arg[10] = -stdOutMode=append
    -> arg[11] = -traceMode=append
    -> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
    -> arg[13] = -mode=JCONTROL
    -> arg[14] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
    -> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
    [Thr 4512] JControlICheckProcessList: process server0 started (PID:5196)
    [Thr 4512] Mon Mar 24 17:07:20 2008
    [Thr 4512] JControlICheckProcessList: process server0 (pid:5196) died (RUN-FLAG)
    [Thr 4512] JControlIResetProcess: reset process server0
    [Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (8)
    [Thr 4512] JControlICheckProcessList: running flight recorder:
         C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189860117 -bz D:\usr\sap\NW2\SYS\global
    [Thr 5144] Mon Mar 24 17:07:20 2008
    [Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
    [Thr 5144] JControlIDisableDebugging: disable debugging server0
    [Thr 5144] JControlIEnableProcess: restart process server0
    [Thr 5144] Mon Mar 24 17:07:20 2008
    [Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
    [Thr 5144] JControlIDisableDebugging: disable debugging server0
    [Thr 5144] JControlIEnableProcess: restart process server0
    Thanks,
    Vivek

    Hi Vivek,
    FYI :
    JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
    The above message can be ignored. You will see that message often in perfectly up/running systems as well.
    Also, the dev_jcontrol file shows that the server process was terminating !
    You need to check std_server0.out file for the errors/exceptions as to why server0 was terminating abruptly. The reason should be apparent from dev_server0 and std_server0 most of the times unless its a startup framework bug where the error messages are not written to the log files.
    So, whenever the server process or dispatcher process fails to start, you should check the corresponding dev_server<n> or dev_dispatcher and std_server<n> / std_dispatcher  files. Also, usually, there will be some exception (if its application related) in the defaultrace file as well under server<n>\log or dispatcher\log depending on which one is failing to start.
    e.g. if server0 is failing to start due to some UME issues, you will see the mention of it in std_server0.out (definitely) and more ellaborate info/exceptions in deafultrace under server0\log as well.
    Hope the above helps.

  • [J2EE:160149]Error while processing library references

    Hi,
    I have an application which was working 9.2.1. I have deployed this application to 9.2.3. I have modified weblogic-application.xml, but it is giving these erros:
    An error occurred during activation of changes, please see the log for details.
    [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml:
    [Extension-Name: beehive-controls-1.0, Specification-Version: 1, Implementation-Version: 1.0, exact-match: false],
    [Extension-Name: wls-commonslogging-bridge, Specification-Version: 1, Implementation-Version: 1.0, exact-match: false],
    [Extension-Name: weblogic-controls-1.0, Specification-Version: 1, Implementation-Version: 1.0, exact-match: false],
    [Extension-Name: wlp-tools-support-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.3, exact-match: false],
    [Extension-Name: wlp-webdav-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.3, exact-match: false],
    [Extension-Name: wlp-services-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.3, exact-match: false],
    [Extension-Name: p13n-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.3, exact-match: false].
    How can I resolve these errors?

    Hi,
    Weblogic Server has two clusters and admin server. The referenced libraries didnt targeted to admin server. Because of that it was giving these errors. I have targeted to admin server all referenced libraries and I have deployed it.
    But,
    When I say start my application, I am taking this error:
    [EJB:010127]Incorrect DataSource type detected.
    The DataSource with JNDI name 'weblogic.jdbc.jts.commercePool',
    specified in the RDBMS deployment descriptor for the EJB 'TrackedAnonymous'
    does not support global transactions. The EJB container requires a DataSource
    that supports global transactions to be specified for transactions to be managed correctly.
    Errors were encountered while performing this operation
    [EJB:010127]Incorrect DataSource type detected. The DataSource with JNDI name 'weblogic.jdbc.jts.commercePool', specified in the RDBMS deployment descriptor for the EJB 'TrackedAnonymous' does not support global transactions. The EJB container requires a DataSource that supports global transactions to be specified for transactions to be managed correctly.
    Here are my data sources:
    cgDataSource
    cgDataSource-nonXA
    DSFDS
    IXPOC9DATASOURCE
    NDSDataSource
    p13nDataSource
    portalDataSource
    portalDataSourceAlwaysXA
    portalDataSourceNeverXA
    samplesDataSource
    All of these datasources targeted to NDSCluster, NDSAdminServer.
    How can I solve this problem?

  • Urgent Help - Server Process stop with Error Code -11113

    Hi All,
    I need help urgently,
    I have installed EP 7.0 on Win 2003, when i restarted the server,
    server process in MMC,  server0 stop with Exitcode -11113
    Anybody have any idea about this
    Thanks
    Sachin

    Sachin,
    Refer to the threads below.
    j2ee stopped exitcode -11113
    Server0 fails JLaunchIExitJava: exit hook is called (rc=-11113)
    Exitcode -11113
    Also,take a look at the SAP NOTE : 810434
    Hope it helps resolve your issue.
    Cheers,
    Sandeep
    p.s Consider rewarding for handy posts!

  • Nodemanager does not restart managed server after Linux OS reboot

    Running Linux 2.6.18, Sun JDK 1.6.0_14, and WebLogic 10.3, we have a correctly functioning nodemanager watching a single managed server. If I kill -9 the managed server, the nodemanager fires up a new one immediately. If, however, we reboot the box, the nodemanager will start cleanly and will not start the managed server. It appears to believe the node should remain down and reports its status as UNKNOWN.
    I've seen where this is a known problem on Windows boxes, easily gotten around by supplying the -Xrs parameter to the startup parms for the managed server. (Section 5 of the general nodemanager config doc.) I don't see, however, where there's an equally clean solution for Linux.
    Things I've tried:
    + When I set the server to DEBUG, it shows zero sign of receiving a shutdown signal. It's dumping loads of cluster messages, etc, into the log and then suddenly the log just ends so it's dying via kill -9. If the nodemanager is still running at that time, it might try to restart the managed server and log it somewhere as permanently failed.
    + The nodemanager only logs to INFO level, and logs no evidence of deciding to leave the node down. (DEBUG is an invalid LogLevel, so that's all I've got.)
    + A restart signal sent from our AdminServer (on another Linux box) successfully starts the managed node through the nodemanager. Nothing unusual occurs or is logged.
    Things I'm curious about:
    + Is there some way to see in what state the nodemanager believes the managed server to be?
    + Is there some value in some doc somewhere that might say the server should not be restarted?
    + Is there not a log of NodeManager client actions? I don't see anything in domain.log or AdminServer.log except when the NM is down.
    Thanks,
    Kevin
    ListenPort=5556
    ListenBacklog=50
    SecureListener=true
    AuthenticationEnabled=true
    NativeVersionEnabled=false
    CrashRecoveryEnabled=true
    JavaHome=/appl/java/jre
    StartScriptEnabled=false
    StopScriptEnabled=false
    StartScriptName=startWebLogic.sh
    StopScriptName=
    LogFile=/appl/bea/wlserver_10.3/common/nodemanager/logs/nodemanager.log
    LogLevel=INFO
    LogLimit=0
    LogCount=1

    can you set NativeVersionEnabled to true. We have faced this in windows which was fixed by changing this property. Some notes from that issue:
    Faced this interesting issue in Windows 2008 environment. Managed Servers were started by node manager and it was expected that on a system restart after a crash, the node manager will restore the state of the managed servers to the state it was before the crash. Node Manger was configured to run as a windows service. Hence it started after the server restart. But the individual managed servers were not getting started. Interestingly, for the managed servers started by the node manager there were no <Managed_Server_Name>.lck file in the <Server>/data/NodeManger folder.
    To fix this always set the following properties in the nodemanager.properties on the node maager home directory.
    CrashRecoveryEnabled=true /* This by default is set to false. This needs to be turned for auto restart after crash to work */
    NativeVersionEnabled=true /* This is by default set to true and it should be set as such. If you turn this off on platforms for which weblogic provide native JNI libraries ( e.g. as in Windows 2008) then this wont create the .lck file and hence node manager wont restart the managed server after the crash.
    Note: As per official documentation .lck files are required for weblogic node managers to do auto restart after system crash
    From Official documentation:
    After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.
    If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
    After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
    */

  • Site does not load after some minutes of creation or after restart the server

    Hello,
    I have been asked to create a test enviroment identical to the production enviroment. So, what I did was:
    Backed up the production web application's content database: Prod_WSS_ContentDB
    Created new test servers (domain controller, sql server and sharepoint 2013 server) in a new, completely isolated, network environment, without any connection with the production environment (specifically Azure)
    Created a new web application in test environment with a new content database.
    Dismounted the new content database with powershell: Dismount-spcontentdatabase Test_WSS_Content
    Copy the Prod_WSS_ContentDB database to the test sql server and restored it with Management Studio.
    Mount the Prod_WSS_ContentDB databe to the web application with powershell:
    Mount-spcontentdatabse Prod_WSS_ContentDB -WebApplication http://testsp/
    Then, when I type http://testsp in the browser it redirects me to http://testsp/SitePages/Home.aspx
    and the site loads exactly as the production environment.
    But, after some minutes, or if I restart the Sharepoint Server, when I navigate to
    http://sitesp I am redirected to http://testsp/SitePages/Home.aspx
    as expected, but the site does not load, the browser just show a complety blank page.
    The Central Administration site loads normally.
    Trying to fix it I found that if I dismount the content database Prod_WSS_ContentDB, then mount the test database Test_WSS_Content,
    then navigate to the site, dismount Test_WSS_Content and finally mount again Prod_WSS_ContentDB, the site loads normally, no blank page, but after some minutes or if I restart the same happens again.
    For the error event I receice in event viewer it seems that the problem is related to database. I have not found a solution for this error... How can I solve  this?
    The error is:
    Log Name:      Application
    Source:        Microsoft-SharePoint Products-SharePoint Foundation
    Date:          6/27/2014 2:44:22 PM
    Event ID:      5586
    Task Category: Database
    Level:         Error
    Keywords:      
    User:          UCETEST\spaccount
    Computer:      TESTSP01.ucetest.edu.do
    Description:
    Unknown SQL Exception -2146893055 occurred. Additional error information from SQL Server is included below.
    A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The handle specified is invalid)
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6FB7E0CD-52E7-47DD-997A-241563931FC2}" />
        <EventID>5586</EventID>
        <Version>15</Version>
        <Level>2</Level>
        <Task>3</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000000000</Keywords>
        <TimeCreated SystemTime="2014-06-27T14:44:22.743159500Z" />
        <EventRecordID>4742</EventRecordID>
        <Correlation />
        <Execution ProcessID="1688" ThreadID="1692" />
        <Channel>Application</Channel>
        <Computer>TESTSP01.ucetest.edu.do</Computer>
        <Security UserID="S-1-5-21-2552298216-324766354-3392103171-1108" />
      </System>
      <EventData>
        <Data Name="int0">-2146893055</Data>
        <Data Name="string1">A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The handle specified is invalid)</Data>
      </EventData>
    </Event>
    Melvintt
    MCTS, Windows Server 2008 R2: Network Infrastructure
    MCTS, Windows Server 2008 R2: Active Directory, Configuring

    Hi,
    According to your post, my understanding is that Site does not load after some minutes of creation or after restart the server.
    Please make sure you create a test environment for existing production site correctly.
    Here are some great articles for your reference:
    Moving content between SharePoint environments
    Copy SharePoint production data to a test environment
    Build a SharePoint 2010 Test/Development Farm
    Best Regards,
    Linda Li
    Linda Li
    TechNet Community Support
    Hello Linda Li,
    I follwed that steps to create my test enviroment... and I have recreated it some times using that same steps, but the problem persits. After some minutes or after I restart the SharePoint server the site does not load.
    Melvintt
    MCTS, Windows Server 2008 R2: Network Infrastructure
    MCTS, Windows Server 2008 R2: Active Directory, Configuring

  • Linked Server unable to Connect in SQL Server 2012 after Restarting SQL Server Service it works fine. Why?

    I have created a Linked Server to Access Database of 64 MB in Size located in Remote System to SQL Server 2012.In Start for Some time it works fine and after it is giving the Error 
    OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.".
    Msg 7303, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
    Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
    Previously I thought it as Permission Issue. By trying some fixes proposed in forums it not fixed. But, after restarting the SQL Server Services without changes to the linked Server it works perfectly. How could i fix it. I don't want restart the SQL Server
    Service it leads to Some other process failures.
    RehaanKhan. M

    After all the Errors, When I am restarting the SQL Server its working correctly.
    Whats the problem it is clearing itself after restarting of SQL Server. Why ?. I can't find anything regarding this in SQL Server .
    The following are the Errors i got connecting to SQl Server.
    OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.".
    Msg 7303, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
    Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
    Error-2:
    Executed as user: RMS\Administrator. Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST". [SQLSTATE 42000] (Error 7303)  OLE DB provider
    "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.". [SQLSTATE 01000] (Error 7412).  The step failed.
    After unchecking the Allow In Process in OLEDB.ACE Provider Properties.
    Msg 7399, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
    The OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" reported an error. Access denied.
    Msg 7301, Level 16, State 2, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
    Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
    for to fix above error i have followed the instructions in the following link,
    http://blogs.msdn.com/b/dataaccesstechnologies/archive/2010/08/19/permissions-needed-to-set-up-linked-server-with-out-of-process-provider.aspx
    This also failed to work. I Restarted SQL Server and make the Linked Server Properties Default to my Configuration and it works fine.
    Can you suggest me a solution for this issue. Every time i don't want to restart SQL Server Services as it effects other jobs and Processes.
    Thank you.
    RehaanKhan. M

  • One of the BizTalk Server processes in the affected computer is being throttled for significant periods because of high database size exceeding the threshold

    Hello Experts,
    I have complex Biz Talk 2013 farm having 20 servers,15 Hosts. In my production environment even if there is no traffic i am getting throttling errors from SCOM for my all the production hosts.
    Error : One of the BizTalk Server processes in the affected computer is being throttled for significant
    periods because of high database size exceeding the threshold
     I checked following things:
    1. MsgBoxDB size 748732 KB
    2. Spool table size  53 MB
    3. Tracking DB size 26724 KB
    4. Host settings --  Message Queue Size = 100, MsgCount = 50000 , Spool MP = 10 , Tracking MP = 10
    5. Ran Message Box viewer  and did not found any error related to DB size. (which counter i should focus on in MBV)
    Note -- for DB i am sharing full backup size because it does not have log file size.
    Please suggest where i should focus?
    Is SCOM reporting correctly because everything is fine in biztalk ?
    Thanks
    Yagya
    https://www.mcpvirtualbusinesscard.com/VBCServer/card.aspx?tag=YagyaDattMishra&wa=wsignin1.0

    Hi Yagyam
    I remember this error from SCOM when you use the standard SCOM BizTalk pack.
    Check the eventlog of the server, do you see any errors in event log, this could give some clue to the root cause. Whenever you have this alert from SCOM, you must have
    some entries in eventlog relating to the alert raised by SCOM.
    Is your message processing by BizTalk hosts are normal? Run the performance monitor to see the bottleneck. Check if there is really throttling.
    As mentioned in this blog, check the state of the SQL Agent on BizTalk's SQL database server, may be try restart the SQL Agent on BizTalk's SQL database server.
    http://blogs.msdn.com/b/timdel/archive/2008/11/19/why-i-love-scom.aspx
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Maybe you are looking for

  • Windows error message and repair?

    Hi everyone. I'm having a huge headache with my macbook right now, maybe someone can help? Sorry this post is so long! Immediately after I click to boot into Windows I get this message with a black screen: "Windows could not start because the followi

  • Apple mobile device service not started

    Each time i try to sync my iphone to itunes it keeps on saying "apple mobile device service not started" I know how to start it and everything its that when i start it it says "Windows could nt start the Aplle Mobile Device service on local computer"

  • How to get the directory name where the class resides

    I have following directory structure. c:\one\two\three\four\five\Test.java package name for Test.java is four.five When I run, four.five.Test, I want to get the compelte path name where currently the Test.class is running i.e. "c:\one\two\three\four\

  • Does creation of new xml file captures latest value?

    HI All, say for instance, if web port has been changed from 8000 to 80 and after this change xml file gets corrupted in apps tier... Does creation of new xml file in apps tier captures latest value of web port 80 and all other latest changes made so

  • Is there a phone number we can call

    Is there a phone number we can call for support?