From users-return-51300-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Wed Apr 17 20:28:36 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 4867C180672 for ; Wed, 17 Apr 2019 22:28:36 +0200 (CEST) Received: (qmail 45668 invoked by uid 500); 17 Apr 2019 20:28:34 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 45643 invoked by uid 99); 17 Apr 2019 20:28:34 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Apr 2019 20:28:34 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 6AFC6180E8A for ; Wed, 17 Apr 2019 20:28:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 5.541 X-Spam-Level: ***** X-Spam-Status: No, score=5.541 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, FORGED_YAHOO_RCVD=1.022, KAM_NUMSUBJECT=0.5, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_NEUTRAL=0.652, URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_TRY_3LD=0.853] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id EhSfykOnIeWG for ; Wed, 17 Apr 2019 20:28:31 +0000 (UTC) Received: from n4.nabble.com (n4.nabble.com [199.38.86.66]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id C6ACF5FAFF for ; Wed, 17 Apr 2019 20:28:28 +0000 (UTC) Received: from n4.nabble.com (localhost [127.0.0.1]) by n4.nabble.com (Postfix) with ESMTP id D5758737BB1B for ; Wed, 17 Apr 2019 15:28:28 -0500 (CDT) Date: Wed, 17 Apr 2019 15:28:28 -0500 (CDT) From: mikmela To: users@activemq.apache.org Message-ID: <1555532908871-0.post@n4.nabble.com> In-Reply-To: References: <1495218760.3421014.982371992.2182CED1@webmail.messagingengine.com> Subject: Re: Migrating storage from 5.10.0 to 5.14.5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit We seems to experience the same issue upgrading from 5.6.0 to 515.8, but in our case we use SQL database as a message store. As it was mentioned and confirmed by us KahaDB has a fallback capability when it encounter older (Version 6) of OpenWire. Unfortunately, it looks like for SQL databases there is no fallback option implemented: 2019-04-17 15:50:26,361 ERROR [Thread-8] (BrokerService.java:639) - Failed to start Apache ActiveMQ (RTCV180R1GPWR78QA12T3DEV-NY-CONNEX61616, null) java.io.UTFDataFormatException: bad string at org.apache.activemq.util.DataByteArrayInputStream.readUTF(DataByteArrayInputStream.java:265) at org.apache.activemq.openwire.v11.BaseDataStreamMarshaller.looseUnmarshalString(BaseDataStreamMarshaller.java:571) at org.apache.activemq.openwire.v11.MessageIdMarshaller.looseUnmarshal(MessageIdMarshaller.java:122) at org.apache.activemq.openwire.OpenWireFormat.looseUnmarshalNestedObject(OpenWireFormat.java:474) at org.apache.activemq.openwire.v11.BaseDataStreamMarshaller.looseUnmarsalNestedObject(BaseDataStreamMarshaller.java:466) at org.apache.activemq.openwire.v11.MessageMarshaller.looseUnmarshal(MessageMarshaller.java:220) at org.apache.activemq.openwire.v11.ActiveMQMessageMarshaller.looseUnmarshal(ActiveMQMessageMarshaller.java:101) at org.apache.activemq.openwire.v11.ActiveMQTextMessageMarshaller.looseUnmarshal(ActiveMQTextMessageMarshaller.java:101) at org.apache.activemq.openwire.OpenWireFormat.doUnmarshal(OpenWireFormat.java:367) at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:201) at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.getLastMessageBrokerSequenceId(JDBCPersistenceAdapter.java:266) at org.apache.activemq.broker.region.DestinationFactoryImpl.getLastMessageBrokerSequenceId(DestinationFactoryImpl.java:147) at org.apache.activemq.broker.region.RegionBroker.(RegionBroker.java:130) at org.apache.activemq.broker.jmx.ManagedRegionBroker.(ManagedRegionBroker.java:108) at org.apache.activemq.broker.BrokerService.createRegionBroker(BrokerService.java:2399) at org.apache.activemq.broker.BrokerService.createRegionBroker(BrokerService.java:2391) at org.apache.activemq.broker.BrokerService.createBroker(BrokerService.java:2348) at org.apache.activemq.broker.BrokerService.getBroker(BrokerService.java:1045) at org.apache.activemq.broker.BrokerService.getAdminConnectionContext(BrokerService.java:2619) at org.apache.activemq.broker.BrokerService.startVirtualConsumerDestinations(BrokerService.java:2780) at org.apache.activemq.broker.BrokerService.startDestinations(BrokerService.java:2610) at org.apache.activemq.broker.BrokerService.doStartBroker(BrokerService.java:739) at org.apache.activemq.broker.BrokerService.startBroker(BrokerService.java:733) at org.apache.activemq.broker.BrokerService.start(BrokerService.java:636) at COM.olf.adapter.jbroker.JBrokerService.startBroker(JBrokerService.java:1507) at COM.olf.adapter.jbroker.JBrokerComponent.run(JBrokerComponent.java:220) at java.lang.Thread.run(Thread.java:748) I'm wondering if there is a way to enable backward compatibility via some kind of property, or there are some other ways to do it? -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html