i'm not 100% sure that this is the right place to come with this issue - if not, i would appreciate someone pointing me in the right direction. i'm starting here because i'm apparently having an problem with Hibernate and the EhCache distribution included with it.

to start with, i am using JBoss 4.0.3SP1 and Hibernate 3.1.1. i am attempting to use 2 .har files as part of my application, for purposes of encapsulation and because my application needs to use two different data sources. i am using EhCache as the second-level cache in both cases.

each .har file i am using is properly formed and deploys without error as a distinctly named service in my JBoss instance. each .har file also includes a properly formed ehcache.xml configuration file, again, deploying without a problem. i can use each instance from my application without issue, and the second-level cache seems to operate smoothly in each case.

the problem i am having is happening when i try to deploy both .har files simultaneously. the first .har service i deploy deploys without incident. however, when i attempt to deploy the second service while the first service is running, i get a series of EhCacheProvider warnings like so:



it doesn't seem to matter which one i deploy first - the pattern remains the same. as long as one hibernate service is deployed, i get warnings like this when i try to deploy the second service. the reason i suspect a bug here is because each service deploys on its own without error. debug logs don't seem to provide me with any more illumination, although i'd be happy to post the relevant snippets if anyone were so interested.

since these are just warnings, ultimately both services successfully deploy simultaneously - i.e., if deployed simultaneously i can use them both without apparent issue, second-level cache and all, so this isn't really a show-stopper right now. but given the nature of some of the operations i'm trying to do, i'm going to ultimately need to be able to tune the cache for each service.

can anybody tell me what is happening here?

bump - am i the only person to encounter this? or should i seek a solution elsewhere?