I am using Java Enterprise (3.1) with Glassfish. I have two seperate EARs which are communicating synchronously via JMS. More specifically:
We have a scenario where, after 开发者_运维问答processing an incoming message A with a Message-Driven Bean, we write a follow-up message B to another queue. We are using Glassfish 3.1.
I\'m using EJB 3.1 and I want to configure an MDB to listen to multiple 开发者_JAVA百科queues. I\'d prefer defining the queue names via XML but the other definitions via annotations.
Given: A JMS message queue. A timer service which puts messages to that queue periodically (from a database).
We have a javax.ejb.TimedObject which queues messages to an MDB like so... ctx = new InitialContext();
in a message driven bean i persist entries to lookup-table with uni开发者_JS百科que entries. Basicly i create a select statement with the criteria api and if i don\'t find an entry, i create one.
Is there any difference between an asynchronous JMS (开发者_Go百科Java Messaging Service) consumer vs an actual MDB (Message Driven Bean). The only difference I see is the MDB class
I am running into a deadlock situation when receiving messages on a pool of MDBs in GlassFish. If I receive multiple messages that concurrently try to update the same set of rows, the MDB throws a Loc
I have a onMessage method where I\'m reciving an ObjectMessage from the Queue and using that information to populate and persist a JPA entity object. But when something goes wrong while persisting the
I developed a resource adapter that I would like to use within my application ear, deployed in JBoss 5.1. After playing around with annotations and xml files, I came up with the following setup.
加载中,请稍侯......