Stefan
No problem! Its much better that you bother us but it ends up working
than you don't bother us and it doesn't work!
Paul
stlecho wrote:
In the mean time I've changed some settings for my WS-Security enabled
endpoint and I am - unfortunately - no longer able to reproduce this issue.
Sorry for bothering.
Regards, Stefan.
stlecho wrote:
Asankha,
In the proxy I've created I have not defined a "fault" sequence, so I
suppose the default one is used.
Regards, Stefan.
asankha wrote:
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
--
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair
VP, Apache Synapse
Office: +44 844 484 8143
Cell: +44 798 447 4618
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
