Message body appears to be write-only in JBoss A-MQ

Solution Unverified - Updated -

Issue

  • We've got an AMQ broker with jdbc persistence and a couple of camel routes similar to:
<route xmlns="http://camel.apache.org/schema/spring" id="route1">
        <from uri="broker:queue:foo"></from>
        <choice>
            <when> 
               <simple>...</simple>
               <to uri="broker:queue:bar"></to>
            </when>
            ....
         </choice>
</route>

  • Those routes redirect jms messages based on some condition, usually we're checking for certain jms properties in the jms header. Sending messages to 'foo' via hawtio works fine. Messages get delivered to 'bar' as expected. My apache cxf based tests achieve this.

  • Our webservices however seem to be sending jms messages that are configured slightly differently. This is just a guess - we're not actually sending messages in an extraordinary way.

  • When AMQ receives one of those jms message it doesn't deliver the message to the expected target queue and throws an exception message body is write-only.

  • Is there a way to make AMQ (or camel) log all jms message objects. I'd like to have a look at the messages that do get routed successfully to be able to compare them to the problematic ones.

Environment

  • Red Hat JBoss A-MQ
    • 6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content