Just to experiment with a flow other than SEDA, I naively
tried

flowName="jms?jmsURL=reliable:tcp://localhost:12345"

for both my application and the loan-broker example. Both
serices catch a NotSerializableException when serializing (if I'm
interpreting the stack trace correctly) the ConcurrentHashMap
in the NormalizedMessage in the ActiveMQMapMessage when trying
to send a new InOut MessageExchange to a peer on the ESB.

I'm assuming this is pilot error on my part. Is there some
magic when using the JMS or cluster flows, perhaps something
I need to change in my application, or in the activemq.xml
configuration?

Thanks...




Reply via email to