om 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 th
ing?"
>> >
>> > We have seen this happenand 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
>
; > > 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-tp1
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-tp14453548s2354
...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.c
ages)
fixed our problem.
--
View this message in context:
http://www.nabble.com/NegativeArraySizeException-in-Unmarshal-tp14453548s2354p14926923.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
s anyone seen this before
or know why it might be happening?apart from the fact something is using
negative number as array size ;)
thanks
/Tom
--
View this message in context:
http://www.nabble.com/NegativeArraySizeException-in-Unmarshal-tp14453548s2354p14453548.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
