[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-users
Subject:    Re: ActiveMQ exits on startup with UTFDataFormatException: bad string
From:       Tim Bain <tbain () alumni ! duke ! edu>
Date:       2015-09-23 13:40:38
Message-ID: CAPVVMa9q240u8xxN6iY+RQGPfnJCnStGB3p2NzduSCJCq2qi4A () mail ! gmail ! com
[Download RAW message or body]


I was hoping that one of the devs (Gary, Tim, Art, etc.) would jump into
this discussion, but since they didn't, please submit a JIRA bug to bring
this issue to their attention.  If the problem is that the OpenWire
versions aren't backwards-compatible, that's either a bug (I was under the
impression that OpenWire was consciously intended to always be
backwards-compatible) or a design change that should have been called out
overtly in the release notes and wasn't.  Submit a bug and someone will
figure out which situation it was and work on a fix.

Thanks for bringing it to our attention.

Tim

On Sun, Sep 13, 2015 at 4:50 AM, gijsbert802 <vandenbrink@zorgdomein.nl>
wrote:

> I did some more debugging and compared 5.11.1 to 5.12.0. What I noticed is
> that 5.11.1 uses v6.MessageIdMarshaller, while 5.12.0 uses v11. Is 5.11.1
> supposed to use the v6 version?
> 
> v6 doesn't have the line where the error occurs
> (info.setTextView(looseUnmarshalString(dataIn));).
> 
> Let me know if you need more debugging data, I'm happy to help.
> 
> 
> 
> 
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-exits-on-startup-with-UTFDataFormatException-bad-string-tp4701955p4701965.html
>  Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> 



[prev in list] [next in list] [prev in thread] [next in thread]