Jason, No, that's not relevant. The question is not whether the Oracle driver is used, but whether ActiveMQ recognizes that fact and responds by using its own Oracle-specific subclass of DefaultJDBCAdapter ( https://github.com/apache/activemq/blob/master/activemq-jdbc-store/src/main/java/org/apache/activemq/store/jdbc/adapter/OracleJDBCAdapter.java). You'll see that there's not much to that class, but that it has an Oracle-specific way to limit the number of results in a response. So if ActiveMQ didn't realize that it should be using that class, then you might see the same behavior as nathanwray, and telling ActiveMQ via configuration that you're using Oracle might result in correct behavior.
Tim On Feb 5, 2018 4:54 AM, "jasons" <jason.sm...@au.abb.com> wrote: > Hi Tim, in case you missed it, or in case I'm missing something......but > doesn't my stack trace confirm Oracle driver selection by the > oracle.jdbc.driver packages? > > Cheers > > Jason. > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
