yes same issue is still present at the moment !
The one and only workaround we have set up has been a new process that sends periodically a kind of 'fake message' to the queue.
This means a really new batch process that every 15minutes sends a Jms message that gets correctly delivered by the queue but then after it is discarded by the application.
This solution is a workaround and, even if we are a little pessimistic, we hope to find a different one, this solution adds network traffic and also some cpu processing.