users@glassfish.java.net

Re: ok for session bean to keep connection reference & leak reclamation ?

From: <glassfish_at_javadesktop.org>
Date: Thu, 22 May 2008 15:02:48 PDT

idle-timeout-in-seconds > connection-leak-timeout-in-seconds

Very insightful. Obviously my values are no good. (I wonder if those were the Netbeans defaults.)

Anyhow, I don't expect that the Session bean will ever go idle in the production environment so it may not matter.

  <connector-connection-pool
    associate-with-thread="false" connection-creation-retry-attempts="0"
    connection-creation-retry-interval-in-seconds="10" connection-definition-name="javax.jms.ConnectionFactory"
    connection-leak-reclaim="false" [b]connection-leak-timeout-in-seconds="60"[/b] fail-all-connections="false"
    [b]idle-timeout-in-seconds="300"[/b] is-connection-validation-required="false" lazy-connection-association="false"
    lazy-connection-enlistment="false" match-connections="true" max-connection-usage-count="0" max-pool-size="32"
    max-wait-time-in-millis="60000" name="jms/HubPool" pool-resize-quantity="2" resource-adapter-name="jmsra"
    steady-pool-size="8" validate-atmost-once-period-in-seconds="0" transaction-support="LocalTransaction">
    <description>Hub connection pool for senders and publishers</description>
  </connector-connection-pool>
[Message sent by forum member 'frenchdrip' (frenchdrip)]

http://forums.java.net/jive/thread.jspa?messageID=276154