About stop

31-40 of 116Refresh
Forum
2

log problem

Hi we have found that when restarting the database in contrast to making stop/start database log ... should have the same effect as stopping the server and then starting it, and therefore should produce 2 logging messages, e.g. [2014-02-07 13:00:00 #1 server] Server on port 6136 has stopped by 13584@odb
Forum
2

ObjectDB shuts down

has stopped. DB can be normally started after it shutdowns and log continues. Logging is currently set ... is shutting down, do you see a stop message in the log? If yes, is it always exactly at the same time ... .       Hi, there is no STOP message in the log. Shutdown doesnt hapen always exactly at the same time
Forum
2

ODB IndexActivation NullPointerException

' * Batch ended at '2LG' * Batch ended at '2oq' * Batch ended at '2LG' And the Application stopped ... build 2.6.7_07. It is unclear why the application stops working and how a NullPointerException ... finished with all activities that may be proceed and should not be stopped before closing the database
Forum
2

Redeployment in GlassFish - Failed to open file

the database file for redeployment? Every time, I need to stop the server, start it again and redeploy ... was already stopped at org.glassfish.web.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1410 ... , or was already stopped .... Sorry for belated reply. The problem was solved by closing the entity
Issue
2

Resource leaking via a rogue Shutdown Hook

application's class loader. When the application is stopped (not the server, just the application) the hook ... application, and after the application has been stopped. The thing to look for is the fact, that the only path to a garbage collection root after stopping is via the hook. Thank you for your report. The shutdown hook is removed in build 2.2.9_03. Lachezar
Forum
1

@Entity saved in Tomcat session - problem

Hi, I have found a problem, when storing @Entity object in Tomcat session. When starting or stopping Tomcat, I get nasty exception - please check attached log. Strange thing ... this serialization problem. Please try it. Notice that after stopping and starting Tomcat entity
Forum
1

A distinguished Name for server or explorer is good for maintaining!

the server, but when I stop it, I get this message: ./server.sh stop
Forum
1

best practice for DB recovery

to recover from a failed instance would be to simply stop all writing, take a backup from the working ... without stopping the application. We can pause it for a short while when we switch back as
Forum
1

Connection is closed Caused by: java.io.EOFException

server to stop ? Of course, the exception encountered is a symptom of the real problem that the server has stopped! Actually, I was concentrating so much on my own logs that I neglected the ObjectDB logs
Issue
1

Exception upon index definition change

should never cause the application to stop. Even the Doctor does not run anymore using this index definition ... to stop Of course. Agreed. However, unfortunately the stack trace doesn't provide much information