Mule

Configuring default-service-exception-strategy on connector throws NullPointerException

Details

  • Includes test case?:
    no
  • User impact:
    High
  • Configuration:
    Hide

    <jms:connector name="JmsConnector" specification="1.1"
    connectionFactory-ref="ConnectionFactory" createMultipleTransactedReceivers="false">
    <default-service-exception-strategy>
    <commit-transaction
    exception-pattern="org.mule.transport.jms.MessageRedeliveredException"/>
    <jms:outbound-endpoint queue="dead.letter" synchronous="true">
    <jms:transaction action="ALWAYS_JOIN"/>
    </jms:outbound-endpoint>
    </default-service-exception-strategy>
    </jms:connector>

    Show
    <jms:connector name="JmsConnector" specification="1.1" connectionFactory-ref="ConnectionFactory" createMultipleTransactedReceivers="false"> <default-service-exception-strategy> <commit-transaction exception-pattern="org.mule.transport.jms.MessageRedeliveredException"/> <jms:outbound-endpoint queue="dead.letter" synchronous="true"> <jms:transaction action="ALWAYS_JOIN"/> </jms:outbound-endpoint> </default-service-exception-strategy> </jms:connector>
  • Similar Issues:
    MULE-4640 Unify default connector and service exception strategy or limit configuration
    MULE-5731 "default-service-exception-strategy" is permitted in flows
    MULE-4515 default-service-exception-strategy does not honor exception-type-filter
    MULE-3128 Improve the <default-exception-strategy> configuration
    MULE-4927 Exception strategy invoked both for connector *and* service exception strategies when exception on sync outbound endpoint
    MULE-4630 Configured Service Exception strategy does not get called for MessageRedeliveredException
    MULE-5895 As a user I want to be able to define a custom default exception strategy that is used when a a flow or service does not define one explicitly
    MULE-4341 Transformerconfigured on an endpoint in exception-strategy are ignored
    MULE-5269 Clean up exception strategy schema elements after exception strategy work in core
    MULE-3196 default-connector-exception-strategy should not be able to be configured on model should it?

Issue Links

Related
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Puneet Gupta added a comment - 23/Nov/09 03:38 PM

Check if ctx is null before doing anything else.

Show
Puneet Gupta added a comment - 23/Nov/09 03:38 PM Check if ctx is null before doing anything else.
Hide
Permalink
Daniel Feist added a comment - 30/Nov/09 05:47 AM

Should you shouldn't be using <default- connector-exception-strategy>? Does this solve the issue.

Ideally we wouldn't have two strategies that are interchangeable. they are either different and shouldn't be interchangeable or there should just be one.

Show
Daniel Feist added a comment - 30/Nov/09 05:47 AM Should you shouldn't be using <default- connector-exception-strategy>? Does this solve the issue. Ideally we wouldn't have two strategies that are interchangeable. they are either different and shouldn't be interchangeable or there should just be one.

People

Vote (0)
Watch (0)

Dates

  • Created:
    23/Nov/09 02:48 PM
    Updated:
    30/Nov/09 06:11 AM
    Resolved:
    30/Nov/09 06:11 AM
Atlassian JIRA (v4.2#587) | Report a problem
Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.