axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jorge Fernandez <>
Subject Check Signature confirmation: stored SV vector not empty
Date Mon, 30 Jul 2007 16:15:09 GMT

I'm getting that exception. I'm using axis2 1.2 and rampart 1.2 in both client and server
sides. I receive that exception in the client.

The first thing I can see in my client is : 
30-jul-2007 16:46:51 verify
INFO: Verification successful for URI "#Timestamp-19502806"

That is the Timestamp sent back from the server. It comes signed even if in my server policy
I don't say that it should be signed.

I searched for

<wsse:SignatureConfirmation> elements in the response as I could see
and I didn't find any.

When I used rampart configuration without policy, I didn't have
any problem. Actually is what I'm using at the client side 
for sending the messages to the sever.

In the server, I'm using sample3 policy from rampart distribution.

Can anybody tell me why is this happening??


Jorge Fernández

This is the stack trace:

org.apache.axis2.AxisFault: WSHandler: Check Signature confirmation: stored SV vector not
    at org.apache.rampart.handler.WSDoAllReceiver.processMessage(
    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.description.OutInAxisOperationClient.send(
    at org.apache.axis2.description.OutInAxisOperationClient.execute(
    at client.Medici_LinkSOAP12PortStub.validateSystem(
    at client.ClientUtilities.validateSystemTest(
    at client.Client.main(
Caused by: WSHandler: Check Signature confirmation:
stored SV vector not empty
    at org.apache.rampart.handler.WSDoAllReceiver.processBasic(
    at org.apache.rampart.handler.WSDoAllReceiver.processMessage(
    ... 9 more


Sé un Mejor Amante del Cine
¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.

View raw message