Just found this shocker:
private static final ExistingSubscriptionPreventsExclusive
EXISTING_SUBSCRIPTION =
new ExistingSubscriptionPreventsExclusive();Looks like a really bad idea as doesn't seem thread safe, as mutliple threads raising these exceptions will overwrite each others stacks. I not even sure that throw is thread safe in that respect? This could also cause memory leaks, because objects refed by the static stack dump won't be garbage collected. Rupert
