KB Article #193442
DBLogger and Unified process unable to start due to serverTimezone configuration
Problem
Integration Engine shows 'Stopped' in the B2Bi UI and the Integrator/data/trace/8 logs show the following lines looping:
INFO :20260329:03.08.53.94:r4edi(b2bx_server):clusterconfig.s4m:352:* Unified is waiting stop *
INFO :20260329:03.08.53.94:r4edi(b2bx_server):clusterconfig.s4m:352:* Unified is terminated *
INFO :20260329:03.08.53.94:r4edi(b2bx_server):clusterconfig.s4m:352:* Unified is waiting start *
INFO :20260329:03.08.53.94:r4edi(b2bx_server):clusterconfig.s4m:352:* Unified is starting *
INFO :20260329:03.08.54.24:r4edi(b2bx_server):clusterconfig.s4m:372:* DBLogger is waiting stop *
INFO :20260329:03.08.54.24:r4edi(b2bx_server):clusterconfig.s4m:372:* DBLogger is waiting start *
INFO :20260329:03.08.54.24:r4edi(b2bx_server):clusterconfig.s4m:372:* DBLogger is starting *
The Integrator/data/log/unified.log shows the following error:
2026-03-30 11:32:05 [Thread-0 ] ERROR L140 UnifiedMain.lambda$execute$2 - Error for /export/axway/b2bi/Integrator/java/lib/jfiler-loader.jar in thread
java.lang.reflect.InvocationTargetException: null
…
Caused by: java.lang.RuntimeException: com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: The server time zone value 'CEST' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the serverTimezone configuration property) to use a more specifc time zone value if you want to utilize time zone support.
The Integrator/data/log/dblogger.log shows the following error:
2026-03-30 11:38:56 [-mainpool-4-thread-3] ERROR L157 StartupManager.lambda$startLogger$5 - Exception while initializing/running the dynamic instance 2; entire logger process will die
java.lang.RuntimeException: com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: The server time zone value 'CEST' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the serverTimezone configuration property) to use a more specifc time zone value if you want to utilize time zone support.
Resolution
Edit the Shared/local/config/runtime/runtimedb.properties file so that the db.url contains "serverTimezone\=<TIME_ZONE>" which should match the database timezone configuration.