Request Redelivery of Acknowledged Messages

Is there a way for my client app to request redelivery of unexpired messages that my client has already acknowledged in a previous instance? Session.recover() will only resend un-acknowledged messages. Mark -- View this message in context: http://activemq.2283324.n4.nabble.com/Request-Redelive

after tomcat 7/java 7 upgrade: failed to process packet: java.net.SocketException: Socket closed

After upgrading my app to run on tomcat 7/java 7 from tomcat 5.5 /java 6 without any changes to any active mq client code or active mq dependencies. I occasionally get these in the logs. Just endless loop forever. 2012-08-09 13:24:19,198 ERROR MulticastDiscoveryAgent-advertise:tcp://localhost:6

Poison Message not getting to DLQ without "assistance"

Hi, We have a simple test where we send a poison message into the queue and the expected behavior of the message being moved to the DLQ is not observed. The message just sits in the original target queue. The message is processed 5 times on the consumer side. No RedeliveryPolicy is set, so the

Re: Apollo: Custom ACL Module

add: to your xml config. On Thu, Aug 9, 2012 at 8:48 AM, 梁振警 wrote: > Hi all, > > Is there any way to control wether a user can subscribe to a topic/queue? > > for example, I want user (id=12345) can only subscribe to /queue/12345, > is there any to do this? > > -- > Zhenjing Liang > > -

Re: Apollo: Custom ACL Module

Yes, you can. Specify an as mentioned here: http://activemq.apache.org/apollo/documentation/user-manual.html#Authorization Use the "id" attribute to specify your destination, and the "kind" attribute to specify the type of destination. See the "Send and create authorized via id_regex" unit tes

The dilemma of not acknowledging messages

Greetings! I want unexpired JMS messages to be redelivered if my client application is stopped and restarted. To accomplish this, I do not have the client acknowledge the receipt of messages. An unfortunate side-effect of this practice is that the db-/N/.log files in the ${activemq.data}/kahadb

Apollo: Custom ACL Module

Hi all, Is there any way to control wether a user can subscribe to a topic/queue? for example, I want user (id=12345) can only subscribe to /queue/12345, is there any to do this? -- Zhenjing Liang

Re: Apollo database authentication

Apollo relies on JAAS LoginModule to handle authentication. Out of the box, there is support for file-based authentication: http://svn.apache.org/viewvc/activemq/activemq-apollo/trunk/apollo-broker/src/main/scala/org/apache/activemq/apollo/broker/security/FileUserLoginModule.scala?view=markup T

Re: null BROKER_NAME to be expected?

The LeaseDatabaseLocker does use the BROKER_NAME column, but the default jdbc locker does not. Old threads would refer to the default locker. The LeaseDatabaseLocker will null out the broker name when it releases the lease. Have a peek at the statements that manipulate the lock table in: http://s

Re: Question about REST and to subscribing Topics

Hi Chris, REST API doesn't support durable topic subscribers. But there's a couple of ways to achieve that: - use virtual topics (http://activemq.apache.org/virtual-destinations.html) - as you're planning to use Apache HttpClient, you can consider using http protocol (http://activemq.apache.org/