Stablest version of ActiveMQ post 4.1.2

I have been using ActiveMQ 4.1.2 for a couple of years and have had a number of problems with it. I echo the views of a recent post on this forum that I prefer reliability of the tool than performance; I do not even mind losing messages, but I want to avoid at any cost out of memory errors,

OCF Script for ActiveMQ 4.1.1

I need to manage ActiveMQ 4.1.1 daemon as an OCF resource in a Linux HA cluster. Has someone already written/tested an OCF resource agent for ActiveMQ (4.1.1)? In particular: an OCF resource agent needs to implement a monitor status function for the resource that would identify conclusively if

ActiveMQ 4.1.1 client hangs on issuing a burst of messages

Env: ActiveMQ 4.1.1, Spring 2.5.4, JDK1.6 I have a number of clients (about 9) connecting to an external broker using TCP transport. When one of the clients sends a volley of messages, the activemq connection seems to deadlock - I say *seems* to because I see no deadlocks in the full thread

Re: Newbie Question

or do you mean you wanna send a message to all of your applications which then invoke methods on mbeans? Kinda JMS - JMX - your app? There are some JMX-over-JMS implementations around Could you please point me to a JMX over JMS implementation? Regards /U

active-ra.jar?

I do not find activemq-ra.jar in the 4.1.1 distribution. This is needed for using Jencks. Can someone send me a pointer to this artifact? Regards /Ur

Re: AMQ4.1.1: Connection problems with simple peer to peer configuration

I am running into the exact same issue that is described in http://issues.apache.org/activemq/browse/AMQ-734 But per the report, the fix is in 4.1.1 (which is what I am running). Could someone tell me if perhaps 4.1.1 is similarly affected despite the fix? Has anyone seen this problem

AMQ4.1.1: Connection problems with simple peer to peer configuration

Env: JDK1.6, Activemq 4.1.1 I have a simple peer to peer setup as follows, client1 --- extBrokerA = network connector extBrokerB --- client2 Messages on topics are exchanged between client1 and client 2 fine till extBrokerA is restarted. When this happens, the activeMQ logs

Re: AMQ4.1.1: External broker drops transport connector for unknown reason

I had a couple of significant problems with 5.0.0 due to which I chose to downgrade to 4.1.1. My main problem now is that sporadically, the messages on topics are not transported over the networkConnector to the rmeote broker, even though there are subscribers to the topic on the remote

AMQ4.1.1: External broker drops transport connector for unknown reason

I have two peers A.xxx.com and B.xxx.com connected using external brokers running on each. A and B each have a number of applications that have transport connections to the respective brokers. [clients] --- tcpConnector --- [ext Broker A] === NetworkConnector === extBroker B] --- tcpConn

Re: AMQ4.1.1: External broker drops transport connector for unknown reason

It appears that U am running into the following problem: https://issues.apache.org/activemq/browse/AMQ-1045 Is there any way to increase the pool size while instantiating AMQ connection factory using Spring? Regards /U -- Original message -- From: [EMAIL

AMQ4.1.1: Use of asyncDispatch

I am using ActiveMQ 4.1.1 with a very simple peer to peer connection. I find that after a few exchanges, the messages from A to B stall - the clients of A seem to hang while sending a message (FWIW, only TextMessages are used): Peer A: transportConnectors transportConnector

Re: AMQ4.1.1: Use of asyncDispatch

I would like to use asyncDispatch to solve this problem. When I try to create a ConnectionFactory using the URL (in Spring configuration, if that matters at all): brokerURL:=tcp://localhost:61616?asyncDispatch=true I get invalid connection parameter exception. The brokerURL

AMQ4.1.1: Tracing messages on the transport connector

I am trying to trace the messages from the transport connector (client to broker), over the nework layer (broker to broker) and finally broker to client (far end transport connector). I create the connection factory with trace=true for each client. This yields no traces. Where should I expect to

Basic configuration of peering two machines

Env: Jre: 1.6, Activemq 4.1.1: I am connecting two machines A and B using external brokers as follows: Machine A: External broker at 61616 Tcp Network connector to B Configuration: transportConnectors transportConnector name=openwire uri=tcp://localhost:61616

AMQ5.0.0: Transport failed, attempting to automatically reconnect due to: java.io.EOFException

I am connecting two external brokers as follows: transportConnector name=openwire uri=tcp://localhost:61616 / networkConnectors networkConnector name=other-broker uri=static://(tcp://10.1.1.135:61616) / /networkConnectors

Re: Problems with simpleAuthenticationPlugin

Is there a syntactic element in the configuration element to indicate that a networkConnector is authenticated using the simpleAuthenticationPlugin? Wording of your email suggests that there is. Could you pl give me an example of aconfiguration of two brokers that authenticate each other using

Problem with SimpleAuthenticationPlugin

I am using ActiveMQ5.0.0 and am using TCP transport with JRE1.6. I am using a rudimentary form of authentication using SimpleAuthenticationPlugin as follows: broker xmlns=http://activemq.org/config/1.0; brokerName=localhost dataDirectory=${activemq.base}/data plugins

Synchronous Are you there? using JMS

I have two entities on either side of a queue. Entity A needs to do a synchronous are you there? on the queue and receive a response synchronously from Entity B. I thought I'd do this: - Define a Queue Are you there and dispatchAsync = false - create a session with CLIENT_ACK set - send

Re: Synchronous Are you there? using JMS

Hi, I just need to be able to ping a functional component from another functional component in a distributed application synchronously. How can this be accomplished using JMS? It appears its not straightforward? Thanks, /U -- Original message -- From: Mario

