Posted: Tue Nov 06, 2007 9:01 am Post subject: Error sending SOAP/JMS from WPS to WMB
Acolyte
Joined: 21 Jun 2006 Posts: 53
Hi,
I'm after some advice on troubleshooting a business process sending a SOAP/JMS message to message broker. I've created a business process and import component in WID. I have used a WSDL generated from Message broker to generate my import webservice binding.
When I attempt to test the module, the error I'm getting is -
00000066 JAXRPCHandler E com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandler$3 onFault WSWS3418E: Error: Exception generated during handler fault processing.
[06/11/07 16:15:56:234 GMT] 00000064 JMSSender E WSWS3014E: Error creating InitialContext: javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.jndi.fscontext.RefFSContextFactory [Root exception is java.lang.ClassNotFoundException: com.sun.jndi.fscontext.RefFSContextFactory]
[06/11/07 16:15:56:250 GMT] 00000064 PivotHandlerW E com.ibm.ws.webservices.engine.PivotHandlerWrapper invoke WSWS3180E: Error: Null response message.
What I'm tryuing to do is to pass a SOAP/JMS message from WPS to Message Broker. I am using MQ as the JMS messaging provider and have defined the JNDI entries and JMS objects. I am not getting as far as broker yet.
Platform is Windows XP
WID 6.0.2.2
WMQ 6.0.2.0
WMB 6.0.0.5
Has anyone come across this type of error when integrating WID/WMB?
Previoiusly I hadn't configured for JNDI via the admin console(I hadn't realised I needed to do that. I thought it was sufficient just to perform the JMSAdmin config for MQ). I have now configured on both admin console and via the JMSAdmin utility but am still getting some errors. Similar to those I was getting previously...
[06/11/07 20:51:07:969 GMT] 0000005b JMSSender E WSWS3014E: Error creating InitialContext: javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.jndi.fscontext.RefFSContextFactory [Root exception is java.lang.ClassNotFoundException: com.sun.jndi.fscontext.RefFSContextFactory]
[06/11/07 20:51:08:391 GMT] 0000005b ExceptionUtil E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "transactionNotSupportedActivitySessionNotSupported" on bean "BeanId(toWMB2App#toWMB2EJB.jar#Module, null)". Exception data: com.ibm.websphere.sca.ServiceRuntimeException: <soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Fault><faultcode>JMS</faultcode><faultstring>WSWS3014E: Error creating InitialContext: javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.jndi.fscontext.RefFSContextFactory [Root exception is java.lang.ClassNotFoundException: com.sun.jndi.fscontext.RefFSContextFactory]</faultstring></soapenv:Fault></soapenv:Body>
The error you're getting is very clear - it can't find the file system context classes for the JNDI InitialContext provider that you're trying to use.
It's just not clear why your code is trying to use the filesystem JNDI Initial Context Provider when the WPS JNDI is available...
You shouldn't be using JMSAdmin at all, if you're trying to deploy to the WAS/WPS JNDI. _________________ I am *not* the model of the modern major general.
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