Repository navigation
bolt-socket-mode establishes a connection before a SocketModeApp#start()/startAsync() method call #937
Description
The following code has not yet started the socketModeApp.
var app = new App(AppConfig.builder().singleTeamBotToken(System.getenv("SLACK_BOT_TOKEN")).build());
var socketModeApp = new SocketModeApp(System.getenv("SLACK_APP_TOKEN"), app);
// socketModeApp.start();
Thread.sleep(Long.MAX_VALUE);However, the log outputs says:
2022-02-18 07:00:58,834 INFO [socket-mode-session-monitor-worker-39] com.slack.api.socket_mode.SocketModeClient The current session is no longer active. Going to reconnect to the Socket Mode server.
2022-02-18 07:00:59,756 INFO [Grizzly(1)] com.slack.api.socket_mode.SocketModeClient New session is open (session id: b3a24a85-3505-4fc5-93ea-7db775496406)
This is due to the default behavior of the underlying SocketModeClient. However, this is an unexpected behavior for bolt-java users and that should be improved in future releases.
Reproducible in:
Any versions
The Slack SDK version
v1.19.0
Java Runtime version
any
OS info
any
Steps to reproduce:
See the description
Activity
Fix slackapi#937 bolt-socket-mode establishes a connection before a S…
Fix slackapi#937 bolt-socket-mode establishes a connection before a S…
Fix #937 bolt-socket-mode establishes a connection before a SocketMod…