I am experiencing exactly the same problem I have the setup like you but the messages after consumption are never removed from the memory and when the highMemory mark is reached there are put on the disk and never cleaned.
I have created my non durable topic from the testTopic sample as described int he Jboss 3.0 RC1, jbossmq-destination-servcies.xml. There is also a example of the durable test topic. I dont find any difference in the two topics. Am I using a durable topic? If yes how can I create a non durable topic?
I've got the same problem: JBoss 3.0.0 JBossMQ, 1 non-durable test-topic, multiple publishers and subscribers (using selectors). With really low (or zero) High/MaxMemoryMark values, CPU usage is way-up and messaging performance is awful, uping the values just postpones the problem. I am just unzipping the download, using the default server and running. Nothing fancy.
How do I get JBossMQ to run for an extended period without a performance hit cleaning up non-persistent maessages.
I tried using the "rollinglogged" PersistenceManager but on Server start-up of jbossmq-service.xml I get a:
DeploymentException, unable to locate method for: getInstance(), etc. What am I missing here?