I was able to fix the issue...
The issue was content-type which was being set as part of the HTTP Request.
The HTTP Request had a content type as application/x-www-form-urlencoded
we changed it to text/xml and the exception doesnt comeup. Perhaps there
is a fork in logic the way data is
I will describe the situation:
Our Producer program is creating message of huge size(150) MB. We can see
the message getting enqueued. Then our consumer tries to consume that
message, but it fails to pull this message from activemq queue. But activemq
shows that message was dequeued. We have
How many messages? Just a single message? With consumer prefetch default of
1000, this could easily overwhelm the consumer
On Tuesday, April 2, 2013, Prashant wrote:
I will describe the situation:
Our Producer program is creating message of huge size(150) MB. We can see
the message getting
Hi,
Thanks for quick response.
We are not facing this issue for messages of smaller sizes say 2 MB.
We are facing the issue only when message size is considerably big(150 MB).
Also, we have not specified prefetch limit implicitly, so it must be taking
default value.
But then why we are not facing
It's possible to set the enabled SSL ciphers suites in the broker using a
connector URL like ssl://…?transport.enabledCipherSuites=….
How can I do the analogous configuration on the client side?
(I found some old discussions about this at
Excellent article! You really took time detailing priority support issues on
ActiveMQ broker's side. I wish you could get into a bit more specifics on
“Client side message priority” – googling jms.messagePrioritySupported
didn’t bring much… How does it impact final message consumption
Hi Everyone,
Is there a workaround to implement a failover for stomp over websocket?
The uri in my web browser is *ws://localhost:61614/stomp* which is working
fine. But adding *failover:(ws://localhost:61614/stomp)* will not work.
Appreciate any guidance.
Regards,
Walter
--
View this
The clientside message priority is kinda the default approach to handling
priority.. no config is needed (on the broker, or the client side) to
enable it... if a producer is sending messages with JMSPriority, then when
the consumer sees it in its prefetch, it will do its best to order them
I had this RMI system property -Djava.rmi.server.ignoreStubClasses=true set
on startup, which was not letting Jconsole work service:jmx urls.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Accessing-remote-AMQ-with-JConsole-tp2350530p4665397.html
Sent from the ActiveMQ
