Hi all,
We're having problems running a cluster of brokers (AMQ 4.1.1) with
auto-discovery. We're using auto-discovery via multicast both for the JMS
clients and for the network-of-brokers. Our architecture is as follows:
There are 4 clients, and 2 brokers. The clients are configured like this:
if it was a
> serialization issue, you wouldn't get an object you can inspect.
>
>
> On 4/30/07, nlif <[EMAIL PROTECTED]> wrote:
>>
>> Hi all,
>>
>> We have a strange problem, maybe someone has seen this or has an idea:
>>
>> In our MessageListener,
Thanks, Christopher,
No, it's not. The broker and the consumer are on two different machines. The
transport is TCP.
We use Jencks for the consumer.
We're currently on ActiveMQ 4.1, but we had this problem on 4.0 as well.
Naaman
Christopher G. Stach II wrote:
>
> nlif wrote:
Thanks, James.
Yes, I'm also inclined to think it's a class loader issue. But then, how
come it doesn't happen all the time?
What may cause it to load another version of the class only some of the
times?
Does ActiveMQ do anything... um, unconventional with class-loading?
Thanks,
Naaman
James.S
Hi all,
We have a strange problem, maybe someone has seen this or has an idea:
In our MessageListener, we cast the Message into ObejctMessage, and then
call getObject() to get the actual object we sent. Upon trying to cast the
object to the proper class (SendMobileNotification), we get a
ClassCa
Hi,
I am trying to setup ActiveMQ with XMPP support, but I get this exception:
2007-03-09 19:31:47,656 ERROR ActiveMQ Transport: tcp:///127.0.0.1:3940
[org.apache.activemq.transport.xmpp.XmppTransport] -
javax.xml.stream.XMLStreamException
at com.bea.xml.stream.MXParser.fillBuf(MXParser
