Home » Support » Issue Tracking » Service terminated silently (crashed?)...is there any way to cause a crash dump?

Service terminated silently (crashed?)...is there any way to cause a crash dump?

Type: BugVersion: 2.6.1Priority: NormalStatus: FixedReplies: 1
#1

After running without issue, uninterrupted for seven months, our instance stopped silently.  The contents of the log are as follows:

Object DB log:
ObjectDB Server started on port 6138.
ObjectDB Server stopped.
ObjectDB Server started on port 6138.
ObjectDB Server stopped.
ObjectDB Server started on port 6138.
ObjectDB Server started on port 6138.  <--This is where I restarted the service.

 

Note there is no "Server stopped" before the final "Server started".

I assume the service crashed.  Are there any startup options we should be using to cause a stack trace upon abrupt termination?

#2

It may be an issue that was found and fixed in version 2.6.5:

    "Fixed server crash on exceeding maximum number of connections specified in configuration."

If you are using an older version you should increase the value in the server configuration, e.g.

<server>
  <connection port="6136" max="1000000" />

Starting 2.6.5 the client gets an exception but the server continues to work as expected and max="0" (which is the default starting 2.6.5) indicates no limit.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)

Post Reply

To post a reply and/or subscribe to update notifications - please login