message-driven-bean

problem with seam and mdb on jboss5.1

由 你说的曾经没有我的故事 提交于 2019-12-08 04:39:05
问题 I have a problem when using a mdb as a seam component. In the bean I inject some other seam somponents. The problem is that when the server restart after a crash and the mdb is deployed it starts reading the messages but seam is not initialized yet and I got an exception(listed above). If i start the server whith the queues empty and submit a message to queue after the server start it is working ok. Is there a posibility to stop or delay the sending off messages on server startup and start

Wildfly JMS: MDB beans idle when messages exist

由 孤街醉人 提交于 2019-12-08 04:32:02
问题 I am using the bundled JMS implementation on Wildfly 8.1 (HornetQ) to OCR a large number of documents. I want to have a pool of 3 MDBs consuming the messages of a Queue with the documents to be OCRed. Each MDB starts a process with the Apache commons-exec and blocks until that process exits. In my test I have 50 JMS messages (each represents a document to be OCRed) which are loaded on the Queue at the beginning of the test. When the processing starts, at any given time I can see that there

Glassfish v3: Can't Deploy MessageDriven Bean - Missing Destination JNDI Name

由 陌路散爱 提交于 2019-12-08 02:39:53
问题 I am trying to deploy an ear that contains an EJB jar. The jar only contains one MDB class: package my.package; import javax.ejb.ActivationConfigProperty; import javax.ejb.MessageDriven; import javax.jms.JMSException; import javax.jms.Message; import javax.jms.MessageListener; import javax.jms.ObjectMessage; import org.slf4j.Logger; import org.slf4j.LoggerFactory; @MessageDriven(mappedName = "jms/FileUploadedQueue", activationConfig = { @ActivationConfigProperty(propertyName =

Pause MDB message Processing

由 血红的双手。 提交于 2019-12-07 13:16:27
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? I doubt you can stop an MDB without stopping the whole application. It is possible with Spring JMS, but not with regular message driven beans. What you could do, and is apparently

@RequestScoped CDI injection into @MessageDriven bean

由 空扰寡人 提交于 2019-12-07 02:50:49
问题 If I have a request scoped CDI bean injected into a @MessageDriven EJB using JMS, as below, can I assume that any given Foo instance will only be used by a single onMessage invocation at a time? In other words, in the below example, can I safely use member variables in the Foo object to store state across subroutines, analogously to a JSF @RequestScoped managed bean? Note that it's ok if the same Foo object gets recycled sequentially from one onMessage call to the next, as long as each

problem with seam and mdb on jboss5.1

由 老子叫甜甜 提交于 2019-12-06 20:08:26
I have a problem when using a mdb as a seam component. In the bean I inject some other seam somponents. The problem is that when the server restart after a crash and the mdb is deployed it starts reading the messages but seam is not initialized yet and I got an exception(listed above). If i start the server whith the queues empty and submit a message to queue after the server start it is working ok. Is there a posibility to stop or delay the sending off messages on server startup and start sending them only when seam is fully funcional? I tried the @Depends antotatin on the bean but withowt

Message selector on MDBean not working properly

由 ﹥＞﹥吖頭↗ 提交于 2019-12-06 14:45:05
I'm having a bit of a problem with an application, the message-selector of my MD Bean doesn't respond to the filter specified, if i use inside the message-selector : module in ('TELCOM1') works perfectly , but if i add a second parameter to the filter (module in ('TELCOM1' , 'TELCOM2') ) it doesn't work at all, doesn't respond to either parameter. Does anybody have an idea of why can this be , I'm running my application on a WAS 8.5.5 but if i run it on WAS 6 works fine. Ok .. doing some more work on why this was happening, i found that i was using WMQv6 with my WAS 8.5.5 , so i change it to

Glassfish v3: Can't Deploy MessageDriven Bean - Missing Destination JNDI Name

由 。_饼干妹妹 提交于 2019-12-06 04:34:43
I am trying to deploy an ear that contains an EJB jar. The jar only contains one MDB class: package my.package; import javax.ejb.ActivationConfigProperty; import javax.ejb.MessageDriven; import javax.jms.JMSException; import javax.jms.Message; import javax.jms.MessageListener; import javax.jms.ObjectMessage; import org.slf4j.Logger; import org.slf4j.LoggerFactory; @MessageDriven(mappedName = "jms/FileUploadedQueue", activationConfig = { @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"), @ActivationConfigProperty(propertyName = "destinationType",

Message Groups in WebSphere MQ

由 妖精的绣舞 提交于 2019-12-05 22:21:56
问题 I have a requirement that I need to process JMS Messages (via MDB) in a way that Messages belonging to a certain group (a group ID is set) are consumed by the same bean instance. The behaviour I require in this is that Messages with the same group ID are processed sequentially (though message ordering is irrelevant), and tying them to the same MDB-instance should provide that. The messages do not carry any kind of sequence number (as it is irrelevant) and we do not know what the first or last

How to restrict pool size of MDB on Glassfish v3

由 微笑、不失礼 提交于 2019-12-05 13:49:54
my Message Driven Bean executes highly intensive operations so I would like to restrict it's pool size or my server would have been overloaded. I have tried this ( code ) but it doesn't work, it's pool is still 32 ( empirically tested, time to time I restart a server so there are no pooled instances ). @MessageDriven( mappedName = "jms/TestTopic", activationConfig = { @ActivationConfigProperty( propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge" ), @ActivationConfigProperty( propertyName = "destinationType", propertyValue = "javax.jms.Topic" ), @ActivationConfigProperty(
订阅 message-driven-bean