Hi, I've got what I think is a really basic JBoss Messaging setup, with JBossAS 4.0.5GA, and JBoss Messaging 1.0.1GA running on a SLES Linux server with JDK 1.5.0_09. Messages persist to a PostgreSQL database. I use JBoss as purely a JMS provider, there are no other AppServer/EJB/MDB components. My JMS client is down the other end of a VPN, which I believe to be stable/reliable. The client is just a couple of classes implementing MessageListener and a couple of classes using MessageProducers to send messages. These classes are hosted in a Jetty servlet container. This runs fine whilst I am developing during the day; but when I leave overnight and return, I come into a set of large stack traces on the client, and a few smaller stack traces on the server. It appears to be coming from, or manifesting itself in the LeasePinger.sendClientPing. I wondered if it was an issue with the VPN link going down, but if I disable the VPN manually, I do not get these stack traces, just a brief message telling me there was an "Error sending lease ping to server for client invoker (session id a011o-9oetow-eve0b98y-1-eve0baiy-6.", which is absolutely fine and understandable. I'll post the stack traces in a following post. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991951#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...