Hi,
I will have to check and get back to you on this.. but I do not think the connection pool timeout is specific to using a bea driver.
I also think there is a session timeout setting in weblogic. Again will have to check and get back to you.
Which is the test environment in which you have test?
Also please compare the config.xml of the 2 env where you have tested the app. I assume you have already done that. That could give an idea as to why you get the error after so long.
Off the track, are you sure your application users can wait that long for a page to load? 20 mins, it is huge. Even if weblogic doesn't time out the user might just timeout himself
HTH
Shikhar
[ June 30, 2008: Message edited by: Shikhar Madhok ]