[ http://jira.jboss.com/jira/browse/JBAS-31?page=comments#action_12310735 ]
     
Scott M Stark commented on JBAS-31:
-----------------------------------

Another problem I'm seeing with this code is the following:

   private void closeAll(Map cmToConnectionsMap)
   {
      if (debug == false)
         return;

      for (Iterator i = cmToConnectionsMap.values().iterator(); i.hasNext();)
      {
         Collection conns = (Collection) i.next();
         for (Iterator j = conns.iterator(); j.hasNext();)
         {
            Object c = ((ConnectionRecord) j.next()).connection;
            CloseConnectionSynchronization cas = 
getCloseConnectionSynchronization(true);
            if (cas == null)
               closeConnection(c);
            else
               cas.add(c);
         }
      }
   }

The call to getCloseConnectionSynchronization(true) with the true flag is going 
to create an orphaned CloseConnectionSynchronization that will never be closed. 
This should be passing in false.


> CachedConnectionManager - inUseConnections not correct
> ------------------------------------------------------
>
>          Key: JBAS-31
>          URL: http://jira.jboss.com/jira/browse/JBAS-31
>      Project: JBoss Application Server
>         Type: Bug
>   Components: JCA service
>     Versions: JBossAS-3.2.6 Final
>     Reporter: Scott M Stark
>     Assignee: Scott M Stark
>  Attachments: test.jsp
>
>
> For CachedConnectionManager service debug option is
> enabled to monitor connections.
> <!-- Enable connection close debug monitoring -->
> <attribute name="Debug">true</attribute>
> Using jmx-console, if we look at the "inUseCount"
> property. The number displayed is not consitent with
> the underlying connection pool. "listInUseConnections"
> shows stack traces for connections that have been
> closed long back. It take a long time for the
> "inUseCount" to drop down, but never drops to 0 even
> after the connection pools correctly show inUseCount as 0.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to