Hello, I am running apache-activemq-5.1.0 under Centos 5.2 and having the
exact same issue - I was under the assumption (from the posts in this tread)
that this was fixedjust reportingThank you!
Exception in thread "ActiveMQ Transport: tcp://localhost/127.0.0.1:61616"
java.lang.ClassCastE
Thanks Rob, I am looking forward to it.
rajdavies wrote:
>
> We are currently going through votes on 5.1 - should be a few days
>
> cheers,
>
> Rob
> On 16 Apr 2008, at 07:44, Ramit Arora wrote:
>
>>
>> Hey Rob,
>> Thanks for the reply. BTW, when do you expect to roll out 5.1? We
>> really
We are currently going through votes on 5.1 - should be a few days
cheers,
Rob
On 16 Apr 2008, at 07:44, Ramit Arora wrote:
Hey Rob,
Thanks for the reply. BTW, when do you expect to roll out 5.1? We
really
need it due to this bug & NFS based master/slave which is broken in
5.0.
Thanks,
Hey Rob,
Thanks for the reply. BTW, when do you expect to roll out 5.1? We really
need it due to this bug & NFS based master/slave which is broken in 5.0.
Thanks,
Ramit
rajdavies wrote:
>
> Hi Ramit,
>
> only just saw you stack trace - this is a known problem - caused by a
> bug in the Inact
Hi Ramit,
only just saw you stack trace - this is a known problem - caused by a
bug in the InactivityMonitor - its fixed in the upcoming 5.1 release
(you could test the release candidate - here:
http://people.apache.org/~chirino/staging-repos/activemq-5.1.0-RC3/org/apache/activemq/apache-act
Hey Fred,
The problem seems to be a bit strange. It occurs only if I use Solaris to
host my broker. The problem is much more frequent if the server machine is
Solaris/x86 rather than Solaris/Sparc. Windows machines are not suffering
from this problem. And the problem disappears if i use JNDI to se
Maybe try to see where the thresold is ... increase 1 or 2 subsribers until
it happens.
A workaround might be to try a network of 2 brokers perhaps to see if its a
scaling issue.
Fred
Ramit Arora wrote:
>
> Hi,
> I am testing ActiveMQ 5.0 using a Perl Publisher (using Net::Stomp) & Java
> Sub
