Error starting WAS - Could not determine the process id of the javaprocess - Websphere

This is a discussion on Error starting WAS - Could not determine the process id of the javaprocess - Websphere ; Hello, After restarting WebSphere Application Server it would no longer start due to the following error.... Could not determine the process id of the java process. Changing the IBMWAS6Service - LBIDEVCellManager01 service status to the "stopped" state. To prevent this ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Error starting WAS - Could not determine the process id of the javaprocess

  1. Error starting WAS - Could not determine the process id of the javaprocess

    Hello, After restarting WebSphere Application Server it would no longer start due to the following error....

    Could not determine the process id of the java process. Changing the IBMWAS6Service - LBIDEVCellManager01 service status to the "stopped" state. To prevent this error, try recreating this service with the -logRoot parameter. The value of the logRoot parameter should be the directory in which the server's .pid file is created.

    This is what shows in the SystemErr.log. Would anyone have any suggestions as to the cause of this error?

    Thanks!


    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R com.ibm.ws.exception.RuntimeError: com.ibm.ws.exception.RuntimeError: com.ibm.ws.exception.ConfigurationWarning: Problem initializing cell sync.
    at com.ibm.ws.runtime.WsServerImpl.bootServerContaine r(WsServerImpl.java:194)
    at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl .java:133)
    at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl. java:387)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:53)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:85)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:58)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:60)
    at java.lang.reflect.Method.invoke(Method.java:391)
    at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.jav a:219)
    at java.lang.Thread.run(Thread.java:568)
    Caused by: com.ibm.ws.exception.RuntimeError: com.ibm.ws.exception.ConfigurationWarning: Problem initializing cell sync.
    at com.ibm.ws.management.component.CellManagerImpl.st art(CellManagerImpl.java:147)
    at com.ibm.ws.runtime.component.ContainerImpl.startCo mponents(ContainerImpl.java:820)
    at com.ibm.ws.runtime.component.ContainerImpl.start(C ontainerImpl.java:649)
    at com.ibm.ws.runtime.component.ServerImpl.start(Serv erImpl.java:444)
    at com.ibm.ws.runtime.WsServerImpl.bootServerContaine r(WsServerImpl.java:187)
    ... 10 more
    Caused by: com.ibm.ws.exception.ConfigurationWarning: Problem initializing cell sync.
    at com.ibm.ws.management.component.CellManagerImpl.in itializeCellSync(CellManagerImpl.java:186)
    at com.ibm.ws.management.component.CellManagerImpl.st art(CellManagerImpl.java:139)
    ... 14 more
    Caused by: java.lang.NullPointerException
    at com.ibm.ws.management.transform.TransformRepositor y.getReleaseFolderList(TransformRepository.java:60 )
    at com.ibm.ws.management.transform.TransformCacheInva lidator.initialize(TransformCacheInvalidator.java: 105)
    at com.ibm.ws.management.sync.CellSync.initialize(Cel lSync.java:190)
    at com.ibm.ws.management.component.CellManagerImpl.in itializeCellSync(CellManagerImpl.java:178)
    ... 15 more

    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at com.ibm.ws.runtime.WsServerImpl.bootServerContaine r(WsServerImpl.java:194)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl .java:133)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl. java:387)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at com.ibm.ws.runtime.WsServer.main(WsServer.java:53)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:85)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:58)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:60)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at java.lang.reflect.Method.invoke(Method.java:391)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.jav a:219)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at java.lang.Thread.run(Thread.java:568)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R Caused by: com.ibm.ws.exception.RuntimeError: com.ibm.ws.exception.ConfigurationWarning: Problem initializing cell sync.
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at com.ibm.ws.management.component.CellManagerImpl.st art(CellManagerImpl.java:147)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at com.ibm.ws.runtime.component.ContainerImpl.startCo mponents(ContainerImpl.java:820)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at com.ibm.ws.runtime.component.ContainerImpl.start(C ontainerImpl.java:649)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at com.ibm.ws.runtime.component.ServerImpl.start(Serv erImpl.java:444)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at com.ibm.ws.runtime.WsServerImpl.bootServerContaine r(WsServerImpl.java:187)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R ... 10 more
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R Caused by: com.ibm.ws.exception.ConfigurationWarning: Problem initializing cell sync.
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at com.ibm.ws.management.component.CellManagerImpl.in itializeCellSync(CellManagerImpl.java:186)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at com.ibm.ws.management.component.CellManagerImpl.st art(CellManagerImpl.java:139)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R ... 14 more
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R Caused by: java.lang.NullPointerException
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at com.ibm.ws.management.transform.TransformRepositor y.getReleaseFolderList(TransformRepository.java:60 )
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at com.ibm.ws.management.transform.TransformCacheInva lidator.initialize(TransformCacheInvalidator.java: 105)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at com.ibm.ws.management.sync.CellSync.initialize(Cel lSync.java:190)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R at com.ibm.ws.management.component.CellManagerImpl.in itializeCellSync(CellManagerImpl.java:178)
    [8/26/08 16:09:50:797 EDT] 0000000a SystemErr R ... 15 more

  2. Re: Error starting WAS - Could not determine the process id of thejava process

    Did the JAVA_HOME env setting change?

    IBMWAS6Service--Could not determine the process id of the javaprocess.

    Looks like someone had a similar problem where the wrong java (the non-IBM one) was being called instead. All my WebSphere is on AIX / Linux so I wish I could give you some better ideas.

    I also saw this from IBM:

    http://www-01.ibm.com/support/docvie...id=swg1PK52495

    Not sure what WAS fixpacks you have installed ... might not be applicable for ya. HTH ...

    Jim

  3. Re: Error starting WAS - Could not determine the process id of thejava process

    Thanks for the heads up.

    I did check the JAVA_HOME settings and java versions and nothing changed on that end.

    We are on WAS 6.0.2.27 and luckily this was our testing server. Fix pack 6.0.2.29 was loaded and it corrected the issue. Not too sure why it started happening in the first place but we are glad it works now. Thanks for your assistance Jim.

+ Reply to Thread