dont know how to put it into jira...
--
View this message in context:
http://old.nabble.com/CMS-3.1-NoSuchElementException-with-failover-tp27125879p27143319.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi,
Anybody any idea of a starting point on this? We need some sort of failover
when connecting to an external broker which is not activemq in this case
oracleAQ
Thanks for help
Andrew
ee7arh wrote:
Hi,
Referring to the article:
This requires some code change to the bridge or the use of some sort of
fault tollerant connection factory wrapper. (The failover: transport will
only work with an ActiveMQ client)
I guess you can vote for
https://issues.apache.org/activemq/browse/AMQ-2455that captures the
requirement and may be
ok thanks a lot, have voted and will keep fingers crossed.
Gary Tully wrote:
This requires some code change to the bridge or the use of some sort of
fault tollerant connection factory wrapper. (The failover: transport will
only work with an ActiveMQ client)
I guess you can vote for
Zemus wrote:
Hi,
I have a problem where TemporaryQueues are left (with 0 consumers) after
the applications creating them have finished.
This scenario occurs for both ActiveMQ 4.1.1 and 5.3.0 on my P4 2.6 GHz, 3
GB RAM, Ubuntu 9.10, Sun JDK, default settings for ActiveMQ.
I've tried
feel free to have a go at fixing it yourself, we are always open to
contributions. Just attach your changes in diff format to the jira.
2010/1/13 ee7arh andrew.hu...@2e-systems.com
ok thanks a lot, have voted and will keep fingers crossed.
Gary Tully wrote:
This requires some code
this sounds like a reasonable theory.
An ActiveMQConnection by default registers interest in the advisory messages
for temp destination removal so it does try and track temp queues as you
suggest.
So if advisory support is enabled for the broker the window for recreation
of a temp queue should be
Hi folks,
we have a 5.3.0 embedded broker that refuses to shutdown cleanly because of
lingering threads.
We reproduced this with a very very basic configuration: with just vm jmx
connectors, no producers and no consumers and and this extremely simple
main() program:
Do you actually call stop() on the broker ? - Have you disabled the
shutdownHook from the broker ?
If you could post your code - or sample of it - might help identify
why your main isn't shutting down
On 13 Jan 2010, at 17:50, Fred Moore wrote:
Hi folks,
we have a 5.3.0 embedded broker
Hi Rob,
If you could post your code - or sample of it - might help
identify why your main isn't shutting down
I actually did... can you access this pastebin here:
http://pastebin.com/f2784245a ?
Cheers,
F.
On Wed, Jan 13, 2010 at 7:52 PM, Rob Davies rajdav...@gmail.com wrote:
Do you
Hi,
I'm looking at ActiveMQ 5.3, with particular interest in the producer flow
control. Is there any way to have per-queue limits on the amount of disk space
a durable queue is using? I've seen the memory limit on the destination policy,
which looks to only apply to non-durable messages.
In
oops - sry Fred - read your first email too quick - could you post the
ThreadExplorer class too ?
thanks,
Rob
On 13 Jan 2010, at 22:24, Fred Moore wrote:
Hi Rob,
If you could post your code - or sample of it - might help
identify why your main isn't shutting down
I actually did... can
When I integrated activemq broker with jboss and deploy the activemq
webconsole.
Changed the startup script to be:
set JAVA_OPTS=%JAVA_OPTS%
-Dwebconsole.type=properties
-Dwebconsole.jms.url=tcp://172.19.174.107:61616 -
ofound solution
turn off activemq managementcontext:
managementContext createConnector=false/
and enable remote JMX connections to the JMX connector by adding startup
arguments to jboss startup script:
-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=1090
14 matches
Mail list logo
