[ http://issues.apache.org/jira/browse/AXIS2-1849?page=comments#action_12458516 ] Ali Sadik Kumlali commented on AXIS2-1849: ------------------------------------------
Hi Dimuthu, Thank you very much for your great effort. With your help, I noticed that the problem was a copy-paste issue found in my receiver :( Please look at the stack trace: [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: ... org.apache.axis2.transport.jms.AxisMdb is my custom receiver that is mostly created from JMSMessageReceiver. Until another eye(yours actually :)) was on the issue, I hadn't recognize the error message "JMS Worker [...] Encountered an Axis Fault : " was written by my receiver. I thought it was catched by a worker which my receiver didn't have a relation anymore. So the issue can be closed. Thanks a lot again! > Security exception is swallowed > ------------------------------- > > Key: AXIS2-1849 > URL: http://issues.apache.org/jira/browse/AXIS2-1849 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: modules > Affects Versions: 1.1 > Environment: Windows XP Professional, JDK 1.4.2.12-b03 > Reporter: Ali Sadik Kumlali > Assigned To: Dimuthu Leelarathne > > 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). > Regards, > 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: > org.apache.ws.security.WSSecurityException: The signature > verification f > ailed > org.apache.axis2.AxisFault: WSDoAllReceiver: security processing failed; > nested > exception is: > org.apache.ws.security.WSSecurityException: The signature > verification f > ailed > at > org.apache.rampart.handler.WSDoAllReceiver.processBasic(WSDoAllReceiv > er.java:275) > at > org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllRece > iver.java:98) > at > org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java: > 74) > at org.apache.axis2.engine.Phase.invoke(Phase.java:381) > at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:521) > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:485) > at org.apache.axis2.transport.jms.AxisMdb.onMessage(AxisMdb.java:245) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
