Posted: Fri Apr 13, 2007 8:11 am Post subject: targetService
Acolyte
Joined: 07 Feb 2006 Posts: 72
A WAS6 application is trying to read a message from an MQ6 queue that was placed there from a WMB6 message flow. The WAS application is using IBM's JMSListenerMDB, and it is receiving the following message:
WSWS3021E: The required "targetService" property was not present in the inbound JMS request message.
The WMB6 code is as follows:
Set OutputRoot.MQRFH2.usr.targetService = 'UpdatePort';
The wsdl is:
<service name="UpdateService">
<port name="UpdatePort" binding="tns:UpdateSOAPBinding">
<soap:address location="jms:/queue?destination=jms/loadQ&connectionFactory=jms/loadQCF&targetService=UpdatePort"/>
</port>
</service>
The WAS Configuration is as follows:
<services xmi:type="applicationserver.ejbcontainer.messagelistener:MessageListenerService" xmi:id="MessageListenerService_1166025818328">
<listenerPorts xmi:id="ListenerPort_1176412010188" name="Load_Queue_Port" connectionFactoryJNDIName="jms/loadQCF" destinationJNDIName="jms/loadQ" maxSessions="1" maxRetries="0" maxMessages="1">
<stateManagement xmi:id="StateManageable_1176412010203" initialState="START"/>
</listenerPorts>
<threadPool xmi:id="ThreadPool_1166025818329" minimumSize="10" maximumSize="50" inactivityTimeout="3500" isGrowable="false" name="Message.Listener.Pool"/>
</services>
Any ideas why the JMSListenerMDB can't read the message off the queue? Is the ESQL correct?
Joined: 15 Jun 2005 Posts: 163 Location: Massachusetts
Code:
SET OutputRoot.MQRFH2.jms.Dst = 'queue:///WMB.APP.AIREQ_SERVICE';
SET OutputRoot.MQRFH2.usr.transportVersion = '1';
SET OutputRoot.MQRFH2.usr.endpointURL ='jms:/queue?destination=jms/APPRequestQueue&connectionFactory=jms/APPRequestQCF&targetService=APPRequestPort' ;
SET OutputRoot.MQRFH2.usr.targetService ='APPRequestPort' ;
SET OutputRoot.MQRFH2.usr.contentType ='text/xml; charset=utf-8' ;
This above code works for me with a WAS application.
However, the one thing which troubled us most was this MDB was running on a Z/OS machine and it din't like the CCSID/encoding values in the MQMD. Just something you might want to be on the lookout for...
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum