issue in /overview

[xjuarez]

HTTP ERROR 500 java.lang.NullPointerException: Cannot invoke "com.dbxtune.central.pcs.objects.DbxCentralSessions.getServerName()" because "srvEntry" is null

URI: | /overview -- | -- 500 java.lang.NullPointerException: Cannot invoke "com.dbxtune.central.pcs.objects.DbxCentralSessions.getServerName()" because "srvEntry" is null OverviewServlet java.lang.NullPointerException: Cannot invoke "com.dbxtune.central.pcs.objects.DbxCentralSessions.getServerName()" because "srvEntry" is null

Caused by:

java.lang.NullPointerException: Cannot invoke "com.dbxtune.central.pcs.objects.DbxCentralSessions.getServerName()" because "srvEntry" is null
	at com.dbxtune.central.controllers.OverviewServlet.printServerLayout_CmRefreshButtons(OverviewServlet.java:480)
	at com.dbxtune.central.controllers.OverviewServlet.doGet(OverviewServlet.java:879)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
	at org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1450)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:799)
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:554)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:571)
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
	at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1624)
	at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1440)
	at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:505)
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1594)
	at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1355)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
	at org.eclipse.jetty.server.Server.handle(Server.java:516)
	at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487)
	at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732)
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479)
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
	at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338)
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315)
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173)
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131)
	at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409)
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034)
	at java.base/java.lang.Thread.run(Thread.java:840)

[goranschwarz]

How does your SERVER_LIST file look like?
You can find this here: ${HOME}/.dbxtune/dbxc/conf/SERVER_LIST

Here is an example on this file for: http://dbxtune.gorans.org/

##===========================================================================
## Fields in this file
## 1 - SERVERNAME (must be unique) (this is connection info sent to the specified DbxTune collector)
## 2 - 1=Enabled, 0=Disabled
## 3 - Some explanation for the role of this server
## 4 - Script that will be used to start the server.
##     NOTE: <SRVNAME> is replaced with the servername in field 1
##===========================================================================
## NOTE about field 1 / ServerName
##  * This must be a unique name
##  * If this field contain any strange char like '/', '\', ';' or ':' then we need to add: -A alternameSrvName
##    The alternate server name will be used for log files, H2 Database Recordings, DbxCentral SchemaName, etc...
##  For example if the server do not run on the default port name, a entry might look like:
##    prod-1a-pg.acme.com:1234 ; 1 ; Some Desc ; ${DBXTUNE_CENTRAL_BASE}/bin/start_postgrestune.sh <SRVNAME> -A prod-1a-pg
##  Or for a SQL-Server with dynamic ports
##    GS-1-WIN\SS_2016 ; 1 ; SQL-Server 2016 on Windows ; ${DBXTUNE_CENTRAL_BASE}/bin/start_sqlservertune.sh <SRVNAME> -A GS-1-WIN__SS_2016
##===========================================================================
## NOTE about field 4 / Script...
## ${DBXTUNE_CENTRAL_BASE} is normally: ${HOME}/.dbxtune/dbxc
## In that script you can specialize how to start the various collectors
## You CAN also put everything (all cmdline switches) in here as well, but the row will be very long...
##===========================================================================
## Layout of buttons in the DBX Central Landing page
## * Servers are laid out in the order they are added in this file
## However you can add some special "#LABEL; " Comments, which means you can arrange servers in groups etc
## Syntax: #FORMAT; {GROUP|LABEL}; Some Text; option1=value, option2=value
## * #FORMAT; GROUP; Name of The Group; border=false         (note: border=true/false is optional)
## * #FORMAT; LABEL; Name of The Label
##===========================================================================


#FORMAT; GROUP; Sybase Servers; border=false
GORAN_UB0_DS       ; 1 ; ASE Version 12.5.4         ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh <SRVNAME>
GORANS_UB1_DS      ; 1 ; ASE Version 15.5           ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh <SRVNAME>
GORAN_UB2_DS       ; 1 ; ASE Version 15.7           ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh <SRVNAME>
GORAN_UB3_DS       ; 1 ; ASE Version 16.0           ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh <SRVNAME>

#FORMAT; GROUP; Microsoft SQL Servers; border=false
gs-1-win:1433      ; 1 ; SQL-Server 2016 on Windows ; ${DBXTUNE_CENTRAL_BASE}/bin/start_sqlservertune.sh <SRVNAME> -A GS-1-WIN__SS_2016
gorans-ub3:1433    ; 1 ; SQL-Server 2019 on Linux   ; ${DBXTUNE_CENTRAL_BASE}/bin/start_sqlservertune.sh <SRVNAME> -A gorans-ub3-ss
prod-2a-mssql      ; 1 ; SQL-Server 2019 on Linux   ; ${DBXTUNE_CENTRAL_BASE}/bin/start_sqlservertune.sh <SRVNAME>
prod-2b-mssql      ; 1 ; SQL-Server 2019 on Linux   ; ${DBXTUNE_CENTRAL_BASE}/bin/start_sqlservertune.sh <SRVNAME>

#FORMAT; GROUP; Other Servers; border=false
#-FORMAT; LABEL; Postgres
gorans-ub3:5432    ; 1 ; Postgress 12.7              ; ${DBXTUNE_CENTRAL_BASE}/bin/start_postgrestune.sh <SRVNAME>  -A gorans-ub3-pg
pg-3a-cos9         ; 1 ; Postgress 16.2              ; ${DBXTUNE_CENTRAL_BASE}/bin/start_postgrestune.sh <SRVNAME>
#-FORMAT; LABEL; MySQL
gorans-ub3:3306    ; 1 ; MySql 8                     ; ${DBXTUNE_CENTRAL_BASE}/bin/start_mysqltune.sh <SRVNAME>     -A gorans-ub3-my -N _gorans-ub3_--_MySql_Test_

Action from you:

Please post your SERVER_LIST here... so I can do some debugging!

However: I fixed the NullPointerException... By simply skipping that entry if it's null...
But I still want to see your SERVER_LISTso I can fix it in a better way

Once I have a fix for you, I'll point you to a URL where I will create a test drop so you can: install and verify that it is fixed...

[goranschwarz]

@xjuarez Can you provide the above information!

[xjuarez]

I have only these

##===========================================================================

Fields in this file

1 - SERVERNAME (must be unique) (this is connection info sent to the specified DbxTune collector)

2 - 1=Enabled, 0=Disabled

3 - Some explanation for the role of this server

4 - Script that will be used to start the server.

NOTE: is replaced with the servername in field 1

##===========================================================================

NOTE about field 1 / ServerName

* This must be a unique name

* If this field contain any strange char like '/', '', ';' or ':' then we need to add: -A alternameSrvName

The alternate server name will be used for log files, H2 Database Recordings, DbxCentral SchemaName, etc...

For example if the server do not run on the default port name, a entry might look like:

prod-1a-pg.acme.com:1234 ; 1 ; Some Desc ; ${DBXTUNE_CENTRAL_BASE}/bin/start_postgrestune.sh -A prod-1a-pg

Or for a SQL-Server with dynamic ports

GS-1-WIN\SS_2016 ; 1 ; SQL-Server 2016 on Windows ; ${DBXTUNE_CENTRAL_BASE}/bin/start_sqlservertune.sh -A GS-1-WIN__SS_2016

##===========================================================================

NOTE about field 4 / Script...

${DBXTUNE_CENTRAL_BASE} is normally: ${HOME}/.dbxtune/dbxc

In that script you can specialize how to start the various collectors

You CAN also put everything (all cmdline switches) in here as well, but the row will be very long...

##===========================================================================

Layout of buttons in the DBX Central Landing page

* Servers are laid out in the order they are added in this file

However you can add some special "#LABEL; " Comments, which means you can arrange servers in groups etc

Syntax: #FORMAT; {GROUP|LABEL}; Some Text; option1=value, option2=value

* #FORMAT; GROUP; Name of The Group; border=false (note: border=true/false is optional)

* #FORMAT; LABEL; Name of The Label

##===========================================================================

#PROD_A1_ASE ; 1 ; PROD Active Side ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh
#PROD_REP ; 1 ; PROD Replication Server ; ${DBXTUNE_CENTRAL_BASE}/bin/start_rstune.sh
#PROD_B1_ASE ; 1 ; PROD Standby Side ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh
#DEV_ASE ; 1 ; DEV ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh
#SYS_ASE ; 0 ; SYS ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh
#INT_ASE ; 0 ; INT ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh
#STAGE_ASE ; 0 ; STAGE ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh
#prod-psql1 ; 1 ; Postgres on default port ; ${DBXTUNE_CENTRAL_BASE}/bin/start_postgrestune.sh
#host-1:1234 ; 1 ; Postgres on non default port ; ${DBXTUNE_CENTRAL_BASE}/bin/start_postgrestune.sh -A prod-1a-pg
#GS-1-WIN\SS_2016 ; 1 ; SQL-Server on dynamic port ; ${DBXTUNE_CENTRAL_BASE}/bin/start_sqlservertune.sh -A GS-1-WIN__SS_2016

Example of using a specialized layout

>>> #FORMAT; GROUP; Sybase Servers; border=false

>>> GORAN_UB0_DS ; 1 ; ASE Version 12.5.4 ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh

>>> GORANS_UB1_DS ; 1 ; ASE Version 15.5 ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh

>>> GORAN_UB2_DS ; 1 ; ASE Version 15.7 ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh

>>> GORAN_UB3_DS ; 1 ; ASE Version 16.0 ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh

>>>

>>> #FORMAT; GROUP; Microsoft SQL Servers; border=false

>>> gs-1-win:1433 ; 1 ; SQL-Server 2016 on Windows ; ${DBXTUNE_CENTRAL_BASE}/bin/start_sqlservertune.sh -A GS-1-WIN__SS_2016

>>> gorans-ub3:1433 ; 1 ; SQL-Server 2019 on Linux ; ${DBXTUNE_CENTRAL_BASE}/bin/start_sqlservertune.sh -A gorans-ub3-ss

>>> prod-2a-mssql ; 1 ; SQL-Server 2019 on Linux ; ${DBXTUNE_CENTRAL_BASE}/bin/start_sqlservertune.sh

>>> prod-2b-mssql ; 1 ; SQL-Server 2019 on Linux ; ${DBXTUNE_CENTRAL_BASE}/bin/start_sqlservertune.sh

>>>

>>> #FORMAT; GROUP; Other Servers; border=false

>>> #FORMAT; LABEL; Postgres

>>> gorans-ub3:5432 ; 1 ; Postgress 12.7 ; ${DBXTUNE_CENTRAL_BASE}/bin/start_postgrestune.sh -A gorans-ub3-pg

>>> #FORMAT; LABEL; MySQL

>>> gorans-ub3:3306 ; 1 ; MySql 8 ; ${DBXTUNE_CENTRAL_BASE}/bin/start_mysqltune.sh -A gorans-ub3-my

##========================================================================================================================================================

SYBASE_PROD ; 1 ; Sybase Produccion ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh

This happened to me after updating, as it was working perfectly before.

[goranschwarz]

@xjuarez try to download and install this "drop": https://gorans.org/www/dbxtune/tmp/dbxtune_2025-12-04.zip

In there I "just" do the following:

				DbxCentralSessions srvEntry = layoutEntry.getSrvSession();
				if (srvEntry == null)
				{
					String info = "layoutEntry={type=" + layoutEntry.getType() + ", text=|" + layoutEntry.getText() + "|, options=" + layoutEntry.getOptions() + "}";
					_logger.warn("In printServerLayout_CmRefreshButtons(), the layoutEntry.getSrvSession() returned NULL. " + info + ". Skipping this entry and continuing.");
					continue;
				}

Meaning the Null Pointer will go away... and a Warning message will be printed to the log ${HOME}/.dbxtune/dbxc/log/DBX_CENTRAL.log
But I'm not 100% sure how your server name SYBASE_PROD will be presented on the landing page
Let me know after you have tested.

Note: In the SERVER_LIST file I would probably change the line
From:

SYBASE_PROD ; 1 ; Sybase Produccion ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh

To:

SYBASE_PROD ; 1 ; Sybase Produccion ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh <SRVNAME>

That enables the script start_asetune.sh to handle multiple server... meaning the <SRVNAME> in you case SYBASE_PROD will be passed to the script...
If you already have that (but it was stripped from your above "output")

