axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ali Sadik Kumlali (JIRA)" <>
Subject [jira] Created: (AXIS2-1849) Security exception is swallowed
Date Fri, 08 Dec 2006 14:46:28 GMT
Security exception is swallowed

                 Key: AXIS2-1849
             Project: Apache Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: modules
    Affects Versions: 1.1
         Environment: Windows XP Professional, JDK
            Reporter: Ali Sadik Kumlali

I need to catch the exception occured in securiy phase. But it seems Rampart just logs the
exception and  not propagate to the transport receiver. Thus, I'm not able to catch it and
notify the sender.

Here is my scenario:

- My WSDL has input only (one-way) operations.
- Client sends signed messages by invoking appropriate method of generated stub.
- Service's keystore doesn't have the public certificate of the client
- Rampart logs the exception[1] BUT doesn't throw it.

Since I wrote my own transport receiver, I'm able to catch any exception(including RuntimeException)
thrown through the execution path(transport receiver -> phases/modules -> message receiver).


Ali Sadik Kumlali

[1] [ERROR][2006-12-08 14:40:48,535] org.apache.axis2.transport.jms.AxisMdb - JMS Wo
rker [JMS Session Delivery Thread] Encountered an Axis Fault : WSDoAllReceiver:
security processing failed; nested exception is: The signature verification f
org.apache.axis2.AxisFault: WSDoAllReceiver: security processing failed; nested
exception is: The signature verification f
        at org.apache.rampart.handler.WSDoAllReceiver.processBasic(WSDoAllReceiv
        at org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllRece
        at org.apache.rampart.handler.WSDoAllHandler.invoke(
        at org.apache.axis2.engine.Phase.invoke(
        at org.apache.axis2.engine.AxisEngine.invoke(
        at org.apache.axis2.engine.AxisEngine.receive(
        at org.apache.axis2.transport.jms.AxisMdb.onMessage(

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message