I'm going to look into the driver detection Monday and see if I can
determine why the driver isn't recognized, if I can articulate the problem
I'm create a bug.
We're using the stock ojdbc7.jar Oracle thin driver so I'm not aware of any
reason why detection should not work.
I found the resource
I'm glad you found a solution (one that's already in the codebase, even).
Is the driver one that we should be recognizing as an Oracle driver? Should
we be writing a bug against the fact that we didn't recognize the driver?
Or are you using a driver that's custom or exotic in some way?
Tim
On
To wrap this up, this issue is known and has been fixed via the
OracleJDBCAdapter class.
The problem we're seeing is due to AMQ not recognizing our driver as an
Oracle driver, which is not unheard of.
We should be able to force the correct adapter with something like:
which will override
Gary, great leads, thank you.
I'm planning to verify the performance of replacing the stock query:
SELECT
ID
,MSG
FROM
table
WHERE
CONTAINER=?
AND ID < ?
AND ID > ?
AND XID IS NULL
ORDER BY
ID
With something oracle-specific that will limit the rows in the
there was some work on limiting queries:
https://issues.apache.org/jira/browse/AMQ-6049
also - the statements can be configured - so you can provide your own
statement via configuration.
http://activemq.2283324.n4.nabble.com/Statements-in-Activemq-Xml-Jdbcpersistence-adapter-td4668983.html
On
Tim, thanks for writing.
Does AMQ support DB-speciifc queries? I could likely write the patch
myself if pointed in the right direction.
DefaultJDBCAdapter.doRecoverNextMessages looks like a method that would be
called at start-up, can you verify?
Or, under what circumstances is that invoked?
I've never heard of this particular problem being reported, but it should
be fairly straightforward to turn it into a top-N query by doing a
sub-select as described in
http://www.oracle.com/technetwork/issue-archive/2006/06-sep/o56asktom-086197.html.
Would you please submit an enhancement request
