You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2007/02/01 17:51:05 UTC
[jira] Created: (CXF-404) Logging of failure to activate a JMS
destination is too low at level fine. It should be error
Logging of failure to activate a JMS destination is too low at level fine. It should be error
---------------------------------------------------------------------------------------------
Key: CXF-404
URL: https://issues.apache.org/jira/browse/CXF-404
Project: CXF
Issue Type: Bug
Components: Transports
Affects Versions: 2.0-M1
Reporter: Gary Tully
Priority: Minor
A JMS destination/endpoint that is badly configured gets a silent failure and nothing is logged unless level is > FINE. This needs to be flagged as an error in the log. In addition, why is the exception swallowed here?
>From JMSDestination:activate(..)
try {
getLogger().log(Level.FINE, "establishing JMS connection");
JMSProviderHub.connect(base, config);
//Get a non-pooled session.
listenerSession = base.sessionFactory.get(base.targetDestination);
listenerThread = new JMSListenerThread(listenerSession);
listenerThread.start();
} catch (JMSException ex) {
getLogger().log(Level.FINE, "JMS connect failed with JMSException : ", ex);
} catch (NamingException nex) {
getLogger().log(Level.FINE, "JMS connect failed with NamingException : ", nex);
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-404) Logging of failure to activate a JMS
destination is too low at level fine. It should be error
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved CXF-404.
------------------------------
Resolution: Fixed
> Logging of failure to activate a JMS destination is too low at level fine. It should be error
> ---------------------------------------------------------------------------------------------
>
> Key: CXF-404
> URL: https://issues.apache.org/jira/browse/CXF-404
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.0-M1
> Reporter: Gary Tully
> Assigned To: Freeman Fang
> Priority: Minor
>
> A JMS destination/endpoint that is badly configured gets a silent failure and nothing is logged unless level is > FINE. This needs to be flagged as an error in the log. In addition, why is the exception swallowed here?
> From JMSDestination:activate(..)
> try {
> getLogger().log(Level.FINE, "establishing JMS connection");
> JMSProviderHub.connect(base, config);
> //Get a non-pooled session.
> listenerSession = base.sessionFactory.get(base.targetDestination);
> listenerThread = new JMSListenerThread(listenerSession);
> listenerThread.start();
> } catch (JMSException ex) {
> getLogger().log(Level.FINE, "JMS connect failed with JMSException : ", ex);
> } catch (NamingException nex) {
> getLogger().log(Level.FINE, "JMS connect failed with NamingException : ", nex);
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CXF-404) Logging of failure to activate a JMS
destination is too low at level fine. It should be error
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang closed CXF-404.
----------------------------
> Logging of failure to activate a JMS destination is too low at level fine. It should be error
> ---------------------------------------------------------------------------------------------
>
> Key: CXF-404
> URL: https://issues.apache.org/jira/browse/CXF-404
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.0-M1
> Reporter: Gary Tully
> Assigned To: Freeman Fang
> Priority: Minor
>
> A JMS destination/endpoint that is badly configured gets a silent failure and nothing is logged unless level is > FINE. This needs to be flagged as an error in the log. In addition, why is the exception swallowed here?
> From JMSDestination:activate(..)
> try {
> getLogger().log(Level.FINE, "establishing JMS connection");
> JMSProviderHub.connect(base, config);
> //Get a non-pooled session.
> listenerSession = base.sessionFactory.get(base.targetDestination);
> listenerThread = new JMSListenerThread(listenerSession);
> listenerThread.start();
> } catch (JMSException ex) {
> getLogger().log(Level.FINE, "JMS connect failed with JMSException : ", ex);
> } catch (NamingException nex) {
> getLogger().log(Level.FINE, "JMS connect failed with NamingException : ", nex);
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-404) Logging of failure to activate a JMS
destination is too low at level fine. It should be error
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang reassigned CXF-404:
--------------------------------
Assignee: Freeman Fang
> Logging of failure to activate a JMS destination is too low at level fine. It should be error
> ---------------------------------------------------------------------------------------------
>
> Key: CXF-404
> URL: https://issues.apache.org/jira/browse/CXF-404
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.0-M1
> Reporter: Gary Tully
> Assigned To: Freeman Fang
> Priority: Minor
>
> A JMS destination/endpoint that is badly configured gets a silent failure and nothing is logged unless level is > FINE. This needs to be flagged as an error in the log. In addition, why is the exception swallowed here?
> From JMSDestination:activate(..)
> try {
> getLogger().log(Level.FINE, "establishing JMS connection");
> JMSProviderHub.connect(base, config);
> //Get a non-pooled session.
> listenerSession = base.sessionFactory.get(base.targetDestination);
> listenerThread = new JMSListenerThread(listenerSession);
> listenerThread.start();
> } catch (JMSException ex) {
> getLogger().log(Level.FINE, "JMS connect failed with JMSException : ", ex);
> } catch (NamingException nex) {
> getLogger().log(Level.FINE, "JMS connect failed with NamingException : ", nex);
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.