Re: Re:Clarifcation on KahaDB support for message priority is needed

Ok. Thanks. -- View this message in context: http://activemq.2283324.n4.nabble.com/Clarifcation-on-KahaDB-support-for-message-priority-is-needed-tp4665014p4665057.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Re:Clarifcation on KahaDB support for message priority is needed

You cannot assume 100% correct 0-9 priority order all the time. The broker will strive to deliver fully in order priority as best it can (in the index, in the store cursors/subscription cursors, and on the client), however that behavior can change slightly based on your config and messaging proper

Re: Re:Clarifcation on KahaDB support for message priority is needed

It's been a bit confusing... According to http://activemq.apache.org/message-cursors.html : The store based cursor also handles cursors for non-persistent messages, which are not stored in the message store. Non-persistent messages are passed dire

NMS.WCF not reaching my WCF service. Help needed.

Hi all, I'm trying to have the NMS.WCF library working with a simple example. First I tried using the MSMQ to get the feeling of queueing in WCF and got it working. I had a queue and when dropping a message, I got my WCF service called upon. This is exactly what I want to achieve with ActiveMQ. Th

Failover issues

Hi, We have 2 network-of-brokers with a failover-configuration, but we're having performance-problems and loosing messages. Clients connect to HostA1 and HostA2. All brokers run 5.8 stable, only persistent messages using KahaDB: HostA1: uri="static:(ssl://HostA2:61616)" duplex=

Re: Re:Re: Re:Re: Re:Re: ActiveMQ 5.8.0 Issue with HTTP Connector

Thats strange! We use the HTTP Connector of ActiveMQ i.e the producer sends a http request (RESTful Call) and gets the message converted into JMS Mesage and is dropped into the queue. Hence the client (producer) doesnt need to have activemq library with him. The messages sent are persistent in na

Re:Re: Re:Re: Re:Re: ActiveMQ 5.8.0 Issue with HTTP Connector

I have just succeed sending a text message whose payload and a string property are both more than 64K. Can you ensure your client and broker are using the same version? At 2013-03-22 15:38:04,yogu13 wrote: >Its the payload which is more than 64K .. the only workaround which i am >aware of is us

Re: Re:Re: Re:Re: ActiveMQ 5.8.0 Issue with HTTP Connector

Its the payload which is more than 64K .. the only workaround which i am aware of is using BytesMessage instead of sending the information as TextMessage.. Is there a way i can send this info as TextMessage ? Thanks for your time.. Regards, -Yogesh -- View this message in context: http://acti

Re:Re: Re:Re: ActiveMQ 5.8.0 Issue with HTTP Connector

Seems one string property of your message is larger than 64KB. It's unusual that one message has a property whose size is larger than 64KB. I guess If it is the payload of the text message rather than a property it will work as there are some workarounds. At 2013-03-22 14:49:46,yogu13 wrote: