You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Franz Amador <fg...@yahoo.com> on 2008/01/11 23:33:32 UTC
T5.0.7: ThreadCleanupHubImpl.cleanup swallows exceptions
ThreadCleanupHubImpl.cleanup (line 53) catches exceptions thrown by service initialization cleanup. It logs them, which is good, but it doesn't pass them up, which is causing me problems. I want to know if Hibernate initialized successfully, but this prevents me from seeing exceptions thrown during the transaction commit in HibernateSessionManagerImpl.threadDidCleanup. Is this an oversight or is there a design goal of having the Registry come up no matter what?
Re: T5.0.7: ThreadCleanupHubImpl.cleanup swallows exceptions
Posted by Howard Lewis Ship <hl...@gmail.com>.
By the time it executes, it is too late to render a response with the
exception. There's nothing that can catch the exception ... the only
thing "above" ThreadCleanupHubImpl is the servlet and then the servlet
container. Further, it is very important that every cleanup listener
be invoked, or you could experience some memory leaks in the
application, as threads hold onto objects inside ThreadLocals.
On Jan 11, 2008 2:33 PM, Franz Amador <fg...@yahoo.com> wrote:
> ThreadCleanupHubImpl.cleanup (line 53) catches exceptions thrown by service initialization cleanup. It logs them, which is good, but it doesn't pass them up, which is causing me problems. I want to know if Hibernate initialized successfully, but this prevents me from seeing exceptions thrown during the transaction commit in HibernateSessionManagerImpl.threadDidCleanup. Is this an oversight or is there a design goal of having the Registry come up no matter what?
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org