Hi Ratha,
Thanks for the feedback.
I tried it as you suggested, but unfortunately still get the
same error message as in my original post :-(
2012-06-18 17:14:47,977 [-] [jms-Worker-1] WARN JMSUtils Can't determine size
of JMS message; unsupported message type : com.ibm.jms.JMSMapMessage
2012-06-18 17:14:47,995 [-] [jms-Worker-1] ERROR BaseUtils Unsupported JMS
message type com.ibm.jms.JMSMapMessage
2012-06-18 17:14:47,997 [-] [jms-Worker-1] ERROR JMSMessageReceiver Unknown
error processing message
org.apache.axis2.transport.base.BaseTransportException: Unsupported JMS message
type com.ibm.jms.JMSMapMessage
at
org.apache.axis2.transport.base.BaseUtils.handleException(BaseUtils.java:166)
at
org.apache.axis2.transport.jms.JMSUtils.setSOAPEnvelope(JMSUtils.java:174)
at
org.apache.axis2.transport.jms.JMSMessageReceiver.processThoughEngine(JMSMessageReceiver.java:190)
at
org.apache.axis2.transport.jms.JMSMessageReceiver.onMessage(JMSMessageReceiver.java:122)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.handleMessage(ServiceTaskManager.java:518)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:430)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I found an old (2008) reference to Synapse not supporting
the JMSMapMessage type. Is it now supported?
http://old.nabble.com/JMS-MapMessage-Support-td17288464.html
Or could it be because it's an IBM MQ JMS message type
(com.ibm.jms.JMSMapMessage)?
Best regards,
Peter
-----Original Message-----
From: vijayaratha vijayasingam [mailto:[email protected]]
Sent: Montag, 18. Juni 2012 16:48
To: [email protected]
Subject: Re: Synapse: JMS MapMessage not supported?
Hi,
Define like this and check..The issue you faced earlier is, i think because
of the null rule set...
<parameter name="transport.jms.ContentType">
<rules>
<jmsProperty>contentType</jmsProperty>
<default>text/xml</default>
</rules>
</parameter>
Thanks
-Ratha
On 18 June 2012 19:37, Wright, Peter <[email protected]> wrote:
> Hi Ratha,
>
> I defined the content-type as you advised
> (not sure if correct, did the same as in sample 250,
> see "JMS_XML_Proxy" in the config below),
> but still get the same error messages about
> "unsupported message type com.ibm.jms.JMSMapMessage".
>
> Any ideas?
>
> Thanks
> Peter
>
> <definitions xmlns="http://ws.apache.org/ns/synapse";>
> <sequence name="fault">
> <makefault>
> <code xmlns:tns="http://www.w3.org/2003/05/soap-envelope";
> value="tns:Receiver"/>
> <reason value="Mediation failed."/>
> </makefault>
> <send/>
> </sequence>
> <sequence xmlns="http://ws.apache.org/ns/synapse"; name="main"
> onError="fault">
> <in>
> <log level="full"/>
> <send/>
> </in>
> <out>
> <send/>
> </out>
> </sequence>
> <sequence name="xml_proxy">
> <log level="full"/>
> <send/>
> </sequence>
> <sequence name="out">
> <send/>
> </sequence>
> <proxy name="JMS_XML_Proxy" transports="jms">
> <target inSequence="xml_proxy" outSequence="out"/>
> <parameter name="transport.jms.ContentType">
> <rules>
> <jmsProperty>contentType</jmsProperty>
> <default>com.ibm.jms.JMSMapMessage</default>
> </rules>
> </parameter>
> </proxy>
> </definitions>
>
> =============================================================
>
> -----Original Message-----
> From: vijayaratha vijayasingam [mailto:[email protected]]
> Sent: Freitag, 15. Juni 2012 19:48
> To: [email protected]
> Subject: Re: Synapse: JMS MapMessage not supported?
>
> Did you define the "content-type" rule @ your proxy configuration..Try to
> define it as "default" and check..
> Thanks
> -ratha
>
> On 15 June 2012 17:31, Wright, Peter <[email protected]> wrote:
>
> > Hi,
> >
> > I need to configure a JMS listener in Apache Synapse that handles JMS
> > MapMessages,
> > but it seems that Synapse doesn't support this message type.
> >
> > Synapse issues the following error message when MapMessages are read:
> >
> > 2012-06-15 13:09:04,614 [-] [jms-Worker-1] WARN JMSUtils Can't determine
> > size of JMS message; unsupported message type : com.ibm.jms.JMSMapMessage
> >
> > 2012-06-15 13:09:04,630 [-] [jms-Worker-1] ERROR JMSMessageReceiver Axis
> > fault processing message
> > org.apache.axis2.AxisFault: Unable to determine content type for message
> > ID:414d5120534544312e45552e4445562e4fd5cce6200bc09d
> > at
> >
> org.apache.axis2.transport.jms.JMSMessageReceiver.processThoughEngine(JMSMessageReceiver.java:167)
> > at
> >
> org.apache.axis2.transport.jms.JMSMessageReceiver.onMessage(JMSMessageReceiver.java:122)
> > at
> >
> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.handleMessage(ServiceTaskManager.java:518)
> > at
> >
> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:430)
> > at
> >
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> > at java.lang.Thread.run(Thread.java:662)
> >
> > Any advice/help?
> > Solution/workaround possible?
> >
> > I have Synapse 2.1.0 installed on Sun Solaris 10,
> > and a number of IBM MQ jar files copied to ./synapse/lib,
> > including com.ibm.mqjms.jar that contains "com.ibm.jms.JMSMapMessage".
> >
> > Thanks a lot,
> > Peter
> >
> > The content of this e-mail is intended only for the confidential use of
> > the person addressed.
> > If you are not the intended recipient, please notify the sender and
> delete
> > this email immediately.
> > Thank you.
> >
> The content of this e-mail is intended only for the confidential use of
> the person addressed.
> If you are not the intended recipient, please notify the sender and delete
> this email immediately.
> Thank you.
>
The content of this e-mail is intended only for the confidential use of the
person addressed.
If you are not the intended recipient, please notify the sender and delete this
email immediately.
Thank you.
