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

[j***@kingsway-financial.com]

I can't start IBM WebSpere Application service after deploying xPression EAR file.

event viewer--application log:
"Could not determine the process id of the java process. Changing the IBMWAS6Service - kNode01 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."

Does anybody know the solution?
Port conflict?

Thanks.

[Graham Hopkins]

Post by j***@kingsway-financial.com
I can't start IBM WebSpere Application service after deploying xPression EAR file.
"Could not determine the process id of the java process. Changing the
IBMWAS6Service - kNode01 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."
Does anybody know the solution?
Port conflict?
Thanks.

Hi,

Could you check the WebSphere Application Server logs for the given server
to see if they contain information about the problem (something like
{install_root}\profiles\{profile}\logs\{server}\SystemOut.log and
SystemErr.log)

Regards

Graham

[Ben_]

Tried to do what the error message says: "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."

When you start the service, the WebSphere Windows service process
(wasservice.exe) will start a java.exe process (the "real" Application
Server) and look at the log directory to see if a PID file is generated. If
not found, it assumes the process did not start correctly and it will kill
it and retry.

You probably changed the location of the log directory of the Application
Server, and you then need to change the Windows service or did not create
the Windows service with the correct settings.

[j***@kingsway-financial.com]

Thank you all.

I was using wrong version of java.
It is fixed once I switched to IBM java.

[g***@cedacri.it]

I have the same problem with Win2003 R2 SP2 and WAS 6.1 Fix Pack 15. Where can I download the version of the JAVA IBM for to resolve this problem?
Thank You All!

[k***@us.ibm.com]

Make sure you use the Java that comes with WebSphere instead of the Java that comes with Windows.

Ken

[g***@cedacri.it]

How can I verify if I use Java Ibm and not Java Windows?

[n***@yahoo.com]

issue "java -version" from the bin directory of the java you are trying to use.

[g***@cedacri.it]

java -version
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build pwi32dev-20060511 (SR2))

IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi322
3-20060504 (JIT enabled)
J9VM - 20060501_06428_lHdSMR
JIT - 20060428_1800_r8
GC - 20060501_AA)
JCL - 20060511a

[g***@cedacri.it]

At this point I think that is not a problem of Java version. But the service doesn't start after the reboot of the system. I ever have this error in the Event Viewer:

Could not determine the process id of the java process. Changing the IBMWAS61Service - server1 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.

Who can I help me?
Thank You

[Juanma Martinez]

Post by g***@cedacri.it
Could not determine the process id of the java process. Changing the IBMWAS61Service - server1 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.
Who can I help me?
Thank You

Have you checked if WAS starts in the normal way (not as a service) by
using the StartServer command ?

[Sri Sunderesan Shanmuganathan]

Post by Juanma Martinez

Could not determine the process id of the java process. Changing the IBMWAS61Service - server1 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.
Who can I help me?
Thank You

Have you checked if WAS starts in the normal way (not as a service) by
using the StartServer command ?
--
Juanma Martinez

Can you provide the detail steps?

[g***@cedacri.it]

I would to add another information about this problem. I have 2 application server in a cluster. On the first application server where can I open the administration console, the services doesn't start, but on second application server the services about nodeagent and server1 start.
Have you some information about this problem?

[g***@cedacri.it]

is there anyone?
I attach my SystemOut.log

[Juanma Martinez]

Post by g***@cedacri.it
is there anyone?
I attach my SystemOut.log

Remember this is not an official support channel. If you need official
help you will have to open a report ticket with IBM through the official
channel.

http://www-01.ibm.com/software/webservers/appserv/was/support/probsub.html

[k***@us.ibm.com]

There are obvious configuration errors in your log file, what have you done to correct them?

Ken

[g***@cedacri.it]

Thank you all for the support, but I have resolved after the installation of the fix pack 17!

[w***@ellerbebecket.com]

In my case, this error was being caused by a 0 byte security.xml file. I copied the contents from a previous version of the file (do a search in your appserver directory) and saved it. After that, each service would start up without issue.

I don't know what caused the file to get stuck at 0 bytes but it could have something to do with some configuration I was doing in the admin console.

[g***@cedacri.it]

I have this problem after that I have installed Fix Pack 19.
Why with Fix Pack 17 I dont'have this problem?

[Z***@EBLACORP.COM]

Hi

I got this issue on Windows 2003 SP2 and IBMWebSphere 6.1.0_15. I resolved it by deleting the process file in
C:\Documents and Settings\Default User\Local Settings\Application Data\javasharedresources

You may have java.exe hang when you started the Service and crashed. You need to kill this process to delete the process file in that folder. Once this is done, I was able to start the services properly.

HTH

regards;
Zack

[t***@fi.ibm.com]

Hello,

For me the error message appeared because I had removed app server specific log folders under '...\WebSphere\AppServer\profiles\AppSrv01\logs' folder. As soon as I restored the sub folders (for example 'server1') from recycle bin the service started successfully.

br,
Tero