Since upgrading to JBoss 4.0.5 and Messaging 1.2beta I've gotten a broken pipe
error twice while running under high load for extended periods. If I stop and
restart the one Queue that is being affected, as well as restart all the
clients of that queue, things start working again. This is
I am using mysql and I am using the mysql-persistence-service.xml file from the
1.2/examples/config directory.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3997576#3997576
Reply to the post :
I decided to upgrade to 4.05 and messaging 1.2beta since I hadn't heard about
about my previous post and I was stuck. Now I cannot start jboss with
messaging twice in a row without deleting all the tables in my mysql database.
If I try to restart it without deleting the tables, I get the
I just switched from messaging 1.0.1CR5 to 1.0.1SP2 because the old version
would consistently silently stop sending messages on certain queues under load.
Now with SP2 I get an error on my client, but nothing on the server. After
20-60 minutes of running under load, I get the following
Ok, I've been running various tests and it seems that once items get stuck in
the jboss queue the only way to fix it is to stop and restart the queue.
When items got stuck, I shut down all my producers and consumers and ran the
following program, it never received a single item from the queue.
Hmm...I thought I had it solved, but then I came in this morning to having
96,000 items stuck in the queue. Stopping and restarting my client apps isn't
pulling anything out. Also, using the admin list messages option isn't
showing any messages, either with selectors like serverID is null or
Sure, let me try to explain it better. I'm using JMS as part of an indexing
system, so items are processed and put in a queue for indexing. If an item has
never been indexed before the serverID property of the messages is set to null,
because I don't care which server it ends up on, just that
At one point I did have 2 consumers on a session, but since my post yesterday I
only have 1.
I'll try to post the code, but I have written some wrappers around things so it
might be a mess to post...
View the original post :
Ok, I tried a test class and everything worked fine. While writing it I did
run into a problem with MessageConsumer.receive(0). My old JMS server would
block indefinitely until there was something to receive. It did not appear as
if JBoss was doing this and I switched my test code to a
Well, after messing with my program and my test case I still can't make this
happen in isolation. It seems like my MessageConsumer stops receiving any
messages where the server Id is not null. The consumer isn't getting closed
since it still receives the rest of its messages. But I have to
Ok, I figured it out, not sure if this was stupidity on my part or just me
expecting the system to behave a certain way.
Basically I am using JMS with an indexing service and each client switched
between two selectors, one looked like : (serverID=+serverID+ OR serverID IS
NULL) and the
I'm trying to switch from SwiftMQ over to JBoss Messaging. I've been having a
problem where messages get stuck in a queue whose consumers are using
selectors. I have read about the issues involved with selectors and speed,
however this is not the case here. I have 4 consumers with a selector
12 matches
Mail list logo
