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 led me to confirm (and make sure) that all
the versions in play were recent and compatible. In the process, I
discovered that the Datasource in the PostgesSQL JDBC jar
(PGPoolingDataSource) had been deprecated and the recommendation was to use
the PGSimpleDatasource and then to implement an external Connection Pooling
solution. I chose Hikari.
So full steps taken :-
1) Updated activemq library to 5.15.9
2) Updated the Postgres JDBC jar to 42.2.8
3) Amended the Datasource from deprecated Pooling to a SimpleConnection
Datasource
4) Incorporated HikariCP as our Connection Pooling solution.
Example activemq config :-
<bean id="postgres-ds" class="com.zaxxer.hikari.HikariDataSource"
destroy-method="close">
<property name="dataSourceClassName"
value="org.postgresql.ds.PGSimpleDataSource" />
<property name="maximumPoolSize" value="20" />
<property name="dataSourceProperties" >
<props>
<prop key="portNumber">5432</prop>
<prop key="databaseName">activemq</prop>
<prop key="serverName">activemq.db.url</prop>
<prop key="user">activemq</prop>
<prop key="password">activemq.db.password</prop>
<prop key="sslMode">verify-ca</prop>
<prop key="sslRootCert">rds.root.cert.url</prop>
<prop key="logUnclosedConnections">true</prop>
</props>
</property>
</bean>
It's been over a week and this has been very stable instead of the daily
issues we were having. There is still an issue getting the connection to RDS
to work with the "very-full" (hence the verify-ca value) but this is very
good progress for now.
Many thanks for pointing me in the right direction
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
