-
1. Re: MaxSize connection exceeds
adrian.brock Aug 26, 2003 12:23 AM (in response to mcoyne)Connections get removed if they are not used (default 15 mins)
and then recreated. They are also removed if there is an error.
You can turn off the idle reaping:
<idle-timeout-minutes>0</idle-timeout-minutes>
Regards,
Adrian -
2. Re: MaxSize connection exceeds
mcoyne Aug 26, 2003 5:19 AM (in response to mcoyne)Thank you for your answer.
I have the Idle-timeout-minutes set to 5. In my test, I have the client application in a tight loop getting connections. Then, I have 6 of such applications to run concurrently (to guarantee there is a need for more than 5 connections).
Therefore, I don't think the connection is not used, not idle. However, I thought that with the maxsize set to 5, JBoss will not create more than 5 connections. But this does not seem what I've seen.
Thanks. -
3. Re: MaxSize connection exceeds
adrian.brock Aug 27, 2003 12:16 AM (in response to mcoyne)It won't which version are you using?
Show the output from JMX console for the managed connection
pool.
Regards,
Adrian -
4. Re: MaxSize connection exceeds
mcoyne Aug 27, 2003 11:46 AM (in response to mcoyne)Dear Adrian:
Thanks again.
We have tested this again and pay close attention to the connection to the database (checking from the oracle database side). Yes, indeed, the maxsize behaves correctly as you've said.
One thing, thoug, we set the minsize to 1 and idletime to 1(minutes). Notice that Jboss would eventually close ALL connections, which I thought that It should keep at least one (since Minsize is 1).
Thoughts?
Thanks. -
5. Re: MaxSize connection exceeds
adrian.brock Aug 27, 2003 12:51 PM (in response to mcoyne)The algorithm isn't very clever.
It reaps idles connections then refills to minSize.
B
Regards,
Adrian -
6. Re: MaxSize connection exceeds
adrian.brock Aug 27, 2003 12:51 PM (in response to mcoyne)The algorithm isn't very clever.
It reaps idles connections then refills to minSize.
Both are asynchronous processes.
Regards,
Adrian