"tprice" wrote:
We occasionally get errors when a JMS topic subscriber disconnects. It appears that sometimes the server does not know that a subscriber has disconnected and generates the following error:

2005-01-06 23:05:32,159 ERROR [org.jboss.mq.server.JMSDestinationManager] The connection to client ID:1 failed.

This causes *all* subsequent JMS_MESSAGES destined for the disconnected subscriber to be added to the JMS_MESSAGES table. Since this application runs 24/7, this eventually causes nasty things to happen with the database.

The configuration we are using is:

Release ID: JBoss [Zion] 4.0.0 (build: CVSTag=JBoss_4_0_0 date=200409200418)
Java version: 1.4.1_07,Sun Microsystems Inc.
Java VM: Java HotSpot(TM) Server VM 1.4.1_07-b02,Sun Microsystems Inc.
OS-System: Linux 2.4.7-10,i386
Oracle

We have also seen the same problem with JBoss 3.2.2, Windows 2K, HSQLDB. I'm trying to avoid turning on tracing because we have dozens of clients subscribed to receive messages at once second intervals and the errors occur so infrequently. However when they do occur, it obviously causes big problems.

Any pointers?
Tim.

 // This is where it prints your message
 public void connectionFailure(ConnectionToken dc) throws JMSException
 {
 log.error("The connection to client " + dc.getClientID() + " failed.");
 connectionClosing(dc);
 }

 public void connectionClosing(ConnectionToken dc) throws JMSException
 {
 if (dc == null)
 return;

 // Close it's ClientConsumer
 ClientConsumer cq = (ClientConsumer) clientConsumers.remove(dc);
 if (cq != null)
 cq.close();
...

Thanks yaar