How to migrate applications deployed in jboss-3.2.6 to jboss

[ozwolverine]

Hello everybody,

I have a problem deployed in jboss-3.2.6 it runs perfect, but after updating my server to jboss-4.0.2 I have problems with the application.

The question is: What changes should I do to make it work with jboss-4.0.2?
I have read Forums, Wiki, and FAQ, but I haven't found a possible solution.

Thanks a lot,
Johnny

[darranl]

The best starting point really will be to describe the first error you are getting and what makes you think it is not working on JBoss 4.0.2.

[ozwolverine]

Hello darrani, sorry for the delay, here I am again,..

The application deploys without problems:

16:34:05,124 INFO [EARDeployer] Init J2EE application:
file:/export/home/jbossadm/jboss-4.0.2/server/default/deploy/etb_ejb.ear
16:34:05,572 INFO [EjbModule] Deploying MiEjb
16:34:05,917 INFO [EJBDeployer] Deployed:
file:/export/home/jbossadm/jboss-4.0.2/server/default/tmp/deploy/tmp61811etb_ejb.ear-contents/etb_ejb.jar
16:34:06,015 INFO [EARDeployer] Started J2EE application:
file:/export/home/jbossadm/jboss-4.0.2/server/default/deploy/etb_ejb.ear
16:34:06,068 INFO [EARDeployer] Init J2EE application:
file:/export/home/jbossadm/jboss-4.0.2/server/default/deploy/jcocomp.ear
16:34:06,751 INFO [EjbModule] Deploying Negocio
16:34:06,771 INFO [EjbModule] Deploying ConectorSapXml
16:34:06,786 INFO [EjbModule] Deploying NegocioMdb
16:34:06,839 INFO [EjbModule] Deploying ConectorSapMdb
16:34:07,430 INFO [EJBDeployer] Deployed:
file:/export/home/jbossadm/jboss-4.0.2/server/default/tmp/deploy/tmp61812jcocomp.ear-contents/jcocomp.jar
16:34:07,571 INFO [TomcatDeployer] deploy, ctxPath=/jcocomp,
warUrl=file:/export/home/jbossadm/jboss-4.0.2/server/default/tmp/deploy/tmp61812jcocomp.ear-contents/jcocomp.war/
16:34:07,801 INFO [EARDeployer] Started J2EE application:
file:/export/home/jbossadm/jboss-4.0.2/server/default/deploy/jcocomp.ear
16:34:07,993 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on
http-0.0.0.0-8080
16:34:08,155 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
16:34:08,181 INFO [JkMain] Jk running ID=0 time=0/66 config=null
16:34:08,202 INFO [Server] JBoss (MX MicroKernel) [4.0.2 (build:
CVSTag=JBoss_4_0_2 date=200505022023)] Started in 30s:870ms

but when running the application appears this:

16:34:29,861 ERROR [LogInterceptor] EJBException in method: public
abstract co.etb.sap.ConectorSapXml
co.etb.sap.ConectorSapXmlHome.create() throws
javax.ejb.CreateException,java.rmi.RemoteException:
javax.ejb.EJBException: Could not instantiate bean
 at
org.jboss.ejb.plugins.AbstractInstancePool.get(AbstractInstancePool.java:180)
 at
org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invokeHome(StatelessSessionInstanceInterceptor.java:78)
 at
org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:90)
 at
org.jboss.ejb.plugins.CallValidationInterceptor.invokeHome(CallValidationInterceptor.java:41)
 at
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:109)
 at
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:335)
 at
org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:146)
 at
org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:116)
 at
org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:121)
 at
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:93)
 at
org.jboss.ejb.SessionContainer.internalInvokeHome(SessionContainer.java:613)
 at org.jboss.ejb.Container.invoke(Container.java:894)
 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
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
 at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
 at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:805)
 at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:406)
 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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
 at sun.rmi.transport.Transport$1.run(Transport.java:148)
 at java.security.AccessController.doPrivileged(Native Method)
 at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
 at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
 at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
 at java.lang.Thread.run(Thread.java:534)

What could the problem be?

Thanks a lot,
Johnny

[darranl]

Is that all of the Exception? Is there a nested cause below it?

The reason I ask is because the EJBException that is created on line 180 is constructed with a nested cause that would contain the real reason for the failure.

[ozwolverine]

"darranl" wrote:
Is that all of the Exception? Is there a nested cause below it?

Well, I'm afraid that is the whole exception.
What this could be?