[jboss-jira] [JBoss JIRA] Updated: (JBAS-1740) Remote Connection does not get closed in case of sloppy client

[Weston Price (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-1740?page=all ]

Weston Price updated JBAS-1740:
-------------------------------

    Fix Version/s: JBossAS-5.0.0.Beta
                       (was: JBossAS-4.0.5.GA)

Modfied according to JCA roadmap meeting.

> Remote Connection does not get closed in case of sloppy client
> --------------------------------------------------------------
>
>                 Key: JBAS-1740
>                 URL: http://jira.jboss.com/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
>         Assigned To: Weston Price
>            Priority: Minor
>             Fix For: JBossAS-5.0.0.Beta
>
>
> 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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira