Cannot SOAP over JMS in SOAPUI but can via HERMESJMS
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2011
07:51 AM
11-02-2011
07:51 AM
Cannot SOAP over JMS in SOAPUI but can via HERMESJMS
I get the following error when trying to send a request to a WebSphere 7 SIB server. I can however directly place a soap message on the request queue via HERMESJMS. What is wrong here?
Error provided below.
Wed Nov 02 10:48:39 EDT 2011:ERROR:javax.jms.JMSException: Failed to initialize the ORB
javax.jms.JMSException: Failed to initialize the ORB
at com.eviware.soapui.impl.wsdl.submit.transports.jms.JMSConnectionHolder.<init>(JMSConnectionHolder.java:78)
at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestSendReceiveTransport.execute(HermesJmsRequestSendReceiveTransport.java:36)
at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestTransport.sendRequest(HermesJmsRequestTransport.java:95)
at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:123)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Error provided below.
Wed Nov 02 10:48:39 EDT 2011:ERROR:javax.jms.JMSException: Failed to initialize the ORB
javax.jms.JMSException: Failed to initialize the ORB
at com.eviware.soapui.impl.wsdl.submit.transports.jms.JMSConnectionHolder.<init>(JMSConnectionHolder.java:78)
at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestSendReceiveTransport.execute(HermesJmsRequestSendReceiveTransport.java:36)
at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestTransport.sendRequest(HermesJmsRequestTransport.java:95)
at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:123)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2 REPLIES 2
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2011
06:34 AM
11-08-2011
06:34 AM
Anyone? Do I actually have to create a support ticket to get this looked at?
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2011
08:56 AM
11-18-2011
08:56 AM
I got a reply via email support that resolved this error:
Open soapUI-<version>.vmoptions
file located in <soapui.home>/bin/ and the following line at the bottom:
-Dcom.ibm.CORBA.ORBInit=com.ibm.ws.sib.client.ORB
You will have to put appropriate jar files into <soapui.home>/bin/ext folder
for this to work.
Restart soapUI and try again. This should solve your problem.
Open soapUI-<version>.vmoptions
file located in <soapui.home>/bin/ and the following line at the bottom:
-Dcom.ibm.CORBA.ORBInit=com.ibm.ws.sib.client.ORB
You will have to put appropriate jar files into <soapui.home>/bin/ext folder
for this to work.
Restart soapUI and try again. This should solve your problem.
