logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (LOG4J2-25) TopicConnection is not closed
Date Mon, 30 Apr 2012 07:37:52 GMT

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

Ralph Goers closed LOG4J2-25.

> TopicConnection is not closed
> -----------------------------
>                 Key: LOG4J2-25
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-25
>             Project: Log4j 2
>          Issue Type: Bug
>            Reporter: Hao Zhong
> In the code snippet [1],  public JMSSink( String tcfBindingName, String topicBindingName,
String username,  String password) creates a TopicConnection but does not close it in any
situation. JMSSink needs to implement a close method to deal with the resource, doesn't it?
> [1]http://svn.apache.org/viewvc/logging/log4j/trunk/src/main/java/org/apache/log4j/net/JMSSink.java?revision=565523&view=markup

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message