Why does HTTP Gateway return HTTP status code "502 Bad Gateway" in JBoss ESB ?

Solution Unverified - Updated -

Issue

  • We are using a HTTP Gateway listener taking in Http communication, in the pipeline we (in order) send a jms, wait for an answer on a topic and then return a message response.
  • This returns a Http "502 Bad Gateway" answer. If the topic subscriber is commented out a message can be returned without issue.
  • Even if I let the esb message go through our topic subscriber action without getting touched the returned result is that the gateway return a 502 directly after that action even if the remaining actions in the pipeline is executed.
  • What can make the HTTP Gateway return a "502 Bad Gateway" answer?

Environment

  • Red Hat JBoss SOA Platform (SOA-P) 5

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