Is there any chance someone might be able to give me some advice on this
please? Ive just run various performance tests using the old endpoint and its a
clear bottle neck in my current implementation. If there is no way to fix the
problem could someone possibly advise me on how to increase performance of my
JMS transport?
Cheers,
Ian Harrigan
From: Ian Harrigan
Sent: Monday, June 22, 2009 6:55 PM
To: Apache ServiceMix Dev ; Apache ServiceMix Users
Subject: Alternative to defaultOperation in new JMS endpoints
Hi,
I was recently trying to convert my old JMS consumer (using <jms:endpoint
role="consumer".../>) to the newer jms:consumer endpoints to take advantage of
various enhancements that it offers however, i have a problem with it kicking
off my BPEL process (which worked fine on the old endpoints).
My old endpoint was as follows:
<jms:endpoint service="client:MessageBrokerProvider"
endpoint="MessageBrokerPort"
targetService="client:MessageBrokerProvider"
defaultOperation="client:Execute"
role="consumer"
destinationStyle="queue"
jmsProviderDestinationName="GATEWAY_INPUT_Q"
connectionFactory="#connectionFactory"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
useMsgIdInResponse ="true"/>
and my new one looks like:
<jms:consumer service="client:MessageBrokerProvider"
endpoint="MessageBrokerPort"
targetService="client:MessageBrokerProvider"
targetEndpoint = "MessageBrokerPort"
destinationName="GATEWAY_INPUT_Q"
connectionFactory="#connectionFactory"
useMessageIdInResponse="true"/>
The exception im getting from service mix is
"java.lang.IllegalArgumentException: Null operation in JBI message exchange",
which makes sense as it isnt there in the new version, whats the alternative to
this? This all works fine with the old endpoint so is there an equivalent to do
what the old one does?
Thanks in advance,
Ian
