from your reply I assume I am in an area of I don't know I don't know.
but to forge forward blindly.
at the time it died google was going through the backend
it has been for the last two days the only user.
when I saw the
ExecutionPoolPulseWorker I figured a new thread was introduced based on a schedule service. so I will restate that there was not a manual shutdown done from all the server logs
that something in ofbiz initiated the shutdown.

and apparently I don't know what might have caused it.

Scott Gray sent the following on 7/19/2010 5:45 PM:
That's just the log of a standard shutdown, where do you get the "service is run 
from webtools that shuts down the server" part of your statement?

Regards
Scott

HotWax Media
http://www.hotwaxmedia.com

On 20/07/2010, at 12:40 PM, BJ Freeman wrote:

well a more direct cause of the demo-trunk dying is a service is run from 
webtools that shuts down the server.

from ofbiz.log
2010-07-19 13:24:41,947 (OFBiz_Shutdown_Hook) [    Container 
Loader.java:113:INFO ] Shutting down containers
2010-07-19 13:24:42,008 (OFBiz_Shutdown_Hook) [ Http11Protocol.java:236:INFO ] 
Stopping Coyote HTTP/1.1 on http-0.0.0.0-xxxx
2010-07-19 13:24:42,009 (OFBiz_Shutdown_Hook) [ Http11Protocol.java:236:INFO ] 
Stopping Coyote HTTP/1.1 on http-0.0.0.0-xxxx
2010-07-19 13:24:42,093 (OFBiz_Shutdown_Hook) [ ServiceDispatcher.java:191:INFO 
] De-Registering dispatcher: oagismgr
2010-07-19 13:24:42,132 (OFBiz_Shutdown_Hook) [ 
WebappClassLoader.java:1998:ERROR] A web application appears to have started a 
thread named [ExecutionPoolPulseWorker(0)] but has failed to stop it. This is 
very likely to create a memory leak.
2010-07-19 13:24:42,133 (OFBiz_Shutdown_Hook) [ 
WebappClassLoader.java:1998:ERROR] A web application appears to have started a 
thread named [ExecutionPoolPulseWorker(1)] but has failed to stop it. This is 
very likely to create a memory leak.


from error log

2010-07-19 13:24:42,132 (OFBiz_Shutdown_Hook) [ 
WebappClassLoader.java:1998:ERROR] A web application appears to have started a 
thread named [ExecutionPoolPulseWorker(0)] but has failed to stop it. This is 
very likely to create a memory leak.
2010-07-19 13:24:42,133 (OFBiz_Shutdown_Hook) [ 
WebappClassLoader.java:1998:ERROR] A web application appears to have started a 
thread named [ExecutionPoolPulseWorker(1)] but has failed to stop it. This is 
very likely to create a memory leak.
2010-07-19 13:24:42,549 (OFBiz_Shutdown_Hook) [ 
WebappClassLoader.java:1998:ERROR] A web application appears to have started a 
thread named [ReferenceCleaner] but has failed to stop it. This is very likely 
to create a memory leak.
2010-07-19 13:24:42,550 (OFBiz_Shutdown_Hook) [ 
WebappClassLoader.java:1998:ERROR] A web application appears to have started a 
thread named [TTLObject(0) pulse] but has failed to stop it. This is very 
likely to create a memory leak.
2010-07-19 13:24:42,550 (OFBiz_Shutdown_Hook) [ 
WebappClassLoader.java:1998:ERROR] A web application appears to have started a 
thread named [TTLObject(1) pulse] but has failed to stop it. This is very 
likely to create a memory leak.
2010-07-19 13:24:42,550 (OFBiz_Shutdown_Hook) [ 
WebappClassLoader.java:1998:ERROR] A web application appears to have started a 
thread named [ThreadPool-0] but has failed to stop it. This is very likely to 
create a memory leak.
2010-07-19 13:24:42,550 (OFBiz_Shutdown_Hook) [ 
WebappClassLoader.java:1998:ERROR] A web application appears to have started a 
thread named [ThreadPool-1] but has failed to stop it. This is very likely to 
create a memory leak.
2010-07-19 13:24:42,550 (OFBiz_Shutdown_Hook) [ 
WebappClassLoader.java:1998:ERROR] A web application appears to have started a 
thread named [ThreadPool-2] but has failed to stop it. This is very likely to 
create a memory leak.
2010-07-19 13:24:42,551 (OFBiz_Shutdown_Hook) [ 
WebappClassLoader.java:1998:ERROR] A web application appears to have started a 
thread named [ThreadPool-3] but has failed to stop it. This is very likely to 
create a memory leak.
2010-07-19 13:24:42,551 (OFBiz_Shutdown_Hook) [ 
WebappClassLoader.java:1998:ERROR] A web application appears to have started a 
thread named [TTLObject(async-update)-0] but has failed to stop it. This is 
very likely to create a memory leak.
2010-07-19 13:24:42,551 (OFBiz_Shutdown_Hook) [ 
WebappClassLoader.java:1998:ERROR] A web application appears to have started a 
thread named [TTLObject(async-update)-1] but has failed to stop it. This is 
very likely to create a memory leak.
2010-07-19 13:24:42,551 (OFBiz_Shutdown_Hook) [ 
WebappClassLoader.java:1998:ERROR] A web application appears to have started a 
thread named [TTLObject(async-update)-2] but has failed to stop it. This is 
very likely to create a memory leak.
2010-07-19 13:24:42,552 (OFBiz_Shutdown_Hook) [ 
WebappClassLoader.java:1998:ERROR] A web application appears to have started a 
thread named [TTLObject(async-update)-3] but has failed to stop it. This is 
very likely to create a memory leak.

BJ Freeman sent the following on 7/15/2010 6:17 PM:
as I get time will go through about a  month worth of console logs
looking for when ofbiz lost connection to derby.


james_sg sent the following on 7/15/2010 6:08 PM:

It may be helpful to show some error log...


BJ Freeman wrote:

I been running the trunk as a demo-site and it finally crashed.
I have not plowed through the logs to see the orgin of the error but it
lost its connection to derby.
getting a lot of can not connect errors.

=========================
BJ Freeman<http://bjfreeman.elance.com>
Strategic Power Office with Supplier Automation
<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com<http://www.specialtymarket.com/>
Systems Integrator-- Glad to Assist

Chat Y! messenger: bjfr33man






Reply via email to