Folks,
Is a default value of 2000ms reasonable for the JMS clientReceiveTimeout? For even moderately long-lived requests, this seems *way* too tight to me. A timeout in the ballpark of 2s seems more appropriate for localhost demo-type situation where you want the user to get rapid feedback if they've set things up wrong, or for tests where again you want things to fail fast. But if that's the motivation, couldn't the demos/tests just configure an appropriately tight timeout, but leave much more slack in the default? Cheers, Eoghan
