Java process/thread isn't killed after the shutdown command
-----------------------------------------------------------
Key: CLEREZZA-283
URL: https://issues.apache.org/jira/browse/CLEREZZA-283
Project: Clerezza
Issue Type: Bug
Environment: Probably any, tested on Ubuntu Linix, Debian Linux,
Windows XP
Reporter: Fabian Baumgartner
Priority: Blocker
The clerezza java process isn't killed/properly shut down after the system
recieves the 'shutdown' command
Console outputs ends with:
...
[FelixStartLevel] INFO org.quartz.core.QuartzScheduler - Scheduler
ApacheSling_$_Fri_Aug_20_15:59:18_CEST_2010 paused.
[FelixStartLevel] INFO org.quartz.core.QuartzScheduler - Scheduler
ApacheSling_$_Fri_Aug_20_15:59:18_CEST_2010 shutdown complete.
[FelixStartLevel] INFO
org.apache.sling.commons.threads.impl.DefaultThreadPoolManager - Stopped Apache
Sling Thread Pool Manager.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Disabling SLF4J API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Disabling Jakarta Commons Logging API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Disabling Log4J API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Disabling Avalon Logger API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Disabling JULI Logger API support.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
