question about c++ client(DeliveryMode::PERSISTENT )

I sent the topic message using persistent: destination = session->createTopic( "TEST.FOO" ); producer = session->createProducer( destination ); producer->setDeliveryMode( DeliveryMode::PERSISTENT ); .. producer->send( message ); and recived the message with the codes: destination = ses

Log4j with JMSAppender to ActiveMQ in Tomcat 5.5

Hi, Env:Tomcat 5.5; ActiveMQ 4.1.1; Log4J 1.2 I am trying to post error messages to a Log4J topic in ActiveMQ via the JMSAppender. I am running the standard downloaded ActiveMQ 4.1.1 with no modifications. When I start up a standalone test case in my IDE it works fine. When I deploy to Tom

Re: messages are received after expiry time

this is fixed - http://issues.apache.org/activemq/browse/AMQ-1056 I guess it was fixed after the 4.1.1 release was cut :( On Jul 18, 2007, at 4:39 PM, ttmdev wrote: I have tried this on 4.1.1 and I'm getting the same results as Suchitha. I dumped the timestamp and expiration header fields

Re: messages are received after expiry time

I have tried this on 4.1.1 and I'm getting the same results as Suchitha. I dumped the timestamp and expiration header fields on receipt and they appear to be set properly. The expiration is equal to timestamp+timetolive_value The JMS specification states the following: "Clients should not receiv

Re: Filtering via Selectors client side or broker side?

The client registers the selector on the broker and the work is done on the broker side. On 7/18/07 9:26 AM, "Raffaele" <[EMAIL PROTECTED]> wrote: > > Hi all, > > my question is, > in a scenario with a client which wants to receive only a subset of all > messages which run on the net, it spec

Filtering via Selectors client side or broker side?

Hi all, my question is, in a scenario with a client which wants to receive only a subset of all messages which run on the net, it specifies a MessageConsumer with a Selector, ok but: What's happen? Broker sends all the messages and the client perform a filtering on its side or the broker really

Re: Msg with timeout sent to a non durable consumer

Thanks for the answer but my question is a bit different, that is in my scenario a normal consumer should be receive only those messages yet live because their time is not expired and not ALL the unreceived messages like retroactive consumer do. So, theere isn't such a capability in ActiveMQ :-(

Re: ActiveMQ and Durable Topic subscriptions after subscriber is uncleanly terminated

Hopefully your problem can be helped with some extra configuration - can you tell us what you are using at the moment ? On Jul 18, 2007, at 10:14 AM, Simon Vicary wrote: Hi all, I have been having some issues which are currently show-stoppers with the use of Durable subscriptions with Ac

Re: Msg with timeout sent to a non durable consumer

This is possible - ActiveMQ can cache messages for retroactive consumers - see http://activemq.apache.org/retroactive-consumer.html cheers, Rob Davies 'Go further faster with Apache Camel!' http://rajdavies.blogspot.com/ On Jul 18, 2007, at 9:28 AM, Raffaele wrote: Hi all, My scenario is

ActiveMQ and Durable Topic subscriptions after subscriber is uncleanly terminated

Hi all, I have been having some issues which are currently show-stoppers with the use of Durable subscriptions with Active MQ Topics for our large scale integration project. I've been writing the subscriber in C#, but the issue also remains for the Java implementation. The standard approach for

Msg with timeout sent to a non durable consumer

Hi all, My scenario is the following: - One publisher publishes some messages on a topic and assign to them a timeout. - The consumer, NO DURABLE, is off when the above messages are sent. I would like that when the consumer becomes on, even though it wasn't a durable subscriber, it is able to r

javax.jms.IllegalStateException: The Consumer is closed

Hi, I Have a client which is subscribed to Durable Topic with Message Selector, Everything works fine. But if i change my system date where my client is running it throws an error saying Jul/18 07:00:03 - WARN - [] - Async exception with no exception listener: org.apache.activemq.transport.Ina