I found that the connection pool configuration in WebLogic has an attribute
'Connection Creation Retry Frequency'. If it is greater than 0 and if the
database is unavailable when the connection pool is created, WebLogic will
attempt to create connections in the pool again after the number of se
glum,
Thank you for your suggestion. Probably your workaround should work. But I
was wondering if there is a configurable parameter that would tell the deployer
not to give up right away and continue to ping the database until it becomes
available.
Thanks,
Yevgeny.
View the original post :
Scenario:
Computers where JBoss AS and the database get restarted. ?omputer with JBoss
starts up first and finds no database because the computer with database has
not fully started yet. JBoss displays the message:
15:48:45,421 WARN [JBossManagedConnectionPool] Throwable while attempting to
g
Thomas,
I have exactly the same problem. I use JBoss 4.0.1 and Axis 1.2RC2. I was
just wondering if you expect this to be fixed in the nearest future?
Thanks,
Yevgeny.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865316#3865316
Reply to the post :
htt
