I query solution of this exception is set on the
internet:wireFormat.maxInactivityDuration=0。
But the problem still exists in my project, so I would like to ask Is it
right? What attributes with the attributes to use associated. Thank you.
--
View this message in context:
http://activemq.228332
Now ,I want to use java.naming.security.principal and
java.naming.security.credentials to connection Activemq, but it fails, I don't
know why .
this is my code:
properties.load(new FileInputStream(new File("./jndi.properties")));
InitialContext
But say we left our ServiceMix v5.0.0 as is, but just wanted to upgrade the
ActiveMQ component, any recommendations on the best method?
Do we just edit the features config and add the required bundles, or is there
another procedure that is recommended?
-Original Message-
From: Krzyszto
You can try to replace the Activemq feature url in etc/org.***.features.cfg
with the new version and remove the data directiry. Please add also the
activemq-camel feature to featuresBoot in the same file. I hope it helps
On May 21, 2014 6:21 PM, "Krzysztof Sobkowiak"
wrote:
> Hi Barry
>
> Service
Hi Barry
Servicemix 5.1.0 will be shipped with ActiveMQ 5.9.1. Currently we have a
problem with installing the web console.
Best regards
Krzysztof
On May 21, 2014 3:24 PM, wrote:
> We are currently running ActiveMQ v5.9.0 with ServiceMix v5.0.0. We are
> looking at upgrading ActiveMQ to v5.9.1
We are currently running ActiveMQ v5.9.0 with ServiceMix v5.0.0. We are
looking at upgrading ActiveMQ to v5.9.1. What is the preferred/standard method
for performing this upgrade?
Do we simply change the features list and associated repository entry? And
then delete the data directory to cle
Hello
I'd like to evaluate the approach with failover and dynamic discovery of
ActiveMQ brokers for "client" libraries, i.e. not the one using the
ActiveMQConnection, e.g. some libraries for MQTT protocol.
For ActiveMQConnection's I may use the "failover://" protocol and in case of
"updateCluster
that is a bug, please raise a jira issue. there is no need to report
an exception in that case. it should be caught by the code and
ignored.
On 21 May 2014 09:39, dorus wrote:
> Hello everybody,
>
> I have an active mq installed in my application, embedded. I have a
> connection for sending messa
Hello everybody,
I have an active mq installed in my application, embedded. I have a
connection for sending messages to a queue and a connection for receiveing
messages from that queue. When I shut down the application, I stop and close
each connection then I stop the broker.
Everything works fin
