Stefan
I suspect that your sequence named "fault" (i.e. the fault handler
sequence) has a <send/> mediator.. is this correct? Can you please share
your synapse.xml and log files (hopefully at level
"log4j.category.org.apache.synapse=DEBUG" for me to analyze the problem
further
asankha
stlecho wrote:
Hi,
I've been configuring an endpoint and a proxy to be able to contact an
external webservice. Messages send to this webservice should be signed with
WS-Security. For testing purposes I've disabled the WS-Security
configuration of the proxy I'm using.
When sending a unsigned request to the webservice, the ESB receives the
following response "<?xml version='1.0' encoding='utf-8'?><SOAP-ENV:Envelope
...><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode> SOAP-ENV:Client
</faultcode><faultstring> EJB Exception: ; nested exception is:
com.bea.wlw.runtime.jws.wssecurity.exception.WLWWSSEException: Policy
requires Message to be signed,Message was not signed.
</faultstring><detail>EJB Exception: ; nested exception is:
com.bea.wlw.runtime.jws.wssecurity.exception.WLWWSSEException: Policy
requires Message to be signed, Message was not signed.
</detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>".
Since the request was voluntarily not signed, this response is correct. But
... after getting the response, I see in the logs that the message is being
re-send automatically. This re-sending happens multiple times per second and
I'm obliged to stop the service (otherwise it keeps on going). Although I'm
not sure that the message is being re-send (could be a logging problem), I
suppose that this behavior is incorrect.
Is it linked to the fact that the response contains a "SOAP Fault" and that
ESB has a special treatment for this kind of responses ?
Regards, Stefan Lecho.
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
