Showing posts with label webshpere. Show all posts
Showing posts with label webshpere. Show all posts

Sunday, August 9, 2009

ADMU7704E: Failed while trying to start the Windows Service associated with

Exception while starting Websphere server:

ADMU0116I: Tool information is being logged in file C:\Program
Files\IBM\WebSphere\AppServer1\profiles\AppSrv01\logs\server1\startServer.log
ADMU7701I: Because server1 is registered to run as a Windows Service, the
request to start this server will be completed by starting the
associated Windows Service.
ADMU7704E: Failed while trying to start the Windows Service associated with
server: server1;
probable error executing WASService.exe: Starting
Service: PG13Node01
Timed out waiting for service to respond to
command, after 60 seconds.Failed to start service, or timed out
while waiting for start to complete. Check the logs for details.


Solution:

In the logs folder for the server, (e.g. ...\profiles\app\logs\server1 )
there is a file called server1.pid, in this case, this file, contains the process id for the server process.
This file it's supossed to be deleted when the server shuts down, but when the server crash down, or when some 'unusual' situation happens the file is not deleted, then when the server is trying to start and find this file, it doesn't start and give some weird exceptions, I don't know why, because I checked and the process id in the file most of the time it's not used by the OS, anyway the server simply doesn't start.

so simply delete the file, and start the server.

CannotInstantiateObjectException

ConnectionFac E J2CA0106E: A 5.0 DataSource was attempted to be used in a WebModule that was not level 2.3.
W NMSV0605W: A Reference object looked up from the context "localhost/nodes/localhost/servers/server1" with the name "jdbc/client" was sent to the JNDI Naming Manager and an exception resulted. Reference data follows:
Reference Factory Class Name: com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl
Reference Factory Class Location URLs:

Exception stack trace: com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. Root exception is java.lang.Exception: Attempted to use a 5.0 DataSource outside of a 2.3 servlet
Cause:

As it explains clearly, trying to use servlet 2.3 under 2.2 dtd defintion.

Solution:

Replace Doctype declartion in web.xml
from

DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.
//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd"

to

DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.
//DTD Web Application 2.3//EN" 
"http://java.sun.com/dtd/web-app_2_3.dtd"