0

Geetting error while trying to connect to websphere8 default messaging provider using following jars using hermesJMS

  1. com.ibm.ws.orb_8.0.0.jar

  2. com.ibm.was.sib.client.thin.jms_8.0.0.jar

  3. com.ibm.ws.ejb.thinclient_8.0.0.jar

Error- javax.naming.NamingException: Error getting WsnNameService properties [Root exception is org.omg.CORBA.TRANSIENT: initial and forwarded IOR inaccessible vmcid: 0x4942f000 minor code: 3591 completed: No

enter image description here

Andy Guibert
  • 41,446
  • 8
  • 38
  • 61
Mukul Gupta
  • 1
  • 1

1 Answers1

0

If you are not stucked with HermesJMS, you could give a try to JMSToolBox on sourceforge that allows to either connect directly to the internal WAS SIB or via a JMS Connection Factory
JMSToolBox is very easy to configure to connect to WAS SIB

titou10
  • 2,814
  • 1
  • 19
  • 42
  • Thanks, but I am using HermesJMS because it is bundled with SOAPUI and we can easily use its functionality in it. – Mukul Gupta Jan 02 '17 at 09:04
  • Could you please suggest if there is way to integrate it with soapui? – Mukul Gupta Jan 03 '17 at 14:27
  • Some features of JMSToolBox are exposed as REST services. Depending on your requirements, in SoapUI you can define REST requests to post/get messages from your MQ provider. Also, you can define scripts and templates that can contain variables (random of from list) and so generate some activity directly from JMSToolBox without SoapUI. Scripts in JTB can also read templates from a predefined directory etc. I still need to expose script via the REST interface... – titou10 Jan 04 '17 at 15:03
  • JMSToolBox REST services documentation is [here](https://sourceforge.net/p/jmstoolbox/wiki/REST) – titou10 Jan 04 '17 at 15:08