Rob, thanks for looking into this. I'll provide a summary of what I
found here for anybody out there doing searches who might run across
this issue:
Basically, if you create several (or many) connection objects, you
end up with these threads piling up in the background. I've also
experi
I have noticed that the default value for syncOnWrite for the AMQ store
is set to false.
Is this a wise default? As a user of a transactional messaging store, I
would have thought the common expectation would be that if my broker
dies, all messages in committed transactions have been safely w
Hi Rob,
Looks like the AMQ store works correctly - thanks for the advice.
Cheers,
David
Rob Davies wrote:
Do you get the same using AMQ store (the default in 5.0) - its the
prefered store over kaha in ActiveMQ 5.0
cheers,
Rob
http://rajdavies.blogspot.com/
On Oct 3, 2007, at 8:50 AM,
er - kinda fixed - there's another leak just need to plug ...
On Oct 2, 2007, at 1:23 PM, WHIRLYCOTT wrote:
On Oct 1, 2007, at 8:27 AM, Rob Davies wrote:
I'm going to see if I can reproduce on OS/X
Any luck?
phil.
--
Whirlycott
k - this is fixed in main trunk now
On Oct 2, 2007, at 1:23 PM, WHIRLYCOTT wrote:
On Oct 1, 2007, at 8:27 AM, Rob Davies wrote:
I'm going to see if I can reproduce on OS/X
Any luck?
phil.
--
Whirlycott
Philip Jacob
A possible fix for this below
http://www.nabble.com/FanoutTransport-Patches-tf4562939s2354.html
-Trevor
--
View this message in context:
http://www.nabble.com/FanoutTransport---how-to-specify-value-for-minAckCount---tf4126265s2354.html#a13023053
Sent from the ActiveMQ - User mailing list archi
There's a copy here...
http://open.iona.com/wiki/display/ProdInfo/FUSE+Message+Broker+Performance+Tuning+Guide
On 28/09/2007, Paul Ortiz <[EMAIL PROTECTED]> wrote:
>
> Yes, it would be really nice to have a look at this document.
>
> P.
>
>
> JigarP wrote:
> >
> > Hi Karthick,
> >
> >I am not
So it sounds like you just wanna mostly use ActiveMQ with PHP and Perl
right? If so I'd recommend just running the broker via the shell
script / windows service / unix service directly; then you don't have
to worry about integrating into some app server and messing about with
all that JCA stuff.
Try upgrading to a newer version; we've fixed up some of the SQL for
locking the database.
Or if you know you're only gonna run a single broker, you can disable
database locking via...
http://activemq.apache.org/maven/activemq-core/xsddoc/http___activemq.org_config_1.0/element/jdbcPersistenceAdap
We are also experiencing more or less the same situation, but with a
configuration comprising 2 brokers, one publisher and one durable
subscriber. The brokers and clients are using 'discovery'.
Has anyone looked into this?
Joe
Naz Irizarry wrote:
>
> BACKGROUND
>
> I am using ActiveMQ 4
I had the same problem. Download the sjsxp.jar from somewhere and add to the
classpath (I saved it to the /lib directory).
see also: http://forums.java.net/jive/thread.jspa?messageID=117971
http://forums.java.net/jive/thread.jspa?messageID=117971
After that it worked =)
Fintan Bolton wrote:
Do you get the same using AMQ store (the default in 5.0) - its the
prefered store over kaha in ActiveMQ 5.0
cheers,
Rob
http://rajdavies.blogspot.com/
On Oct 3, 2007, at 8:50 AM, David Sitsky wrote:
I have discovered an issue with the latest activemq 5.0 (revision
581510) which seems
I have discovered an issue with the latest activemq 5.0 (revision
581510) which seems to have been present for some time, at least for the
last month.
I have an application using transactions, and kaha persistence, and two
consumers feeding off a queue.
I sometimes see the same message being
13 matches
Mail list logo
