-
15. Failure during invoke: Unspecified
izgur Jan 27, 2011 8:44 AM (in response to izgur)No... nothing changes...
so it is not a namespace problem and not a dateTime problem for sure...
The WSDL:
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions name="PspService"
targetNamespace="http://tempuri.org/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"
xmlns:tns="http://tempuri.org/"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy"
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:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:wsa10="http://www.w3.org/2005/08/addressing"
xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex"
xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype">
<wsdl:types>
<xsd:schema targetNamespace="http://tempuri.org/Imports">
<xsd:import schemaLocation="PspService0.xsd" namespace="http://tempuri.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_SayHello_InputMessage">
<wsdl:part name="parameters" element="tns:SayHello"/>
</wsdl:message>
<wsdl:message name="IPspService_SayHello_OutputMessage">
<wsdl:part name="parameters" element="tns:SayHelloResponse"/>
</wsdl:message>
<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="SayHello">
<wsdl:input wsaw:Action="http://tempuri.org/IPspService/SayHello" message="tns:IPspService_SayHello_InputMessage"/>
<wsdl:output wsaw:Action="http://tempuri.org/IPspService/SayHelloResponse" message="tns:IPspService_SayHello_OutputMessage"/>
</wsdl:operation>
<wsdl:operation name="ProcessMessage">
<wsdl:input wsaw:Action="http://tempuri.org/IPspService/ProcessMessage" message="tns:IPspService_ProcessMessage_InputMessage"/>
<wsdl:output wsaw:Action="http://tempuri.org/IPspService/ProcessMessageResponse" message="tns:IPspService_ProcessMessage_OutputMessage"/>
</wsdl:operation>
<wsdl:operation name="ProcessSingleMessage">
<wsdl:input wsaw:Action="http://tempuri.org/IPspService/ProcessSingleMessage" message="tns:IPspService_ProcessSingleMessage_InputMessage"/>
<wsdl:output wsaw:Action="http://tempuri.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="SayHello">
<soap:operation soapAction="http://tempuri.org/IPspService/SayHello" style="document"/>
<wsdl:input><soap:body use="literal"/></wsdl:input>
<wsdl:output><soap:body use="literal"/></wsdl:output>
</wsdl:operation><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>
<wsdl:service name="PspService">
<wsdl:port name="serviceEndpoint" binding="tns:serviceEndpoint">
<soap:address location="http://platform/PspService.svc"/>
</wsdl:port>
</wsdl:service>
<plnk:partnerLinkType name="RaLinkType">
<plnk:role name="RaProvider" portType="tns:IPspService"/>
</plnk:partnerLinkType>
</wsdl:definitions>
So.. it must be JBOSS - .NET problem...
Any idea what I can do any more?
-
16. Failure during invoke: Unspecified
objectiser Jan 27, 2011 9:02 AM (in response to izgur)As I put in my last post, you will need to contact the jbossws project to find out what additional diagnostics you can use to determine whether the soapAction is being passed.
The trace log you uploaded shows that it is loading the soapAction as part of the external service's WSDL, prior to sending the request - but does not provide enough information as to whether it is actually sending the soapAction.
-
17. Failure during invoke: Unspecified
izgur Jan 27, 2011 9:02 AM (in response to izgur)I got one more reply... apache team
It's very strange, ODE-260 was fixed a long time ago in version 1.2,and now I can see, that version 1.3.3 still contains this bug. I thinkmaintainer didn't apply all my patches, missed some fixes, so thisparticular case is still here. Well, in bug report [1] there is cleardescription when this bug appears, it appears when external servicereturns empty SOAP message without body and without header.
<?xml version='1.0' encoding='utf-8'?>
<soapenv:Envelopexmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body />
</soapenv:Envelope>
You cannot work around this bug, you have to either return some dummydata or header from your external service, or apply patch [2] andrecompile ODE runtime. I'm going to reopen this bug report to notifydeveloper, that this bug still persist.
Just one note, I work with JPA DAO, and as I see you work with JBoss,and so I think you work with Hibernate. If that so, you can try to workaround with just disabling debug logging for class " org.apache.ode.bpel.runtime.
ScopeFrame",I don't know but it can help you.
Is my issue solveable ?:)
-
18. Failure during invoke: Unspecified
objectiser Jan 27, 2011 9:09 AM (in response to izgur)From a quick inspection of the patch, this just seems to be a workaround to overcome the impact of the fault response.
It would be good to have this patch applied, so that null values don't result in exceptions (in case they are expected, however in your case I don't think you are expecting a null value.
-
19. Failure during invoke: Unspecified
izgur Jan 28, 2011 3:05 AM (in response to objectiser)Hey !
I got no answer on the jboss web services forum...
But I used the time and installed tcpdump... and made a pcap capture...
The SoapAction is not sending !!!
In the HTTP post i see:
Connection: keep-alive
Content-Type: text/xml; charset=UTF-8
Host: psplatform.dyndns.org
SOAPAction: ""
Transfer-Encoding: chunked
Any idea why it's not included? How cai i set the SOAPAction ?
Regards, Igor!
-
20. Failure during invoke: Unspecified
izgur Jan 28, 2011 4:15 AM (in response to izgur)Hm... writing a proxy which inserts the soapaction header?
If your client isn't sending that now, and aren't willing to change it, you might be able to write some sort of proxy that adds the header and passes along the request as a stopgap solution. Might be easier than rewriting the server-side handler.
Common, there must be a solution on JBoss ?
-
21. Failure during invoke: Unspecified
objectiser Jan 28, 2011 4:36 AM (in response to izgur)As I mentioned before we have an integration test that invokes a .NET service:
The only difference I can see is that the integration tests run against JBossWS-native 3.2.2.GA. So you might want to try using that version to see if that makes any difference.
Regards
Gary
-
22. Failure during invoke: Unspecified
izgur Jan 28, 2011 5:11 AM (in response to objectiser)Sorry for these newbie questions... but how do I upgrade that it works for sure... I've got a running server...
1. stop server
2. download jbossws-native-3.2.2.GA to riftsaw/install/ws-stack
3. riftsaw/install/ ant deploy -Ddatabase=mysql -Dws.stack=native -Dws.version=3.2.2.GA
4. run server
Is that all ? Without cleaning the 3.2.1 package, ...
-
23. Failure during invoke: Unspecified
objectiser Jan 28, 2011 5:25 AM (in response to izgur)You don't need to download the jbossws stack - this will be automatically done when installing.
So just stop the server then do:
ant undeploy -Ddatabase=mysql
and then
ant deploy -Ddatabase=mysql -Dws.version=3.2.2.GA
Regards
Gary
-
24. Failure during invoke: Unspecified
izgur Jan 28, 2011 6:06 AM (in response to objectiser)Thank you Gary! There were no problems upgrading to 3.2.2.GA.
But... nothing has changed ! the log, the send request... everything the same...
I dont know if u saw what i was told on the WS forum: http://community.jboss.org/thread/161847
Any idea how I could do that double check ??
About your test example with the doNet.wsdl... the service isn't working anymore... so i can't test it ...
-
25. Failure during invoke: Unspecified
objectiser Jan 28, 2011 6:41 AM (in response to izgur)Igor JStarter wrote:
Any idea how I could do that double check ??
Sorry don't know - best solution might be to provide a simple test case that we (and the jbossws team) can run.
Igor JStarter wrote:
About your test example with the doNet.wsdl... the service isn't working anymore... so i can't test it ...
Just checked - the service runs within our vpn, so that is why you can't access it. But the test does run successfully as part of the integration tests.
-
26. Failure during invoke: Unspecified
izgur Jan 28, 2011 10:43 AM (in response to objectiser)Can u tell me 100% that when calling your doNET.wsdl your SOAPAction is not empty ?
About the test case... The external web service is a .svc service... And for a test... I'm invoking a helloworld now returning hello + string..
So i think it's easy to test. If you don't have a svc?wsdl, then I can send you by PRIVATE my partners, ready to copy to bpel...
-
27. Failure during invoke: Unspecified
mbaluch Jan 31, 2011 5:19 AM (in response to izgur)Hi Igor
what version of Riftsaw are you using? All I saw in your posts is Riftsaw 2.1... The issue metioned by Gary was found in Riftsaw 2.1.0.Final and fixed in Riftsaw 2.1.1.Final (see https://issues.jboss.org/browse/RIFTSAW-279).
If you're alredy using 2.1.1.Final or higher then please disregard this post.
Regards
Marek
-
28. Failure during invoke: Unspecified
izgur Jan 31, 2011 7:09 AM (in response to mbaluch)Thank you very much for your reply... We assumed it was a bug, but now we are sure ...
Does anyone know what was changed in 2.1.1 ?
Do I have a chance to update my RiftSaw 2.1.0 to work ?
-
29. Failure during invoke: Unspecified
objectiser Jan 31, 2011 9:10 AM (in response to izgur)Hi Igor
I'm in a workshop so only have limited email/internet access.
Can you try upgrading to RiftSaw 2.2.0.Final?
Regards
Gary