Forum Discussion
SmartBear_Suppo
10 years agoSmartBear Alumni (Retired)
Hi Alejandro,
I'm not sure, kind of strange that you had to reinstall for it to work.
That pattern does not look right, a typical jms endpoint in SoapUI Pro should look similar to jms://ActiveMQSession::queue_Q1::queue_Q1. What looks to be throwing it off is "BTE::VC - NSC", what is the session name that you configured in HermesJMS? It should not contain any double colons in the name i.e ::
Regards,
Marcus
SmartBear Support
So, I decided to reinstall SoapUI Pro and it's working now. Weird, not sure what's different. If you have any idea of what could have happened, let me know.
I'm not sure, kind of strange that you had to reinstall for it to work.
jms://BTE::VC - NSC::queue_INBOUND.REQUEST::queue_LOCAL.INBOUND.RESPONSE.SAVE
That pattern does not look right, a typical jms endpoint in SoapUI Pro should look similar to jms://ActiveMQSession::queue_Q1::queue_Q1. What looks to be throwing it off is "BTE::VC - NSC", what is the session name that you configured in HermesJMS? It should not contain any double colons in the name i.e ::
Regards,
Marcus
SmartBear Support
- qweasd19 years agoRegular VisitorI have configured HermesJMS and was able to browse and send messages to WebSphereMQ but when I use the JMS endpoint to send request from SOAPUI I keep getting authentication error below. Am I missing something in my SOAPUI configuration?
MQJMS2013: invalid security authentication supplied for MQQueueManager
Related Content
- 10 months agoSaswat
- 12 years agoTarget_MN_-_soa