Re: Producer broker never resumes publishing after ResourceAllocationException

Yes. Even though Broker B has been cleaned up and brought back up Broker A just keeps writing to local storage instead of forwarding the messages to broker B. -- View this message in context: http://activemq.2283324.n4.nabble.com/Producer-broker-never-resumes-publishing-after-ResourceAllocation

Re: Producer broker never resumes publishing after ResourceAllocationException

I wonder if there's a bug with the JMS bridge. I would just use Camel instead of the JMS bridge. So basically what's happening is Broker A will get producer flow control from trying to send to B, then B is taken down and cleaned up and brought back, and Broker A isn't automatically starting to sen

Re: CPP-Client API to get version string?

On 02/12/2013 04:38 PM, JRR wrote: Thanks for the tip. However it appears this doesn't show the full version, or perhaps I am missing something. I've used the getProviderMajorVersion() and getProviderMinorVersion() and I've succesfully viewed: 3.4 for 3.4.5 and 3.5 for 3.5.0 The values r

Re: CPP-Client API to get version string?

Thanks for the tip. However it appears this doesn't show the full version, or perhaps I am missing something. I've used the getProviderMajorVersion() and getProviderMinorVersion() and I've succesfully viewed: 3.4 for 3.4.5 and 3.5 for 3.5.0 The values returned for getCMSVersion(), getCMSMaj

Re: Producer broker never resumes publishing after ResourceAllocationException

Thanks for the response ceposta. Yes, I get the reason for the flow control kicking in. My primary question though is, is there a way to make the broker A (producer) from resuming the publishing automatically once the consumer (broker B) has eased up instead of having to restart the broker A manual

Re: Producer broker never resumes publishing after ResourceAllocationException

Well, looks like Broker B's store is only 512MB and broker A's store is up to 15GB. If broker A is forwarding messages and broker B is storing them (consumers cannot keep up), then your store limits will be reached on broker B. This would explain the producer flow control stack trace you posted fro

Producer broker never resumes publishing after ResourceAllocationException

Hi All. I'm not sure if a similar question has already been posted. I tried searching the forums and couldn't find any. We are using activemq 5.5.1 and have a producer on machine A publishing persistent messages to a local queue A (within broker A) that is bridged to a queue B (within broker B) on

Re: CPP-Client API to get version string?

On 02/12/2013 12:38 PM, JRR wrote: Hello, Is there an API in the CPP-client that returns the current version of the AMQ-CPP-Client library that's being used? I scanned the API documents, but nothing popped out. We have products that use different versions of the CPP client, since they were ship

CPP-Client API to get version string?

Hello, Is there an API in the CPP-client that returns the current version of the AMQ-CPP-Client library that's being used? I scanned the API documents, but nothing popped out. We have products that use different versions of the CPP client, since they were shipped at different times. And we'd like

RE: Stuck Messages

Were you able to see anything in the activemq.xml that I had sent back to you? From: Gaurav Sharma [via ActiveMQ] [mailto:ml-node+s2283324n4662994...@n4.nabble.com] Sent: Thursday, February 07, 2013 11:13 AM To: Masanz, Don Subject: Re: Stuck Messages Aah, I see. So, a good place to start is: ht

Re: Reorder of messages

Hi James, Thanks for the comments. Also, I put a little more detail about the critical part of what I am after in a previous response on a different relpy on this thread. Mulling over it for awhile, does the following sound feasible? Or am I getting convoluted? "Normal" flow of messages from o

Re: Successfully delivered message ends up on DLQ

if you are using transacted consumers it can happen if you get a duplicate deliver after a failover. but in that case there should be a string property called dlqDeliveryFailureCause on the message in the dlq On 12 February 2013 10:20, jliezers wrote: > Hi, > > I'm running ActiveMQ version 5.6.

Re:Re: Failover event

The command BrokerInfo is telling you what broker your client has connected, When the broker is shut down,the transportInterupted method of TransportListener is called and it indicates that your client has disconnected with the broker which the previous BrokerInfo represents. At 2013-02-12 1

Re: osgi manifest headers are missed in 5.8.0 release

Just to add, that for this release we aimed at ease of use in the osgi land. There's room to make things more modular (according to the new modules of the project itself) in the future and any help with that is more than welcomed :) Regards -- Dejan Bosanac -- Red Hat, Inc. Fus

Re: osgi manifest headers are missed in 5.8.0 release

Hi Dmytro, with previous version you'd use activemq-core, which also contained all broker classes, so there's no much of a difference now. You only need to use activemq-osgi bundle instead of activemq-core one. There's an activemq-client feature among karat features that's supposed to be used if y

Re: osgi manifest headers are missed in 5.8.0 release

Hi Dejan, thank you for details. As I see, activemq-osgi contains all functionality (client, broker, all transports, dependencies etc.). I'd like to use only small functionality sub-scope (e.g. client + http transport). With previous versions, I can use bundles/modules I need. With the latest ver

Re:Byte Arrays In IMapMessage

Hi,for properties of a message, the type of their value can only be boolean, byte, short, int, long, float, double, or String.You can not assign its value with byte array type. You can call the setBytes method of the message like this: message.setBytes("TEST-ByteArray", bytes); The other simple

Re: osgi manifest headers are missed in 5.8.0 release

Hi Dmytro, we changed the modules of the activemq for 5.8.0 and how it integrates with osgi containers. You can find more details on it here http://activemq.apache.org/osgi-integration.html but in a nutshell, there's now activemq-osgi bundle that incorporates all classes and is ready to be used

Byte Arrays In IMapMessage

Trying to add a byte[] as an item in an IMapMessage... IMapMessage message = producer.getSession().CreateMapMessage(); string sval = "STRANGE BYTES FROM WORD DOC: üøôðôìèìäôìàìÜìÜìÜìÜàìàØàìÔÐÔÐÌÈÌÐ"; byte[] bytes = Encoding.UTF8.GetBytes(sval); message.Properties.SetBytes("TEST-ByteArray", bytes)

[ANNOUNCE] Apache ActiveMQ 5.8.0

The Apache ActiveMQ team is delighted to announce the release of Apache ActiveMQ 5.8.0. This release adds AMQP support and resolves 160 issues and enhancements. Full details and download link can be found in the release page: http://activemq.apache.org/acti

Successfully delivered message ends up on DLQ

Hi, I'm running ActiveMQ version 5.6.0 on linux. Very occasionaly a message ends up on a DLQ even though consumer logs give every indication that the message has been successfully delivered and processed. The consumer Spring jms listener acknowledge attribute is set to "client" I can't find an

Re: Failover event

I've been trying implementing TransportListener interface and passing a reference to ActiveMQConnectionFactory. I could see that when I launch my application the transportResumed method is called and then the onCommand method several times, with a WireFormatInfo object, a BrokerInfo object and a Co