The file-pm is not officially supported anymore and does not get called by default. I wonder if that was clear in the installation instructions? The best PM is the JDBC2 or 3, with your choice of JDBC supporting database. MySQL and Postgres are good choices, HSQLDB (the install default) doesn't have any problem with limited datasets, but YMMV.
According to the instructions, HSQLDB is not a good choice either (my recent exp. with it agrees). I am working on the jdbc2-service for Informix (our DB of choice) as an alternative.
I was really just looking for any explanation as to why the file-pm takes all the messages out of the queues, and the MessageCache puts them all right back (and possibly if there is a way to prevent that). I have googled and search all these forums with no luck.
Anyway, just so I don't go chasing my tail again; does the same thing happen with the jdbc2 pms ? I am hoping that it does not remove all the messages and put them all back when you start JBoss ( 2 hour startup time != good ).
Thanks Gorano! That explains things quite well.
To sum up, this is a *feature* which will hopefully be fixed in a future release.