Title: Signature
Hi Matt,
Thanks for the information. I will pass this response onto the
developer to look into testing (and moving to) 5.5.x in our
environment. I will also forward your FuseSource build suggestions
onto our developer.
As for the back-end datastore, we are using MySQL for the AMQ and
probably also the transactions. I can confirm this if there's any
issues involving the use of MySQL.
Thanks.
On 2/7/12 9:31 AM, Matt Pavlovich wrote:
Hi Brian-
This list is fine, as it sounds like an ActiveMQ-related issue.
There are some known issues with AMQ 5.4.2 that could lead to that
problem. Also, client-side issues such as exhausting connection
pools, or leaking connections could cause "stuck message"
behavior.
I suggest doing some testing against new 5.5.x ActiveMQ releases.
Specifically, I suggest using the FuseSource builds, since they
are more frequent than the Apache releases at this time. They
are free to use.
Are you using KahaDB as a back-end data store for AMQ?
Transactions?
Hope this helps,
Matt Pavlovich
On 2/6/12 9:40 PM, Brian Wright wrote:
Hello,
I'm actually asking this question on behalf of one of our
developers. As I understand ActiveMQ (and Servicemix), when a
message is placed into a queue, an event is fired off telling
the consumer a new message is now present. It is then the
consumer's job to pick up the new message and process it.
We had a recent issue where it appeared that new message arrival
events were either not firing or firing off very slowly to the
consumer as messages were placed into the queue. So, the
message queue was backing up and messages were not being
processed. Note that we have about 8 different queues on this
Servicemix server, but only one of the queues exhibited this
behavior. As a result, the processing ground to a halt on this
specific queue and queue messages backed up. Once we restarted
everything involving servicemix, activemx and the consumer of
the queue, everything went back to normal processing speed.
I'm trying to determine if there are any known issues that could
cause this behavior within ActiveMQ. We are running Apache
Servicemix version 4.3.1-fuse-01-09 using ActiveMQ version 5.4.2
(looks like the ActiveMQ packages were included with the
Servicemix package).
As another question, since it appears ActiveMQ was included in
the Servicemix package, should I ask this question on the
Servicemix forum instead?
Any help would be appreciated.
Thanks.
--
|
Brian Wright
Sr. UNIX Systems
Administrator
901 Mariners Island Blvd Suite 200
San Mateo, CA 94404 USA
Email bri...@marketo.com
Phone
+1.650.539.3530
www.marketo.com
|
 |
--
Signature
|
Brian Wright
Sr. UNIX Systems Administrator
901 Mariners Island Blvd Suite 200
San Mateo, CA 94404 USA
Email bri...@marketo.com
Phone
+1.650.539.3530
www.marketo.com
|
 |
|
