Opened 11 years ago

Last modified 10 years ago

#940 new defect

IZ714: Connection pool does not consider the max idle time for open connections

Reported by: rhierlmeier Owned by:
Priority: normal Milestone:
Component: hedeby Version: 1.0u5
Severity: Keywords: Sun bootstrap


[Imported from gridengine issuezilla]

        Issue #:      714             Platform:     Sun         Reporter: rhierlmeier (rhierlmeier)
       Component:     hedeby             OS:        All
     Subcomponent:    bootstrap       Version:      1.0u5          CC:    None defined
        Status:       STARTED         Priority:     P3
      Resolution:                    Issue type:    DEFECT
                                  Target milestone: 1.0u5next
      Assigned to:    adoerr (adoerr)
      QA Contact:     adoerr
       * Summary:     Connection pool does not consider the max idle time for open connections
   Status whiteboard:

     Issue 714 blocks:
   Votes for issue 714:     Vote for this issue

   Opened: Mon Dec 21 03:05:00 -0700 2009 


   During my long term tests I found that the SDM system closes connections to
   remote jvms too early. We defined that the connection be kept 5 minutes open.
   However if you enable logging of class
   (level FINE) you will see the following log entry very often:

   12/21/2009 10:05:58|262||I|Closing
   idle connection executor_vm@grawp[76] (0s idle)

   Connections are closed even if they are 0s idle.


   This issue has performance impact on the SDM system. A SDM jvm caches
   connections to remote jvms only for a very short time. As result very often new
   ssl connection must be established.


   The problem lies in class ConnectionProxy. The method
   ConnectionProxy$ConnectionHandler#getIdleTime returns the idle time of the
   connection in milliseconds. The field ConnectionProxy#maxIdleTime defines the
   max idle time of a connection in seconds.

   In ConnectionProxy#getConnection the idle connections are closed of the
   following conditioin is true:

    handler.getIdleTime() > maxIdleTime && count > minConnectionCount

   This means the connection are only kept open for 300ms.


   There is no work around possible, the issue must be fixed.

   How to test

   Write a junit test that checks that the max idle time for a connection is
   correctly considered.

   After implementing this issue the complete SDM system must be tested
   thoroughly.  Performance measurements should be done to ensure that the fix
   affects the system performance positively.

   ETC: 1PD
               ------- Additional comments from afisch Tue Jan 19 10:05:23 -0700 2010 -------
   took it

Change History (0)

Note: See TracTickets for help on using tickets.