Exception Strategy executed more than once for the same exception, help?

[Bas van Driel-2]

Hi,

I’m new to mule, and got some problems with the exception strategies:


Problem 1:
a connector exception should be thrown, but a service exception is thrown next to it

When executing a service with a synchronous outbound endpoint defined that is not reachable, I would expect the service to only throw a connector exception. But next to the connector exception it also throws a service exception 2 times. When the outbound endpoint is defined asynchronous, then it behaves as expected (so only a connector exception is thrown).

Problem 2:
a connector exception should be thrown, but it is thrown 2 times instead of one time.

When executing a service with a cxf outbound endpoint defined that is not reachable, I would expect the service to throw a connector exception 1 time. But in this case the connector exception is thrown 2 times: 1 time on the HTTP connector and 1 time on the CXF connector.

Below the test configuration used:
<?xml version="1.0" encoding="UTF-8"?>
<mule
    xmlns="http://www.mulesource.org/schema/mule/core/2.2"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:cxf="http://www.mulesource.org/schema/mule/cxf/2.2"
    xmlns:http="http://www.mulesource.org/schema/mule/http/2.2"
   
    xsi:schemaLocation="
        http://www.mulesource.org/schema/mule/cxf/2.2 http://www.mulesource.org/schema/mule/cxf/2.2/mule-cxf.xsd
        http://www.mulesource.org/schema/mule/http/2.2 http://www.mulesource.org/schema/mule/http/2.2/mule-http.xsd
        http://www.mulesource.org/schema/mule/core/2.2 http://www.mulesource.org/schema/mule/core/2.2/mule.xsd ">  
                   
    <model name="TestCase">
       
        <service name="Test1">

            <inbound>
                <http:inbound-endpoint address="http://localhost:8087/klacht" synchronous="true"/>
            </inbound>
            <outbound>
                <pass-through-router>
                    <http:outbound-endpoint address="http://localhost:8091" method="POST" synchronous="true"/>
                </pass-through-router>
            </outbound>              
        </service>

        <service name="Test2">

            <inbound>
                <http:inbound-endpoint address="http://localhost:8086/klacht" synchronous="true"/>
            </inbound>
            <outbound>
                <pass-through-router>
                    <cxf:outbound-endpoint address="http://localhost:8091/klacht" proxy="true" synchronous="true"/>
                </pass-through-router>
            </outbound>          
        </service>

    </model>
</mule>

You can just use the configuration and execute the cases from a browser. Test1 relates to Problem1, Test2 relates to Problem2.
If you add a log statement to the routeException method of the DefaultExceptionStrategy, then you can see the problem.

Is this normal behavior? What to do about the service exception thrown next to the connector exception?

Can someone please help?

Thx
Bas van Driel

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Andrew Perepelytsya]

Hi,

Is it behaving the same without cxf in the mix?

Andrew

[Bas van Driel-2]

HI Andrew,

Sorry for not getting back earlier, I got struck by influenza...

The answer to your question for each of our problems is:
Problem 1 (service exception thrown next to connector exception) occurs for non-cxf (i.e. 'normal' http for instance) endpoints TOO.
Problem 2 (2 connector exceptions thrown instead of 1) ONLY happens with the cxf connector over http. It looks like the http connector throws a connection error, and then on top that the cxf connector also throws one. I would expect one of the two to throw the exception (actually i would expect the http should throw it and cxf should not if it is layered on top of http, because cxf knows that http will already throw the connection exception).

Any ideas ?

Bas

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email