Messages Not Always Delivered

[stuartw]

I am currently experiencing an intermittent problem in an application that I have developed where messages are not always delivered to my MDB. My application is running in JBoss AS 4.2.3 with JBoss Messaging 1.4.4 installed and I am using an Oracle database. I have managed to recreate this problem in a more simple test application running in the same environment.

My simple application behaves as follows:

1. A JSP calls a session bean to put x messages on a queue
2. An MDB consumes each message and creates an entry in the database to signify that it has received the message (EJB3 entity bean)
3. The ID of the database entry created is then put on a second queue
4. An MDB consumes each message from the second queue and updates the relevant database entry to signify that it has received the message

On loading 100 messages onto the queue I generally find that 99 entries have been created in the database and that 98 of those entries have been updated. I.e. 99 messages were consumed by the first MDB and 98 messages were consumed by the second MDB. This is not always the case, sometimes both figures are 100, sometimes both are lower.

Has anyone else experienced a similar poblem or does anyone have any suggestions for what I might be doing wrong?

[gaohoward]

I think you can use jmx-console to inspect message count on the queue to help further diagnosis.

Howard

[stuartw]

Hi Howard,

I should probably have said in my original post that I have had a look in the jmx-console and on my first queue there seems to be a message waiting (currently being delivered) but on my second queue there are not any messages waiting to be delivered.

Thanks,

Stuart

[gaohoward]

Can you try jbm 1.4.5.GA ?

[stuartw]

I have tried 1.4.5.GA with my test application and see the same results

[gaohoward]

Do you have a test to upload?

[stuartw]

Hi,

I have uploaded the application that I have been using to test this. The steps to recreate are as follows:

1. Deploy attached files

2. Open http://localhost/queue-test in a browser

3. Enter something in the value field

4. Submit the form

5. Run the following SQL: select count(*), state from message group by state;

If everything has worked then this shoud show that there are 100 entries in the PROCESSED state. Any time I run this I end up with around 98-99 entries in the PROCESSED state and 1-2 in the INITIAL state.

Thanks,

Stuart

[gaohoward]

I saw in the queue-test-oracle-ds.xml you use OracleXADataSource as the data source class. JBoss Messaging doesn't need an XA data source to work with. You need a normal datasource instead. Please try using a normal oracle datasource.

Howard

[stuartw]

Hi Howard,

The  datasource file that I have uploaded is the one used only by my  application. Please find uploaded the datasource file that is used by  JBoss Messaging, this uses a normal datasource. I have also uploaded my  oracle-persistence-service.xml (from the directory jboss-messaging.sar)  so that you verify that JBoss Messaging is indeed using this normal  datasource.

Thanks,

Stuart

[stuartw]

I have now managed to discover that this is behaviour is cased by a bug in JBoss 4.2.3 (https://jira.jboss.org/jira/browse/JBAS-5801) and that a workaround is available. More details can be found in http://community.jboss.org/thread/49345.pdf