message-driven-bean

问题 Can we pause the MDB message processing for some time? For example: Jboss 1-deployed MDB for message processing. Jboss 2:-Bean for gathering user details. If the MDB from jboss 1 calls bean in jboss 2 for getting users details. If this is the case, when we restart the Jboss 2, we need to pause the MDB in jboss 1 till the jboss 2 is UP. Is there any option to pause MDB, so that we can avoid failure of message? 回答1: I doubt you can stop an MDB without stopping the whole application. It is

问题 I wrote an unit-test for an activity which finally puts a message into a queue. As soon as a message is put into that queue, a message driven bean starts processing. But I don't want to test MDBs in a unit test. How can I tell OpenEJB to ignore them? I set up OpenEJB with several properties: p.setProperty(Context.INITIAL_CONTEXT_FACTORY, "org.apache.openejb.client.LocalInitialContextFactory"); p.setProperty("openejb.deployments.classpath.include", ".*"); p.setProperty("openejb.localcopy",

问题 I have an java EE application which has one message-driven bean and it runs fine on JBoss 4, however when I configure the project for JBoss 6 and deploy on it, I get this error; WARN [org.jboss.ejb.deployers.EjbDeployer.verifier] EJB spec violation: ... The message driven bean must declare one onMessage() method. ... org.jboss.deployers.spi.DeploymentException: Verification of Enterprise Beans failed, see above for error messages. But my bean HAS the onMessage method! It would not have worked

问题 I am trying to understand concepts related to MDB, MQ, JMS. I did research on SO before asking this question. Is this possible scenario: MDB deployed on Application Server, say on JBOSS (on physical Server-A). MQ (say ApacheMQ) on a difference physical server-B. So can the MDB deployed in physical server-A get messages from physical server-B? If this is possible, then does MDB use JMS API's? I have heard Jboss has MQ, which i presume MQ withing Jboss application server; however i want MDB in

问题 I have 2 EJB app, A and B. A has a stateless session that send a message to app B (Message driven bean). App B send a message back to app A. Now, I have the value I want in the message listener in the stateless session bean in A. But I need to show it from Main. I tried declaring a variable and store the value in it. But when I call it from Main, the value is lost. @Stateful public class AManagerBean implements ejb.AManagerRemote { @Resource(mappedName = "jms/QueueConnectionFactory") private

问题 I need to programmatically stop a Message-driven bean from receiving messages from a JMS queue. My environment is WebSphere Application Server v7. I think it could be done by some MBean operation on an Activation Specification MBean, but I can't locate the activationSpec using WebSphere's adminclient API. I've browsed the JMX tree using JConsole and also tried printing out every available MBean and searching for the name of the activationspec. It's nowhere to be found. Is this the right

问题 I need to set the max pool size on a MDB on weblogic 10.3. I inserted this annotation on MDB directly @ActivationConfigProperty(propertyName="MaxPoolSize", propertyValue="1")}) but it seems not to work. Is there any other option to set? 回答1: Try using weblogic work manager settings to constrain the number of concurrent threads. The max-threads-constraint can be applied to a work manager set up for the specific MDB (or as part of a pool if you apply it to more than one bean) so, for instance

问题 Is it legal to inject a @Stateful into an MDB? @Stateful public class InteruptBean implements Interrupt { .... } @MessageDriven(...) public class EchoTrigger implements MessageListener { @EJB Interrupt interrupt; .... } Or better phrased: Can I use a stateful EJB to pass state around in an asynchronous Event Driven Architecture? 回答1: Yes, it's "legal", but it's nonsensical. MDBs instances are pooled like SLSBs. The MDB will become non-functional after the SFSB times out. It might work to

问题 I got following error while deploying my ear in wildfly 8.1.0 server 1)Error: Caused by: javax.resource.spi.InvalidPropertyException: Destination is mandatory", "jboss.deployment.subunit.\"wildfly.ear\".\"wildfly- ejb.jar\".component.ReRattingMDB.START" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"wildfly.ear\".\"wildfly-ejb.jar\".component.ReRattingMDB.START: java.lang.RuntimeException: javax.resource.spi.InvalidPropertyException: Destination is mandatory 2

问题 We have a MDB listening to a Queue reading data and sending data to another Queue @MessageDriven( activationConfig = { @ActivationConfigProperty( propertyName = "destinationType", propertyValue = "javax.jms.Queue" ) }, mappedName = "jms/dataQ") public class DataMDB implements MessageListener { @Resource(name="jms/dataQueueConnectionFactory") private ConnectionFactory connectionfactory; @Resource(name="jms/dataDestinationQ") private Destination destination; ... } and an XML (ibm-ejb-jar-bnd