[xjuarez]

I apologize, I made a mistake when pasting the content.

My line does contain what you mentioned, I'll try the new version

SYBASE_PROD ; 1 ; Sybase Produccion ; ${DBXTUNE_CENTRAL_BASE}/bin/start_asetune.sh

I'll keep you informed

[xjuarez]

It's working now, but when I try to view a previous report, I get this error.

2025-12-06 04:25:33.074 - ERROR - qtp2002097394-45 - DailySummartReportServlet - Problems doGet(): op='get', message=Unsupported database file version or invalid file header in file "/data/dbxcentral/.dbxtune/dbxc/data/ESPEJO_2025-11-28.mv.db" [90048-240]
org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported database file version or invalid file header in file "/data/dbxcentral/.dbxtune/dbxc/data/ESPEJO_2025-11-28.mv.db" [90048-240]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:690) ~[h2-2.4.240.jar:2.4.240]
at org.h2.engine.SessionRemote.readSQLException(SessionRemote.java:669) ~[h2-2.4.240.jar:2.4.240]
at org.h2.engine.SessionRemote.readException(SessionRemote.java:652) ~[h2-2.4.240.jar:2.4.240]
at org.h2.engine.SessionRemote.done(SessionRemote.java:626) ~[h2-2.4.240.jar:2.4.240]
at org.h2.engine.SessionRemote.initTransfer(SessionRemote.java:170) ~[h2-2.4.240.jar:2.4.240]
at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:445) ~[h2-2.4.240.jar:2.4.240]
at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:337) ~[h2-2.4.240.jar:2.4.240]
at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:124) ~[h2-2.4.240.jar:2.4.240]
at org.h2.Driver.connect(Driver.java:59) ~[h2-2.4.240.jar:2.4.240]
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:681) ~[java.sql:?]
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:190) ~[java.sql:?]
at com.dbxtune.sql.conn.DbxConnection.connect(DbxConnection.java:400) ~[dbxtune.jar:?]
at com.dbxtune.central.controllers.DailySummartReportServlet.connect(DailySummartReportServlet.java:111) ~[dbxtune.jar:?]
at com.dbxtune.central.controllers.DailySummartReportServlet.createReport(DailySummartReportServlet.java:360) ~[dbxtune.jar:?]
at com.dbxtune.central.controllers.DailySummartReportServlet.doGet(DailySummartReportServlet.java:228) ~[dbxtune.jar:?]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) ~[javax.servlet-api-3.1.0.jar:3.1.0]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) ~[javax.servlet-api-3.1.0.jar:3.1.0]
at org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1450) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:799) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:554) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:571) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1624) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1440) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:505) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1594) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1355) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.server.Server.handle(Server.java:516) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487) ~[jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732) [jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479) [jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277) [jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) [jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105) [jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104) [jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338) [jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315) [jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173) [jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131) [jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409) [jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883) [jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034) [jetty-all-9.4.58.v20250814-uber.jar:9.4.58.v20250814]
at java.base/java.lang.Thread.run(Thread.java:840) [?:?]

[goranschwarz]

DbxTune is using H2 as a database to store recordings... https://www.h2database.com/html/main.html

I don't want to use "to old software", so betweeen releases I'm upgrading various components.
In this release I upgraded H2 from version 2.1 to version 2.4 (hence the massage about h2-2.4.240.jar)
Unfortunately H2 is not backward compatible (so older recordings has to be manually upgraded or deleted) -- see more at the end...

