AMQ reports STOMP client still connected althought it isn't

[Aleksandar Ivanisevic <al...@ivanisevic.de>]

I'm still having a problem described here

http://fusesource.com/forums/thread.jspa?threadID=1000&tstart=0

and here:

http://issues.apache.org/activemq/browse/AMQ-1715

It doesn't happen very often and it is always a result of some very
rare event, like a severe OOM situation or a machine crash, but when
it happens i have not only to restart AMQ, but also delete the
complete AMQ data directory which obviously affects other pending
messages.

Is there a way to force the subscriber out without touching pending
messages for other durable subscribers? I've tried deleting every file
in data/kr-store which contains my client's client-id but then AMQ
won't even start, obviusly I've deleted too much. Where is it written?
What format are the files in data/kr-store directory?