Awesome! Thanks.
cheers,
j.
On Mon, May 31, 2010 at 1:10 PM, Gary Tully wrote:
> Test case is great, thanks, I have opened
> https://issues.apache.org/activemq/browse/AMQ-2754 to track this, just
> validating the fix at the moment.
>
> On 8 May 2010 07:43, Jamie McCrindle wro
uce Snyder wrote:
> On Fri, May 7, 2010 at 3:19 PM, Jamie McCrindle
> wrote:
>> Greetings all,
>>
>> After some weeks of scratching my head, I _believe_ I have found the
>> magic combination that appears to be causing messages to become stuck
>> in our network of
APPLE.local-57893-1273267004592-0:1) stopped
On Fri, May 7, 2010 at 10:20 PM, Jamie McCrindle
wrote:
> Oh, this is using:
>
> ActiveMQ 5.3.1
> Spring 2.5.6
>
> On Fri, May 7, 2010 at 10:19 PM, Jamie McCrindle
> wrote:
>> Greetings all,
>>
>> After some weeks of
Oh, this is using:
ActiveMQ 5.3.1
Spring 2.5.6
On Fri, May 7, 2010 at 10:19 PM, Jamie McCrindle
wrote:
> Greetings all,
>
> After some weeks of scratching my head, I _believe_ I have found the
> magic combination that appears to be causing messages to become stuck
> in our net
Greetings all,
After some weeks of scratching my head, I _believe_ I have found the
magic combination that appears to be causing messages to become stuck
in our network of brokers. It's so convoluted that it's entirely
likely that the error isn't what I think it is but I have managed to
create a t
Awesome. Thanks for looking into that... you're right. I changed the
transacted to false in the original test and it worked... (I also
spotted a bug in the original test in that it was creating both
sessions from the same connection). In case anyone is interested, the
updated test is attached...
*
It fails at:
assertNotNull(message1);
btw.
On Sat, Apr 17, 2010 at 12:06 AM, Jamie McCrindle
wrote:
> :) It's the mailing list software conspiring, I tell you... adding it
> directly into the mail instead:
>
> package org.example.activemq;
>
> impor
stop();
}} catch(Throwable t) { t.printStackTrace(); }
try { if(brokerService2 != null) { brokerService2.stop();
}} catch(Throwable t) { t.printStackTrace(); }
}
}
}
On Fri, Apr 16, 2010 at 6:56 PM, Tracy Snell wrote:
> You did do something wrong! You forgot to attach the test
Hiya,
We've been getting an issue with using a static Network of Brokers
where if we publish something to broker 1, it doesn't get picked up by
broker 2. We've tried various values for dynamicOnly, networkTTL and
prefetchSize.
I've attached a test case that, assuming I've written it correctly,
hi
Thanks Bruce,
Will give that a go. There seem to be a few 5.4.0 fixes addressing
this issue which is why we didn't move to 5.3 straight away but will
try it and see.
cheers,
j.
On Wed, Mar 10, 2010 at 3:05 PM, Bruce Snyder wrote:
> On Tue, Mar 9, 2010 at 11:27 AM, Jamie McCrindle
Hi,
It appears we may be getting by this
https://issues.apache.org/activemq/browse/AMQ-2009 or some variant of
it i.e. messages are getting stuck in a queue. We are busy looking at
our config and gradually making changes to try and resolve it but we
can't replicate in dev so it's slow going. We're
to raise a bug
> On 19 Jan 2010, at 16:49, Jamie McCrindle wrote:
>
>> Hiya,
>>
>> We've worked around the problem by increasing the buffer size but it's
>> not the best solution. I'd like to raise a bug in Jira but it's for
>> authorized users
Hiya,
We've worked around the problem by increasing the buffer size but it's
not the best solution. I'd like to raise a bug in Jira but it's for
authorized users only. Is there another way to get it in?
cheers,
j.
On Thu, Jan 14, 2010 at 11:30 AM, Jamie McCrindle
wrote:
- http://fusesource.com/
> ActiveMQ in Action - http://www.manning.com/snyder/
> Blog - http://www.nighttale.net
>
>
> On Thu, Jan 14, 2010 at 12:09 PM, Jamie McCrindle
> wrote:
>
>> Hi All,
>>
>> It appears that the ActiveMQ FuseSource Stomp PHP client can't
Hi All,
It appears that the ActiveMQ FuseSource Stomp PHP client can't handle
messages larger than 1024 bytes. The code is as follows in Stomp.php:
$rb = 1024;
$data = '';
$end = false;
do {
$read = fread($this->_socket, $rb);
if ($read ===
d, Sep 30, 2009 at 1:30 PM, Jamie McCrindle
> wrote:
>> Hi All,
>>
>> I've just got hit by an OutOfMemoryError: unable to create new native
>> thread issue. I've switched UseDedicatedTaskRunner to false which
>> appears to have resolved the issue for now
ing
there.
Yeah, I'm wondering that as well. I'll see if I can do a little more
investigation... see if I can reproduce it in a different environment.
On Thu, Oct 1, 2009 at 3:26 PM, Bruce Snyder wrote:
> On Thu, Oct 1, 2009 at 7:57 AM, Jamie McCrindle
> wrote:
>> Hi Bruce,
> On Thu, Oct 1, 2009 at 5:13 AM, Jamie McCrindle
> wrote:
>> Hi All,
>>
>> I've just got hit by an OutOfMemoryError: unable to create new native
>> thread issue. I've switched UseDedicatedTaskRunner to false which
>> appears to have resolved the is
Hi All,
I've just got hit by an OutOfMemoryError: unable to create new native
thread issue. I've switched UseDedicatedTaskRunner to false which
appears to have resolved the issue for now but I have a feeling I'm
just masking a deeper problem.
I have the following set up:
2 ActiveMQ brokers confi
Hi All,
I've just got hit by an OutOfMemoryError: unable to create new native
thread issue. I've switched UseDedicatedTaskRunner to false which
appears to have resolved the issue for now but I have a feeling I'm
just masking a deeper problem.
I have the following set up:
2 ActiveMQ brokers confi
Solved:
org.apache.activemq
activemq-core
5.1.0
org.apache.activemq
activeio-core
org.apache.activemq
activeio-core
3.1.0
On Thu, May 22, 2008 at 7:19 PM, Jamie McCrindle
<[EM
I'm using ActiveMQ 5.1.0 and moving to a 5.2.0 snapshot isn't an option...
On Thu, May 22, 2008 at 7:18 PM, Jamie McCrindle
<[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'm getting hit by AMQ-1132 - the activeio-core-test.jar is being
> included by maven and the log
Hi all,
I'm getting hit by AMQ-1132 - the activeio-core-test.jar is being
included by maven and the log4j.properties inside the jar file is
overriding my own log4j.properties (with associated /target/test.log
exception).
Anybody know a workaround in maven. The exclusions mechanism doesn't
allow f
If you can use Java 6, try the following setting:
-XX:+HeapDumpOnOutOfMemoryError
(and -XX:HeapDumpPath if you want the dump to go somewhere specific)
This will give you a heap dump which should help a _lot_ to diagnose
the problem. I'd recommend checking out the Memory Analyzer plugin for
Eclip
Hiya,
We had some connection problems with MySql not dropping old
connections quickly enough, the configuration from the mysql site was
quite good (i.e. it solved our problem):
http://dev.mysql.com/doc/refman/5.0/en/connector-j-usagenotes-j2ee.html#connector-j-usagenotes-tomcat
just replace the
Hi guys,
As always, great job on ActiveMQ!
We're switching to MySQL for one of our deployments and we've just run
into http://issues.apache.org/activemq/browse/AMQ-1236 (Pure JDBC
Master Slave problem with ActiveMQ 4.1.1 and MySQL).
Are there any plans to release 4.1.2 anytime soon or should I s
Hi,
As far as I'm aware you have two options: either switch off locking in
your jdbc adapter
(http://www.mail-archive.com/[EMAIL PROTECTED]/msg03257.html)
or try the code attached to this defect:
https://issues.apache.org/activemq/browse/AMQ-1086.
If you choose to switch off locking, Pure JDBC M
Thanks James,
I moved away from failover:tcp://localhost:61616 for reasons that now
completely escape me. I'll put that back in and see the problem goes
away.
cheers,
j.
On 3/5/07, James Strachan <[EMAIL PROTECTED]> wrote:
On 3/5/07, Jamie McCrindle <[EMAIL PROTECTED]> wrote
Hi all,
I keep getting the following exception at what appear to be random intervals:
2007-03-05 14:42:40,367 INFO [ActiveMQ Transport: tcp://localhost/1
27.0.0.1:51515] FailoverTransport.handleTransportFailure | Transport failed, att
empting to automatically reconnect due to: java.io.EOFExcepti
29 matches
Mail list logo
