[JBoss-user] [Messaging, JMS & JBossMQ] - Re: JMS fills up database

2005-01-11 Thread tprice
Thanks Adrian  for the resposne.

I'm creating a subscriber using:

topicSubscriber = session.createSubscriber(topic);
which, I think, should default to a non durable subscription. Is there 
something else I need to do?

Tim.


View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861614#3861614

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861614


---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Messaging, JMS & JBossMQ] - JMS fills up database

2005-01-07 Thread tprice
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:

anonymous wrote : 2005-01-06 23:05:32,156 WARN  
[org.jboss.mq.server.ClientConsumer] Could not send messages to a receiver.
  | java.net.SocketException: Connection reset
  | at java.net.SocketInputStream.read(SocketInputStream.java:168)
  | at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
  | at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
  | at 
org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBufferedInputStream.java:67)
  | at 
java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2133)
  | at 
java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2316)
  | at 
java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2383)
  | at 
java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2455)
  | at 
java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2604)
  | at java.io.ObjectInputStream.readByte(ObjectInputStream.java:845)
  | at 
org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:279)
  | at java.lang.Thread.run(Thread.java:536)
  | 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.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861163#3861163

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861163


---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user