we have a fiew Windows2000 boxes running with WebSphere 5.0.1. Now we
upgraded the first of this boxes to 5.0.2.1 (SP2 and cumulative fix). Since
then some
EARs are not starting any more. We get following error when the EAR gets
loaded:
[11/4/03 16:03:32:812 CET] 3cb81012 EJBContainerI I WSVR0037I: Starting EJB
jar: crmKissBskEjb.jar
[11/4/03 16:03:32:812 CET] 3cb81012 EJBContainerI E WSVR0040E: addEjbModule
failed for crmKissBskEjb.jar [class
com.ibm.ws.runtime.component.DeployedModuleImpl]
java.lang.VerifyError: (class:
com/swisscom/crm/modules/crmKissBsk/svc/ejb/_EJSRemoteStatelessKissBskHome_2
3de7edb_Tie, method: remove__javax_ejb_Handle signature:
(Lorg/omg/CORBA_2_3/portable/InputStream;Lorg/omg/CORBA/portable/ResponseHan
dler;)Lorg/omg/CORBA/portable/OutputStream;) Incompatible object argument
for meth
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:262)
at com.ibm.rmi.util.Utility.loadTie(Utility.java:407)
at
com.ibm.rmi.javax.rmi.PortableRemoteObject.exportObject(PortableRemoteObject
.java:100)
at
javax.rmi.PortableRemoteObject.exportObject(PortableRemoteObject.java:85)
at com.ibm.ejs.oa.EJSOAImpl.registerServant(EJSOAImpl.java:178)
at com.ibm.ejs.oa.EJSOAImpl.registerServant(EJSOAImpl.java:147)
at
com.ibm.ejs.container.WrapperManager.registerInternal(WrapperManager.java:31
6)
at com.ibm.ejs.container.WrapperManager.faultOnKey(WrapperManager.java:545)
at com.ibm.ejs.util.cache.Cache.findAndFault(Cache.java:401)
at com.ibm.ejs.container.WrapperManager.getWrapper(WrapperManager.java:259)
at com.ibm.ejs.container.EJSHome.getWrapper(EJSHome.java:529)
at
com.ibm.ejs.container.EJSContainer.loadBeanMetaData(EJSContainer.java:1365)
at
com.ibm.ejs.container.EJSContainer.getHomeWrapperCommon(EJSContainer.java:97
6)
at
com.ibm.ejs.container.EJSContainer.getHomeInstance(EJSContainer.java:899)
at com.ibm.ejs.container.EJSContainer.startBean(EJSContainer.java:878)
at
com.ibm.ws.runtime.component.EJBContainerImpl.startBean(EJBContainerImpl.jav
a:1255)
at
com.ibm.ws.runtime.component.EJBContainerImpl.install(EJBContainerImpl.java:
988)
at
com.ibm.ws.runtime.component.EJBContainerImpl.start(EJBContainerImpl.java:14
62)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.jav
a:415)
at
com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart
(DeployedApplicationImpl.java:787)
at
com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.jav
a:351)
at
com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicati
onImpl.java:575)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(Application
MgrImpl.java:268)
at
com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.jav
a:246)
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.jav
a:543)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:418)
at
com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerIm
pl.java:123)
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.jav
a:543)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:418)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
I know that this ear is using OrbixWeb classes that contain old
org.omg.CORBA classes. It seems that these classes are now causing the
problems during server startup. It seems, that WebSphere runs a check when
loading the EAR. When using ServicePack 1, WebSphere does not care about
this additional "old" OrbixWeb orb. Also the application runs fine using
SP1, but does not even start when using SP2.
Any help on this would be apprechiated.
Thanks in advance
Beat Ris
Swisscom IT Service AG
[snip]
>
> I know that this ear is using OrbixWeb classes that contain old
> org.omg.CORBA classes. It seems that these classes are now causing the
> problems during server startup. It seems, that WebSphere runs a check when
> loading the EAR. When using ServicePack 1, WebSphere does not care about
> this additional "old" OrbixWeb orb. Also the application runs fine using
> SP1, but does not even start when using SP2.
>
> Any help on this would be apprechiated.
> Thanks in advance
>
> Beat Ris
> Swisscom IT Service AG
>
>
>
>
>
>
Something may have changed in the classloader settings - make sure yours
are the same as your 5.0.1 installation. Sounds like PARENT_FIRST might
do the trick.
Also, did you update the JDK when applying the fix? You may need to.
Ken
PARENT_FIRST solved the problem.
Thanks a lot.
Beat
"Ken Hygh" <ken...@nc.rr.com> schrieb im Newsbeitrag
news:bpafs4$4jnk$1...@news.boulder.ibm.com...