JBOSS EAP-5.1: javax.ejb.EJBException: Invalid invocation, check your deployment packaging

[tushar21s]

Hi All,

I had a work around to upgrade my Application from Jboss 3 to Jboss 5.1. In this process all EJB's are migrated to EJB2.X from EJB1.X. The Jboss server startup seems to be fine but when my application try to invoke the EJB functions I got this error for each EJB:

javax.ejb.EJBException: Invalid invocation, check your deployment packaging,method=public abstract com.logistics.oypa.ejb.session.shipmentReport.ShipmentReportMgr com.logistics.oypa.ejb.session.shipmentReport.ShipmentReportMgrHome.create() throws javax.ejb.CreateException,java.rmi.RemoteException

The Stack Trace is here:

at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invokeHome(StatelessSessionContainer.java:172)

    at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome(CachedConnectionInterceptor.java:187)

    at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invokeHome(StatelessSessionInstanceInterceptor.java:97)

    at org.jboss.ejb.plugins.CallValidationInterceptor.invokeHome(CallValidationInterceptor.java:56)

    at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:125)

    at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:350)

    at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:161)

    at org.jboss.ejb.plugins.SecurityInterceptor.process(SecurityInterceptor.java:230)

    at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:205)

    at org.jboss.ejb.plugins.security.PreSecurityInterceptor.process(PreSecurityInterceptor.java:99)

    at org.jboss.ejb.plugins.security.PreSecurityInterceptor.invokeHome(PreSecurityInterceptor.java:88)

    at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:132)

    at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:107)

    at org.jboss.ejb.SessionContainer.internalInvokeHome(SessionContainer.java:639)

    at org.jboss.ejb.Container.invoke(Container.java:1109)

    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:597)

    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)

    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)

    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)

    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)

    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)

    at org.jboss.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:169)

    at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:118)

    at org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:209)

    at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:195)

    at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)

    at org.jboss.proxy.ejb.SecurityContextInterceptor.invoke(SecurityContextInterceptor.java:64)

    at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)

    at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:184)

    at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)

    at $Proxy344.create(Unknown Source)

The exception occurs while creating the interface :

public interface ShipmentReportMgrHome extends javax.ejb.EJBHome

{

   ShipmentReportMgr create() throws javax.ejb.CreateException,java.rmi.RemoteException;

}

[ebross]

Hi Tushar,

The problem seems to come from your deployment and presumably packaging, Note that JBoss 3.x and 5.1 have different deployments structures. I am not sure how backward compatible  JBOSS EAP-5.1 (Java EE 5) is with with ejb2 (Java EE 4). Look at the  JBOSS EAP-5.1 Release Notes.

BTW, why not upgrade to 3.x rather than 2.1? – It will take the same amount of effort.

[periklis_douvitsas]

have a look at this

https://community.jboss.org/message/112228

Also, have a look at this one

https://community.jboss.org/thread/168447

What version of jdk are you using?

Hope it helps

[sfcoy]

Does your ShipmentReportMgr EJB implementation have a:

{code:java}public void ejbCreate() {
}{code}

method?

Do the <home>...</home>, <remote>...</remote> and <ejb-class>...</...ejb-class> elements in the ejb-jar.xml file contain correct class and interface names?

[tushar21s]

Yes Stephen the implementation of ShipmentReportMgr EJB have public void ejbCreate() {} method.

The ejb-jar.xml file contains correct class and interface names because they were working on EJB1.X. Should there be jboss.xml files also in the META-INF folder?

[tushar21s]

I am using jdk1.6

[tushar21s]

Hi Ebross,

I referred to the document( JBOSS EAP-5.1 Release Notes)  while upgradation and it was really helpful. Till now we are not planning to upgrade to 3.x directly due to some reasons but yes the jboss5 is backward compatible to EJB2.X. In the deployment folder we have jars and wars (notpackaged into an ear) can this be a problem?