JMS Binding: in/out message

Question

Hi there,
Could anyone help with the following problem I'm facing with?
The problem is, the JMS Binding Component complains about the JMS MapMessage it received from a queue that was sent by an application client. Since the WSDL operation is in/out, according to the log JMS BC thinks
the JMSReplyTo field of the JMS message is not set. However, my application client does set this field.
On open esb, I have a JMS SU that provides request/reply JMS service. The WSDL for it is as follows:
<binding ...>
<jms:binding/>
<operation name="docServiceOperation">
<jms:operation destination="XWPDocQueue" destinationType="Queue" timeToLive="60000" redeliveryHandling="1:1000; 3:5000; 4:move(queue:DeadQueue)"/>
<input>
<jms:message messageType="MapMessage">
<jms:mapmessage>
<jms:mappart name="serviceName" part="serviceName" type="string"/>
</jms:mapmessage>
</jms:message>
</input>
<output>
<jms:message messageType="MapMessage">
<jms:mapmessage>
<jms:mappart name="message" part="message" type="string"/>
</jms:mapmessage>
</jms:message>
</output>
</operation>
</binding>
It's backed up by a BPEL SU.
The service assembly (with BPEL and JMS SU) is correctly deployed.
Now the problem is when the application client sends a MapMessage to the queue DocQueue, the JMS BC throws an erorr which says the JMS message is premature.
The application client code is something like this:
@Resource(mappedName = "jms/ConnectionFactory")
private static ConnectionFactory connectionFactory;
@Resource(mappedName = "XWPDocQueue")
private static Queue queue;
@Resource(mappedName="jms/XWPDocReplyQueue")
private static Queue replyQueue;
* Main method.
* @param args the destination used by the example
* and, optionally, the number of
* messages to send
public static void main(String[] args) {
try {
connection = connectionFactory.createConnection();
Session session = connection.createSession(
false,
Session.AUTO_ACKNOWLEDGE);
MessageProducer producer = session.createProducer(dest);
MapMessage message = session.createMapMessage();
for (int i = 0; i < NUM_MSGS; i++) {
System.out.println("replayQueue="+replyQueue);
message.setJMSReplyTo(replyQueue);
message.setString("serviceName", "transformImmediateXBRL");
message.setString("version", "1.0");
message.setString("corelationid", "");
message.setString("env", "DEV");
message.setBoolean("timingReq", false);
message.setString("metadata", FileHelper.loadContent(metatdataFilename));
message.setString("payload", FileHelper.loadContent(payloadFilename));
message.setInt("status", 0);
message.setString("message", "");
message.setString("timingInfo", "");
producer.send(message);
* Send a non-text control message indicating end of
* messages.
producer.send(session.createMessage());
} catch (JMSException e) {
System.err.println("Exception occurred: " + e.toString());
} finally {
if (connection != null) {
try {
connection.close();
} catch (JMSException e) {
The error trace on the server is:
[#|2008-05-27T12:54:22.512+1000|SEVERE|sun-appserver9.1|sun-jms-binding.com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint|_ThreadID=365;_ThreadName=JMSJCA sync #0(XWPDocQueue);_RequestID=ab5b3f47-ebde-48cd-bba9-82d3b0ff41c7;|JMSBC-E0713: Failed to process JMS message [com.stc.jmsjca.core.WMessageIn@1201bbe] in onMessage: JMSBC-E0715: Message exchange pattern for binding operation docServiceOperation is inout; can not send back output reply if no JMSReplyTo field is specified in JMS message with JMSMessageID ID:41-137.172.75.188(be:11:b3:ba:36:f5)-4477-1211856855154
com.sun.jbi.jmsbc.MessageExchangeProcessingException: JMSBC-E0715: Message exchange pattern for binding operation docServiceOperation is inout; can not send back output reply if no JMSReplyTo field is specified in JMS message with JMSMessageID ID:41-137.172.75.188(be:11:b3:ba:36:f5)-4477-1211856855154
at com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint.processInboundRequest(InboundMessageProcessorListenerEndpoint.java:399)
at com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint.onMessage(InboundMessageProcessorListenerEndpoint.java:225)
at com.stc.jmsjca.core.Delivery.deliverToEndpoint(Delivery.java:1105)
at com.stc.jmsjca.core.SyncDelivery$SyncWorker.runOnceStdNoXA(SyncDelivery.java:700)
at com.stc.jmsjca.core.SyncDelivery$SyncWorker.run(SyncDelivery.java:757)
|#]
[#|2008-05-27T12:54:22.606+1000|INFO|sun-appserver9.1|com.stc.jmsjca.core.Delivery|_ThreadID=365;_ThreadName=JMSJCA sync #0(XWPDocQueue);|JMSJCA-E027: Message with msgid=[ID:41-137.172.75.188(be:11:b3:ba:36:f5)-4477-1211856855154] was seen 4 times. It will be forwarded (moved) to queue DeadQueue with msgid [ID:42905-137.172.75.188(eb:2d:3d:71:d4:7d)-4557-1211856862606]|#]
[#|2008-05-27T12:54:22.621+1000|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=380;_ThreadName=JMSJCA sync #14(XWPDocQueue);_RequestID=642c7e8b-0fd9-404a-b494-dc8daa956325;|[Fatal Error] :1:1: Premature end of file.
|#]
[#|2008-05-27T12:54:22.621+1000|SEVERE|sun-appserver9.1|sun-jms-binding.com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint|_ThreadID=380;_ThreadName=JMSJCA sync #14(XWPDocQueue);_RequestID=642c7e8b-0fd9-404a-b494-dc8daa956325;|JMSBC-E0713: Failed to process JMS message [com.stc.jmsjca.core.WMapMessageIn@451566] in onMessage: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:239)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283)
at com.sun.jbi.jmsbc.XmlUtil.createDocumentFromInputSource(XmlUtil.java:74)
at com.sun.jbi.jmsbc.XmlUtil.createDocumentFromXML(XmlUtil.java:90)
at com.sun.jbi.jmsbc.JMSNormalizer.addPart(JMSNormalizer.java:587)
at com.sun.jbi.jmsbc.JMSNormalizer.buildMessagePayloadFromMapMessage(JMSNormalizer.java:339)
at com.sun.jbi.jmsbc.JMSNormalizer.buildMessagePayload(JMSNormalizer.java:232)
at com.sun.jbi.jmsbc.JMSNormalizer.normalize(JMSNormalizer.java:178)
at com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint.normalizeMessage(InboundMessageProcessorListenerEndpoint.java:691)
at com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint.processInboundRequest(InboundMessageProcessorListenerEndpoint.java:423)
at com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint.onMessage(InboundMessageProcessorListenerEndpoint.java:225)
at com.stc.jmsjca.core.Delivery.deliverToEndpoint(Delivery.java:1105)
at com.stc.jmsjca.core.SyncDelivery$SyncWorker.runOnceStdNoXA(SyncDelivery.java:700)
at com.stc.jmsjca.core.SyncDelivery$SyncWorker.run(SyncDelivery.java:757)
|#]
The JMS BC thinks the JMS message it received does not have a JMSReplyTo field, but my client does set this field to a live queue.
Does anyone know why? Thanks very much.
Skysword
Edited by: Skysword on May 27, 2008 11:59 PM

Answer 1

PicFlix is picture/video messaging. You can try removing that feature