When starting DbxCentral you probably got the error message (and it should not start)

				if (originEx.getErrorCode() == 90048 || originEx.getMessage().contains("Unsupported database file version"))
				{
					_logger.error("Origin H2 exception", originEx);

					_logger.error("============================================================================");
					_logger.error("== The H2 Database file is probably created with an earlier version of H2 ==");
					_logger.error("============================================================================");
					_logger.error("== ACTION: You need to upgrade/MIGRATE the H2 database to the DbxTune provided H2 Version.");
					_logger.error("== There should be 2 versions of the h2-*.jar provided under ${DBXTUNE_HOME}/lib/h2-2.*.jar A never verion and an older version.");
					_logger.error("== Note: In below command 'h2-2.x.yyy.jar' needs to be replaced with the older version JAR File, found under ${DBXTUNE_HOME}/lib/h2-2.*.jar");
					_logger.error("== ACTION: ${DBXTUNE_HOME}/bin/dbxtune.sh dbxcdbcopy --fromOldH2Jar ${DBXTUNE_HOME}/lib/h2-2.x.yyy.jar --exec");
					_logger.error("==         If you leave out '--exec' at the end, it will only investigate and print some information.");
					_logger.error("== The migration will do the following:");
					_logger.error("==  - Start a H2 server running the 'previous' H2 version.");
					_logger.error("==  - Copy all the tables to a new H2 DB using the later/current H2 Version. Note: This takes hours...");
					_logger.error("==  - When it's done: ");
					_logger.error("==    o Remove or rename current db file 'DBXTUNE_CENTRAL_DB.mv.db' to something else (if you want to save it)");
					_logger.error("==    o Rename the new db file 'DBXTUNE_CENTRAL_DB_NEW.mv.db' to 'DBXTUNE_CENTRAL_DB.mv.db'");
					_logger.error("==    o Start DbxCentral again, and watch the log for errors or strange messages.");
					_logger.error("==    o Then start all the collectors");
					_logger.error("== Note: Collector databases will probably also face the same issue...");
					_logger.error("==       For the moment there is NO upgrade path for them; Just delete *todays* recording(s) and start the collector(s) again.");
					_logger.error("============================================================================");
					_logger.info ("Requesting a 'shutdown' since we can't continue with the old H2 database version...");

When starting AseTune (or any other collector) you probably got the error message (and it should not start)

				if (originException.getErrorCode() == 90048 || originException.getMessage().contains("Unsupported database file version"))
				{
					_logger.error("============================================================================");
					_logger.error("== The H2 Database file is probably created with an earlier version of H2 ==");
					_logger.error("============================================================================");
					_logger.error("== For the moment there is NO upgrade path for Collectors; Just delete *todays* recording(s) and start the collector(s) again.");
					_logger.error("== ACTION: Delete *todays* recording and start the collector again.");
					_logger.error("============================================================================");
					_logger.info ("Requesting a 'shutdown' since we can't continue with the old H2 database version...");

So for "daily" recordings:

• Just delete the H2 database file
• Start the collector again

And for "DbxCentral":

• Upgrade the DBX_CENTRAL database
• example: ${DBXTUNE_HOME}/bin/dbxtune.sh dbxcdbcopy --fromOldH2Jar ${DBXTUNE_HOME}/lib/h2-2.x.yyy.jar --exec
• on ok: Follow instructions how to "switch out" the DBX_CENTRAL database file.

Let me know your progress :)

NOTE: in GitLab, when posting: press "Preview" -- Then you will see how your "post" will look like!
If you want to past a "code" section see: https://www.markdownguide.org/extended-syntax/#fenced-code-blocks

[goranschwarz]

I see now that you are trying to create a DSR - Daily Summary Report ... on an OLD database version!

Here is a workaround for that:

• start a H2 Server using the OLDER H2 JAR (JAR = H2 software version)
• Then connect to the OLDER version, using a URL see below

Example:

• On the DbxCentral machine start a H2 server (using the older H2 jar):
  java -cp /path/to_dbxtune_software/lib/h2-2.1.214.jar org.h2.tools.Server -tcp -tcpPort 9999 -tcpAllowOthers -baseDir /data/dbxcentral/.dbxtune/dbxc/data/
  Note: That the port number is 9999 or you can choose some other port if 9999 is bussy
• In the DbxCentral UI: Click on the ASE Sever --> Choose "Create Daily Summary Report on Current Recording"
  • in the URL use jdbc:h2:tcp:9999//hostname.acme.com/ESPEJO_2025-11-28;IFEXISTS=TRUE -- change "hostname.acme.com" to your hostname or IP address of the DbxCentral machine

Hopefully you could now "temporarily" read older versions of the H2 databases

[goranschwarz]

@xjuarez Please close the issue; when you feel that issue is solved... Or: Provide additional information!