Custom exception strategy - handleLifecycleException not catched

[gvsg ()]

All,

I implemented my own custom exception strategy which extends from DefaultExceptionStrategy.

Although when I call an EJB in the outbound endpoint then the handleLifecycleException method of the DefaultExceptionStrategy is called instead of my class.  When I have a transformer exception then
my exception strategy class is called correctly.  I'm using Mule 2.2.1.


<service name="cronExceptionTester">
        <inbound>.....</inbound>
        <outbound>
                 <pass-through-router>
                        <ejb:outbound-endpoint method="callEJBMethod" address="...." />
                 </pass-through-router>
        </outbound>
                       
        <custom-exception-strategy class="myCustom.VGServiceExceptionStrategy"
                           enableNotifications="true">
                <file:outbound-endpoint path="E:/error/"
                                                               connector-ref="general"
                                                               outputPattern="#[ORIGINALNAME]"/>
        </custom-exception-strategy>
</service>


Is this a mule bug or should I add my strategy somewhere else to make this working?

Kind regards,

Guy

                       

[antoine.borg]

Why aren't you using a custom-service-exception-strategy?

A

gvsg wrote:

> All,
>
> I implemented my own custom exception strategy which extends from
> DefaultExceptionStrategy.
>
> Although when I call an EJB in the outbound endpoint then the
> handleLifecycleException method of the DefaultExceptionStrategy is called
> instead of my class.  When I have a transformer exception then
> my exception strategy class is called correctly.  I'm using Mule 2.2.1.
>
>
> <service name="cronExceptionTester">
> <inbound>.....</inbound>
> <outbound>
> <pass-through-router>
> <ejb:outbound-endpoint method="callEJBMethod" address="...." />
> </pass-through-router>
> </outbound>
>
> <custom-exception-strategy class="myCustom.VGServiceExceptionStrategy"
>                            enableNotifications="true">
> <file:outbound-endpoint path="E:/error/"
>                                                              
> connector-ref="general"
>                                                              
> outputPattern="#[ORIGINALNAME]"/>
> </custom-exception-strategy>
> </service>
>
>
>
> Is this a mule bug or should I add my strategy somewhere else to make this
> working?
>
> Kind regards,
>
> Guy
>
>
>  

--

Antoine Borg, Director of Services | Tel: [phone]
ricston Ltd., BP 2, 1180 Uccle, Brussels, BELGIUM

See our full schedule of Mule and Android courses:
http://www.ricston.com/courses/schedules/

email: _antoine.borg_@... <mailto:antoine.borg@...> |
blog: blog.ricston.com <http://blog.ricston.com> | web: ricston.com
<http://www.ricston.com/>



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

    http://xircles.codehaus.org/manage_email

[gvsg]

I don't use the custom-service-exception-strategy because I want to catch all exceptions.
Therefor I should extend the DefaultExceptionStrategy class.  But only the handleRoutingException method of my class is invoked.  I don't understand why the handleLifecycleException of my class is not invoked when such an error occur?  So I assume that it is a Mule bug.

Kind regards,

Guy

antoine.borg wrote:

Why aren't you using a custom-service-exception-strategy?

A

gvsg wrote:
> All,
>
> I implemented my own custom exception strategy which extends from
> DefaultExceptionStrategy.
>
> Although when I call an EJB in the outbound endpoint then the
> handleLifecycleException method of the DefaultExceptionStrategy is called
> instead of my class.  When I have a transformer exception then
> my exception strategy class is called correctly.  I'm using Mule 2.2.1.
>
>
> <service name="cronExceptionTester">
> <inbound>.....</inbound>
> <outbound>
> <pass-through-router>
> <ejb:outbound-endpoint method="callEJBMethod" address="...." />
> </pass-through-router>
> </outbound>
>
> <custom-exception-strategy class="myCustom.VGServiceExceptionStrategy"
>                            enableNotifications="true">
> <file:outbound-endpoint path="E:/error/"
>                                                              
> connector-ref="general"
>                                                              
> outputPattern="#[ORIGINALNAME]"/>
> </custom-exception-strategy>
> </service>
>
>
>
> Is this a mule bug or should I add my strategy somewhere else to make this
> working?
>
> Kind regards,
>
> Guy
>
>
>  
--

Antoine Borg, Director of Services | Tel: [phone]
ricston Ltd., BP 2, 1180 Uccle, Brussels, BELGIUM

See our full schedule of Mule and Android courses:
http://www.ricston.com/courses/schedules/

email: [e-mail] <mailto:[e-mail]> |
blog: blog.ricston.com <http://blog.ricston.com> | web: ricston.com
<http://www.ricston.com/>



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

    http://xircles.codehaus.org/manage_email

[gvsg]

I extended from DefaultExceptionStrategy to catch all exceptions.  
The service exception strategy does not catch all exceptions.  For example my lifecycle exception below (The callEJBMethod will fail as the other system is down).  

I assume that this is a bug or does someone has a working example?

Kind regards,

Guy

antoine.borg wrote:

Why aren't you using a custom-service-exception-strategy?

A

gvsg wrote:
> All,
>
> I implemented my own custom exception strategy which extends from
> DefaultExceptionStrategy.
>
> Although when I call an EJB in the outbound endpoint then the
> handleLifecycleException method of the DefaultExceptionStrategy is called
> instead of my class.  When I have a transformer exception then
> my exception strategy class is called correctly.  I'm using Mule 2.2.1.
>
>
> <service name="cronExceptionTester">
> <inbound>.....</inbound>
> <outbound>
> <pass-through-router>
> <ejb:outbound-endpoint method="callEJBMethod" address="...." />
> </pass-through-router>
> </outbound>
>
> <custom-exception-strategy class="myCustom.VGServiceExceptionStrategy"
>                            enableNotifications="true">
> <file:outbound-endpoint path="E:/error/"
>                                                              
> connector-ref="general"
>                                                              
> outputPattern="#[ORIGINALNAME]"/>
> </custom-exception-strategy>
> </service>
>
>
>
> Is this a mule bug or should I add my strategy somewhere else to make this
> working?
>
> Kind regards,
>
> Guy
>
>
>  
--

Antoine Borg, Director of Services | Tel: [phone]
ricston Ltd., BP 2, 1180 Uccle, Brussels, BELGIUM

See our full schedule of Mule and Android courses:
http://www.ricston.com/courses/schedules/

email: [e-mail] <mailto:[e-mail]> |
blog: blog.ricston.com <http://blog.ricston.com> | web: ricston.com
<http://www.ricston.com/>



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

    http://xircles.codehaus.org/manage_email

[Dirk Olmes]

gvsg wrote:
>
> I extended from DefaultExceptionStrategy to catch all exceptions.  
> The service exception strategy does not catch all exceptions.  For example
> my lifecycle exception below (The callEJBMethod will fail as the other
> system is down).  

Some exceptions are handled by the connector exception strategy. The
line is not always 100% clear so if you might want to try that, too.

-dirk

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

    http://xircles.codehaus.org/manage_email