Just doing a test here where I've set the journal size to 8192 bytes to force the condition to happen much sooner for me. The test is still running, however I've got 1550 journal files, the highest named file is data-7512. So it doesn't look like it's the number of journal files. Is there any chance you're running low on disk space? Maybe it's worth trying a test where you increase the journal file size to see if that helps things?
I'm running a second test now, different data but this time it doesn't appear to stop at the 256th file.
Trouble is over the last year of building and testing aps with Fuse I've had a number of these weird and unexplained and often unrepeatable scenarios.
Earlier this year I had issues with out of memory errors from the JVM, then I had issues with messages going missing, now this. I'm concerned about its stability.
I know there were some deadlock issues in the broker related to the persistent store that were resolved awhile ago, but it's possible there's still one edge condition that's yet to be discovered. If you do run into this again the best thing to do to help diagnose the problem is to get a thread dump, if you're on UNIX do a kill -3 on the JVM or in Windows you'd do Ctrl-Break and capture the output. A thread dump would help us determine if it's indeed a deadlock and give an idea of where it's happening.
Unfortunately despite many attempts I've not been able to create this again. Figures.
I've had plenty of other one off scenarios I can only create once. I must start backing up the logs.