No user defined transport headers in pulled messages from queue OSB JMS WLS -


IM is facing a problem with my JM message. Here's the case: In my main PS, I send an employee on request, to whom employees from BS get emploeeId> Reaction is a collection of employees During main action in the main collection, I want to add an employee to the Loop JMS queue as a simple message through the whole collection and ID. In the user-defined transport header in each loop iteration, if the messageName 'even' or 'odd' relies on the employee id on the outbound request as a statement. On the logged result I can see that the header has been properly added (still for every employee) I publish my JMS-BS which adds messages to the queue. When I want to draw my message to JMSConsumerPS, I do not have any transport headers that I have added. The consumer has the assets of all the headers set as 'yes'. My complete logging in the consumer

  $ inbound / ctx: transport   

and What do I get:

  & lt; Thieves: Transportation & gt; & Lt; Thief: uri & gt; MyURI & lt; / Thief: uri & gt; & Lt; Thief: Mode & gt; Request & lt; / Thief: Mode & gt; & Lt; Thief: qualityOfService & gt; Best effort & lt; / Thief: qualityOfService & gt; & Lt; con: request xsi: type = "jms: jmsrequestmetaData" xmlns: jms = "http://www.bea.com/wli/sb/transports/jms" xmlns: xsi = "http: //www.w3.org / 2001 / XMLSchema-Example "& gt; & Lt; tran: header xsi: type = "jms: jmsrequest headers" xmlns: tran = "http://www.bea.com/wli/sb/transports" & gt; & Lt; jms: JMSDeliveryMode & gt; 2 & lt; / jms: JMSDeliveryMode & gt; & Lt; Jms: jmsexpiration & gt; 0 & lt; / jms: JMSExpiration & gt; & Lt; Jms: jmsmessageID & gt; ID: & amp; Lt; 834866.1398327222060.0 & gt; & Lt; / jms: JMSMessageID & gt; & Lt; Jms: jmSPriority & gt; 4 & lt; / jms: JMSPriority & gt; & Lt; jms: JMSRedelivered & gt; False & lt; / jms: JMSRedelivered & gt; & Lt; Jms: jmstimestamp & gt; 1398327222060 & lt; / jms: JMSTimestamp & gt; & Lt; jms: jmsxdeliveryacount & gt; 1 & lt; / Jms: JMSXDeliveryCount & gt; & Lt; / Tran: Header & gt; & Lt; tran: encoding xmlns: tran = "http://www.bea.com/wli/sb/transports" & gt; UTF-8 & lt; / tran: encoding & gt; & Lt; Jms: message type & gt; Text & lt; / Jms: message type & gt; & Lt; / Thief: Request & gt;   

Thanks for the help

Just an estimate.

I was installing transport headers inside - the exact location. I had a "published" operation in the proxy and I was setting up a transport header before the publication operation. I have to "publish header settings" to be "published" in the work / work. Now it works as expected.

, the possibility of link will soon die - Oracle Community ...

Comments

Popular posts from this blog

Java - Error: no suitable method found for add(int, java.lang.String) -

java - JPA TypedQuery: Parameter value element did not match expected type -

c++ - static template member variable has internal linkage but is not defined -