| Author |
Message
|
| cadenza |
 Posted: Wed Jun 26, 2013 8:27 pm Post subject: Can SOAPInput node handle WSA in Gateway mode |
 |
|
Apprentice
Joined: 01 Jun 2004
Posts: 48
|
Hi,
I am using WMB 7.0.0.2. My flow is a SOAPInput -> Compute -> SOAPReply
Operation Mode - Gateway
Use WS-Addressing & Place to Local Env both are checked.
I have tried using SOAP UI (v 4.5.2) with WS-Addressing set for one way to get HTTP 202 status code.
The flow dies in the SOAPInput Node. It returns 202 code if I uncheck Use WS-Addressing.
Here is the error trace.
| Code: |
BIP3701E: A Java exception was thrown whilst calling the Java JNI method ''TomcatNodeRegistrationUtil_invoke
Axis2''. The Java exception was ''org.apache.axis2.AxisFault: Failed to send a fault reply message''. The Java stack trace was ''Frame : 0 org.apache.axis2.AxisFault: F
ailed to send a fault reply message| @: com.ibm.broker.axis2.Axis2Invoker.processExceptionInInboundPipelineProcessing(Axis2Invoker.java:3091)| @: com.ibm.broker.axis2.A
xis2Invoker.invokeAxis2(Axis2Invoker.java:2911)| @: com.ibm.broker.axis2.TomcatNodeRegistrationUtil.invokeAXIS2(TomcatNodeRegistrationUtil.java:474)|Frame : 1 org.apach
e.axis2.AxisFault: Can not find the transport sender : null| @: org.apache.axis2.util.MessageContextBuilder.setupCorrectTransportOut(MessageContextBuilder.java:382)| @:
org.apache.axis2.util.MessageContextBuilder.createFaultMessageContext(MessageContextBuilder.java:337)| @: com.ibm.broker.axis2.Axis2Invoker.handleAxis2Fault(Axis2Invok
er.java:3608)| @: com.ibm.broker.axis2.Axis2Invoker.processExceptionInInboundPipelineProcessing(Axis2Invoker.java:3081)| @: com.ibm.broker.axis2.Axis2Invoker.invokeAxis
2(Axis2Invoker.java:2911)| @: com.ibm.broker.axis2.TomcatNodeRegistrationUtil.invokeAXIS2(TomcatNodeRegistrationUtil.java:474)''.
|
Any thoughts on what is happening as the above issue does not let me know what was wrong in the message being sent. |
|
| Back to top |
|
 |
| mgk |
| Posted: Wed Jun 26, 2013 9:07 pm Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi.
Gateway mode should work with WsA. Please try a more recent fix pac to see if this problem has been resolved (I think it might have but I can't quite remember). If not, please raise a PMR.
Kind regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| vikas.bhu |
| Posted: Wed Jun 26, 2013 9:41 pm Post subject: |
|
|
Disciple
Joined: 17 May 2009
Posts: 159
|
|
| Back to top |
|
|
| ghoshly |
| Posted: Thu Jun 27, 2013 12:40 am Post subject: Error in 7.0.0.5 but not in 8.0.0.2 |
|
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
Similar error prevails in 7.0.0.5 as well but not in 8.0.0.2
In 8.0.0.2, even we check both the check box to use WS addressing and place WS addressing Headers in localenvironment, mentined above error is not present, but we do not get those headers in localEnvironment.
See below
| Code: |
LocalEnvironment
Destination
SOAP
Reply
ReplyIdentifier:BLOB:[B@3ba03ba
RouterList
DestinationData
labelName:CHARACTER:InvoiceExportRequest
SOAP
Input
Transport
HTTP
MaxClientWaitTime:INTEGER:180 |
|
|
| Back to top |
|
|
| ghoshly |
| Posted: Thu Jun 27, 2013 9:56 pm Post subject: Should we go ahead and raise PMR ? |
|
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
Should we go ahead and raise PMR on WMB 8.0.0.2 to get WS headers populated in LocalEnvironment tree?
Please help to identify any tweak needs to be done to get this working. |
|
| Back to top |
|
|
| mgk |
| Posted: Fri Jun 28, 2013 9:37 pm Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
The exception may be because you are trying to send a reply to a one-way message? try removing the SOAPReply node - if WsA detects a one-way message (because the reply to is wsa:none) they it will automatically send the reply from the Input node before the message makes it down the flow.
Kind regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
|
|
