PQ69219: ADMIN SERVER STARTING FROM COMMAND LINE BUT NOT FROM WINDOWS SERVICES. | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Admin Server will not start through Windows Services without adding the j2ee.jar into the admin.config's classpath. . Without the C:\WebSphere\AppServer\lib\j2ee.jar in the admin.config's classpath the error in tracefile is as follow: . [11/10/02 10:57:05:062 EST] 10f245a5 AdminServer X WSVR0009E: Error occurred during startup java.lang.NoClassDefFoundError: javax/sql/DataSource at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:695) at java.security.SecureClassLoader.defineClass(SecureClassLoader.ja va:133) at java.net.URLClassLoader.defineClass(URLClassLoader.java:319) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java(Comp iled Code)) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java(Comp iled Code)) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java(Compiled Code)) . ... (not all of error listed) . WSVR0067E: Failed to initialize WebSphere Administration server [11/10/02 10:57:09:609 EST] 10ee05aa AdminServer X WSVR0009E: Error occurred during startup java.lang.NoClassDefFoundError: javax/sql/DataSource at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:695) at java.security.SecureClassLoader.defineClass(SecureClassLoader.ja va:133) at java.net.URLClassLoader.defineClass(URLClassLoader.java:319) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java(Comp iled Code)) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java(Comp iled Code)) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java(Compiled Code)) . ... (not all of file listed) . Level 3's notes: Believe the problem is the shutdown sequence. For Advanced edition, the trasaction service shutdown first, then it shuts down the serious event logger. The termination process of serious event logging is as following. First, stop getting any new event; then flush all existing events in the queue to database. To write serious event to database, the logger starts a transaction but the transaction service is shutdown already, therefore the exception is thrown which complains that transaction can not start as the server is shutting down. . The problem could happen for both admin server and app server in AE. The reason this problem doesn't manifest most of time is that there is no serious event in the queue during termination time. This really depends on timing, code path for the setup.Local fix Workaround: In order to start the admin server through window service, you have to add C:\WebSphere\AppServer\lib\j2ee.jar in the admin.config's class path. This is a step not documented in the WebSphere Application Server Version 4.0.4 Release Notes.Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 4.0 users * **************************************************************** * PROBLEM DESCRIPTION: With SQL as repository, an exception * * is received during adminserver stop * **************************************************************** * RECOMMENDATION: * **************************************************************** The problem is in the shutdown sequence. For Advanced edition, the transaction service shutdown first, then it shuts down the serious event logger. The termination process of serious event logging is as following: First, stop getting any new events, then flush all existing events in the queue to the database. To write serious event to the database, the logger starts a transaction but the transaction service is shutdown already, therefore the exception is thrown which complains that transaction can not start as the server is shutting down.Problem conclusion The shutdown sequence codes are rewritten, so the serious event logger will get shut down before the transaction service shutdown, therefore, the serious event logger can write serious event to the database and finish the transaction before it is shutdown.Temporary fix WAS_SysMgmt_cumulative_eFixes/20Dec2002 folder on wasdoc0.raleigh.ibm.com/aparsComments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ69219
IBM Group: Software Group
Modified date: Jan 10, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.