Re: Question about REST and to subscribing Topics

2012-08-09 Thread Dejan Bosanac
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

Re: Apollo database authentication

2012-08-09 Thread ceposta
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

Apollo: Custom ACL Module

2012-08-09 Thread 梁振警
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

The dilemma of not acknowledging messages

2012-08-09 Thread fenbers
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

Re: Apollo: Custom ACL Module

2012-08-09 Thread ceposta
Yes, you can. Specify an access_rule 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

Re: Apollo: Custom ACL Module

2012-08-09 Thread Hiram Chirino
add: access_rule allow=12345 action=receive consume kind=queue id=12345/ to your xml config. On Thu, Aug 9, 2012 at 8:48 AM, 梁振警 liangzhenj...@gmail.com 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

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

2012-08-09 Thread john bush
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

Request Redelivery of Acknowledged Messages

2012-08-09 Thread fenbers
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: