JDA repeading every action endlessly
See original GitHub issueWhen i try to execue a command (such as send direct message ONE time), it will send 8 messages. This issue began in 3.2.0_XXX and is still a thing. It’s very annoying, since i have to use outdated versions (3.1.0_XXX)
Code i use for sending direct messages is:
PrivateChannel dm = targetUser.openPrivateChannel().complete();
dm.sendMessage("Message content").queue();
dm.close();
Issue Analytics
- State:
- Created 6 years ago
- Comments:18 (8 by maintainers)
Top Results From Across the Web
java - How do I schedule a task to run at periodic intervals?
Fixed-rate execution is appropriate for recurring activities that are sensitive to absolute time, such as ringing a chime every hour on the hour ......
Read more >JDA MMS Upgradation | Integrative Systems
Integrative Systems JDA MMS implementation, support, and integration, services can help businesses leverage the capabilities of system effectively.
Read more >Strange Problem in Windows 2008 Task Scheduler
Repeat task every 15 minutes indefinitely. I'm not sure why this fixed the problem, but it did. I hope this works for someone...
Read more >Why did it take so long for the FAA – JDA Journal
FAA's Slow Part 23 Rulemaking Speed. Revision of Airworthiness Standards for Normal, Utility, Acrobatic, and Commuter Category Airplanes.
Read more >Digital Supply Chain For Dummies® JDA Software ... - Stample
JDA and the JDA logo are trademarks or registered trademarks of JDA Software Group, Inc. All other trademarks are the property of their...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I really don’t think this is a JDA problem. A common mistake is that your bot listens to it’s own message or that you just have multiple instances of your bot running.
or the event listener added multiple times