Re: Failed to load: class path resource [activemq.xml]

Yup, this is correct. commons-dbcp was upgraded to commons-dbcp2 On Tue, Dec 15, 2015 at 10:52 AM, Kai B wrote: > ActiveMQ seems to come with commonc-dbcp2, so you should use > org.apache.commons.dbcp2.BasicDataSource as your datasource: > >

Re: Failed to load: class path resource [activemq.xml]

ActiveMQ seems to come with commonc-dbcp2, so you should use org.apache.commons.dbcp2.BasicDataSource as your datasource: Sparg wrote > Hi all, > > After of implement the persistence

Re: Secure broker and web console: Cannot send to queue

Did this used to work in an older version of ActiveMQ, such as 5.12.1? If so, you can open up a JIRA and I will take a look. It's possible there is a regression here because a lot of changes were made when the upgrade was done from Jetty 8 to Jetty 9.2 since there are API incompatibilities

Secure broker and web console: Cannot send to queue

I have added the simpleAuthenticationPlugin to my broker (ActiveMQ 5.13.0 on linux) and configured a few users and groups. This works fine so far and users can only access those queues they are authorized for. I have also configured the 'system' user that has full rights on all queues:

Failed to load: class path resource [activemq.xml]

Hi all, After of implement the persistence with "MySQL" (http://activemq.apache.org/jdbc-support.html) I'm find the next problem: *** File config: --> activemq.xml

Re: Selective consuming of priority messages with message groups

You get all the things you described by continuing to use policy.setPrioritizedMessages(true) and not having selectors on priority. Normal-priority messages are still processed before low-priority messages when both are waiting, and messages in a group are still processed one at a time. But you

Re: big memory jump after restart

On 12/15/2015 08:30 PM, cuneyt wrote: > After deleting kahadb files and restarting activemq 5.8, memory consumption > hits 72%, 61% of which is used by JmxMBeanServer > > > QueueProducers MBean have entries similar to

Re: Selective consuming of priority messages with message groups

Hi guys, Thank you all for the suggestions; you sure taught me some new stuff ;-) I'll take those as a reference and will try to work out a new model for processing the messages in order to avoid the problem this whole discussion was started because in the first place. Cheers, Frankie --

Re: Issue with MessageConsumer and MessageSelector

Please define concretely "Acking happens as needed." I strongly suspect based on what you've written that you're wrong and acking is in fact not happening as it needs to. Do you understand how round-robin dispatch works for a queue with your two consumers? Do you understand what a consumer's

Re: Issue with MessageConsumer and MessageSelector

Tim, I am currently playing in my dev environment. I have one consumer which is event driven implementing MessageListener. This consumer is a client_ack consumer and during my development I have not yet acked anything to not remove the messages. My Listener does not at this point, just shows that

Re: Selective consuming of priority messages with message groups

Also, if your consumers can't process all of the messages before the low-priority ones age off, then you very clearly need more consumers, not priority selectors. Selecting on priority as you've done for the same number of consumers will at best result in the same number of messages consumed (and

big memory jump after restart

After deleting kahadb files and restarting activemq 5.8, memory consumption hits 72%, 61% of which is used by JmxMBeanServer QueueProducers MBean have entries similar to below:

Re: JMS to JMS Bridge

I think the solution is simply to create an explicit ConnectionFactory and set it as the localQueueConnectionFactory on the bridge: ... ... -- View this message in context:

Re: JMS to JMS Bridge

I think the solution is simply to create an explicit ConnectionFactory and set it as the localQueueConnectionFactory on the bridge: ... ... -- View this message in context: