• Post Reply Bookmark Topic Watch Topic
  • New Topic

Deploying EJBs Websphere 5.0 Requiring JRE 1.4  RSS feed

 
Kevin Urcioo
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have some EJBs that require Java 1.4. How can I upgrade the Websphere JDK/JRE to allow these EJBs to function.
Currently the EJBs complain about the java.util.logging package.
I tried pointing the server.xml to the Sun's JDK 1.4, but Websphere poped with this message:
[1/15/03 17:29:42:336 EST] 813bc1 WsServer E WSVR0008E: Error encountered
reading META-INF/ws-server-components.xml
com.ibm.ws.exception.ConfigurationError
at
com.ibm.ws.runtime.service.ComponentManagerImpl.load(ComponentManagerImpl.ja
va:68)
at
com.ibm.ws.runtime.service.ComponentManagerImpl.<init>(ComponentManagerImpl.
java:51)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:109)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:232)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
Caused by: org.xml.sax.SAXException: System property org.xml.sax.driver not
specified
at
org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:9
0)
at
com.ibm.ws.runtime.service.ComponentManagerImpl.load(ComponentManagerImpl.ja
va:66)
... 8 more
---- Begin backtrace for nested exception
org.xml.sax.SAXException: System property org.xml.sax.driver not specified
at
org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:9
0)
at
com.ibm.ws.runtime.service.ComponentManagerImpl.load(ComponentManagerImpl.ja
va:66)
at
com.ibm.ws.runtime.service.ComponentManagerImpl.<init>(ComponentManagerImpl.
java:51)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:109)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:232)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
[1/15/03 17:29:42:366 EST] 813bc1 WsServer E WSVR0009E: Error occurred
during startup
 
Chris Mathews
Ranch Hand
Posts: 2712
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In the past WebSphere would only run under IBM JVMs. I am not sure if this is still true with WebSphere 5, but I would venture that it is. If this is the case then you are going to be stuck with J2SE 1.3 since IBM does not have a 1.4 implementation that I am aware. You could always try to run WebSphere in another JVM but it will be an unsupported configuration and I wouldn't recommend it.
 
Chris Mathews
Ranch Hand
Posts: 2712
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
BTW, J2SE 1.4 is not required to be supported until J2EE 1.4. Therefore, most vendors do not support J2SE 1.4 in their Application Servers yet. I highly recommend you stick to J2SE 1.3 during development. At least until J2EE 1.4 becomes widely supported.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!