[
https://issues.apache.org/jira/browse/JS2-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855268#action_12855268
]
Randy Watler commented on JS2-1183:
-----------------------------------
The unstopped TimerThread above does not appear to be defined in Jetspeed or
APA sources. TimerThreads are normally spawned by Timer/TimerTask instances and
I have verified that it is probably not due to JetspeedContainerServlet
instances. Here is the likely candidate:
"Timer-0" daemon prio=10 tid=0x0000000040c7bc00 nid=0x1073 in Object.wait()
[0x00007f4959ca4000..0x00007f4959ca4c70]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00007f4972294bb0> (a java.util.TaskQueue)
at java.lang.Object.wait(Object.java:485)
at java.util.TimerThread.mainLoop(Timer.java:483)
- locked <0x00007f4972294bb0> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:462)
Unfortunately, this does not indicate the context of this Timer. At this point,
I assume that this particular timer is defined and invoked in a dependency.
Timers associated with Ehcache and MySQL Drivers have been accounted for.
> 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
> Affects Versions: 2.2.1
> Reporter: Ate Douma
> Fix For: 2.2.2
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
