We dont use this multicast, we are in control of the clients as well as the broker as its an "in-house" standalone client application that connects to the broker/server. "Random" clients cannot connect....
James.Strachan wrote: > > On 22/01/2008, James Strachan <[EMAIL PROTECTED]> wrote: >> Are you positive you are using exactly the same jars on the client >> side and broker? > > Bear in mind with multicast discovery, someone on your network could > be running a different version of ActiveMQ... > > >> >> On 17/01/2008, TOPPER_HARLEY <[EMAIL PROTECTED]> wrote: >> > >> > Thanks for the reply, but I dont think thats our issue. We are still on >> 4.1.1 >> > and dont use persistent messaging at all. >> > >> > Thanks for the input though... >> > >> > >> > dmarks wrote: >> > > >> > > "Has anyone seen this before or know why it might be happening?" >> > > >> > > We have seen this happen....and think it may be related to persisted >> > > messages generated from 4.1.1 having problems once 5.0.0 was brought >> up. >> > > Simply clearing out the datastore (we didn't need to save those >> messages) >> > > fixed our problem. >> > > >> > > >> > >> > -- >> > View this message in context: >> http://www.nabble.com/NegativeArraySizeException-in-Unmarshal-tp14453548s2354p14926935.html >> > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> > >> > >> >> >> -- >> James >> ------- >> http://macstrac.blogspot.com/ >> >> Open Source Integration >> http://open.iona.com >> > > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://open.iona.com > > -- View this message in context: http://www.nabble.com/NegativeArraySizeException-in-Unmarshal-tp14453548s2354p15019895.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
