[jboss-jira] [JBoss JIRA] Updated: (JBAS-1740) Remote Connection does not get closed in case of sloppy client
Jesper Pedersen (JIRA)
jira-events at lists.jboss.org
Thu Feb 5 16:31:44 EST 2009
[ https://jira.jboss.org/jira/browse/JBAS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesper Pedersen updated JBAS-1740:
----------------------------------
Fix Version/s: (was: JBossAS-5.1.0.Beta1)
Assignee: (was: Jesper Pedersen)
> Remote Connection does not get closed in case of sloppy client
> --------------------------------------------------------------
>
> Key: JBAS-1740
> URL: https://jira.jboss.org/jira/browse/JBAS-1740
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA service
> Affects Versions: JBossAS-4.0.1 Final
> Reporter: Michael Kopp
> Priority: Minor
>
> If the Client that gets a remote Connection (WrapperDataSourceService) does not close it properly (sloppy or crash), it will never be released again.
> This can be solved rather easily, the finalize method of the Server part of the proxy should call close.
> Thus if the client object gets garbage collected (or the JVM dies), the server object (proxy) will be garbage collected and the finalize method called.
> This thing is that a sloppy or crashing client can occupy all available connections, leaving all other applications with no connection to work with.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list