You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Curt Arnold (JIRA)" <ji...@apache.org> on 2008/08/13 19:08:44 UTC

[jira] Resolved: (LOG4J2-25) TopicConnection is not closed

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

Curt Arnold resolved LOG4J2-25.
-------------------------------

    Resolution: Invalid

This JIRA is for log4j 2.0 development.  To report a bug against log4j 1.2, please use http://issues.apache.org/bugzilla.

> 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.
-
You can reply to this email to add a comment to the issue online.


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