java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30000ms.


Samebug tips

This might be cause due to an overload in your database accesses. Try to implement a queue or using an Executor to access the database server.


8 months ago
Expert tip

Solutions on the web

Solution icon of stackoverflow
HikariPool-1 - Connection is not available, request timed out after 30000ms.

Solution icon of github
HikariPool-1 - Connection is not available, request timed out after 30000ms.

Solution icon of github
via GitHub by devpuck
, 5 months ago
HikariPool-1 - Connection is not available, request timed out after 30000ms.

Solution icon of github
via GitHub by psybox
, 6 months ago
HikariPool-1 - Connection is not available, request timed out after 30000ms.

Solution icon of github
HikariPool-1 - Connection is not available, request timed out after 30000ms.

Solution icon of github
via GitHub by Victorsueca
, 1 year ago
The owner protected this stack trace.

Solution icon of stackoverflow
HikariPool-1 - Connection is not available, request timed out after 42734ms.

Solution icon of stackoverflow
via Stack Overflow by Lucas Soares
, 6 months ago
HikariPool-1 - Connection is not available, request timed out after 37892ms.

Solution icon of stackoverflow
HikariPool-1 - Connection is not available, request timed out after 937894ms.

Solution icon of stackoverflow
HikariPool-1 - Connection is not available, request timed out after 30001ms.

Stack trace

java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30000ms.
	at com.zaxxer.hikari.pool.HikariPool.createTimeoutException(HikariPool.java:548)
	at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:186)
	at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:145)
	at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:83)
	at de.arraying.Arraybot.managers.ManagerSync.addCustomCommand(ManagerSync.java:192)
	at de.arraying.Arraybot.commands.CommandsCommand.onCommand(CommandsCommand.java:100)
	at de.arraying.Arraybot.commands.Command.execute(Command.java:72)
	at de.arraying.Arraybot.listeners.ListenerChat.onGuildMessageReceived(ListenerChat.java:68)
	at net.dv8tion.jda.core.hooks.ListenerAdapter.onEvent(ListenerAdapter.java:299)
	at net.dv8tion.jda.core.hooks.InterfacedEventManager.handle(InterfacedEventManager.java:64)
	at net.dv8tion.jda.core.handle.MessageCreateHandler.handleDefaultMessage(MessageCreateHandler.java:97)
	at net.dv8tion.jda.core.handle.MessageCreateHandler.handleInternally(MessageCreateHandler.java:47)
	at net.dv8tion.jda.core.handle.SocketHandler.handle(SocketHandler.java:38)
	at net.dv8tion.jda.core.requests.WebSocketClient.handleEvent(WebSocketClient.java:688)
	at net.dv8tion.jda.core.requests.WebSocketClient.onTextMessage(WebSocketClient.java:437)
	at com.neovisionaries.ws.client.ListenerManager.callOnTextMessage(ListenerManager.java:352)
	at com.neovisionaries.ws.client.ReadingThread.callOnTextMessage(ReadingThread.java:262)
	at com.neovisionaries.ws.client.ReadingThread.callOnTextMessage(ReadingThread.java:240)
	at com.neovisionaries.ws.client.ReadingThread.handleTextFrame(ReadingThread.java:965)
	at com.neovisionaries.ws.client.ReadingThread.handleFrame(ReadingThread.java:748)
	at com.neovisionaries.ws.client.ReadingThread.main(ReadingThread.java:110)
	at com.neovisionaries.ws.client.ReadingThread.run(ReadingThread.java:66)

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 year ago
4 times, 3 months ago
3 times, 9 months ago
Samebug visitor profile picture
Unknown user
Once, 3 weeks ago
Samebug visitor profile picture
Unknown user
Once, 3 weeks ago
31 more bugmates