AMQ-3742 created.
Instead of reproducing the whole stomp test, I've just added a test case to it
and submitted the patch - I hope that's ok
Cheers,
-- David
On 27/02/2012, at 10:10 PM, tabish...@gmail.com [via ActiveMQ] wrote:
> On Sun, 2012-02-26 at 22:45 -0800, davidw wrote:
> > Thanks f
Are there any drawbacks to turning on thread pools in terms of performance?
It would seem like it would use less memory but might have switching costs.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Failover-with-networkConnectors-tp4415677p4425654.html
Sent from the Acti
You need to allow the access to advisory topics as well, like
Regards
--
Dejan Bosanac
Senior Software Engineer | FuseSource Corp.
dej...@fusesource.com | fusesource.com
skype: dejan.bosanac | twitter: @dejanb
blog: http://www.nighttale.net
ActiveMQ in Action: http://www.manning.com/snyder/
O
I actually copied the wrong log snippet-
the errors we're actually seeing in the log are 'user is not authorized to
create topic' errors
10:51:03,831 ERROR [stderr] (MSC service thread 1-11)
javax.jms.JMSException: User admin is not authorized to create:
topic://ActiveMQ.Advisory.Connection
1
Thanks for pointing this out Laures as we are using 5.5.1. We will definitely
add this case to our failure mode testing and use your thread pool
workaround if we experience the issue.
I am curious if using the NIO transport as we do makes any difference. I
doubt it since it still uses TCP to make
please note that if you are using activemq 5.5 there is a bug in the failover
mechanism that can keep your network bridges from beeing created.
see: https://issues.apache.org/jira/browse/AMQ-3575
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Failover-with-networkConnecto
On Sun, 2012-02-26 at 22:45 -0800, davidw wrote:
> Thanks for your reply.
>
> I think I found the issue - shortly before the message that failed to be sent
> through was another message that had a null body (and was much smaller in the
> tcp dump so I missed it).
>
> It seems to be a problem
i'm encountering critical problems with activemq in our dev enviroment,
activemq brokers seem to hang and not respond to other brokers or jms
consumers/producers.
my example setup is an activemq network of embedded brokers (2 to be
precise),
one process with an embedded broker produces work,
a w
