Pretty sure yeah, not trying to be smart, both are apache-activemq-4.1.1.jar, size is 4532261 on both. I thought it might be something to do with the fact that we use a Future to cancel a task that may be sending data. We use future.cancel(true) allowing the thread to be interruped, maybe its not a good idea to interrupt a thread that is sending in AMQ?
James.Strachan wrote: > > Are you positive you are using exactly the same jars on the client > side and broker? > > 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 > > -- View this message in context: http://www.nabble.com/NegativeArraySizeException-in-Unmarshal-tp14453548s2354p15019889.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
