Recommended way to handle message priority with a single resource

Hello, I read this FAQ: http://activemq.apache.org/how-can-i-support-priority-queues.html However, I do not like either of the solutions. First one seems to imply that I have to have consumers dedicated to each priority. Second one implies that I can only rearrange the order once as I put them

ActiveMQ's default persistance is not transactional for me

Hello, I currently have ActiveMQ with MySQL for message persistence installed on machine X. On machine Y, I have a service running that uses Jencks to allow the persistence of its own data to DB and message sending to machine X to happen in a single transaction. It all works well. I switched

Re: ActiveMQ's default persistance is not transactional for me

, it starts to behave wrongly. Koichi rajdavies wrote: could you supply a test case ? On 7 Jul 2008, at 19:47, Qwerty777 wrote: Hello, I currently have ActiveMQ with MySQL for message persistence installed on machine X. On machine Y, I have a service running that uses Jencks

Re: Web Admin page throwing an HTTP ERROR: 500

because it was working just fine for the longest time (several weeks of uninterrupted down time). Koichi Hans Bausewein wrote: Qwerty777 wrote: Hey all, When I go to http://mycompany.com:8161/admin/index.jsp (obviously made-up), the web admin used to show up and work. In fact, the test

Web Admin page throwing an HTTP ERROR: 500

Hey all, When I go to http://mycompany.com:8161/admin/index.jsp (obviously made-up), the web admin used to show up and work. In fact, the test ActiveMQ's web admin still still works. Here's the error that I see: HTTP ERROR: 500 org.apache.jsp.index_jsp RequestURI=/admin/index.jsp Caused by: