Is there a list maintained somewhere of AMQ specialty consultants?
We're interested in having someone out to review our setup and provide
recommendations.
Thanks
Nathan
Jason, you should try removing the changes you made to your configuration
and verify if the correct driver is auto-detected.
You should see one of the following log lines at startup:
try {
adapter = finder.newInstance(dirverName);
LOG.info("*Database "** + kind + **" driver override recognized for
We're working on what sounds like the same issue Jason.
We have not confirmed that we can force AMQ to use the OracleJDBCAdapter
but that is our current line.
I'm also investigating why detection is not working. The driver name hasn't
changed so it's not obvious. I have a lead I'm running out righ
quot;
> > lockKeepAlivePeriod="3000">
> >
> >
> >
> >
> > which will override limitQuery with an inner select and a ROWNUM clause:
> >
> > @Override
> > public String limitQuery(String query) {
> > return "SELECT * FR
rride limitQuery with an inner select and a ROWNUM clause:
@Override
public String limitQuery(String query) {
return "SELECT * FROM (" + query + ") WHERE ROWNUM <= " +
getMaxRows();
}
Thank you again Gary and Tim for your help.
Nathan
On Fri, Feb 2, 2
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-td4668
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?
Th
