Forum Discussion

amit123's avatar
amit123
15 years ago

Tibco SOAP over JMS- SOAP Action/Binding issue

Hello,

Am trying to test SOAP over EMS (tibco),configured the concrete wsdl,created a project in SOAP UI 3.6.2 , was able to configure the Hermes JMS,am able to see all the queues and topics and was able to add the JMS end point to the SOAPEventsouprce binding,but when I start the server(which is a tibco SOAP event source),I see the below error .Am able to post the request onto the queue and SOAPEVENt source is able to read it but its getting stuck there .
SOAP UI generated URL for jms queue: "jms://MyEMS::queue_queue.wf.wfhm.il.ilc.ilonline.imagedata.upload"

Am guessing if this is a BUG in SOAPUI and its not able to read the soapaction and bindings properly from the WSDL.

Any suggestions/advises ? If any one encountered the same issue?

ERROR :

<?xml version = "1.0" encoding = "UTF-8"?>
<ns0:ErrorReport xmlns:ns0 = "http://www.tibco.com/pe/EngineTypes">
<StackTrace>Job-138000 Error in [IntegrationServices/IL Online Correspondent Interface -soap/MainProcesses/Receive ILOL Message.process/SOAPEventSource]
Unable to dispatch the SOAP message to a Service. The URL/SoapAction specified in the incoming message was invalid.
at com.tibco.bw.service.binding.soap.jms.SoapJmsEventContextProcessor4EvSrcCxt.postProcess(SoapJmsEventContextProcessor4EvSrcCxt.java:80)
at com.tibco.plugin.share.jms.impl.JMSEventContext.postProcess(JMSEventContext.java:231)
at com.tibco.pe.core.ProcessGroup.eval(ProcessGroup.java:54)
at com.tibco.pe.plugin.Activity.eval(Activity.java:241)
at com.tibco.pe.core.TaskImpl.eval(TaskImpl.java:574)
at com.tibco.pe.core.Job.a(Job.java:712)
at com.tibco.pe.core.Job.k(Job.java:501)
at com.tibco.pe.core.JobDispatcher$JobCourier.a(JobDispatcher.java:249)
at com.tibco.pe.core.JobDispatcher$JobCourier.run(JobDispatcher.java:200)
</StackTrace>
<Msg>Unable to dispatch the SOAP message to a Service. The URL/SoapAction specified in the incoming message was invalid.</Msg>
<FullClass>com.tibco.plugin.share.soap.errors.InternalException</FullClass>
<Class>InternalException</Class>
<ProcessStack>IntegrationServices/IL Online Correspondent Interface -soap/MainProcesses/Receive ILOL Message.process/SOAPEventSource</ProcessStack>
<MsgCode>SOAPPLUGIN-100047</MsgCode>
</ns0:ErrorReport>


Thanks in Advance
Amit

2 Replies

  • gherr's avatar
    gherr
    Occasional Contributor
    15 years ago
    Hi Amit,

    we encountered the same problem and yes it is a bug in soapUI. The JMS transport always uses the operation name as soap action instead of the one specified in the WSDL.

    I've fixed this issue in 3.6.1 and submitted a patch in this post http://www.eviware.com/forum/viewtopic.php?f=13&t=5759 to SoapUI Bugs.

    Unfortunately, it has not been included into the main release yet. But now, there is at least one more user who would need this patch...

    Regards.

    Gabor
  • xuxe's avatar
    xuxe
    Occasional Contributor
    15 years ago
    Hi, there's a bunch of stuff that soapUI do not automatically obtains from the WSDL (when regarding JMS bindings). However, this isn't properly an issue since you can define as many JMS properties as you wish, and therefore you can always specify the SoapAction = "expectedSoapAction".

    Obviously, it would be great that you don't need to be tuning each request with stuff that could easy be obtained from the service's specification. Another example, the endpoint's destination from the port.

    By the way, another feature that I've been waiting is the use of temporary queues (for replies). Any hope to have that feature available?

    Cheers!

    José Escudero