• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Migrating Websphere 5.02 to JDK1.4.1

 
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
I am trying to deploy an application developed using JDK1.4.1 on Websphere 5.02. The problem is I am getting too many NoClassDefFoundError and ClassNotFoundException. I believe the appserver is using its own Jdk1.3 version apis/jre available in Websphere/Appserver/java directory.
I did change the JAVA_HOME property in setCMDLine.bat file in Websphere/Appserver/bin directory to point to jdk1.4.2 directoy. But some how the appserver is using its own java version(java1.3) in the runtime the errors are being thrown .
I wanted to know how do I change the settings in Websphere 5.02 to support
jdk1.4.2 from the current version jdk 1.3. I believe somewhere internally the JAVA_HOME is hardcoded to point to its own java version. Also, I did notice one more thing. After changing the JAVA_HOME as mentioned above,the StartServer.log and SystemOut.log files are showing different versions of JAVA. In the beginning of the log files, the environment properties are writen in the log files. Here , I can see the StartServer.log file is pointing to JDK1.4.2 and the SystemOut.log file is pointing to its own java(ie Websphere/Appserver/java). Based on this I also suspect there are two classes one which runs in the start up (ie com.ibm.ws.bootstrap.WSLauncher) is using the new settings what I made and writing to StartServer.log file. Then the control is taken by com.ibm.ws.management.tools.WsServerLauncher file which uses its own Java version and writes into SystemOut.log file. That means both are in different environments?.
Can some Websphere gurus answer for me
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You cannot make WAS 5.02 work with JDK 1.4. It will not work. Do not try it. You must rewrite your application to not use any JDK 1.4 specific API's.
Kyle
 
Ranch Hand
Posts: 925
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
actually I've found a patch that will make it work ...
Websphere JDK1.4 patch
 
Kyle Brown
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Simon Lee:
actually I've found a patch that will make it work ...
Websphere JDK1.4 patch


Umm, how could a patch from Oracle possibly help WebSphere run on JDK 1.4? And what's more, I'm making this as a firm statement of support from the IBM WebSphere product group (which I work for). WAS 5.02 will not run on JDK 1.4. Don't do it.
Kyle
 
tumbleweed
Posts: 5089
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If you are using an Oracle patch to get Websphere to work with JDK1.4 in a production environment you are looking for big trouble.
I'd listen to Kyle's advice, very few people on this planet of ours know as much about Websphere as he does.
[ November 25, 2003: Message edited by: Johannes de Jong ]
 
Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic