JBossMessageEndpointFactory ClassNotFoundException when I re

[michele.curioni]

Hi there,
I have implemented a JCA 1.5 inbound-resourceadapter within my ear file.
The resource adapter code is contained in a .rar file;
the messagelistener-type interface is contained in a .jar file that is referenced from the manifest file of the rar.
I have a MDB that implements the messagelistener-type, which is contained in another jar file.
All of them are part of the ear.

When I deploy and start the application everything works fine.

If I then stop the MDB via the JMX console,
when I try to start it again, I get a ClassNotFoundException for the messagelistener-type.

Here is the stacktrace:
[JBossMessageEndpointFactory] Starting failed jboss.j2ee:service=EJB,plugin=invoker,binding=message-inflow-driven-bean,jndiName=local/Solve3/RawProtocolRoutingMDBean@23247054 org.jboss.deployment.DeploymentException: Could not load messaging-type class biz.thelogicgroup.solve3.inputdriver.MessageRouting; - nested throwable: (java.lang.ClassNotFoundException: biz.thelogicgroup.solve3.inputdriver.MessageRouting)
at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:39)
at org.jboss.ejb.plugins.inflow.JBossMessageEndpointFactory.resolveMessageListener(JBossMessageEndpointFactory.java:312)


I tried to reference the jar file that contains the messagelistener-type from the jar file that contains the MDB, but no difference.

Any idea?

Thanks,
Michele

[weston.price]

As a test could you try the following:

1) Move the RAR out of the EAR file and deploy it as a standalone adapter
2) Keep the jar with the message-listener-type in the RAR file standalone deployment.
3) Deploy the MDB either in an EAR or as a standalone ejb jar file.

Thanks.

[weston.price]

Also, could you post your jboss.xml file that you are using to tie the MDB to the adapter.

[weston.price]

Also, make sure the jar that contains the message-listener is reference from the MANIFEST.MF of your ejb.jar file as well for the internal EAR deployment.

[michele.curioni]

Hi there,
I'd rather avoid deploying the rar separately, because it needs quite a few things that are part of the ear. I don't want to have to deploy many different files.

I give you more details about the content of the ear:

- InputDriver.jar contains the message-listener interface, as well as other classes needed by the rar
- InputDriver.rar is the resource adapter
- RawProtocolService.jar contains the MDB that implements the message-listener interface, and its manifest points to InputDriver.jar in this way: "Class-Path: InputDriver.jar"

jboss.xml for the MDB is this:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 4.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd">

<enterprise-beans>

<ejb-name>MyApp/RawProtocolService</ejb-name>
<jndi-name>MyApp/RawProtocolService</jndi-name>
<local-jndi-name>MyApp/RawProtocolServiceLocal</local-jndi-name>
<method-attributes>
</method-attributes>


<message-driven>
<ejb-name>MyApp/RawProtocolRoutingMDBean</ejb-name>
<resource-adapter-name>MyApp.ear#InputDriver.rar</resource-adapter-name>
</message-driven>
</enterprise-beans>
<assembly-descriptor/>
<resource-managers/>


Thanks,
Michele

[weston.price]

I ran a simple test with your configuration and I am not seeing the error.

What version of JBoss are you using?

[michele.curioni]

I'm using 4.0.2.

Did you try to deploy, stop the MDB with JMX console, and restart it?

[weston.price]

Yes.

I did not test against 4.0.2, I used 4.2. I will set that up.

[weston.price]

4.0.2 (no patches applied) works without error as well.

[weston.price]

If you can send me your email I can forward you the project I am using to test this. Maybe we can find the difference between the two.

[michele.curioni]

Hi there,

I tried your project, and it works fine for me too on both version of jboss (4.0.2 and 4.2.0)

I cannot see any difference in the structure of the ear nor in the descriptors.

Is there anything else we can try?

Thanks,
Michele

[weston.price]

Nothing really jumps out at me. The only thing I can think of is if your listener interface is referencing classes that cannot be found. Can you check this?