You should still handle it robustly.

- Godmar

On Mon, Aug 23, 2010 at 12:24 PM, Christian Grün christian.gruen@gmail.comwrote:

It's never advisable to shoot down BaseX – although open databases will be correctly closed even with SIGINT. Instead, use the "stop" comand to properly terminate the server process:

$ basexserver --help Usage: BaseXServer [-dpz] [stop] stop stop server -d debug mode -p<port> server port -s start as service -z suppress logging

On Mon, Aug 23, 2010 at 5:45 PM, Godmar Back godmar@gmail.com wrote:

...

When I interrupt BaseXServer with SIGINT, I occasionally see backtraces

like

...

this one.

• Godmar

Starting BaseXServer on port 1985 BaseX 6.2.3 [Server] Server was started. java.io.IOException: Stream closed at sun.nio.cs.StreamEncoder.ensureOpen(StreamEncoder.java:26) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:99) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:116) at java.io.OutputStreamWriter.write(OutputStreamWriter.java:203) at java.io.Writer.write(Writer.java:140) at org.basex.server.Log.write(Log.java:76) at org.basex.server.ServerProcess.run(ServerProcess.java:178) java.io.IOException: Stream closed at sun.nio.cs.StreamEncoder.ensureOpen(StreamEncoder.java:26) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:99) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:116) at java.io.OutputStreamWriter.write(OutputStreamWriter.java:203) at java.io.Writer.write(Writer.java:140) at org.basex.server.Log.write(Log.java:76) at org.basex.server.ServerProcess.run(ServerProcess.java:178)

---

BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk