Actually any command that would call back to the CommandContext for command execution would suffer from this problem. The CommandExecutor has a single thread executorService, it should have a pool of multiple threads.