Re: ActiveMQ producer/consumer hangs when on of the consumer didn't respond

Am i not supposed to use PooledConnectionFactory for consuming messages.See the below Java Doc http://activemq.apache.org/maven/act...onFactory.html A JMS provider which pools Connection, Session and MessageProducer instances so it can be used with tools like Spring's JmsTemplate. NOTE this im

Strange -Dactivemq.base behavior

Hi, I'm trying to change the location of -Dactivemq.base. In the activemq script, you can do this by setting the environment variable ACTIVEMQ_BASE to something besides the default, which is $ACTIVEMQ_HOME. I set ACTIVEMQ_BASE=/tmp, and ran activemq with a simplified version of the conf/active

Problem trying to route with Interceptors

I have a main queue named QUEUE.COLOR. 1 Producer send a lot of messages to QUEUE.COLOR Messages only have "red ..." or "blue..." in their body In trying to route the messages with "red ..." to QUEUE.RED and the messages with "blue..." to QUEUE.BLUE ONLY USING AN INTERCEPTOR My problem: message

Re: Stomp: unsubscribe durable consumer - only works if client id == subscription name

Hi Michael, this works as intended. Take a look at activemq.subscriptionName property description at http://activemq.apache.org/stomp.html Cheers -- Dejan Bosanac Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net

Re: Killing activemq with connected JMS listener

it's not a question of exception throwing... I mean the only way to treat properly Connection objects exception is in the ExceptionListener and you can throw your exception only in ExceptionListener. It's just a question of trace in fact. Without ExceptionListener you have the impression that Act

Re: Killing activemq with connected JMS listener

Where are you suggesting an exception is thrown with no ExceptionListener ? On 19 Mar 2009, at 10:02, mffrench wrote: With ExceptionListener it's working well ! :) Anyway I think you should get this exception without any ExceptionListener ! javax.jms.JMSException: java.io.EOFException

Re: Killing activemq with connected JMS listener

With ExceptionListener it's working well ! :) Anyway I think you should get this exception without any ExceptionListener ! javax.jms.JMSException: java.io.EOFException at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49) at org.apache.activemq.Active

Clustering amq

I've clustered three amq server with A configurated a duplex bridge to B and c B and c with no networkConnector configuration then two clients Consumer connected to A and B seperately , one client Producer connected to A i noticed in this case some messages were missed. why? any idea? i

Re: Killing activemq with connected JMS listener

Well I'm not agree with you. As specified by the JMS specification the Connection object supports an optional ExceptionListener. ExceptionListener are the best way to treat the disconnection exception or other exception BUT without ExceptionListener you should get a disconnection exception in the

Re: Killing activemq with connected JMS listener

ah ok, I think you need an exception listener: see: http://java.sun.com/products/jms/javadoc-102a/javax/jms/Connection.html#setExceptionListener(javax.jms.ExceptionListener) On logging" see the activemq FAQ entry on logging 2009/3

Re: Killing activemq with connected JMS listener

Hello, I didn't register any ExceptionListener in my JMS consumer nor in my JMS producer. So there is no treatment of any kind which can hide the waited exception and do an automatic reconnection for example - I'll be happy to do this but without any exception raised from activemq I do not know

Re: ActiveMQ and Websphere App Server integration

I got this working now =) The correct namespace for ActiveMQWASInitialContextFactory is actually org.apache.activemq.jndi.ActiveMQWASInitialContextFactory. Note the "WAS" there is in the middle. I experienced JNDI lookup failures too, and the key thing to overcome those was to define the redun

Message dispatch stops after changing subscription selectors

Using ActiveMQ 5.2.0, I have a junit test where I make a durable subscription to a topic with a selector String selector = "TD_A_ALARM_TYPE = '0'"; consumer = session.createDurableSubscriber((Topic)destination, consumerName, selector, false); I get messages where that property is specified.