Why JMSCorrelationID is getting lost when message moves to DLC Handler ?

Solution Verified - Updated -

Issue

  • User is facing an issue when running route in JBoss Fuse 6.2. Here JMSCorrelationID is getting lost when message moves to DLC Handler.
  • Same route runs fine in JBoss Fuse 6.0.
  • Route tries to do following:

    • Read a file via file consumer and pass to internal Active MQ endpoint.
    • Receive the message on internal Active MQ endpoint, set JMSCorrelationID as JMSMessageID, set date and send to Log Active MQ endpoint. Send the message to HTTP endpoint and handle the response.
    • If HTTP endpoint is available handle good or bad response by checking the CamelHttpResponseCode and then route to SUCCESS or FAILURE Active MQ endpoint. Then send to LOG Active MQ endpoint by setting date.
    • If HTTP endpoint is not available or any error occurs in invocation, DLC Handler is called which sets the exception,date and sends to Log Active MQ. Here user is loosing JMSCorrelationID in JBoss Fuse 6.2. But it works fine in JBoss Fuse 6.0.
  • Is there is any change or user is missing any configuration?

Environment

  • Red Hat JBoss Fuse
    • 6.2.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.