Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Admin Service won't start for Websphere 4.0 AE

 
simona afifi
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
com.ibm.ejs.sm.adminserver.classpath=C:/WebSphere40/AppServer/properties;C:/WebSphere40/AppServer/lib/bootstrap.jar;c:/sqllib/java/db2java.zip
 
Tony Chen
Ranch Hand
Posts: 286
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Did you run the usejdbc2.bat file (under \SQLLIB\java12 directory) of DB2? Make sure "JDBC 2.0" is in the inuse file.
 
simona afifi
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I ran the batch file and checked the file inuse it is showing JDBC2.0
 
Kazunori Sugimoto
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi! I had a same problem.But I solve this problem
by adding j2ee.jar to classpath of WAS.
good luck!
 
David O'Meara
Rancher
Posts: 13459
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"kazunori",
The Java Ranch has thousands of visitors every week, many with surprisingly similar names. To avoid confusion we have a naming convention, described at http://www.javaranch.com/name.jsp.
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.
Thanks.
Dave
 
Shalini Komarla
Ranch Hand
Posts: 59
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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,
Shalini.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic