You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2009/09/15 01:30:57 UTC

[jira] Resolved: (CXF-2434) Set JMSConfig's reconnectionOnException default value to be true

     [ https://issues.apache.org/jira/browse/CXF-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang resolved CXF-2434.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.4
                   2.1.7

Committed the patch into trunk, 2.2.x-fixes branch and 2.1.x-fixes branch.

> Set JMSConfig's reconnectionOnException default value to be true  
> ------------------------------------------------------------------
>
>                 Key: CXF-2434
>                 URL: https://issues.apache.org/jira/browse/CXF-2434
>             Project: CXF
>          Issue Type: Improvement
>    Affects Versions: 2.1.3, 2.0.10, 2.1.4, 2.2, 2.0.11, 2.1.5, 2.2.1, 2.2.2, 2.0.12, 2.1.6, 2.2.3
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 2.1.7, 2.2.4, 2.3
>
>
> JMS transport will try to wrap a connectionFactory with Spring's SingleConnectionFactory, and the SingleConnectionFactory's default vaule of reconnectOnException is false.  It will cause the SingleConnectionFactory not try to reconnection the JMS broker when the exception is thrown.
> So we need to set the JMSConfig's default value of reconnectOnException to be true to enable this recovery feature by default.

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