On Wed, Mar 25, 2009 at 1:19 AM, Erik Drolshammer wrote:
> I don't want to use JDBC if I can avoid it. I thought I _had_ to after
> reading http://activemq.apache.org/shared-file-system-master-slave.html.
>
> When I removed the JDBC-element and thus used KahaDB things seems to be
> working again.
Bruce Snyder wrote:
On Tue, Mar 24, 2009 at 1:17 AM, Erik Drolshammer wrote:
Bruce Snyder wrote:
On Mon, Mar 23, 2009 at 10:00 AM, Erik Drolshammer
wrote:
It seems this setup use DerbyDB and not Kahastore. Is this the only option?
Are there alternative setups that I might try?
Yes, the jou
On Tue, Mar 24, 2009 at 1:17 AM, Erik Drolshammer wrote:
> Bruce Snyder wrote:
>>
>> On Mon, Mar 23, 2009 at 10:00 AM, Erik Drolshammer
>> wrote:
>>>
>>> Hi!
>
> Good morning :)
>
>
>>> We try to set up two brokers according to [1] to get some redundancy in
>>> our
>>> solution. The shared filesy
Bruce Snyder wrote:
On Mon, Mar 23, 2009 at 10:00 AM, Erik Drolshammer wrote:
Hi!
Good morning :)
We try to set up two brokers according to [1] to get some redundancy in our
solution. The shared filesystem is based on GFS, but it doesn't seem to work
that well. The master node use a lot of
On Mon, Mar 23, 2009 at 10:00 AM, Erik Drolshammer wrote:
> Hi!
> We try to set up two brokers according to [1] to get some redundancy in our
> solution. The shared filesystem is based on GFS, but it doesn't seem to work
> that well. The master node use a lot of cpu, but the throughput is horrible
Hi!
We try to set up two brokers according to [1] to get some redundancy in
our solution. The shared filesystem is based on GFS, but it doesn't seem
to work that well. The master node use a lot of cpu, but the throughput
is horrible.
Can anyone point me to some resources describing the setup
