it should fix the occurrence of the first error as those values are
used in the clientId created by the network connectors.
On 27 September 2012 14:36, Robin Kåveland Hansen wrote:
> Thanks for the reply!
>
> 2012/9/27 Gary Tully :
>> it may be as simple as giving your brokers unique names or ad
Thanks for the reply!
2012/9/27 Gary Tully :
> it may be as simple as giving your brokers unique names or adding a
> unique name attribute to the netwok connector.
>
I have named the following now:
brokerName -> jmsbroker-${hostname}
transportConnector -> ${hostname}-transport
networkConnector ->
it may be as simple as giving your brokers unique names or adding a
unique name attribute to the netwok connector.
On 20 September 2012 15:39, Robin Kåveland Hansen wrote:
> My project has been using activemq as the central part of our
> integration platform for a while now. Recently we have made
Has nobody run into this before?
--
Kind regards,
Robin Kåveland Hansen