JBM messages getting stuck in queue?

[theoverlord]

The basic problem is that JBM messages appear to be getting stuck in a queue somewhere. I don't know where they're getting stuck and I don't know how to troubleshoot it.

I'm using JBM 1.4.1.Beta1 and JBoss AS 4.2.2.GA. I'm also using JBR 2.2.2.SP8.

I'm using a clustered queue on clustered JBoss application servers.

Non-clustered JBoss instances containing MDBs are configured to consume the messages from the clustered queue. I'm using a JBM bridge to take messages from the clustered queue and deliver them to a local queue on the non-clustered JBoss instances which are then consumed by the MDBs.

The MDBs are returning a response using a typical temporary queue replyTo pattern.

Anyhow messages all flow nicely for a while but then it all gets jammed up and stuck and petty quickly nothing is moving.

What do you think is going on?

How do I even begin to trouble shoot the problem?

I tried using the JMX console but it shows nothing in the queue (listAllMessages). In fact I've never seen the JMX console show anything in the queue ever and I believe it's malfunctioning. It always returns "[]".

I'm also getting a lot of deadlock error messages relating to the JBM_COUNTER table. JBM is apparently trying to increment some counter by doing a select followed by an update. The database I'm using is Sybase 15. I'm using an a transaction isolation level of READ_COMITTED and have changed the table to datarow locking.

[timfox]

For a start, JBM 1.4.1 is for *JBoss AS 5 only*, I've no idea if it would work with JBoss AS 4.x.

[theoverlord]

I think I found my problem.

I had set my MDB maximum pool size way too high (15 - lol)

I reduced the maximum pool size to 2.

I'm still performing tests as I type this and it appears to be more stable.

I can see how setting a maximum MDB pool size too high would cause the problem.

[theoverlord]

Well, I spoke too soon. Messages are getting stuck again.

How do I determine what the state of the queues and/or bridge are?

It's really hard to figure out where the problem is.

[theoverlord]

"timfox" wrote:
For a start, JBM 1.4.1 is for *JBoss AS 5 only*, I've no idea if it would work with JBoss AS 4.x.

The reason I "upgraded" to JBM 1.4.1.Beta1 was because I had the problem I reported with JBM 1.4.0.SP3 in hopes it would solve my problem but alas it has not.

[timfox]

Almost certainly your problem is a config issue or a misunderstanding of how clustering or MDBs work. If you have a support contract someone can take you through it.

If you're looking for free support, there have been plenty of threads on this forum on how to configure MDBs with clustered queues. This is something that comes up again and again.

You can also try 1.4.0.SP3_CP03 which is the latest version for JBoss AS 4.x (look in svn). http://anonsvn.jboss.org/repos/messaging/tags/

[theoverlord]

I believe I do have a support contract.

I'll try JBM 1.4.0.SP3_CP03 soon.

Thank you.

[timfox]

If you have a support contract you should be using EAP 4.3 cp01, which already has JBM 1.4.0.SP3_CP02 built in.

The community versions are not supported.

[theoverlord]

What versioin of JBR should I use with 1.4.0.SP3_CP03 ?