Tim Bain wrote
> That's especially strange that the data type would switch from 51 to 49;
> that sounds to me like the data being read got updated/replaced between
> the
> two occurrences, but to an object type that's still not recognized, which
> is very strange.
Yes, I thought so as well which
That's especially strange that the data type would switch from 51 to 49;
that sounds to me like the data being read got updated/replaced between the
two occurrences, but to an object type that's still not recognized, which
is very strange.
Is there anything in your activemq.xml that would be hard-
Update - so just checked after the upgrade last night and the error has
re-occurred albeit with a different unknown data type. Please see the stack
trace below? Any ideas on what next to try?
WARN | Could not create JDBC tables; they could already exist. Failure was:
INSERT INTO ACTIVEMQ_LOCK(ID
Thanks for the reply;
There was indeed a mismatch in library versions. 5.15.8 to the client's
5.15.9. I have upgraded the broker to the client version and will give it a
few days and report back. I also noticed that there were newer versions of
PostgreSQL JDBC drivers and have downloaded the latest
java:566)[:]
> at
>
> org.apache.activemq.console.Main.runTaskClass(Main.java:262)[activemq.jar:5.15.8]
> at
> org.apache.activemq.console.Main.main(Main.java:115)[activemq.jar:5.15.8]
> INFO | Database lock driver override not found for :
> [postgresql_nat
RROR | Failed to start Apache ActiveMQ (localhost, null)
java.io.IOException: Unknown data type: 51
at
org.apache.activemq.openwire.OpenWireFormat.doUnmarshal(OpenWireFormat.java:359)[activemq-client-5.15.8.jar:5.15.8]
at
org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWir
