We were using Tanuki java service wrapper to run ActiveMQ previously.
After migrating to a 64-bit server running Windows Server 2008 R2, we're
not able to install ActiveMQ as a service unless we pay for the Standard or
Professional version of java service wrapper.
I read that others were using Ap
read 1-11) at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:202)
10:51:03,861 ERROR [stderr] (MSC service thread 1-11) ... 1 more
Thank you for any advice.
On Mon, Feb 27, 2012 at 10:42 AM, qt4x11 wrote:
> I modified our ActiveMQ configuration to use ActiveMQ Simple
>
We have ActiveMQ clustering between our two servers configured as a network
of brokers. Our config files look like
http://activemq.apache.org/schema/core";
brokerName="receiver" persistent="false" useJmx="false"
dataDirectory="${activemq.base}/data"
destroyApplicationContextOnStop="true">
the connection was
> shut down?
>
>
>
> Cheers,
>
> Torsten Mielke
> tors...@fusesource.com
> tmie...@blogspot.com
>
>
> On Apr 11, 2012, at 12:58 AM, qt4x11 wrote:
>
> > We have ActiveMQ clustering between our two servers configured as a
> network
&g
We are trying to instantiate a new ActiveMQConnectionFactory in our code
using the brokerURL
failover:(ssl://107.22.0.25:61616,ssl://174.129.78.76:61616
)?tcp.keepAlive=true
This does not work. We get a stack trace during application deployment
14:47:19,203 ERROR [stderr] (MSC service thread 1-
Worked like a charm! Thank you!
On Thu, Oct 20, 2011 at 5:54 PM, Timothy Bish wrote:
> On Thu, 2011-10-20 at 17:34 -0500, qt4x11 wrote:
> > We are trying to instantiate a new ActiveMQConnectionFactory in our code
> > using the brokerURL
> >
> > failover:(
