Re: message clears from db if application or activemq restarts..

no-one knows about it...?? i think there might be some configuration missing or something else. please check it. -- View this message in context: http://activemq.2283324.n4.nabble.com/message-clears-from-db-if-application-or-activemq-restarts-tp3491807p3500297.html Sent from the ActiveMQ - User

Re: ActiveMQ restarting by itself

The machine did not restart. The broker restarted by itself without the windows service restarting. The log shown is from the broker that restarted. -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-restarting-by-itself-tp3482243p3499613.html Sent from the ActiveMQ

RE: Scaleability problems with queue subscriptors

We are using the STOMP protocol which doesn't support that. I was curious if there might be any settings server side which would help with the scalability of concurrent subscribes? > -Original Message- > From: Gary Tully [mailto:gary.tu...@gmail.com] > Sent: Wednesday, May 04, 2011 5:39

Re: ActiveMQ 5.5: Not able to get the DLQ_DELIVERY_FAILURE_CAUSE_PROPERTY value

Sorry forgot to attach the log file, resending message with a log file. Hi Gary, I have enabled the advisoryForConsumed. My Queue name is 'Test' and it has a listener . Correspondingly there is an advisory topic called 'ActiveMQ.Advisory.MessageConsumed.Queue.Test' and this has its own listen

Re: ActiveMQ 5.5: Not able to get the DLQ_DELIVERY_FAILURE_CAUSE_PROPERTY value

Hi Gary, I have enabled the advisoryForConsumed. My Queue name is 'Test' and it has a listener . Correspondingly there is an advisory topic called 'ActiveMQ.Advisory.MessageConsumed.Queue.Test' and this has its own listener. My use case to illustrate my problem is below:- 1) Send a message to Te

Re: Question about "forced expiration" of connections

there is no timer thread in the pool, the checks for expiry; time since first use, and idle timeout - time sense last used, are done when a connection is returned to the pool via a close or got from the pool. So it works well in the getConnection() doWork() closeConnection() pattern but with a lon

Re: ActiveMQ 5.5: Not able to get the DLQ_DELIVERY_FAILURE_CAUSE_PROPERTY value

note that advisoryForConsumed is disabled by default, it needs to be enabled via a destination policy entry. http://activemq.apache.org/advisory-message.html On 5 May 2011 15:22, karen wrote: > Hi Gary, > > I might have another problem that might surface due to exceptions not being > sent back to

Re: ActiveMQ 5.5: Not able to get the DLQ_DELIVERY_FAILURE_CAUSE_PROPERTY value

Hi Gary, I might have another problem that might surface due to exceptions not being sent back to ActiveMQ. I use an advisory topic to know if the message was sucessfully consumed or did an error inccur. Thus my queue 'Test' has an advisory called 'ActiveMQ.Advisory.MessageConsumed.Queue.Test'.

Question about "forced expiration" of connections

Hi. Because of weird network problems (tcp connections becoming "stale" without being closed explicitely after a few days), I need to make sure that the connections used by my consumers are recreated frequently. This is what I do at the startup of my application: ... pooledConnectionFactory.setE

Re: ActiveMQ 5.5: Not able to get the DLQ_DELIVERY_FAILURE_CAUSE_PROPERTY value

Hi Gary Thanks alot for your help and time. Really appreciate it. Will use the exception listerner apprach. -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-5-Not-able-to-get-the-DLQ-DELIVERY-FAILURE-CAUSE-PROPERTY-value-tp3492931p3498091.html Sent from the Act

Re: ActiveMQ 5.5: Not able to get the DLQ_DELIVERY_FAILURE_CAUSE_PROPERTY value

yep, the exception is trapped. But an error handler would be called. You need to register an error handler with the container that will rethrow the runtime exception, I think then it will get back to amq. On 5 May 2011 11:25, karen wrote: > Hi Gary > > Thanks alot. I now understand that the sprin

Re: ActiveMQ 5.5: Not able to get the DLQ_DELIVERY_FAILURE_CAUSE_PROPERTY value

Hi Gary Thanks alot. I now understand that the spring framework is catching the exception. I used the SimpleMessageListenerContainer as you advised. But again did not get the DLQ exception string. I think the same thing is happening in this container as well. I have attached the activemq and wrap

Re: how to stop AMQ gracefully?

calling the stop method on the brokerService is what is needed. That has a @PreDestroy annotation so spring should do the right thing when the application context is destroyed. You may need to include in your spring xml to have the annotation respected. 2011/5/1 Michal Singer : > Hi, I am using w