Window > Preferences > General > Editors
Uncheck the box for Close editors automatically.
You might also want to try installing Mylyn to manage related files in a task context (eg., to have all the files relevant to a bug or work item grouped such that when you enable/disable the task, files will be automatically reopened/closed. Mylyn also lets you filter your Project or Package Explorer so you only see the files you care about at the moment.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222187#4222187
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222187
I've got a MDB that is a JMS Queue listener using ActiveMQ as the broker.
According to the ActiveMQ docs, you set destination options using URL query syntax: http://activemq.apache.org/destination-options.html
I'm trying to configure my MDB to be an exclusive consumer for the queue like so:
| @MessageDriven(activationConfig = {
| @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),
| @ActivationConfigProperty(propertyName="destination", propertyValue="FOS?consumer.exclusive=true"),
| @ActivationConfigProperty(propertyName="acknowledgeMode", propertyValue="Auto-acknowledge"),
| @ActivationConfigProperty(propertyName="subscriptionDurability", propertyValue="NonDurable")
| })
| @ResourceAdapter("activemq-rar.rar")
|
The destination options do not seem to be making it through, as I've got 10 messages getting processed at once. Anybody see anything I'm doing wrong? Is there something else I need to do to turn off pooling in JBoss?
no clustering
JBoss 5.0.0.GA
ActiveMQ 5.2.0.GA
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222177#4222177
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222177
ActiveMQ's solution was above and beyond the TTL. This is a serious issue that needs to be fixed by the JBOSS folks asap. No respectable messaging middle-ware should ever be held hostage to a rogue client.
Unfortunately, we had to abandon our migration to JBM from ActiveMQ because of this issue (and a couple of other anomalies that have to do with reconnects). While we love the clustering capabilities of the system, the reliability leaves much to be desired under stressful conditions. For now, our MDB no longer use jbossmq and now use JBM, our client interaction with our servers will stay with ActiveMQ until these issues are resolved.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222172#4222172
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222172