journaledJDBC checkpoints

I noticed strange behavior when I switched from amqPersistenceAdapter to journaledJDBC. After non consumed messages are stored in database, producers and consumers become very slow. After enabling debug traces I see very frequent checkpoints, almost after every other message. Anyone knows what can

how can consumer skip messages to process them later?

Is there a way for consumer to skip messages that cannot be processed? But keep processing other messages. And process old ones later. Tried to not acknowledge messages but looks like there is a limit on pending messages (40). I use persistent queues. Thanks -- View this message in context: htt