Axis 1.7.4 with Rampart 1.7 Outflow does not complete
Can anyone tell me if this looks like and Axis or Rampart bug?
The Axis OutFlow Phase does not complete correctly. We are using Axis2 1.7.4 with Rampart 1.7.0. We encountered a situation where the OutFlow phase does not appear to complete properly, it aborts and goes through the 'flowComplete()'
sequence without executing the remaining phases.
This is triggered from a SOAP request with a username/password security header. The web service request is properly handled by the web service (Axis .aar) and a response is issued. The response is formed properly but as it goes through
the Axis OutFlow something goes wrong.
Our Axis2.xml defines a 'PostSecurity' phase handler after 'Security' (see below).
Phase 'Security' is invoked, which invokes the Rampart handler, but there is no 'post-condition' message for 'Security' and the 'PostSecurity' phase is not invoked. This results in a bad message header and an exception being thrown for
a bad signature because our code did not get executed.
My question is; does this indicate an unhandled exception possibly occurring in the Axis phase handling code? or is there some normal condition (error) that can cause this?
The Axis2 logs show this sequence of events:
<Soap Response message being processed through 'OutFlow'>
Checking pre-condition for Phase "MessageOut"
Invoking phase "MessageOut"
Invoking Handler 'AddressingOutHandler' in Phase 'MessageOut'
Addressing is disabled. Not adding WS-Addressing headers.
Checking post-conditions for phase "MessageOut"
Checking pre-condition for Phase "SecurityPolicyDetermination"
Invoking phase "SecurityPolicyDetermination"
Invoking Handler 'AuthenticationHandler' in Phase 'SecurityPolicyDetermination'
SoapAction is (http://my/oe/MediationService/MediationPortType/QueryAllSchemaRequestResponse
Checking post-conditions for phase "SecurityPolicyDetermination"