Morven's questions

I have a Tomcat server that won't shut down.

It is listening on the correct port (8005, for this one) to receive the SHUTDOWN command. I can issue that command, either with the bin/shutdown.sh script or by telnetting to that port and typing SHUTDOWN.

At this point, the shutdown port closes; I can no longer connect to it. The AJP13 port stays open, though; nothing is logged in catalina.out, and things don't shut down.

Anyone seen this before?

This is on Solaris 10 on Sparc, if it matters (it probably doesn't) and Tomcat version 6.0.20.

I have a server (T5220, though I doubt it matters) running Solaris 10 8/07 and I have a ZFS pool, "mysql", on internal disk. Within it I have a filesystem "mysql/data/4.1.12", which I snapshot hourly with a script from cron.

I have one snapshot, created as one of those hourly snaps, that will not destroy. I have renamed it out of sequence to be "mysql/data/4.1.12@wibble" so that my script will not try and fail to destroy it, but it was originally within the sequence, though I doubt that matters. It renames successfully. The snapshot can be successfully navigated and read from through the .zfs/snapshots directory. It has no clones based on it.

Trying to destroy it does this:

(265) root@web-mysql4:/# zfs destroy mysql/data/4.1.12@wibble
cannot destroy 'mysql/data/4.1.12@wibble': dataset already exists
(266) root@web-mysql4:/# 

which is apparently nonsensical: of course it already exists, that's the point!

Anyone seen anything like this before? Web searches show nothing obviously similar.

I can provide patches installed if necessary.