Re: Sharing embedded broker across webapp contexts

Mario, Thanks for the explanation. If I incorporate the JNDI configuration of amq, would Tomcat automatically start the broker? I need to create an embedded broker with network connectors. If I specify xbean configuration in JNDI, would Tomcat automatically create the broker and issue

Re: Sharing embedded broker across webapp contexts

Mario, How do I specify the network connector in the JNDI configuration? Is there a way to point Tomcat to the xbean configuration for the broker instead of replicating the configuration element by element? I use the xbean config file to specify the JMX configuration, ceiling on the memory

Re: Sharing embedded broker across webapp contexts

Thank you very much! /U -- Original message -- From: Mario Siegenthaler [EMAIL PROTECTED] I just played around with it a little: The easiest syntax is: Resource name=jms/ConnectionFactory auth=Container

Sharing embedded broker across webapp contexts

I am using activemq 4.1.1 on JDK6 with Tomcat 5.5.x. I have a couple of webapp contexts in a servlet container that use activemq broker. I have been using an external broker but would like to embed the broker in the servlet container. I have the following questions. 1) Assume I have webapps A

Message not sent to all Topic subscribers

I am connecting two (Tomcat) JDK 1.6 VMs using 4.1.1 external broker as follows: VM1 (broker 1) - VM2 (broker 2) (main: broker 1) (main: broker 1) (failover: broker 2)

Re: Message not sent to all Topic subscribers

// On VM1: bean id=jmsFactory class=org.apache.activemq.ActiveMQConnectionFactory property name=brokerURL valuefailover:(tcp://localhost:61616,tcp://VM2:61616)?initialReconnectDelay=100/value /property /bean bean

Re: Message not sent to all Topic subscribers

Yes, the brokers are networked together - messages from VM1 come into VM2. The only problem is that not all subscribers ('Postmaster's below) get all the messages. And all the messages are received by all the subscribers on VM1. Could I use Hermes or the logger interceptor to debug this or is

Using loggingInterceptor

Hi - I would like to use the loggingInterceptor to trace the problem of why messages are getting delivered. The example on the activemq site describes how to use the plugin with xbeans configuration. I use Spring (2.0) configuration of active brokers - is there a simple example of how to

Network of brokers - messages not forwarded

Hello... I am using ActiveMQ 4.1.1 with Spring 2.0 and JDK6. I have a network of two brokers deployed as follows: HostA: transportConnectorURIs = tcp://localhost:61616 networkConnectorURIs = tcp://HostB:61616 Number of JMS Clients = 1 HostB:

BrokerFactoryBean and ConnectionFactory

I don't understand a basic element of ActiveMQ: how does the connection factory reference the broker factory bean? The examples I have seen define a broker factory bean B and a connection factory F with a depends-on (Spring) dependency of F on B. Since the connection factory must be obtaining a

Unrecognized xbean element mapping

Hi - I am using Spring 2.0 with ActiveMQ 4.1.1 (JDK6, Tomcat 5.5.x). I am instantiating a broker using Xbean as follows: ?xml version=1.0 encoding=UTF-8? beans xmlns=http://activemq.org/config/1.0; broker brokerName=MyBroker persistent=false useJmx=false

Re: BrokerFactoryBean and ConnectionFactory

Thanks for the explanation. On a related note, could you pl explain if I can use a BrokerService or a BrokerFactoryBean in my Spring configuration without the xbean stuff? I am running into the Unrecognized xbean element mapping error due to the reference to http://activemq.org/config/1.0 and

RE: Problems with VM transport

Suchitha, Thanks for your help. I thought a URL of the form tcp://host... refers to an external broker, not an embedded one? Am I mistaken? I need to run the broker within the servlet container VM, not as a separate process. Thanks, /U -- Original message --

Re: Problems with VM transport

Adrian, Thanks for the note. Startup: vm://localhost During runtime (after an event): failover(vm://localhost,tcp://remote:61616) Would modifying the broker URL of the connection factory cause problems?

Re: Problems with VM transport

Hi - I am using the embedded broker in a servlet container. Each webapp in the servlet container instantiates a connection factory that refers to broker URL of vm://localhost?broker.persistent=false as follows: (Servlet Container (WebApp1

Re: Problems with VM transport

To follow up on my last mail: I can perhaps avoid the problem by using distinct brokernames for each webapp; but that would create distinct embedded brokers perhaps? I need both the webapps to share the same broker so they receive messages published by each other. Regards, /U --

Problems with VM transport

Hello... I have a couple of basic questions on ActiveMQ. I would appreciate any hits as I am stuck. I am using ActiveMQ 4.1 with JDK6. 1) When I use an embedded broker with vm transport (vm://localhost) the instantiation of my Spring SimpleMessageListenerContainer always fails with a

Peer transport mode: AMQ4.1 runs out of heap space

Environment: JDK1.6 ActiveMQ 4.1 Linux Kernel 2.6.17-1.2630 Setup: VM1 on local workstation configured with Peer transport Topics: 2 published Number of subscribers: 2 Queues: None Broker configuration: bean id=jmsFactory

Re: Using peer transport

I would quite appreciate any suggestions on using the peer transport. Is it the right transport to bridge two embedded brokers running on distinct servers? Also, is it possible for me to programmatically alter the peer broker's address? Regards /U -- Original message

Using peer transport

I am using AMQ4.1. I have two JVM processes running (on different physical servers). I would like each VM to have an embedded broker and yet connect to the peer VM's embedded broker. Finally, I would like subscribers on both the VMs to receive published messages on the topic regardless of