Re: Question: Object properties on DLQ (adding exception to message for DLQ)

achan wrote: > > 2008/9/8 Demian Mrakovich <[EMAIL PROTECTED]>: >> >> Thanks for reply! >> >> Not sure what you mean by create a new message. Rollback/retries are >> handled >> by transactions. Creating a new message from the client can't be >>

Re: Question: Object properties on DLQ (adding exception to message for DLQ)

FWIW in the JMS specifications, properties > are meant to be primitive types, not complex objects - so using an > ObjectMessage and setting the payload is typically more JMS compliant > > 2008/9/8 Demian Mrakovich <[EMAIL PROTECTED]>: >> >> On ActiveMQ 4.1.1 >>

Question: Object properties on DLQ (adding exception to message for DLQ)

On ActiveMQ 4.1.1 I'm trying to add an exception to a failed message so that I can get the exception that caused it when it is received on my DLQ listener. I cannot add a string property since the message is read-only when it is received by the client. So I tried having the _producer_ create a

Re: No clientID specified for connection disconnect request

gt;> >>> >>> rajdavies wrote: >>>> >>>> work around could be to turn async dispatch off in the vm:// >>>> transport - e.g. vm://localhost?async=false >>>> >>>> On 8 Jul 2008, at 23:42, Benoitx wrote: >>>>

Re: ActiveMQ stops accepting consumer requests

I create a new connection, send message and close connection for each and every message, yes. My consuming MDBean has a max pool size of 15. The queue size may at times be up over ten thousand (my consumers are kindy slow). I might add we are using XA transactions, don't know if it has anything t

Re: ActiveMQ stops accepting consumer requests

I am having the same problem with AMQ 4.2, so this is nothing new with AMQ 5. Occasionally ActiveMQ just stops consuming messages and a restart is required. I have no idea what causes this, but I think it maybe happens during high load. Brian Munroe-2 wrote: > > I am building a very basic web s

Re: Redelivery sticks to and blocks a consumer thread

(at least for some systems) . So, is there a configuration option I have missed somewhere or is this still a firm design decision? Hoping for a reply, Demian rajdavies wrote: > > I'd certainly try 5.1 > > cheers, > > Rob > On 6 Jun 2008, at 14:05, Demian Mrakovich

No clientID specified for connection disconnect request

Just upgraded from 4.1 to 5.1 and get this exception now right after every message is received. Messages get processed fine anyway, but the stacktrace really litters the log and maybe it is a symptom of an error of some kind. Googled this message, but to no avail... Any suggestions on how to get r

Re: Redelivery sticks to and blocks a consumer thread

Thanks, So you can confirm that threads are no longer blocked during retries in 5.1? Can I find any docs/info on the retry mechanism in 5.1 anywhere? rajdavies wrote: > > I'd certainly try 5.1 > > cheers, > > Rob > On 6 Jun 2008, at 14:05, Demian Mrakovich wrote:

Re: Redelivery sticks to and blocks a consumer thread

Hi, bumping this one... Has this (I'd have to say major) issue been addressed in newer versions of ActiveMQ? Jason Rosenberg wrote: > > All, > > I have been experimenting with using exponentialBackOff as a redelivery > policy. I have multiple parallel consumers. I'm using AMQ 4.1.1, using >

Re: onMessage does not get called

Thank you, nice hint :) The business method on the bean that sends the message had TransactionAttributeType.SUPPORTED, I just set it to TransactionAttributeType.REQUIRED and it works now. James.Strachan wrote: > > On 23/01/2008, Demian Mrakovich <[EMAIL PROTECTED]> wrote: >>

onMessage does not get called

This is driving me crazy... I am running ActiveMQ under JBoss, and I have one dispatcher EJB3 bean which sends to a queue and one message-driven bean connecting to the same queue. I call a method on my dispatcher bean which posts a message to the queue and it gets picked up by the MD bean just f