Opened 9 years ago

Closed 9 years ago

#373 closed bug (fixed)

Tomcat Application fails to stop

Reported by: jewgenij Owned by:
Priority: minor Milestone: 6.8.1
Component: Core Version: 6.8
Keywords: Tomcat Cc:

Description

Tomcat (from bundle) cannot shutdown properly by shutdown.bat script.
The Tomcat log is looking like that:

Nov 26, 2013 2:08:23 PM org.apache.catalina.core.StandardServer? await
Information: A valid shutdown command was received via the shutdown port. Stoppi
ng the Server instance.
Nov 26, 2013 2:08:23 PM org.apache.coyote.AbstractProtocol? pause
Information: Pausing ProtocolHandler? http-apr-8080?
Nov 26, 2013 2:08:24 PM org.apache.coyote.AbstractProtocol? pause
Information: Pausing ProtocolHandler? ajp-apr-8009?
Nov 26, 2013 2:08:25 PM org.apache.catalina.core.StandardService? stopInternal
Information: Stopping service Catalina
Nov 26, 2013 2:08:25 PM org.apache.catalina.loader.WebappClassLoader? clearRefere
ncesJdbc
Schwerwiegend: The web application logicaldoc registered the JDBC driver [org
.hsqldb.jdbc.JDBCDriver] but failed to unregister it when the web application wa
s stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregiste
red.
Nov 26, 2013 2:08:25 PM org.apache.catalina.loader.WebappClassLoader? clearRefere
ncesThreads
Schwerwiegend: The web application logicaldoc appears to have started a threa
d named [HSQLDB Timer @20bc83db] but has failed to stop it. This is very likely
to create a memory leak.
Nov 26, 2013 2:08:25 PM org.apache.catalina.loader.WebappClassLoader? clearRefere
ncesThreads
Schwerwiegend: The web application logicaldoc appears to have started a threa
d named [Thread-4] but has failed to stop it. This is very likely to create a me
mory leak.
Nov 26, 2013 2:08:25 PM org.apache.catalina.loader.WebappClassLoader? clearRefere
ncesThreads
Schwerwiegend: The web application logicaldoc appears to have started a threa
d named [webdav] but has failed to stop it. This is very likely to create a memo
ry leak.
Nov 26, 2013 2:08:25 PM org.apache.catalina.loader.WebappClassLoader? clearRefere
ncesThreads
Schwerwiegend: The web application logicaldoc appears to have started a threa
d named [dav-resources.data] but has failed to stop it. This is very likely to c
reate a memory leak.
Nov 26, 2013 2:08:25 PM org.apache.catalina.loader.WebappClassLoader? clearRefere
ncesThreads
Schwerwiegend: The web application logicaldoc appears to have started a threa
d named [Scheduler_Worker-1] but has failed to stop it. This is very likely to c
reate a memory leak.
Nov 26, 2013 2:08:25 PM org.apache.coyote.AbstractProtocol? stop
Information: Stopping ProtocolHandler? http-apr-8080?
Nov 26, 2013 2:08:25 PM org.apache.coyote.AbstractProtocol? stop
Information: Stopping ProtocolHandler? ajp-apr-8009?
Nov 26, 2013 2:08:25 PM org.apache.coyote.AbstractProtocol? destroy
Information: Destroying ProtocolHandler? http-apr-8080?
Nov 26, 2013 2:08:25 PM org.apache.coyote.AbstractProtocol? destroy
Information: Destroying ProtocolHandler? ajp-apr-8009?

Change History (5)

comment:1 Changed 9 years ago by car031

  • Milestone 6.8.1 deleted
  • Priority changed from Critical to Trivial

By seing at your logs it seems that Tomcat stopped and the port 8080 is left ready.
Can you check please if you see any tomcat process?
on linux you can check the output of this command:
ps -ef | grep java

comment:2 Changed 9 years ago by jewgenij

The tomcat process is still open; i still see the tomcat-java-window (win 7 x64).
Before starting tomcat there is no java process at all.

comment:3 Changed 9 years ago by car031

In this case it seems this is an issue in the tomcat binaries or some kind of issues with your OS, more than a LogicalDOC bug.
Moreover we don't have other known issues on this point.

Please manually kill that process, and start tomcat in this way:
C> catalina.bat start

Then stop it in this way:
C> catalina.bat stop

comment:4 Changed 9 years ago by jewgenij

Already tried it, same result.
Not sure that is not an logicaldoc application issue because i could start and stop the same tomcat server (without logicaldoc) without any problems.
I used also a tomcat from apache not from the bundle and there i had the same behaviour.
I looks to me like a logicaldoc issue. Any suggenstions??

comment:5 Changed 9 years ago by car031

  • Milestone set to 6.8.1
  • Priority changed from Trivial to Minor
  • Resolution set to fixed
  • Status changed from new to closed
  • Summary changed from Tomcat Application failed to stop to Tomcat Application fails to stop
Note: See TracTickets for help on using tickets.