You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Jamie Le Grange <ja...@googlemail.com> on 2006/01/16 15:25:13 UTC
Clustering and the JMSMarshaller
hi,
I'm getting a serialization exception from the JMSFlow when using
clustering and a JMSServiceComponent (i.e. client --> topic -->
jmsservicecomponent). The serialization exception is because
ActiveMQTextMessage isn't serializeable and it looks like the default
JmsMarshaller is adding the ActiveMQ message into the normalized
message as a property i.e.:
normalizedMessage.setProperty("org.servicemix.jms.message", message);
which the JMSFlow is then trying to serialize as part of the message exchange.
Am I doing something wrong?
it doesn't look like anything in 2.0.2 uses the
"org.servicemix.jms.message" property.
Re: Clustering and the JMSMarshaller
Posted by Guillaume Nodet <gn...@gmail.com>.
This is a known issue https://jira.logicblaze.com/jira/browse/SM-178.
I will fix the jms components and quartz components asap.
Cheers,
Guillaume Nodet
Jamie Le Grange wrote:
>hi,
>
>I'm getting a serialization exception from the JMSFlow when using
>clustering and a JMSServiceComponent (i.e. client --> topic -->
>jmsservicecomponent). The serialization exception is because
>ActiveMQTextMessage isn't serializeable and it looks like the default
>JmsMarshaller is adding the ActiveMQ message into the normalized
>message as a property i.e.:
>
>normalizedMessage.setProperty("org.servicemix.jms.message", message);
>
>which the JMSFlow is then trying to serialize as part of the message exchange.
>
>Am I doing something wrong?
>
>it doesn't look like anything in 2.0.2 uses the
>"org.servicemix.jms.message" property.
>
>
>
>