Forum Discussion
Alejandro21
10 years agoOccasional Contributor
Hi Marcus,
I found this previous post with the exact problem
viewtopic.php?f=2&t=22792&p=52116&hilit=websphere+mq&sid=431ba96d745a216245ee121de8422af8#p52116
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.
Now that I was able to setup my jms endpoint, I tried testing it and I received the following error.
Fri Aug 08 10:50:56 EDT 2014:ERROR:Exception in request: com.eviware.soapui.impl.wsdl.submit.RequestTransportRegistry$CannotResolveJmsTypeException:
Bad jms alias!
For JMS please use this endpont pattern:
for sending 'jms://sessionName::queue_myqueuename'
for receive 'jms://sessionName::-::queue_myqueuename'
for send-receive 'jms://sessionName::queue_myqueuename1::queue_myqueuename2'
Fri Aug 08 10:50:56 EDT 2014:ERROR:An error occurred [
Bad jms alias!
For JMS please use this endpont pattern:
for sending 'jms://sessionName::queue_myqueuename'
for receive 'jms://sessionName::-::queue_myqueuename'
for send-receive 'jms://sessionName::queue_myqueuename1::queue_myqueuename2'], see error log for details
Fri Aug 08 10:50:57 EDT 2014:INFO:Error getting response for [DispatchWorkOrderSoap.OpGetDispatchWorkOrder:Test Request]; com.eviware.soapui.impl.wsdl.submit.RequestTransportRegistry$CannotResolveJmsTypeException:
Bad jms alias!
For JMS please use this endpont pattern:
for sending 'jms://sessionName::queue_myqueuename'
for receive 'jms://sessionName::-::queue_myqueuename'
for send-receive 'jms://sessionName::queue_myqueuename1::queue_myqueuename2'
It basically says that I'm using a wrong jms alias. This is how my endpoint is configured
jms://BTE::VC - NSC::queue_INBOUND.REQUEST::queue_LOCAL.INBOUND.RESPONSE.SAVE
I didn't change the pattern, it is just the way it was built when I created the jms endpoint.
Any idea of where/what to start checking?
Thanks,
Alejandro
I found this previous post with the exact problem
viewtopic.php?f=2&t=22792&p=52116&hilit=websphere+mq&sid=431ba96d745a216245ee121de8422af8#p52116
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.
Now that I was able to setup my jms endpoint, I tried testing it and I received the following error.
Fri Aug 08 10:50:56 EDT 2014:ERROR:Exception in request: com.eviware.soapui.impl.wsdl.submit.RequestTransportRegistry$CannotResolveJmsTypeException:
Bad jms alias!
For JMS please use this endpont pattern:
for sending 'jms://sessionName::queue_myqueuename'
for receive 'jms://sessionName::-::queue_myqueuename'
for send-receive 'jms://sessionName::queue_myqueuename1::queue_myqueuename2'
Fri Aug 08 10:50:56 EDT 2014:ERROR:An error occurred [
Bad jms alias!
For JMS please use this endpont pattern:
for sending 'jms://sessionName::queue_myqueuename'
for receive 'jms://sessionName::-::queue_myqueuename'
for send-receive 'jms://sessionName::queue_myqueuename1::queue_myqueuename2'], see error log for details
Fri Aug 08 10:50:57 EDT 2014:INFO:Error getting response for [DispatchWorkOrderSoap.OpGetDispatchWorkOrder:Test Request]; com.eviware.soapui.impl.wsdl.submit.RequestTransportRegistry$CannotResolveJmsTypeException:
Bad jms alias!
For JMS please use this endpont pattern:
for sending 'jms://sessionName::queue_myqueuename'
for receive 'jms://sessionName::-::queue_myqueuename'
for send-receive 'jms://sessionName::queue_myqueuename1::queue_myqueuename2'
It basically says that I'm using a wrong jms alias. This is how my endpoint is configured
jms://BTE::VC - NSC::queue_INBOUND.REQUEST::queue_LOCAL.INBOUND.RESPONSE.SAVE
I didn't change the pattern, it is just the way it was built when I created the jms endpoint.
Any idea of where/what to start checking?
Thanks,
Alejandro
Related Content
- 10 months agoSaswat
- 12 years agoTarget_MN_-_soa