JMS integration with Nirvana Message Broker

Solution In Progress - Updated -

Issue

We have got an installation of a JBoss 5.2 on a RHEL host. We connect to a external JMS queue. The JMS-Queue is situated on a Software AG Nirvana Message Broker. We use the corresponding client libs (ContextFactory: com.pcbsys.nirvana.nSpace.NirvanaContextFactory)

The messages are pure xml and have got a size from about a few kbytes. On JBoss there is a message driven bean that is connected to the queue. What's happening now is as follows
- Messages will be send to the queue
- MDB on JBoss receives them, processes them
- JBoss is commiting the CMT (chnages can be seen in database)
- Anyway after a while (100 messages) the processing stops.
- Shutting down the server is not possible. Thread dump reveals there are still some active threads running nirvana code
- When process is killed, messages are returned to the queue

It seems that there is no ACK send back to nirvana server.

  • Is there a known bug in JBoss MDB features that will result in such behaviour?
  • Which component is responsible for sending the ACK (JBoss EJB Container, TX-manager or even the jms client framework)?

Environment

Red Hat JBoss Enterprise Application Platform (EAP) 5.2.0

  • EJB 2.0
  • Nirvana Message Broker integration

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.