Oh, sweet! Good riddance! ;-) Thanks, Kind regards, Endre
On Sun, Nov 5, 2023 at 2:52 PM Matt Pavlovich <mattr...@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. > >
