java.sql.SQLTransientConnectionException

HikariPool-1 - Connection is not available, request timed out after 30000ms.


Samebug tips1

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.

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.


Solutions on the web130

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

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

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

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

Solution icon of liferay
via Liferay Issues by Brett Swaim, 5 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
HikariPool-1 - Connection is not available, request timed out after 30000ms.

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

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

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

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, 1 month ago
3 times, 7 months ago
Samebug visitor profile picture
Unknown user
Once, 3 weeks ago
Samebug visitor profile picture
Unknown user
Once, 3 weeks ago
27 more bugmates