Ah, good point. Our simplest example is now running. So let's move on to next tests.
Thanx for your help. Klaus. gnodet wrote: > > You may want to try with the processorName="standard" attribute on the > JMS endpoint. The default processor uses multiplexing, which is not > available on all jms providers. > > On 8/22/06, Klaus Alfert <[EMAIL PROTECTED]> wrote: >> >> >> Thanx for you quick answer, it helped a lot. >> But I am still tumbling from exception to exception. Now, MQ chokes on >> the >> send-call :-( >> >> [junit] 26441 [Thread-0] INFO smix.console - >> javax.jms.JMSException: >> MQJMS1013: operation invalid whilst session is using asynchronous >> delivery >> [junit] 26441 [Thread-0] INFO smix.console - at >> com.ibm.mq.jms.services.ConfigEnvironment.newException( >> ConfigEnvironment.java:567) >> [junit] 26441 [Thread-0] INFO smix.console - at >> com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1051) >> [junit] 26441 [Thread-0] INFO smix.console - at >> com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1108) >> [junit] 26441 [Thread-0] INFO smix.console - at >> >> org.apache.servicemix.jms.multiplexing.MultiplexingProviderProcessor.process >> (MultiplexingProviderProcessor.java:164) >> [junit] 26442 [Thread-0] INFO smix.console - at >> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange( >> AsyncBaseLifeCycle.java:399) >> [junit] 26442 [Thread-0] INFO smix.console - at >> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange( >> BaseLifeCycle.java:43) >> [junit] 26442 [Thread-0] INFO smix.console - at >> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound( >> DeliveryChannelImpl.java:623) >> [junit] 26442 [Thread-0] INFO smix.console - at >> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting( >> AbstractFlow.java:169) >> [junit] 26442 [Thread-0] INFO smix.console - at >> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java >> :177) >> [junit] 26442 [Thread-0] INFO smix.console - at >> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java >> :227) >> [junit] 26442 [Thread-0] INFO smix.console - at >> org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java >> :291) >> [junit] 26442 [Thread-0] INFO smix.console - at >> EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown >> Source) >> [junit] 26442 [Thread-0] INFO smix.console - at >> java.lang.Thread.run(Thread.java:595) >> [j >> >> I'll take a look on it tomorrow. >> >> Klaus. >> >> >> gnodet wrote: >> > >> > I' m trying to fix this problem. >> > If will disable geronimo module until the plugin works again. >> > [..] >> > >> > -- >> > Cheers, >> > Guillaume Nodet >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Exceptions-in-servicemix-jms-with-WebSphereMQ-tf2141329.html#a5928806 >> Sent from the ServiceMix - Dev forum at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > > -- View this message in context: http://www.nabble.com/Exceptions-in-servicemix-jms-with-WebSphereMQ-tf2141329.html#a5939451 Sent from the ServiceMix - Dev forum at Nabble.com.
