getting these in server out
WARN | Committed before 503 null
WARN | Committed before 503 null
WARN | Committed before 503 null
WARN | Committed before 503 null
WARN | Committed before 503 null
WARN | Committed before 503 null
as I hit http://:8161/admin/
??
never had such problem in 5.
In short, yes. I needed to uncomment some lines in my
/etc/default/activemq to enable JMX. I will post the changes hopefully
tomorrow.
On 29 August 2010 08:28, Romain CHANU wrote:
> Hi James,
>
> I have the issue as well. Have you found anything solution yet?
>
> Cheers,
>
> Romain
Thanks Dejan. Good to hear many people are using later versions in
production.
I'd like to hear of any stability issues with the features of interest to
us (see below), especially master/slave + Durable Topics.
An indication of a release maturity might be useful - for example, 5.4
beta1, beta2 .
glad that helped, thanks for posting back.
On 30 August 2010 11:28, Theo Bot wrote:
> Gary,
>
> Your repsonse led me to the solution. It was indeed the missing
> destination. The script had an argument called 'queue' instead of
> 'destination'.
>
> Theo
>
> On Mon, Aug 30, 2010 at 12:03 PM, Gary
Gary,
Your repsonse led me to the solution. It was indeed the missing
destination. The script had an argument called 'queue' instead of
'destination'.
Theo
On Mon, Aug 30, 2010 at 12:03 PM, Gary Tully wrote:
> Maybe the source will help, it is the destination attribute:
> http://fisheye6.atlass
Maybe the source will help, it is the destination attribute:
http://fisheye6.atlassian.com/browse/activemq/tags/activemq-5.4.0/activemq-core/src/main/java/org/apache/activemq/broker/CompositeDestinationBroker.java?r=985385#l84
Guess you need to see if you can reproduce and possibly produce a test
ok, there is a new announcement in the news section and the download
link now has the latest version in it, that should help clarify the
latest available release. Thanks for the feedback.
On 27 August 2010 22:13, TreyH wrote:
>
> Thanks Gary. I'm a little confused about the status of 5.4. The
Hi Ravi,
there has been a lot of improvements since 5.0 and many people uses
later versions in production. I'd certainly recommend testing the
latest release in your environment and report any potential problems
you might find.
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Inte
Hi,
stop command tries first to connect to the broker using JMX, and waits
for 30 sec to be stopped. Only after that it tries to kill it. Perhaps
you don't have JMX turned on or the script for some reason cannot
connect to it.
I opened a Jira issue to improve on this behavior
https://issues.apach
