10 Replies Latest reply on Aug 9, 2007 6:11 AM by marklittle

classloader problem?

jw Aug 8, 2007 8:38 AM

Im using ESB 4.2.MR3.

A client sends a JMS Object Message. The content is of type ClassA.
In an action I can call

message.getBody().get().getClass().getName()

and it returns the right class name (which is ClassA). But trying to
assign the value like

ClassA a;

a = (ClassA)message.getBody().get()

raises a ClassCastException. It seems, that different Classloaders are used. Serializing message.getBody().get() and deserializing it into a solves the problem (but that must be only a workaround).

Any ideas whats wrong?

1. Re: classloader problem?

marklittle Aug 8, 2007 10:36 AM (in response to jw)

Can you show me the code that you use to populate the message you're sending? Is it an ESB-aware client, for example?
Actions
2. Re: classloader problem?

claudio_br Aug 8, 2007 10:54 AM (in response to jw)

Try to create the message with MessageType.JAVA_SERIALIZED, but ClassA must implements Serializable
Actions
3. Re: classloader problem?

jw Aug 8, 2007 11:05 AM (in response to jw)

Hi Mark

The message comes through the gateway. So | just write a normal JMS Object Message to the queue the gateway is listening.
Actions
4. Re: classloader problem?

marklittle Aug 8, 2007 11:57 AM (in response to jw)

So if I'm understanding you correctly, you're using the standard JMS Gateway? Do you provide your own JMS composer implementation?

The standard gateway composer creates a default Message, which is XML. Can you also confirm (by calling Message.getType()) that you're dealing with an XML implementation?
Actions
5. Re: classloader problem?

marklittle Aug 8, 2007 12:18 PM (in response to jw)

BTW, just so we're clear, when you said:

Serializing message.getBody().get() and deserializing it into a solves the problem (but that must be only a workaround).

What precisely did you do?
Actions
6. Re: classloader problem?

marklittle Aug 8, 2007 8:43 PM (in response to jw)

Can you also try the following: set org.jboss.soa.esb.message.default.uri in the "core" section of the ESB property file to urn:jboss/esb/message/type/JAVA_SERIALIZED and rerun your example.
Actions
7. Re: classloader problem?

jw Aug 9, 2007 4:43 AM (in response to jw)

Hi Mark

Hot deplyment was the problem. It works after a restart.

Just to answer your questions:

So if I'm understanding you correctly, you're using the standard JMS Gateway?

yes

Do you provide your own JMS composer implementation?

no

Can you also try the following: set org.jboss.soa.esb.message.default.uri in the "core" section of the ESB property file to urn:jboss/esb/message/type/JAVA_SERIALIZED and rerun your example.

has no effect. message.getType() is always XML (but that's not a problem for me).

Thanks for help
Juerg
Actions
8. Re: classloader problem?

marklittle Aug 9, 2007 5:14 AM (in response to jw)

So this wasn't an issue with JBossESB? I just want to be sure we don't miss something in the next GA release. Thanks.
Actions
9. Re: classloader problem?

jw Aug 9, 2007 5:35 AM (in response to jw)

no, I think it's a 'hot deployment side effect' and not an ESB problem.
Actions
10. Re: classloader problem?

marklittle Aug 9, 2007 6:11 AM (in response to jw)

OK, thanks.
Actions

Go to original post