Thanks for your help. I thought that a filter would be the best place to release resources? I'll check for deadlocks - that seems to be pretty hard.
Reto -----Urspr�ngliche Nachricht----- Von: Ralph Einfeldt [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 24. Januar 2002 09:22 An: Tomcat Users List Betreff: AW: Tomcat - Request Handling If the resources are allocated in the jsp there are two options: - use a try/finally block in your jsp where you release all resources that are allocated - if you have several jsp's that allocate the same resources you can create a subclass that allocates and free's the resources (have done that more than 2 years ago, so I can't remember the details) P.S: Make shure that your code doesn't produce a deadlock if two or more requests are processed at the same time. (That's my first guess for the reason that causes the symptoms you observed) Watch for synchronized and for locks on resources you use (database, files, ...). > -----Urspr�ngliche Nachricht----- > Von: Reto Badertscher [mailto:[EMAIL PROTECTED]] > Gesendet: Donnerstag, 24. Januar 2002 08:42 > An: Tomcat Users List > Betreff: Tomcat - Request Handling > What can i do to ensure that the resource is always released > (my servlet forwards to a JSP, after the JSP has finished the > resource can be released). > Would it be better to write a subclass of a JSP and implement > this in a finally block of the service method? -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
