Thanks much. I tried the new style JMS endpoints and at least attempted to make a connection. Looks like firewall issues not related to servicemix right now.
Chris Custine wrote: > > It also looks like you are using the old style JMS endpoints. I would > recommend using the new JMS endpoints as they are much more flexible. > http://servicemix.apache.org/servicemix-jms-new-endpoints.html > > The syntax is slightly different but it should only take a few minutes to > convert the endoint config you show below. > > Thanks, > Chris > -- > Chris Custine > FUSESource :: http://fusesource.com > My Blog :: http://blog.organicelement.com > Apache ServiceMix :: http://servicemix.apache.org > Apache Directory Server :: http://directory.apache.org > > > On Fri, Aug 21, 2009 at 9:27 AM, jrrosel > <[email protected]>wrote: > >> >> I am doing some quick research on servicemix and one of our main >> requirement >> is the ability to work with Websphere MQ. I am attempting to get the >> simple >> eip/jms tutorial to use Websphere MQ instead of ActiverMQ. I am getting >> the >> following error when I place an xml file in the poller directory: >> >> ERROR - JmsComponent - Error processing exchange >> InOnly[ >> id: ID:172.25.128.178-1233d039424-7:2 >> status: Active >> role: provider >> service: {urn:servicemix:tutorial}jms >> endpoint: myQueue >> in: <?xml version="1.0" encoding="UTF-8"?><testMessage>Testing >> Message</testMe >> ssage> >> ] >> java.lang.NullPointerException >> at >> org.apache.servicemix.jms.standard.StandardProviderProcessor.process( >> StandardProviderProcessor.java:71) >> at >> org.apache.servicemix.soap.SoapEndpoint.process(SoapEndpoint.java:368 >> ) >> at >> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLi >> feCycle.java:627) >> at >> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(Async >> BaseLifeCycle.java:581) >> at >> org.apache.servicemix.common.AsyncBaseLifeCycle.onMessageExchange(Asy >> ncBaseLifeCycle.java:535) >> at >> org.apache.servicemix.common.SyncLifeCycleWrapper.onMessageExchange(S >> yncLifeCycleWrapper.java:60) >> at >> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBoun >> d(DeliveryChannelImpl.java:623) >> at >> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlo >> w.java:172) >> at >> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.j >> ava:168) >> at >> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.jav >> a:134) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec >> utor.java:650) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor >> .java:675) >> at java.lang.Thread.run(Thread.java:595) >> WARN - SimpleEndpoint - SimpleEndpoint.fail called: >> WARN - FileComponent - Message in file >> c:\servicemix_tutorial\ >> tutorial\poller\testing.xml could not be handled successfully: null >> java.lang.NullPointerException >> at >> org.apache.servicemix.jms.standard.StandardProviderProcessor.process( >> StandardProviderProcessor.java:71) >> at >> org.apache.servicemix.soap.SoapEndpoint.process(SoapEndpoint.java:368 >> ) >> at >> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLi >> feCycle.java:627) >> at >> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(Async >> BaseLifeCycle.java:581) >> at >> org.apache.servicemix.common.AsyncBaseLifeCycle.onMessageExchange(Asy >> ncBaseLifeCycle.java:535) >> at >> org.apache.servicemix.common.SyncLifeCycleWrapper.onMessageExchange(S >> yncLifeCycleWrapper.java:60) >> at >> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBoun >> d(DeliveryChannelImpl.java:623) >> at >> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlo >> w.java:172) >> at >> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.j >> ava:168) >> at >> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.jav >> a:134) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec >> utor.java:650) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor >> .java:675) >> at java.lang.Thread.run(Thread.java:595) >> >> My jms su xbean.xml is as follows: >> >> <beans xmlns:jms="http://servicemix.apache.org/jms/1.0"; >> xmlns:tut="urn:servicemix:tutorial" >> xmlns:util="http://www.springframework.org/schema/util";> >> >> <jms:endpoint service="tut:jms" >> endpoint="myQueue" >> role="provider" >> processorName="standard" >> destinationStyle="queue" >> jmsProviderDestinationName="JRR.TESTIN.Q" >> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; >> connectionFactory="#mqConnectionFactory"/> >> >> <bean id="mqConnectionFactory" >> class="com.ibm.mq.jms.MQQueueConnectionFactory"> >> <property name="transportType" value="1" /> >> <property name="queueManager" value="LEUSEG05" /> >> <property name="hostName" value="leuseg05.leinternal.com" /> >> <property name="channel" value="java.channel" /> >> <property name="port" value="1416" /> >> </bean> >> >> </beans> >> >> Any suggestions? I do see that the defaultMEP property in my xbean is >> in-out >> but the error message references inOnly. >> >> Thanks, >> Jeremy >> -- >> View this message in context: >> http://www.nabble.com/Servicemix-JMS-and-Websphere-MQ-tp25082012p25082012.html >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/Servicemix-JMS-and-Websphere-MQ-tp25082012p25117746.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
