This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Hi all, I have simple struts app. Flow of app as: Action call(.do call)> DB interaction (fetch huge data)>bring back and show on jsp page
we are not using any BEA pooling. So there is no question that there is BEA conn pool time out. we have tested this application in test environment and it is taking aroun 20 min to display page but it never shows Error 500. on the other hand, when we deployed this production, it is giving error 500 if request taked more that 1.5 min to preocess.
If request is getting completed (including data fetch from DB) withing 1.5 min, the jsp page will be shown.
Any help and suggestions are highly appreciable.
Thanks!<br />kady m
Joined: Jun 27, 2008
even i searched a lot on this. is ther any way, we can change application side settings? update web.xml/weblogic.xml? if server side settings cam be avoided, that will be great...
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