Thanks for your help! With your workaround, it is working. Beacuse my .NET Webservice contains some errors, it responded sometimes with SOAP Fault messages. These caused a RuntimeException in JBPM BPEL: 16:04:48,531 ERROR [StartListener] could not deliver request | org.jbpm.graph.def.DelegationException | at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:299) | at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:293) | at org.jbpm.bpel.def.BpelDefinition.startProcessInstance(BpelDefinition.java:58) | at org.jbpm.bpel.service.messager.StartListener.onMessage(StartListener.java:120) | at org.jboss.mq.SpyMessageConsumer.run(SpyMessageConsumer.java:707) | at java.lang.Thread.run(Thread.java:595) | Caused by: org.jbpm.graph.def.DelegationException | at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:299) | at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:293) | at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:293) | at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:293) | at org.jbpm.bpel.def.Activity.enter(Activity.java:89) | at org.jbpm.graph.def.Transition.take(Transition.java:92) | at org.jbpm.graph.def.Node.leave(Node.java:349) | at org.jbpm.bpel.def.Activity.leave(Activity.java:149) | at org.jbpm.bpel.def.ProcessInstanceStarter.visit(ProcessInstanceStarter.java:42) | at org.jbpm.bpel.def.Receive.accept(Receive.java:67) | at org.jbpm.bpel.def.ProcessInstanceStarter.visit(ProcessInstanceStarter.java:81) | at org.jbpm.bpel.def.Sequence.accept(Sequence.java:84) | at org.jbpm.bpel.def.ProcessInstanceStarter.visit(ProcessInstanceStarter.java:28) | at org.jbpm.bpel.def.BpelDefinition.startProcessInstance(BpelDefinition.java:55) | ... 3 more | Caused by: org.jbpm.graph.def.DelegationException | at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:299) | at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:293) | at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:293) | at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:293) | at org.jbpm.bpel.def.Activity.enter(Activity.java:89) | at org.jbpm.graph.def.Transition.take(Transition.java:92) | at org.jbpm.graph.def.Node.leave(Node.java:349) | at org.jbpm.bpel.def.Activity.leave(Activity.java:149) | at org.jbpm.bpel.def.Assign.execute(Assign.java:36) | at org.jbpm.bpel.def.Activity.enter(Activity.java:84) | ... 12 more | Caused by: java.lang.RuntimeException: no wsdl fault matches the contents of the soap detail element: [EMAIL PROTECTED]: null]] | at org.jbpm.bpel.service.soap.PortCaller.readFault(PortCaller.java:502) | at org.jbpm.bpel.service.soap.PortCaller.call(PortCaller.java:97) | at org.jbpm.bpel.service.messager.MessagerSession.invoke(MessagerSession.java:140) | at org.jbpm.bpel.service.def.Invoker.invoke(Invoker.java:80) | at org.jbpm.bpel.def.Invoke.execute(Invoke.java:27) | at org.jbpm.bpel.def.Activity.enter(Activity.java:84) | ... 17 more
Looking at the code, I think, the SOAP faults generated by Microsoft IIS do not correspond to the SOAP faults jbpm bpel expects. I don't know if it is possible to make IIS produce SOAP faults jbpm understands, but if not, it would be great if jbpm bpel would provide some information of the SOAP faults received from MS IIS instead of simply throwing a RuntimeException. Here are two of the SOAP fault messages that caused RuntimeExceptions: <soapenv:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> | <soap:Header> | <wsa:Action xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing";> | http://schemas.xmlsoap.org/ws/2004/03/addressing/fault | </wsa:Action> | <wsa:MessageID> | uuid:c45ff8fa-f54e-4ceb-99ef-d1458b39dac0 | </wsa:MessageID> | <wsa:RelatesTo> | uuid:a0f43bce-492f-4380-91be-ab96cd7d3586 | </wsa:RelatesTo> | <wsa:To> | http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous | </wsa:To> | <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";> | <wsu:Timestamp wsu:Id="Timestamp-9aff2810-527c-4752-b4ff-72f624262952" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";> | <wsu:Created> | 2006-01-11T15:05:14Z | </wsu:Created> | <wsu:Expires> | 2006-01-11T15:10:14Z | </wsu:Expires> | </wsu:Timestamp> | </wsse:Security> | </soap:Header> | <soap:Body> | <soap:Fault> | <faultcode> | soap:Server | </faultcode> | <faultstring> | Server was unable to process request. ---> Object reference not set to an instance of an object. | </faultstring> | <detail> | </detail> | </soap:Fault> | </soap:Body> | </env:soapenv:Envelope> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> | <soap:Header> | <wsa:Action xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing";> | http://schemas.xmlsoap.org/ws/2004/03/addressing/fault | </wsa:Action> | <wsa:MessageID> | uuid:2f3d64bd-32b1-481d-a0c4-38270f2ba4b9 | </wsa:MessageID> | <wsa:RelatesTo> | uuid:d767334d-6c39-4e69-b1ac-d4adb7006af2 | </wsa:RelatesTo> | <wsa:To> | http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous | </wsa:To> | <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";> | <wsu:Timestamp wsu:Id="Timestamp-1043946e-37d6-4d3e-88a3-b03670f0ea71" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";> | <wsu:Created> | 2006-01-11T13:44:54Z | </wsu:Created> | <wsu:Expires> | 2006-01-11T13:49:54Z | </wsu:Expires> | </wsu:Timestamp> | </wsse:Security> | </soap:Header> | <soap:Body> | <soap:Fault> | <faultcode> | soap:Client | </faultcode> | <faultstring> | Server did not recognize the value of HTTP Header SOAPAction: . | </faultstring> | <detail> | </detail> | </soap:Fault> | </soap:Body> | </soapenv:Envelope> Regards, Martin View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916915#3916915 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916915 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
