JMS Adapter - Consuming empty opaque element

Question

Hi All,
In a BPEL(lets say BPEL A) using JMS Adapter I am posting an message/payload into JMS Topic as Opaque element using produce_message.
Now in another router(Bpel B) I am listening to this topic using consume_message and trying to retrive the message.
Problem : In the consuming side ie., BPEL B's receive I receive the message as Empty opaque element.
ie.,
<receiveEBMFromIntegrationTopic_InputVar>
<part name="opaque">
<opaqueElement/>
</part>
</receiveEBMFromIntegrationTopic_InputVar>
Although in BPEL A the message that I have invoked produce_message on JMSAdapter is this :
<PublishEBMToTopic_Produce_Message_InputVar>
<part name="opaque">
<opaqueElement>
<ns2:HeaderMsg>
<ns2:MessageID>PIMS-2012-06-22T13:12:13+05:30</ns2:MessageID>
<ns2:MessageDate>2012-06-22T13:12:13+05:30</ns2:MessageDate>
<ns2:MessageVersion>V2</ns2:MessageVersion>
<ns2:MessagePriority>4</ns2:MessagePriority>
<ns2:MessageDomain>GPRD</ns2:MessageDomain>
<ns2:MessageRetryCount>0</ns2:MessageRetryCount>
<ns2:CorrelationID>PIMS-2012-06-22T13:12:13+05:30</ns2:CorrelationID>
<ns2:SourceSystemName>PIMS</ns2:SourceSystemName>
<ns2:SystemEnvironmentCode>Dev</ns2:SystemEnvironmentCode>
<ns2:BOName>Clinical Study</ns2:BOName>
<ns2:BOOperation>Sync</ns2:BOOperation>
<ns2:DownGradeVersionFlag>N</ns2:DownGradeVersionFlag>
</ns2:HeaderMsg>
<ns2:BodyMsg>
<ns2:ClinicalStudyEBO>
<ns2:StudyNumber>M13-3201</ns2:StudyNumber>
<ns2:ProtocolTitle>XYZ</ns2:ProtocolTitle>
<ns2:ABORecordInfo>
<ns2:LastSourcedFrom>PIMS</ns2:LastSourcedFrom>
<ns2:LastSourcedModifiedDate>2012-06-11T00:00:00.000+05:30</ns2:LastSourcedModifiedDate>
</ns2:ABORecordInfo>
</ns2:ClinicalStudyEBO>
</ns2:BodyMsg>
</opaqueElement>
</part>
</PublishEBMToTopic_Produce_Message_InputVar>
Can someone help me in knowing why I am getting an empty element in receivving side . Thanks for helping!
Regards,
Sridhar.

Answer 1

Hi Sridhar,
First thing To do is certify that the published message is ok in the JMS topic.
You can check that in the Weblogic Admin Console, you will need a durable subscriber to be able to check messages in a topic, or change temporarily to a queue that is easier to check the messages that are in.
Cheers,
Vlad