[
https://issues.apache.org/jira/browse/JS2-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033086#comment-13033086
]
Ate Douma commented on JS2-1183:
--------------------------------
Hmm, I discovered some more "easy" ThreadLocal usage fixes (after quite some
debugging that is) which I will apply shortly.
I don't think I can possibly solve all potential mis-usages though, especially
not if they are coming from 3rd party libraries.
But with only basic usage, I don't see any of these errors reported anymore
(triggering them however shouldn't be too difficult).
Additional and important gain from these changes however is that I now
(finally) can reload Jetspeed application without it breaking anymore!
Of course, the portlet applications themselves get "disconnected" as we don't
have a "deregistration" callback mechanism in place, but if I manually reload
those too the portal and the portlet applications simply continue to work
thereafter.
> Tomcat 6.0.24+ logs SEVERE errors on the console during shutdown from
> WebappClassLoader clearReferencesThreads and clearThreadLocalMap
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JS2-1183
> URL: https://issues.apache.org/jira/browse/JS2-1183
> Project: Jetspeed 2
> Issue Type: Task
> Components: Container
> Reporter: Ate Douma
> Assignee: Ate Douma
> Priority: Minor
> Attachments: catalina.out
>
>
> Since Tomcat 6.0.24 and higher Tomcat now actively verifies potential
> "shutdown" problems concerning application created thread, ThreadLocal
> instances etc.
> If it encounters such issues, it reports this as SEVERE errors, which by
> default end up in the console output or catalina.out.
> While these reporting "issues" indeed need looking into, the Console logging
> is rather annoying.
> For the Jetspeed 2.2.1 installer which will bundle Tomcat 6.0.26, I'll add an
> override of the Tomcat logging.properties to redirect these errors to the
> localhost FileHandler instead (logs/localhost.{date}.log).
> For Jetspeed 2.2.2 the reported "issues" warrant further investigation to see
> if these need to be solved or not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-dev-h...@portals.apache.org
