Home » Fusion Middleware & Colab Suite » Weblogic & Application Server » PL/SQL Application Time out occuring after 30 mins (Oracle Application Server 10g,10.1.2, Red Hat Linux Advanced Server)
PL/SQL Application Time out occuring after 30 mins [message #302417] Mon, 25 February 2008 10:00 Go to next message
kmsalih
Messages: 197
Registered: March 2006
Senior Member
Hi,

We have a PL/SQL Application deployed on Oracle Application Server 10g.

My issue is, if any user works on the plsql application after 30 minutes ie idle, it is giving timeout error.

What i have to change on the Oracle Application Server Side to avoid the timeout?

I tried with PlsqlConnectionTimeout and it is not working.

Please give a solution.

Thanks & Regards
Salih KM
Re: PL/SQL Application Time out occuring after 30 mins [message #302445 is a reply to message #302417] Mon, 25 February 2008 12:40 Go to previous messageGo to next message
BlackSwan
Messages: 22718
Registered: January 2009
Senior Member
The timeout could be happening within the Apache webserver.
Re: PL/SQL Application Time out occuring after 30 mins [message #302575 is a reply to message #302445] Tue, 26 February 2008 03:31 Go to previous messageGo to next message
kmsalih
Messages: 197
Registered: March 2006
Senior Member
Thanks for your reply.

Currently the Timeout parameter in httpd.conf is 300. If i change this to a higher value say 3600 (1 hour), whether the timeout will occur if the user is idle for 55 minutes?

Is there any other parameter related to Timeout?

Thanks,
Salih
Re: PL/SQL Application Time out occuring after 30 mins [message #303996 is a reply to message #302575] Mon, 03 March 2008 11:36 Go to previous message
andrew again
Messages: 2574
Registered: March 2000
Senior Member
Make sure the timeout parameter isn't a response timeout (timeout to a call to the backed hasn't reponded within 300sec). That very different to an inactivity timeout. HTTP is a connectionless protocol, so you need to understand where the timeout is occuring. Is is from a connection pool to the database? Firewalls can be responsible for killing idle Oracle session originating from e.g. connection pools.

Try posting an error message just like you'd expect anyone else to provide you with...
Previous Topic: Oracle Application Server Wireless Deployment
Next Topic: installation problem
Goto Forum:
  


Current Time: Fri Aug 29 17:35:33 CDT 2014

Total time taken to generate the page: 0.26675 seconds