-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix #1409 Socket Mode: Slow message consumption when listeners do not immediately return ack() #1411
Merged
seratch
merged 1 commit into
slackapi:main
from
seratch:issue-1409-faster-bolt-socket-mode
Jan 8, 2025
Merged
Fix #1409 Socket Mode: Slow message consumption when listeners do not immediately return ack() #1411
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
40 changes: 40 additions & 0 deletions
40
bolt-jakarta-socket-mode/src/test/java/samples/ConcurrencyTestApp.java
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
package samples; | ||
|
||
import com.slack.api.bolt.App; | ||
import com.slack.api.bolt.AppConfig; | ||
import com.slack.api.bolt.jakarta_socket_mode.SocketModeApp; | ||
import com.slack.api.model.event.MessageChangedEvent; | ||
import com.slack.api.model.event.MessageDeletedEvent; | ||
import com.slack.api.model.event.MessageEvent; | ||
import config.Constants; | ||
|
||
public class ConcurrencyTestApp { | ||
|
||
public static void main(String[] args) throws Exception { | ||
App app = new App(AppConfig.builder() | ||
.singleTeamBotToken(System.getenv(Constants.SLACK_SDK_TEST_SOCKET_MODE_BOT_TOKEN)) | ||
.build()); | ||
|
||
app.event(MessageEvent.class, (req, ctx) -> { | ||
// Without concurrency option, this time-consuming task slows the whole message processing mechanism down | ||
try { | ||
Thread.sleep(1000L); | ||
} catch (InterruptedException e) { | ||
throw new RuntimeException(e); | ||
} | ||
ctx.asyncClient().reactionsAdd(r -> r | ||
.channel(req.getEvent().getChannel()) | ||
.name("eyes") | ||
.timestamp(req.getEvent().getTs()) | ||
); | ||
return ctx.ack(); | ||
}); | ||
app.event(MessageChangedEvent.class, (req, ctx) -> ctx.ack()); | ||
app.event(MessageDeletedEvent.class, (req, ctx) -> ctx.ack()); | ||
|
||
String appToken = System.getenv(Constants.SLACK_SDK_TEST_SOCKET_MODE_APP_TOKEN); | ||
// SocketModeApp socketModeApp = new SocketModeApp(appToken, app); | ||
SocketModeApp socketModeApp = new SocketModeApp(appToken, app, 10); | ||
socketModeApp.start(); | ||
} | ||
} |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would there be any shortcomings from always using an
executorService
where the defaultconcurrency = 1
Other then maintaining backwards compatible behavior is there a use case where
is preferred over
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the suggestion! Indeed, this approach is also an option, but for now I'd like to avoid moving the runBoltApp to a different thread, even though it's a slight difference. When we make the concurrent mode the default, simplifying the code as you suggest is worth considering.