Nondurable subcriber received the msg after JBM reboot

[lanceliao1]

We are using Jboss4.2.2 JBM 1.4.2 sp1.
publish persistent 50,0000 msg

publisher.publish(objMsg, DeliveryMode.PERSISTENT, PRIORITY,0);

All msg subscriber are Nondurable subscriber.

Due to some subscriber are very slow,jmx console show depth are increasing.And we fount the count of JBM_MSG&JBM_MSG_REF are increasing too.
After rebooting JBM and client,the new client begin to consume old messages in db. Why?

[lanceliao1]

Test again,It is my mistake.
The new subscriber do not receive old pending msg after JBM reboot.

But,the records in db does not deleted,my JBM_MSG_REF has more than 50,000 records.

[gaohoward]

you can manually deleted them by yourself if you don't need them.

[lanceliao1]

Thanks for reply.
Any plan to delete the out-of-date msg automatic if no durable subscriber?
The system will slow down when the records increasing in huge messages situation.

[timfox]

Yes, this is the way JBM 2.0 already work (see JIRA).

JBM 1.x is in maintenance only mode, we're not planning on backporting new features.