You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Endre Stølsvik <En...@stolsvik.com> on 2023/11/05 12:52:59 UTC

activemq-JDBC-store vs. ActiveMQ 6.0

Hi!

I am working on something I believe is a performance problem wrt. the
TransactJDBCAdapter, i.e. for Microsoft SQL Server. *(Situation: It does
not include an override for the method "limitQuery(..)", i.e. e.g. include
"TOP X", which results in the SQL server sending back all messages for a
given destination - this is a particularly gnarly situation with MS SQL
Server, as if you do a SELECT, but only read the ResultSet partially (e.g.
200 rows of 20k), the following rs.close() will have to read in all
remaining rows to discard the resultset, a limitation of the underlying TDS
protocol)*.

However, the reason for mailing: While doing this research, I have come to
understand that the entire package 'org.apache.activemq.store.jdbc.journal'
is deprecated and legacy. That package also relies on certain imports,
'org.apache.activeio.journal.Journal' (notice activeIO), which otherwise is
not needed. The broker certainly boots and works, in JDBC mode, even with
this package and dependency deleted.

If true, would it not be a good idea to delete this with the major number
upgrade to 6.0?

Thanks,
Kind regards,
Endre Stølsvik.

Re: activemq-JDBC-store vs. ActiveMQ 6.0

Posted by Endre Stølsvik <En...@stolsvik.com>.
Oh, sweet! Good riddance! ;-)

Thanks,
Kind regards,
Endre

On Sun, Nov 5, 2023 at 2:52 PM Matt Pavlovich <ma...@gmail.com> wrote:

> Hi Endre-
>
> Check this commit:
>
> https://github.com/apache/activemq/pull/993
>
> I already removed it as prep to the Jakarta work for ActiveMQ 6.0.0
>
> Thanks,
> Matt Pavlovich
>
> > On Nov 5, 2023, at 6:52 AM, Endre Stølsvik <En...@stolsvik.com> wrote:
> >
> > Hi!
> >
> > I am working on something I believe is a performance problem wrt. the
> > TransactJDBCAdapter, i.e. for Microsoft SQL Server. *(Situation: It does
> > not include an override for the method "limitQuery(..)", i.e. e.g.
> include
> > "TOP X", which results in the SQL server sending back all messages for a
> > given destination - this is a particularly gnarly situation with MS SQL
> > Server, as if you do a SELECT, but only read the ResultSet partially
> (e.g.
> > 200 rows of 20k), the following rs.close() will have to read in all
> > remaining rows to discard the resultset, a limitation of the underlying
> TDS
> > protocol)*.
> >
> > However, the reason for mailing: While doing this research, I have come
> to
> > understand that the entire package
> 'org.apache.activemq.store.jdbc.journal'
> > is deprecated and legacy. That package also relies on certain imports,
> > 'org.apache.activeio.journal.Journal' (notice activeIO), which otherwise
> is
> > not needed. The broker certainly boots and works, in JDBC mode, even with
> > this package and dependency deleted.
> >
> > If true, would it not be a good idea to delete this with the major number
> > upgrade to 6.0?
> >
> > Thanks,
> > Kind regards,
> > Endre Stølsvik.
>
>

Re: activemq-JDBC-store vs. ActiveMQ 6.0

Posted by Matt Pavlovich <ma...@gmail.com>.
Hi Endre-

Check this commit:

https://github.com/apache/activemq/pull/993

I already removed it as prep to the Jakarta work for ActiveMQ 6.0.0

Thanks,
Matt Pavlovich

> On Nov 5, 2023, at 6:52 AM, Endre Stølsvik <En...@stolsvik.com> wrote:
> 
> Hi!
> 
> I am working on something I believe is a performance problem wrt. the
> TransactJDBCAdapter, i.e. for Microsoft SQL Server. *(Situation: It does
> not include an override for the method "limitQuery(..)", i.e. e.g. include
> "TOP X", which results in the SQL server sending back all messages for a
> given destination - this is a particularly gnarly situation with MS SQL
> Server, as if you do a SELECT, but only read the ResultSet partially (e.g.
> 200 rows of 20k), the following rs.close() will have to read in all
> remaining rows to discard the resultset, a limitation of the underlying TDS
> protocol)*.
> 
> However, the reason for mailing: While doing this research, I have come to
> understand that the entire package 'org.apache.activemq.store.jdbc.journal'
> is deprecated and legacy. That package also relies on certain imports,
> 'org.apache.activeio.journal.Journal' (notice activeIO), which otherwise is
> not needed. The broker certainly boots and works, in JDBC mode, even with
> this package and dependency deleted.
> 
> If true, would it not be a good idea to delete this with the major number
> upgrade to 6.0?
> 
> Thanks,
> Kind regards,
> Endre Stølsvik.