I still don't see why you need to change the IdleRemover.

If the aged timeout is less than the idle timeout, you pass that as the 
interval.
It just means it is going to make more frequent calls to removedTimeOut.

There is no loss here since it just checks one connection (the oldest unused)
to see whether it timed out, or you have more complicated processing.
It may check more with your policy.

I'd suggest you identify a TimeoutPolicy that can be plugged into the 
InternalManagedConnectionPool.PoolParams 
(with a default policy for when it is not specified - that is the current 
default).

This would encapsulate:
1) The interval used when registerting with the idle remover
2) What happens at return connection (i.e. should it kill it)
3) What happens on the callback from the idle remover
4) What data (javabean object) needs storing in the ConnectionListener to 
satisfy the policy
Any others?

Something like:

  | public interface ConnectionTimeoutPolicy
  | {
  |    void setPoolParams(PoolParams pp); // invoked at pool startup after 
construction
  |    long getRemoverInterval(); // invoked at pool startup before registering 
with idle remover
  |    boolean isTimedOut(ConnectionListener cl); // invoked on each return
  |    ArrayList /* connections to destroy */ removeTimedOut(Arraylist 
connectionListeners); // invoked from the idle remover callback
  |    Object initTimeOutParams(); // inserted into each ConnectionListener
  | }
  | 

The only issue is how you make it easily configurable through the stylesheet
and maintain backwards compatibily for older configurations.
i.e. we need somebody using the current configuration to be unaware
of this change.
How is your xslt :-)

This gives you what you want and it is possible for somebody else to override
the behaviour in the future.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865966#3865966

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865966


-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to