https://bz.apache.org/bugzilla/show_bug.cgi?id=58506
Gordon Daugherty <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- OS| |All CC| |[email protected] --- Comment #1 from Gordon Daugherty <[email protected]> --- Here's an alternative solution that preserves the configuration interface but significantly changes the test's behavior: When no "JNDI name Receive queue" is provided create a single temporary queue and internally use that queue name for that field. This way the execution behavior would always be asynchronous with requests going out at a consistent rate regardless of how fast the replies are coming back. This has the advantage of avoiding the "Coordinated Omission" problem (search "Gil Tene Coordinated Omission" if you're not familiar with that concept). This solution keeps the configuration interface simple. The downside is that people that were using the TemporaryQueueExecutor approach would see new behavior when they upgrade; these more-accurate results are likely to show worse peformance numbers so we'd get some questions when people do that upgrade. -- You are receiving this mail because: You are the assignee for the bug.
