Here it is: 2008-09-29 13:23:52,777 [7.28.130.231-WH24CU6052] [asyncDelivery0] DEBUG JMSMessageReceiver Received JMS message to destination : null Message ID : ID:c3e2d840d4d8c8f54040404040404040c311c62f4115feca Correlation ID : null ReplyTo ID : null 2008-09-29 13:23:52,777 [7.28.130.231-WH24CU6052] [asyncDelivery0] TRACE JMSMessageReceiver Message : REMSY MESSAGE 2008-09-29 13:23:52,809 [7.28.130.231-WH24CU6052] [jms-Worker-1] DEBUG BaseUtils Non SOAP/XML message received Exception in thread "jms-Worker-1" java.lang.NullPointerException at org.apache.synapse.transport.base.BaseUtils.handleLegacyMessage(BaseUtils.java:298) at org.apache.synapse.transport.base.BaseUtils.setSOAPEnvelope(BaseUtils.java:259) at org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:216) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Asankha C. Perera Sent: September 29, 2008 12:55 PM To: [email protected] Subject: Re: [esb-java-user] MQ series message listener Hi Remsy Can you please dump the JMS header and the message body here? The ESB interprets this as a "legacy" message - and I assume your payload is not SOAP 1.1/1.2 or POX/XML...? asankha Schmilinsky, Remsy wrote: Hi Asankha, I resolved the MQ problem by following these instructions. Basically it tells you how to generate the jndi bindings file: http://www.ibm.com/developerworks/websphere/techjournal/0502_woolf/0502_woolf.html http://www.nabble.com/Axis2-JMS-Transport-to-WebSphere-MQ-td14738492.html but now I get this error everytime I put a message on the queue: Exception in thread "jms-Worker-3" java.lang.NullPointerException at org.apache.synapse.transport.base.BaseUtils.handleLegacyMessage(BaseUtils.java:298) at org.apache.synapse.transport.base.BaseUtils.setSOAPEnvelope(BaseUtils.java:259) at org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:216) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) any ideas ? thanks Remsy -----Original Message----- From: [EMAIL PROTECTED] [ mailto:[EMAIL PROTECTED] Behalf Of Schmilinsky, Remsy Sent: September 26, 2008 9:09 AM To: [email protected] Subject: Re: [esb-java-user] MQ series message listener Hi Asankha. The problem was the version of MQ series, it is way old. I have to find the corresponding jms spec version. thanks remsy -----Original Message----- From: Schmilinsky, Remsy Sent: September 25, 2008 3:06 PM To: ' [email protected]' Subject: RE: [esb-java-user] MQ series message listener Hi Asankha. Maybe this is going off topic, but I just can't get the JNDI working. I found this article: http://www.boodi.com/2008/08/ibm-websphere-mq-and-tomcat-jndi.html Do I need to set a JNDI context within tomcat like this ? <Resource name="ConnectionFactory" auth="Container" type="com.ibm.mq.jms.MQTopicConnectionFactory" factory="com.ibm.mq.jms.MQTopicConnectionFactoryFactory" description="JMS Queue Connection Factory for sending messages" HOST="remote-server" PORT="1480" CHAN="SVR_CHANNEL" TRAN="1" QMGR="QM"/> then reference it within axis2.xml ? thanks Remsy -----Original Message----- From: [EMAIL PROTECTED] [ mailto:[EMAIL PROTECTED] Behalf Of Asankha C. Perera Sent: September 24, 2008 10:06 PM To: [email protected] Subject: Re: [esb-java-user] MQ series message listener Hi Remsy Hi. I am only allowed to connect to the mq manager with these parameters, so I don't have access to the remote mq server. Can I use these parameters to establish an MQ listener: manager name, queue name, host, channel, port, userid, password and I have the ibm mq jar files on the lib directory. Can you try to simply connect to a MQ destination and print a message? Try to use a simple client extended from something like [1]. You will need to make the MQ client JAR/s available to this program, and also set the JNDI properties to correctly connect to your remote MQ server. When you have successfully connected with this JMS client, you have everything needed to connect to MQ from the ESB - which will be very clear then. You copy the same JAR/s into the ESB's lib folder, and specify them in the axis2.xml and or JMS addresses. Do I need to have esb on the same server of wmq ? No asankha [1] http://java.sun.com/j2ee/1.4/docs/tutorial/examples/jms/simple/src/SimpleSynchConsumer.java _____ _______________________________________________ Esb-java-user mailing list [email protected] http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
_______________________________________________ Esb-java-user mailing list [email protected] http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
