Re: Performance: queues/topics vs. selectors

Hi, thanks for your hints ... To delete the inactive Queue is a good idea. I would like to set the check period to 2 days instead of soconds .. is it OK? best regards Shine -- View this message in context:

Re: leveldb messages lost

Are you using 5.6.0? - Michael Hayes B.Sc. (NUI), M.Sc. (DCU), SCSA SCNA -- View this message in context: http://activemq.2283324.n4.nabble.com/leveldb-messages-lost-tp4653078p4653086.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: ActiveMQ one message received several times

The JMS 1.1 spec is worth a look here. http://download.oracle.com/otndocs/jcp/7195-jms-1.1-fr-spec-oth-JSpec/ Sections 4.4.12 Duplicate Delivery of Messages and 4.4.13 Duplicate Production of Messages cover the issue. Note the comment on client usage of AUTO_ACKNOWLEDGE - such clients must

Re: JMS Appender reconnect to Broker

You can achieve automatic client reconnect by using the failover transport. http://activemq.apache.org/failover-transport-reference.html Then your client will attempt to reconnect transparently and when successful, messages (in this case the messages are logs) can be sent to the broker. -

Re: leveldb messages lost

Hi, Try replacing the fusemq-leveldb jar with the following snapshot. That should take care of the 'NotYetImplemented exception'.

AMQ-1703 - Create lightweight ActiveMQ client jar

Some time ago a patch was submitted to create a lightweight set of dependencies for people who are just writing a simple client - https://issues.apache.org/jira/browse/AMQ-1703 This was also discussed at http://activemq.2283324.n4.nabble.com/ActiveMQ-client-without-Spring-td3178034.html By my

broker interceptor works in 5.5.1, but not in 5.6.0

My problem is the following: I have written an interceptor for an activemq5.5.1 message broker. The interceptor intercepts incoming messages by overriding the *public void send(ProducerBrokerExchange producerExchange, Message messageSend)* method in Broker filter. It then validates the messages

Re: Unable to connect/send messages with MQTT transport from JMS client

You would have to use an MQTT specific api to access the MQTT protocol. A java API to MQTT can be found at: http://mqtt-client.fusesource.org/ These is no JMS API to the MQTT protocol AFAIK. On Thu, May 24, 2012 at 6:29 AM, Dmytro Pishchukhin dmytro.pishchuk...@gmail.com wrote: Hello, I'm

Re: World-writable KahaDB files?

Do you think we could have done something in the ActiveMQ startup scripts to protect against even odd environments like the one you encountered? On Thu, May 3, 2012 at 12:43 AM, justintime jus...@techadvise.com wrote: My apologies, it's something on the system, not in the code. That'll teach

Re: AMQ-1703 - Create lightweight ActiveMQ client jar

What would be cool is if we can use the proguard-maven-plugin to byte code analyze the absolute minium client jar that is needed. We could also shave off lots of bytes if we drop support for older broker version from the client jar. Right now a client includes something like 9 versions of

Unexpected Pending Messages Values

I've found several posts about this issue, but only a few answers, and I was not able to resolve my problem with those answers. I'm trying to understand why the pending message count on the ActiveMQ admin page can have a positive value (approx 50,000 in our case) while it appears the queue is

Suspicious ActiveMQSession messages in my log

I am running ActiveMQ 5.6 on Java 6 on Ubuntu 11.10 inside Tomcat 6. I have a Master-Slave shared file system setup with Kaha DB and Spring 3.0.6. I just restarted my Tomcat server and I just started seeing TONS of messages similar to the following ones: 00:15:28,566 DEBUG ActiveMQSession:559 -