As far as I know this is implementation-specific, and yes, for AMQ
connections can time-out. See
http://activemq.apache.org/configuring-wire-formats.html
http://activemq.apache.org/configuring-wire-formats.html for information
about the openwire maxInactivityDuration setting.
-E
bill richard
I have a two-broker network of brokers, and I have clients that use
Spring+Jencks+Geronimo TM. I started up the two brokers, then sent 2K
messages to a queue (while consumers were active) and got the following
error on the AMQ console:
2007-07-31 00:40:33,368 [Thread-5 ] INFO DemandForwa
As I posted earlier, I have a two-broker network-of-brokers configuration.
Both brokers are configured for Kaha. I just tried a test where I dumped
10K small persistent messages in quick succession onto a queue. The
consumers are just reading and throwing away the messages. All clients are
usi
7;s snapshot
>
>
> cheers,
>
> Rob
>
> 'Go Get Integrated - ride the Camel! - http://activemq.apache.org/
> camel/'
> http://rajdavies.blogspot.com/
>
>
>
> On Jul 30, 2007, at 10:37 PM, eta wrote:
>
>>
>> I have a two-broker
I have a two-broker network set up using a build of 5.0 from svn from last
week, with consumers on both machines. When I dump messages into queues
they are all received by the consumers but the consoles of both brokers are
covered with messages resembling this:
2007-07-30 14:27:04,911 [.168.5.24
http://activemq.apache.org/ssl-transport-reference.html
pascals wrote:
>
> Hello,
>
> We need to exchange confidential information with ActiveMQ; Is it possible
> to secure the communication between an ActiveMQ client and the broker? For
> instance by using it over HTTPS?
>
> Thanks for any h
I've been messing with the JDBC database locker code recently, and yes, it
will work as you described. The default database locker service start()
method will not return until it has acquired the lock, indicating that it is
the master broker.
I'm not sure what the recommended way around this wou
