my dog learned polymorphism
The moose likes Websphere and the fly likes Admin Service won't start for Websphere 4.0 AE Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of OCA Java SE 8 Programmer I Study Guide this week in the OCAJP 8 forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "Admin Service won Watch "Admin Service won New topic

Admin Service won't start for Websphere 4.0 AE

simona afifi

Joined: Jan 08, 2002
Posts: 2
I migrated WAS 3.5 environment to WAS 4.0 AE environment, after installation the admin service won't start. This is the error in the log
AdminServer X WSVR0009E: Error occurred during startup
java.lang.NoClassDefFoundError: javax/sql/ConnectionPoolDataSource
I located this class in j2ee.jar
The classpath parameter in admin.config;C:/WebSphere40/AppServer/lib/bootstrap.jar;c:/sqllib/java/
Tony Chen
Ranch Hand

Joined: Jan 29, 2001
Posts: 286
Did you run the usejdbc2.bat file (under \SQLLIB\java12 directory) of DB2? Make sure "JDBC 2.0" is in the inuse file.

SCJP Java 2 - IBM Certified Enterprise Developer - WebSphere V4.0 & V5.0 - IBM Certified System Administrator - WebSphere Network Deployment V6.0 - Canadian Securities Course (CSC) Certification
simona afifi

Joined: Jan 08, 2002
Posts: 2
I ran the batch file and checked the file inuse it is showing JDBC2.0
Kazunori Sugimoto

Joined: Aug 29, 2002
Posts: 2
Hi! I had a same problem.But I solve this problem
by adding j2ee.jar to classpath of WAS.
good luck!
David O'Meara

Joined: Mar 06, 2001
Posts: 13459

The Java Ranch has thousands of visitors every week, many with surprisingly similar names. To avoid confusion we have a naming convention, described at
We require names to have at least two words, separated by a space, and strongly recommend that you use your full real name. Please edit your profile and select a new name which meets the requirements.
Shalini Komarla
Ranch Hand

Joined: Aug 28, 2002
Posts: 59
I had the same problem last week actually.
My issue was that although I was running JDBC 2.0 on the server that had websphere installed, I was NOT running JDBC 2.0 on the remote server where the WAS database resided. I don't know if your database is on a remote server or not, bu that was my problem.

Regards,<br />Shalini
I agree. Here's the link:
subject: Admin Service won't start for Websphere 4.0 AE
It's not a secret anymore!