1 2 3 Previous Next 34 Replies Latest reply: Feb 3, 2011 5:36 AM by Igor JStarter RSS

Failure during invoke: Unspecified

Igor JStarter Novice

Hey!

 

Using Jboss5.1, ESB4.8 and Riftsaw2.1...

 

I did now some web services in BPEL, but I'm stuck now with my partners WS which I can't call...

 

When I deploy the BPEL, it deploys well. Than I call it from the SoapUI... In the log... after retrieving schemas i see:

2011-01-25 16:46:17,489 WARN  [org.jboss.ws.tools.wsdl.WSDL11Reader] (ODEServer-8) UsingAddressing extensibility element not supported yet.

2011-01-25 16:46:18,094 WARN  [org.jboss.soa.bpel.runtime.ws.WebServiceClient] (ODEServer-8) Fault response: faultType=(unknown)

2011-01-25 16:46:18,131 ERROR [org.apache.ode.bpel.runtime.INVOKE] (ODEServer-6) Failure during invoke: Unspecified

2011-01-25 16:46:18,152 INFO  [org.apache.ode.bpel.engine.BpelRuntimeContextImpl] (ODEServer-6) ActivityRecovery: Registering activity 11, failure reason: Unspecified on channel 21

2011-01-25 16:48:16,558 ERROR [org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl] (http-172.17.3.15-9000-1) Timeout or execution error when waiting for response to MEX {MyRoleMex#hqejbhcnphr5xri3gjngns [Client hqejbhcnphr5xri3gjngnr] calling {http://kkissiskratel/notifyRap}notifyRap.process(...)} java.util.concurrent.TimeoutException: Message exchange org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl$ResponseFuture@ad40bd timed out(120000 ms) when waiting for a response!

java.util.concurrent.TimeoutException: Message exchange org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl$ResponseFuture@ad40bd timed out(120000 ms) when waiting for a response!

    at org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl$ResponseFuture.get(MyRoleMessageExchangeImpl.java:250)

 

2011-01-25 16:48:16,560 ERROR [org.jboss.wsf.common.invocation.InvocationHandlerJAXWS] (http-172.17.3.15-9000-1) Method invocation failed with exception: null

java.lang.reflect.InvocationTargetException

 

The partners WS is a SVC WS. And I'm passing a dateTime parameter.... Could there be some problems?

Any other idea?

  • 1. Failure during invoke: Unspecified
    Igor JStarter Novice

    I think I got the TRACE level now working...

     

    2011-01-27 09:36:20,503 ERROR [org.apache.ode.jacob.vpu.JacobVPU] (ODEServer-1) Method "onResponse" in class "org.apache.ode.bpel.runtime.INVOKE$2" threw an unexpected exception.

    java.lang.IllegalArgumentException: Cannot stringify null Node!

        at org.apache.ode.utils.DOMUtils.domToString(DOMUtils.java:420)

        at org.apache.ode.bpel.runtime.ScopeFrame.initializeVariable(ScopeFrame.java:236)

        at org.apache.ode.bpel.runtime.ACTIVITY.initializeVariable(ACTIVITY.java:166)

        at org.apache.ode.bpel.runtime.INVOKE$2.onResponse(INVOKE.java:121)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.apache.ode.jacob.vpu.JacobVPU$JacobThreadImpl.run(JacobVPU.java:451)

        at org.apache.ode.jacob.vpu.JacobVPU.execute(JacobVPU.java:139)

        at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.execute(BpelRuntimeContextImpl.java:959)

        at org.apache.ode.bpel.engine.BpelProcess.handleJobDetails(BpelProcess.java:467)

        at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:468)

        at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:450)

        at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob$1.call(SimpleScheduler.java:526)

        at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob$1.call(SimpleScheduler.java:521)

        at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:284)

        at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:239)

        at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob.call(SimpleScheduler.java:520)

        at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob.call(SimpleScheduler.java:504)

        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

        at java.util.concurrent.FutureTask.run(FutureTask.java:138)

        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

        at java.lang.Thread.run(Thread.java:619)

    2011-01-27 09:36:20,504 ERROR [org.apache.ode.bpel.engine.BpelEngineImpl] (ODEServer-1) Scheduled job failed; jobDetail=JobDetails( instanceId: 429 mexId: hqejbhcnphr5xxkxk4xawp processId: null type: INVOKE_RESPONSE channel: 20 correlatorId: null correlationKeySet: null retryCount: null inMem: false detailsExt: {})

    java.lang.RuntimeException: java.lang.IllegalArgumentException: Cannot stringify null Node!

        at org.apache.ode.jacob.vpu.JacobVPU$JacobThreadImpl.run(JacobVPU.java:464)

        at org.apache.ode.jacob.vpu.JacobVPU.execute(JacobVPU.java:139)

        at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.execute(BpelRuntimeContextImpl.java:959)

        at org.apache.ode.bpel.engine.BpelProcess.handleJobDetails(BpelProcess.java:467)

        at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:468)

        at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:450)

        at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob$1.call(SimpleScheduler.java:526)

        at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob$1.call(SimpleScheduler.java:521)

        at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:284)

        at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:239)

        at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob.call(SimpleScheduler.java:520)

        at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob.call(SimpleScheduler.java:504)

        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

        at java.util.concurrent.FutureTask.run(FutureTask.java:138)

        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

        at java.lang.Thread.run(Thread.java:619)

    Caused by: java.lang.IllegalArgumentException: Cannot stringify null Node!

        at org.apache.ode.utils.DOMUtils.domToString(DOMUtils.java:420)

        at org.apache.ode.bpel.runtime.ScopeFrame.initializeVariable(ScopeFrame.java:236)

        at org.apache.ode.bpel.runtime.ACTIVITY.initializeVariable(ACTIVITY.java:166)

        at org.apache.ode.bpel.runtime.INVOKE$2.onResponse(INVOKE.java:121)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.apache.ode.jacob.vpu.JacobVPU$JacobThreadImpl.run(JacobVPU.java:451)

        ... 16 more

  • 2. Failure during invoke: Unspecified
    Gary Brown Master

    Might be worth setting tracing on packages org.jboss.ws and org.jboss.wsf aswell, to see why the message is being received as a null.

  • 3. Failure during invoke: Unspecified
    Igor JStarter Novice

    Yes, that was what i needed to get a smart log ...

     

    Does that mean that my imported (changed) WSDL is not ok ?

    But I imported the same wsdl into SoapUI... works well ..

     

    2011-01-27 10:32:15,883 TRACE [org.jboss.ws.core.CommonMessageContext] (ODEServer-3) get(org.jboss.ws.DOMContentCanonicalNormalization): null

    2011-01-27 10:32:15,884 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-3) getChildNodes

    2011-01-27 10:32:15,884 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-3) getChildNodes

    2011-01-27 10:32:15,970 TRACE [org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP] (ODEServer-3) Read input stream with metadata={X-AspNet-Version=[2.0.50727], Date=[Thu, 27 Jan 2011 09:44:07 GMT], Content-Length=[698], MicrosoftOfficeWebServer=[5.0_Pub], ResponseCodeMessage=Internal Server Error, ResponseCode=500, Content-Type=[text/xml; charset=utf-8], Connection=[close], X-Powered-By=[ASP.NET], Server=[Microsoft-IIS/6.0], Protocol=HTTP/1.1, Cache-Control=[private]}

    2011-01-27 10:32:15,971 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-3) [X-AspNet-Version=2.0.50727]

    2011-01-27 10:32:15,971 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-3) [Date=Thu, 27 Jan 2011 09:44:07 GMT]

    2011-01-27 10:32:15,972 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-3) [Content-Length=698]

    2011-01-27 10:32:15,972 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-3) [MicrosoftOfficeWebServer=5.0_Pub]

    2011-01-27 10:32:15,972 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-3) [Content-Type=text/xml; charset=utf-8]

    2011-01-27 10:32:15,973 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-3) [Connection=close]

    2011-01-27 10:32:15,973 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-3) [X-Powered-By=ASP.NET]

    2011-01-27 10:32:15,973 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-3) [Server=Microsoft-IIS/6.0]

    2011-01-27 10:32:15,973 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-3) [Cache-Control=private]

    2011-01-27 10:32:15,974 DEBUG [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-3) createMessage: [contentType=text/xml; charset=utf-8]

    2011-01-27 10:32:15,974 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-3) createMessage

    <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><s:Fault><faultcode xmlns:a="http://schemas.microsoft.com/ws/2005/05/addressing/none">a:ActionNotSupported</faultcode><faultstring xml:lang="sl-SI">The message with Action '' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver.  Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).</faultstring></s:Fault></s:Body></s:Envelope>

    2011-01-27 10:32:15,977 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-3) Using style: document

    2011-01-27 10:32:15,978 TRACE [org.jboss.wsf.common.DOMUtils] (ODEServer-3) createElement {http://schemas.xmlsoap.org/soap/envelope/}s:Envelope

    2011-01-27 10:32:15,978 TRACE [org.jboss.wsf.common.DOMUtils] (ODEServer-3) createElement {http://schemas.xmlsoap.org/soap/envelope/}s:Body

    2011-01-27 10:32:15,994 TRACE [org.jboss.wsf.common.DOMUtils] (ODEServer-3) createElement {http://schemas.xmlsoap.org/soap/envelope/}s:Fault

    2011-01-27 10:32:16,016 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-3) getChildNodes

    2011-01-27 10:32:16,016 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-3) -----------------------------------

    2011-01-27 10:32:16,017 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-3) Transitioning from XML_VALID to DOM_VALID

    2011-01-27 10:32:16,017 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-3) removeContents

    2011-01-27 10:32:16,017 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-3) getChildElements

    2011-01-27 10:32:16,017 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-3) getChildNodes

    2011-01-27 10:32:16,018 TRACE [org.jboss.wsf.common.DOMUtils] (ODEServer-3) createElement {}faultcode

    2011-01-27 10:32:16,022 TRACE [org.jboss.ws.core.soap.SOAPFaultImpl] (ODEServer-3) convertToFaultElement : org.jboss.ws.core.soap.SOAPFaultElementImpl@f0a3a5[[faultcode: null]]

    2011-01-27 10:32:16,023 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-3) addChildElement: org.jboss.ws.core.soap.SOAPFaultElementImpl@f0a3a5[[faultcode: null]]

    2011-01-27 10:32:16,023 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-3) appendChild: org.jboss.ws.core.soap.SOAPFaultElementImpl@f0a3a5[[faultcode: null]]

    2011-01-27 10:32:16,023 TRACE [org.jboss.wsf.common.DOMUtils] (ODEServer-3) createElement {}faultstring

    2011-01-27 10:32:16,024 TRACE [org.jboss.ws.core.soap.SOAPFaultImpl] (ODEServer-3) convertToFaultElement : org.jboss.ws.core.soap.SOAPFaultElementImpl@87bebd[[faultstring: null]]

    2011-01-27 10:32:16,024 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-3) addChildElement: org.jboss.ws.core.soap.SOAPFaultElementImpl@87bebd[[faultstring: null]]

    2011-01-27 10:32:16,024 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-3) appendChild: org.jboss.ws.core.soap.SOAPFaultElementImpl@87bebd[[faultstring: null]]

    2011-01-27 10:32:16,025 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-3) -----------------------------------

    2011-01-27 10:32:16,025 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-3) getChildNodes

    2011-01-27 10:32:16,027 TRACE [org.jboss.ws.core.MessageTrace] (ODEServer-3) Incoming Response Message

    <s:Envelope xmlns:s='http://schemas.xmlsoap.org/soap/envelope/'>

    <s:Body>

      <s:Fault xmlns:s='http://schemas.xmlsoap.org/soap/envelope/'>

       <faultcode xmlns:a='http://schemas.microsoft.com/ws/2005/05/addressing/none'>a:ActionNotSupported</faultcode>

       <faultstring xml:lang='sl-SI'>The message with Action &apos;&apos; cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver.  Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).</faultstring>

      </s:Fault>

    </s:Body>

    </s:Envelope>

  • 4. Failure during invoke: Unspecified
    Igor JStarter Novice

    and the imported wsdl:

    <wsdl:definitions

                    targetNamespace="http://uritemp.org/"

                    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"

                    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

                    xmlns:tns="http://uritemp.org/"

                    xmlns:xsd="http://www.w3.org/2001/XMLSchema"

                    xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract"

                    xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"

                    xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype">

    <wsdl:types>

    <xsd:schema targetNamespace="http://uritemp.org/Imports">

    <xsd:import schemaLocation="PspService0.xsd" namespace="http://uritemp.org/"/>

    <xsd:import schemaLocation="PspService1.xsd" namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>

    <xsd:import schemaLocation="PspService2.xsd" namespace="http://schemas.microsoft.com/2003/10/Serialization/Arrays"/>

    </xsd:schema>

    </wsdl:types>

    <wsdl:message name="IPspService_ProcessMessage_InputMessage">

    <wsdl:part name="parameters" element="tns:ProcessMessage"/>

    </wsdl:message>

    <wsdl:message name="IPspService_ProcessMessage_OutputMessage">

    <wsdl:part name="parameters" element="tns:ProcessMessageResponse"/>

    </wsdl:message>

    <wsdl:message name="IPspService_ProcessSingleMessage_InputMessage">

    <wsdl:part name="parameters" element="tns:ProcessSingleMessage"/>

    </wsdl:message>

    <wsdl:message name="IPspService_ProcessSingleMessage_OutputMessage">

    <wsdl:part name="parameters" element="tns:ProcessSingleMessageResponse"/>

    </wsdl:message>

     

    <wsdl:portType msc:usingSession="false" name="IPspService">

    <wsdl:operation name="ProcessMessage">

    <wsdl:input wsaw:Action="http://uritemp.org/IPspService/ProcessMessage" message="tns:IPspService_ProcessMessage_InputMessage"/>

    <wsdl:output wsaw:Action="http://uritemp.org/IPspService/ProcessMessageResponse" message="tns:IPspService_ProcessMessage_OutputMessage"/>

    </wsdl:operation>

    <wsdl:operation name="ProcessSingleMessage">

    <wsdl:input wsaw:Action="http://uritemp.org/IPspService/ProcessSingleMessage" message="tns:IPspService_ProcessSingleMessage_InputMessage"/>

    <wsdl:output wsaw:Action="http://uritemp.org/IPspService/ProcessSingleMessageResponse" message="tns:IPspService_ProcessSingleMessage_OutputMessage"/>

    </wsdl:operation>

    </wsdl:portType>

     

    <wsdl:binding name="serviceEndpoint" type="tns:IPspService">

     

    <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>

    <wsdl:operation name="ProcessMessage">

    <soap:operation soapAction="http://uritemp.org/IPspService/ProcessMessage" style="document"/>

    <wsdl:input>

    <soap:body use="literal"/>

    </wsdl:input>

    <wsdl:output>

    <soap:body use="literal"/>

    </wsdl:output>

    </wsdl:operation>

    <wsdl:operation name="ProcessSingleMessage">

    <soap:operation soapAction="http://uritemp.org/IPspService/ProcessSingleMessage" style="document"/>

    <wsdl:input>

    <soap:body use="literal"/>

    </wsdl:input>

    <wsdl:output>

    <soap:body use="literal"/>

    </wsdl:output>

    </wsdl:operation>

    </wsdl:binding>

     

    <wsdl:service name="PspService">

    <wsdl:port name="serviceEndpoint" binding="tns:serviceEndpoint">

    <soap:address location="http://PspService.svc"/>

    </wsdl:port>

    </wsdl:service>

     

     

       <plnk:partnerLinkType name="RaLinkType">

          <plnk:role name="RaProvider" portType="tns:IPspService"/>

      </plnk:partnerLinkType>

  • 5. Failure during invoke: Unspecified
    Igor JStarter Novice

    I believe that's the matter of : Call into WCF Service WITHOUT specifying SoapAction ...

    How to solve that ?

  • 6. Failure during invoke: Unspecified
    Igor JStarter Novice

    How can i get RiftSaw to insert something like

     

    POST http://psplatform.dyndns.org/OpcWeb/PspService.svc HTTP/1.1

    Accept-Encoding: gzip,deflate

    Content-Type: text/xml;charset=UTF-8

    SOAPAction: "http://tempuri.org/IPspService/ProcessSingleMessage"

    User-Agent: Jakarta Commons-HttpClient/3.1

    Host: psplatform.dyndns.org

    Content-Length: 953

     

    or just somehow setProperty name="soapaction" value="http::/namespace/WSDLmethod

     

    I think that could solve the problem... I hope RiftSaw hasn't issues with invoking .NET services ...

  • 7. Failure during invoke: Unspecified
    Gary Brown Master

    Hi Igor

     

    You need to put the soap action into the WSDL representing the service being called.

     

    We have an integration test that invokes a .NET service, and it required the soap actions to be added to the wsdl before it would work, e.g.:

     

      <wsdl:binding name="Service1Soap" type="tns:Service1Soap">

        <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>

        <wsdl:operation name="nextDay">

          <soap:operation soapAction="http://soa.jboss.com/nextDay" style="document"/>

          <wsdl:input>

            <soap:body use="literal"/>

          </wsdl:input>

          <wsdl:output>

            <soap:body use="literal"/>

          </wsdl:output>

        </wsdl:operation>

         .....

     

    Regards

    Gary

  • 8. Failure during invoke: Unspecified
    Igor JStarter Novice

    Hey Gary...

     

    Sorry... but I don't see any difference from my operation in the posted wsdl above

    (and after TRACE enabled i see it in the log too - so i think it's not erasing it):

     

      <wsdl:binding name="serviceEndpoint" type="tns:IPspService">

        <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>

        <wsdl:operation name="ProcessMessage">

          <soap:operation soapAction="http://tempuri.org/IPspService/ProcessMessage" style="document"/>

          <wsdl:input>

            <soap:body use="literal"/>

          </wsdl:input>

          <wsdl:output>

            <soap:body use="literal"/>

          </wsdl:output>

        </wsdl:operation>

        <wsdl:operation name="ProcessSingleMessage">

          <soap:operation soapAction="http://tempuri.org/IPspService/ProcessSingleMessage" style="document"/>

          <wsdl:input>

            <soap:body use="literal"/>

          </wsdl:input>

          <wsdl:output>

            <soap:body use="literal"/>

          </wsdl:output>

        </wsdl:operation>

      </wsdl:binding>

     

    Idea ?

  • 9. Failure during invoke: Unspecified
    Gary Brown Master

    Can you include the log for the message trace of the request - as the soap action should be included.

  • 11. Failure during invoke: Unspecified
    Igor JStarter Novice

    I posted my log under my profile - documents and set it visible to all...  (i don't know how to upload to this reply)

     

    Please... take a look...

     

    The outgoing request message from the log:

    2011-01-27 10:53:48,732 TRACE [org.jboss.ws.core.MessageTrace] (ODEServer-4) Outgoing Request Message

    <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>

    <env:Header/>

    <env:Body>

      <ProcessSingleMessage xmlns='http://tempuri.org/'>

       <p:iServiceID xmlns:p='http://tempuri.org/'>2</p:iServiceID>

       <p:iTypeID xmlns:p='http://tempuri.org/'>2</p:iTypeID>

       <p:calTermin xmlns:p='http://tempuri.org/'>2011-01-29T00:00:00.000+01:00</p:calTermin>

       <p:sMessage xmlns:p='http://tempuri.org/'>2</p:sMessage>

       <p:iKey xmlns:p='http://tempuri.org/'>2</p:iKey>

       <p:sValue xmlns:p='http://tempuri.org/'>2</p:sValue>

       <p:sTransactionID xmlns:p='http://tempuri.org/'>2</p:sTransactionID>

       <p:sDomoticIP xmlns:p='http://tempuri.org/'>2</p:sDomoticIP>

       <p:sUsername xmlns:p='http://tempuri.org/'>2</p:sUsername>

       <p:sPassword xmlns:p='http://tempuri.org/'>2</p:sPassword>

      </ProcessSingleMessage>

    </env:Body>

    </env:Envelope>

  • 12. Failure during invoke: Unspecified
    Gary Brown Master

    According to:

     

    2011-01-27 10:32:14,314 DEBUG [org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder] (ODEServer-3) END buildMetaData:

    UnifiedMetaData:

    implementation: 3.2.1.GA

    deploymentName: null

     

    (truncated)

     

    authMethod=null

    properties={}

     

    OperationMetaData:

    qname={http://tempuri.org/}ProcessMessage

    javaName={http://tempuri.org/}ProcessMessage

    style=document/literal/WRAPPED

    oneWay=false

    soapAction=http://tempuri.org/IPspService/ProcessMessage

     

    OperationMetaData:

    qname={http://tempuri.org/}ProcessSingleMessage

    javaName={http://tempuri.org/}ProcessSingleMessage

    style=document/literal/WRAPPED

    oneWay=false

    soapAction=http://tempuri.org/IPspService/ProcessSingleMessage

    2011-01-27 10:32:14,340 DEBUG [org.jboss.ws.metadata.umdm.EndpointMetaData] (ODEServer-3) Create new config [name=Standard Client,file=META-INF/standard-jaxws-client-config.xml]

     

     

    the soapAction has been retrieved from the WSDL. (Namespace is different to your wsdl, but I assume that is just global replace of the actual domain).

     

    What version of jbossws are you using?

  • 13. Failure during invoke: Unspecified
    Igor JStarter Novice

    I was just talking with my partner... he will merge the 2 wsdls into one...   If there was a problem, i will see in some minutes...

     

    I'm using jboss Native ws - 3.2.1 GA (default riftsaw 2.1)...

  • 14. Failure during invoke: Unspecified
    Gary Brown Master

    The only thing I can suggest is posting on the jbossws forum, and asking whether there is further tracing that can be enabled to find out whether the soapAction is being included as part of the outbound HTTP/SOAP request.

1 2 3 Previous Next