Details
-
Bug
-
Resolution: Done
-
Major
-
7.1.0.Final
-
None
Description
This is easy to reproduce: start a CacheManager which has a Transport configured with a non-existent resource name for the JGroups configuration.
Would be great to have a better error message.