JBossDeveloper

This is not really an easy change...

Paging itself on 2.1.2 is using duplicate detection to avoid duplicating messages from paging. If you are using duplicate detection for your own ends when you get a duplicated message the whole page read will be rejected since the system will think that it has already read before.

I think the best would be you avoiding using duplicate-detection and paging together with 2.1.2.

This doesn't affect the latest versions since we have fixed it already.

If you want to hack on the code... look at PagingStoreimpl::onDepage...    there's a call to PostOffice::route and the PostOfficeImpl::route will take care of the duplicate detection and will cancel the whole page when it happens.

So the easier solution for you will be avoid duplicate-detection & Paging for now while you move away from 2.1.2