Never mind. All you have to do is add this to your Apache Camel pom.xml:
<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-openwire-legacy</artifactId>
<version>5.18.5</version>
</dependency>
I feel silly. Thank you for your help Robbie. Have a great weekend.
Regards,
William Crowell
From: William Crowell via users <[email protected]>
Date: Wednesday, February 4, 2026 at 2:03 PM
To: [email protected] <[email protected]>
Cc: William Crowell <[email protected]>
Subject: Re: Strange OpenWire Version Issue Using a Camel Route Migrating
Messages From ActiveMQ Classic 5.5.1 to 6.1.7
Robbie,
Thanks for your reply. Any way around it other than upgrading? Can I use an
additional transportConnector using a different protocol? What would that
protocol be?
Regards,
William Crowell
From: Robbie Gemmell <[email protected]>
Date: Wednesday, February 4, 2026 at 12:58 PM
To: [email protected] <[email protected]>
Subject: Re: Strange OpenWire Version Issue Using a Camel Route Migrating
Messages From ActiveMQ Classic 5.5.1 to 6.1.7
Its probably not that strange really. The log messages looks very much
like: newer client tries newer Openwire protocol version, older broker
doesnt support that version and barfs, indicates what it does support,
but newer client doesnt automatically support that ancient version,
boom.
You mention using Camel 4.8.0. It looks to use activemq 5.18.5:
https://github.com/apache/camel/blob/camel-4.8.0/parent/pom.xml#L59
and only uses a main client dep.
The ancient 5.5.1 broker, from 2011, only supports up to Openwire v7:
https://github.com/apache/activemq/tree/activemq-5.5.1/activemq-core/src/main/java/org/apache/activemq/openwire
The 5.18.5 client dep does not automatically carry support for
Openwire v7:
https://github.com/apache/activemq/tree/activemq-5.18.5/activemq-client/src/main/java/org/apache/activemq/openwire,
as that old protocol version now lives only in the optional legacy
module:
https://github.com/apache/activemq/tree/activemq-5.18.5/activemq-openwire-legacy/src/main/java/org/apache/activemq/openwire
with several other old protocol versions predating 5.6.0 in 2012.
Robbie
On Tue, 3 Feb 2026 at 22:22, William Crowell via users
<[email protected]> wrote:
>
> Good afternoon,
>
> I am using an Apache Camel route (version 4.8.0) and moving messages from an
> ActiveMQ Classic broker (version 5.5.1) to another ActiveMQ Classic broker
> (version 6.1.7).
>
> The operating system is Rocky Linux 9.
>
> When I run the Camel route and it connects to the 5.5.1 source server I get:
>
> ...
> 2026-02-03 22:11:03,335 WARN
> [org.apa.cam.com.jms.DefaultJmsMessageListenerContainer] (Camel (camel-1)
> thread #2 - JmsConsumer[test]) Setup of JMS message listener invoker failed
> for destination 'test' - trying to recover. Cause: The JMS connection has
> failed: Invalid version: 7, could not load
> org.apache.activemq.openwire.v7.MarshallerFactory
> 2026-02-03 22:11:03,349 ERROR
> [org.apa.cam.com.jms.DefaultJmsMessageListenerContainer] (Camel (camel-1)
> thread #2 - JmsConsumer[test]) Could not refresh JMS Connection for
> destination 'test' - retrying using FixedBackOff{interval=5000,
> currentAttempts=0, maxAttempts=unlimited}. Cause: Disposed due to prior
> exception
> ….
>
> The error I get on the source 5.5.1 broker is:
>
> 2026-02-03 22:11:08,359 | INFO | Transport failed: java.io.IOException:
> Unknown data type: 68 |
> org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
> Transport: tcp:///172.31.24.115:49406
>
> I have tried adjusting the wireFormat.version to 5,6,7 and even zero.
>
> Maybe I should use STOMP or WS protocol instead? AMQP is not available on
> ActiveMQ Classic 5.5.1.
>
> Regards,
>
> William Crowell
>
>
> This e-mail may contain information that is privileged or confidential. If
> you are not the intended recipient, please delete the e-mail and any
> attachments and notify us immediately.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
CAUTION: This email originated from outside of the organization. Do not click
on links or open attachments unless you recognize the sender and know the
content is safe.
This e-mail may contain information that is privileged or confidential. If you
are not the intended recipient, please delete the e-mail and any attachments
and notify us immediately.
CAUTION: This email originated from outside of the organization. Do not click
on links or open attachments unless you recognize the sender and know the
content is safe.
This e-mail may contain information that is privileged or confidential. If you
are not the intended recipient, please delete the e-mail and any attachments
and notify us immediately.
