Help HikariPool error and more, l2jserver

[dymek1984]

Hi, i work on l2jserver develop (2.6.2.0)

MariaDB 10.5
Openjdk11

Everything was ok but when i test my server after some time (more than 12h) i get :

  Quote

[WARN ] 2020-04-29 10:24:21 PooledConnectionFactory: HikariCPPooledConnectionFactory: Unable to get a connection!

java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30093ms.
    at com.zaxxer.hikari.pool.HikariPool.createTimeoutException(HikariPool.java:695) ~[HikariCP-3.4.3.jar:?]

Expand  

 

i read that maxidletime and maxpoolsize have to be change but even when i changemaxidletime to 30 i have errors again after same amount of time.

and at beggining of server loading have this info:

  Quote

[WARN ] 2020-04-29 14:31:56 HikariConfig: HikariPool-1 - idleTimeout has been set but has no effect because the pool is operating as a fixed size pool.

Expand  

My second error:

  Quote

[ERROR] 2020-04-28 12:12:56 L2GameClient: Client [Character: HellRaiser[268480842] - Account: hellraiser - IP: -----------] disconnected, too many floods 0 long and 0 short!

Expand  

i have change some options in config about flood protection but still have this error, this is while farming.

 

ps. I have post this on l2jserver forum but it seems dead ;/ 

[Tryskell]

If it's not about HikariCP configurations or a custom which make your connection pool dry, I suppose it's your environnement/hardware which struggle keeping the link opened.

[dymek1984]

i have check all my connections, and all are close after execute. 

I read that hikaripool error is not only in l2j server, and is fixed by change the 

two options:

 

wait_timeout  <- this is for sql

max-lifetime <- this is for hikaricp

i cant find where i can find the hikari options.

[Tryskell]

We speak about a connection request which couldn't be set after 30s of wait, I doubt setting it higher would change anything.

[Rootware]

Possible HikariCP isn't the right place where need to search the problem. It's only "little" pool manager of MySQL connections. It's means what this only the bridge between two systems.

 

Possible you have some problems with inet connection or database stability or OS stability overall.

[Tryskell]

Not sure if that will help you :

 

https://github.com/brettwooldridge/HikariCP/issues/1007

 

As I suggested, your connection pool probably goes dry due to a leak.

Edited May 6, 2020 by Tryskell

[dymek1984]

I have add all my customs (not so much that connect to db) same as l2jserver staff make. I have change 

wait_timeout = 33000; in maria db because  
hikaricp options are hardcoded 
and cant be changed, we will see if 
this change somethig. if not ill try to start clean

l2jserver just for test if my custom make this error. 

Edited May 7, 2020 by dymek1984

[Elfo]

Please paste all the HikariCP related configuration

[dymek1984]

this is in databesa.properties

  Quote

# Database Connection Pool
# Available: BoneCP, C3P0, HikariCP, ApacheDBCP, ViburDBCP
# Default: HikariCP
ConnectionPool = HikariCP

# Default: 100
MaxConnections = 100

# Default: 0
MaxIdleTime = 0

Expand  

 

and this is in HikariConfig.class

 

  Quote

   private static final long CONNECTION_TIMEOUT = SECONDS.toMillis(30);
   private static final long VALIDATION_TIMEOUT = SECONDS.toMillis(5);
   private static final long IDLE_TIMEOUT = MINUTES.toMillis(10);
   private static final long MAX_LIFETIME = MINUTES.toMillis(30);
   private static final int DEFAULT_POOL_SIZE = 10;
 

Expand