Hi there,
we're facing the issue that the MessageServlet does not serve the messages
as UTF-8.
Though we defined the defaultContentType to text/xml;charset=UTF-8 in the
web.xml - jetty overrides the charset.
Is there another solution than writing a custom servlet?
Regards
Ralph
--
View this
Hi All,
I am new to ActiveMQ, I need to configure SSL for activemq communications.
Please let me know what are advantages / disadvantages with SSL.
1. If I am go ahead without ssl what are the advantages/disadvantages?
2. If I am proceed with SSL what are the advantages/disadvantages?
thanks in
Hi ,I am sending multiple text messages in a loop which sends around 5000
test messages one by one.After sometime the active MQ drops few messages by
throwing the below error.It does not process all the messages and few
messages were not processed due to the following error.Please someone can
help
I found the problem came back. It is not caused by JMX configuration.
And probably, after the restart will be good for a while, i found.
I have no solution.
--
View this message in context:
Are you able to make a minimal test case that illustrates the problem
consistently and quickly? (Ideally this would be a single consumer on a
single destination; the simpler the better.) If you can make something
that someone else can easily run to demonstrate the problem, one of us
would be
The only ActiveMQ-specific aspect of this question is that to use SSL you
have to configure it appropriately:
http://activemq.apache.org/how-do-i-use-ssl.html. So there's a cost of a
small amount of effort.
Otherwise you can research whether you should use SSL in general via
Google:
Which version of the broker and client are you using? If you are using an
older version of the broker or the client you could try updating to newer
versions to see if the problem still exists.
If you are using the newest versions, are you able to reproduce this issue
in a unit test or test case?
I agree on the versions - first match the client and broker version and see
if that helps. Running with the latest too is a good idea to make sure this
isn't a bug that was already fixed.
With that said, one workaround that may help here - disable the cache
feature in the protocol (it helps by
Hi,
I am using ActiveMQ-5.11. I am running embedded Jetty server and using
MessageServlet as mentioned http://activemq.apache.org/rest.html to send
and consume.
Once I create a consumer or producer to messages, I am not able to
disconnect it later. I can see in Jconsole that these
Have you found a solution for this case ?
Thanks !!
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Disabling-SSLv3-in-embedded-web-console-jetty-tp4687156p4698861.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
The failover transport will retry forever by default, so a failure to
connect will never result in control being returned to your code. If you
want that, you can set the maxReconnectAttempts URI option to return
control after a certain number of successive failures. See
My producer resides in a web application. The failover switch works as
intended, however, when both of my ActiveMQ brokers are down, it doesn't
seem to timeout and just throw an exception. What I want to achieve is a
non-blocking producer.
My broker URL is basically:
12 matches
Mail list logo