Thanks Marina,
I've included the output from my server below. You can see the database has
changed size from 473MB to 1.8MB and the problem is fixed. That's great and
something I can shedule into maintenance windows on our systems.
In production and test I always use asadmin to start/stop the server (albeit
through init.d scripts) however, in developement I sometimes have to resort
to a kill, maybe once a month.
Thanks for your help and keep up the great work on glassfish!
Thanks,
Steve.
# du -s -h /opt/glassfish/glassfish/domains/domain1/lib/databases/* 473M
/opt/glassfish/glassfish/domains/domain1/lib/databases/ejbtimer # service
glassfish stop stoping glassfish : Waiting for the domain to stop
.................. Command stop-domain executed successfully. [ OK ] # rm -f
-r
/opt/glassfish/glassfish/domains/domain1/applications/ejb-timer-service-app/
# rm -f -r /opt/glassfish/glassfish/domains/domain1/lib/databases/ejbtimer/ #
service glassfish start starting glassfish : Waiting for domain1 to start
................................... Successfully started the domain : domain1
domain Location: /opt/glassfish/glassfish/domains/domain1 Log File:
/opt/glassfish/glassfish/domains/domain1/logs/server.log Admin Port: 4848
Command start-domain executed successfully. [ OK ] # du -s -h
/opt/glassfish/glassfish/domains/domain1/lib/databases/* 1.8M
/opt/glassfish/glassfish/domains/domain1/lib/databases/ejbtimer #
--
[Message sent by forum member 'stevenb']
View Post: http://forums.java.net/node/838859