| Author |
Message
|
| amit1310 |
 Posted: Thu Feb 24, 2011 7:33 am Post subject: Error reading SOAP JMS Messages |
 |
|
Newbie
Joined: 22 Jan 2011
Posts: 9
|
Hi All,
Did post on this forum regarding the issue that we were facing with reading 'SOAP over JMS' message, there were issues on Datapower which have now been resolved. However we are getting this error now.
Could you please have a look and let me know.
0010de8 PivotHandlerW W com.ibm.ws.webservices.engine.PivotHandlerWrapper invoke WSWS3734W: Warning: Exception caught from invocation to com.ibm.ws.webservices.engine.server.ServerEngine$1:
WebServicesFault
faultCode: Server.NoService
faultString: WSWS3163E: Error: The Web services engine could not find a target service to invoke! targetService is SwiftcallbackSoapPort
faultActor: null
faultDetail:
WSWS3163E: Error: The Web services engine could not find a target service to invoke! targetService is SwiftcallbackSoapPort
at com.ibm.ws.webservices.engine.server.ServerEngine$1.getHandler(ServerEngine.java:237)
at com.ibm.ws.webservices.engine.handlers.WrappedHandler.invoke(WrappedHandler.java:59)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:229)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:229)
at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:336)
at com.ibm.ws.webservices.engine.transport.jms.JMSListenerMDB.onMessage(JMSListenerMDB.java:468)
at com.ibm.ejs.container.MessageEndpointHandler.invokeMdbMethod(MessageEndpointHandler.java:1014)
at com.ibm.ejs.container.MessageEndpointHandler.invoke(MessageEndpointHandler.java:747)
at $Proxy13.onMessage(Unknown Source)
at com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl.invokeEndpoint(JmsJcaEndpointInvokerImpl.java:201)
at com.ibm.ws.sib.ra.inbound.impl.SibRaDispatcher.dispatch(SibRaDispatcher.java:788)
at com.ibm.ws.sib.ra.inbound.impl.SibRaSingleProcessListener$SibRaWork.run(SibRaSingleProcessListener.java:585)
at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:419)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1497) |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Feb 24, 2011 7:48 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Presumably connected to this?
The error:
| Quote: |
| WSWS3163E: Error: The Web services engine could not find a target service to invoke! |
seems fairly clear cut . It's also a WAS error rather than a WMQ one, and Mr Google found this for me:
http://www-01.ibm.com/support/docview.wss?uid=swg1PM27844
There are undoubtably other ways to get that error. Including not having a service of that name I'd imagine.
Why do you think this is a problem with the SOAP message? Or WMQ?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| amit1310 |
| Posted: Thu Feb 24, 2011 9:41 am Post subject: Re:Error reading SOAP JMS Messages |
|
|
Newbie
Joined: 22 Jan 2011
Posts: 9
|
| Thanks for the post. Did see this link on google search results but we work for a client where every issue (even obvious ones) are vendor issues (meaning us). Wanted to check with this forum once before posting it to the client. |
|
| Back to top |
|
|
| amit1310 |
| Posted: Thu Feb 24, 2011 12:12 pm Post subject: Re:Error reading SOAP JMS Messages |
|
|
Newbie
Joined: 22 Jan 2011
Posts: 9
|
| Thanks but the post that you have mentioned clearly mentions that this happens only when you upgrade to '6.1.0.33 or 7.0.0.13 ' from previous versions, where as we are on '6.1.0.25'. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Feb 24, 2011 12:15 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
There's another post here somewhere with a similar issue, in which someone was not constructing the MQ message with sufficient context to include the Operation.
Some digging around for SOAP JMS may help. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Feb 24, 2011 12:20 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
More specifically IIRC the information was in the MQ RFH header. So make sure you have set up your system to handle it correctly. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
