Re: What is "Cross Language Clients and Protocols" means?

http://activemq.apache.org/rest.html Doesn't matter the producer On Mar 29, 2016 9:02 PM, "bryanevil" wrote: > Lets say I have an existing c++ want to stream messages (struct, binary > stream, string, format really doesn't metter) to java world. Does ActiveMQ > provide

What is "Cross Language Clients and Protocols" means?

Lets say I have an existing c++ want to stream messages (struct, binary stream, string, format really doesn't metter) to java world. Does ActiveMQ provide c++ message producer and java message consumer that can bridge between these two world? Does the "Cross Language Clients and Protocols" stated

Re: ActiveMQ with KahaDB as persistent store becomes very slow (almost unresponsive) after creating large no (25000+) of Topics

Thank you Christopher for your suggestion. I'll check this with 5.13.2 -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-with-KahaDB-as-persistent-store-becomes-very-slow-almost-unresponsive-after-creating-large-s-tp4709985p4710043.html Sent from the ActiveMQ -

Re: activemq-all jar tight coupling with log4j

The file log4j.properties in activemq-all was added on 2/12/15 (not sure what release of ActiveMQ that correlates to). That's the kicker. When we upgraded recently from 5.11.1 to 5.13.1 is when the problem became apparent. You can see why. It's a non-trivial exercise to coordinate multiple teams

Re: activemq-all jar tight coupling with log4j

Nothing has been changed so I don't know what you are referring to. That log4j dependency has been included in that jar for a while, since AMQ-3715. The main point of that jar file is it is an easy way to spin up a broker for testing and it is supposed to contain concrete dependencies of things

Re: NFS v4 locks "given up" w/o any logging?

To close the loop on this for anyone that digs it up later... While the issue of lock handoff is still an open one, and one that I think may require a new Locker scheme, the underlying cause of the issue I was seeing with my activemq cluster was due to a difference in understanding on how the

Re: activemq-all jar tight coupling with log4j

Per the online documentation, using activemq-all is a legitimate way to connect to a broker. For those that were happily using it up until now, whether others consider it 'overkill' or not, they are now screwed by this change. Regardless, stating that one can 'fine tune' dependencies by switching

Re: activemq-all jar tight coupling with log4j

On 03/29/2016 02:43 PM, stak wrote: So are you saying that activemq-all.jar is not a production grade jar to be used as a client jar when they want to connect to an external activemq as a client?. Is the purpose of that jar really only for a quick unit test of sorts? -- View this message in

Re: activemq-all jar tight coupling with log4j

If you just need to connect as a JMS client, you just need the activemq-client jar and its transitive dependencies. If you are using something like maven then you can add that jar to your pom file and then exclude dependencies you don't want (in this case log4j). On Tue, Mar 29, 2016 at 2:43 PM,

Re: activemq-all jar tight coupling with log4j

So are you saying that activemq-all.jar is not a production grade jar to be used as a client jar when they want to connect to an external activemq as a client?. Is the purpose of that jar really only for a quick unit test of sorts? -- View this message in context:

Re: activemq-all jar tight coupling with log4j

On 03/29/2016 12:30 PM, stak wrote: In a particular application, logback is being used for the application logging. When the application added dependency on activemq-all 5.13.1 jar in order to access ActiveMQ, it appears that activemq-all has dependendency on log4j which seem to conflicting the

activemq-all jar tight coupling with log4j

In a particular application, logback is being used for the application logging. When the application added dependency on activemq-all 5.13.1 jar in order to access ActiveMQ, it appears that activemq-all has dependendency on log4j which seem to conflicting the whole logging and made it cumbersome.

Re: ActiveMQ with KahaDB as persistent store becomes very slow (almost unresponsive) after creating large no (25000+) of Topics

Can you try version 5.13.2 and see if that helps? There was a performance bug related to durables (AMQ-6158) in KahaDB that was fixed which might help here. On Tue, Mar 29, 2016 at 12:17 AM, Shobhana wrote: > I enabled debug logs to see what was happening when AMQ could

Re: Support for setting default message expiry for MQTT messages

Thank you Tim for super-quick response :-) I will check this option. -- View this message in context: http://activemq.2283324.n4.nabble.com/Support-for-setting-default-message-expiry-for-MQTT-messages-tp4710015p4710018.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Support for setting default message expiry for MQTT messages

On 03/29/2016 09:54 AM, Shobhana wrote: Hi, We use AMQ 5.13.1 and connect to AMQ using Eclipse Paho's MQTT V3 client lib to exchange MQTT messages between message publishers and durable subscribers. Some of our durable subscribers (running on Android app) may go offline for extended periods

Support for setting default message expiry for MQTT messages

Hi, We use AMQ 5.13.1 and connect to AMQ using Eclipse Paho's MQTT V3 client lib to exchange MQTT messages between message publishers and durable subscribers. Some of our durable subscribers (running on Android app) may go offline for extended periods (say when mobile data connection is disabled