synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Anderson (JIRA)" <>
Subject [jira] Closed: (SYNAPSE-145) makefault does not change the http response code of the out message to http code 500 (it keeps 202)
Date Thu, 11 Oct 2007 15:52:50 GMT


Paul Anderson closed SYNAPSE-145.

    Resolution: Invalid

Configuring an immediate RESPONSE fixes both problems - Synapse responds immediately without
trying to send message onward, and the http code returned with the fault is 500.

<sequence name="myfault">
            <code value="tns:Receiver" xmlns:tns=""/>
            <reason value="Authorization failed!"/>
          <log level="full"/>
          <property name="RESPONSE" value="true" />

> makefault does not change the http response code of the out message to http code 500
(it keeps 202)
> ---------------------------------------------------------------------------------------------------
>                 Key: SYNAPSE-145
>                 URL:
>             Project: Synapse
>          Issue Type: Bug
>         Environment: JDK6 on RHEL3
>            Reporter: Paul Anderson
>            Priority: Minor
> <sequence name="myfault">
>           <makefault>
>             <code value="tns:Receiver" xmlns:tns=""/>
>             <reason value="Authorization failed!"/>
>           </makefault>
> <send/>
> </sequence>
> I think this should return http code 500 with the SOAP fault, to be WS-I compliant. Can
I set this http code manually?
> Also, how do I say 'don't try to continue further message processing onwards, BUT do
respond with the fault out message?
> The <send/> returns the fault to the client, but first it tries to send the 'in'
message onward, and it has no explicit destination so I get:
>   2614 [HttpServerWorker-1] ERROR Axis2Sender ( - Unexpected error
during Sending message onwards
> org.apache.axis2.AxisFault: Address information does not exist in the Endpoint Reference
(EPR).The system cannot infer the transport mechanism.
>         at org.apache.axis2.description.ClientUtils.inferOutTransport(
>         at org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.execute(
>         at org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(
>         at org.apache.synapse.core.axis2.Axis2Sender.sendOn(
>         at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(
>         at org.apache.synapse.mediators.builtin.SendMediator.mediate(
>         at org.apache.synapse.mediators.AbstractListMediator.mediate(
>         at org.apache.synapse.mediators.base.SequenceMediator.mediate(
>         at org.apache.synapse.mediators.MediatorFaultHandler.onFault(
>         at org.apache.synapse.FaultHandler.handleFault(
>         at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(
>         at org.apache.axis2.engine.AxisEngine.receive(
>         at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(
>         at org.apache.axis2.transport.nhttp.ServerWorker.processPost(
>         at
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message