more detail please see:
http://www.jboss.com/index.html?module= ... ic&t=78121

I post the topic in jboss portal user forum.
but nobody give an answer.

Now,After I deploy the .ear to jboss(which runing a jboss portal 2.21RC2),The exception will be thrown.
I have to restart the server.

About this problem,I think,mostly it's a hibernate 3 bug.
So I turn to here for help.

Thanks in advance.

any one help?

Your link is truncated, could you edit it ?

http://www.jboss.com/index.html?module= ... ic&t=78121

the url。

Sorry 。

thanks for your reply。

I'd try a different cache provider. EhCache is a static cache. This can cause issues in a shared environment.

is Jboss tree cache situable?

maybe it is more reliable

As steve stated, EHCache is static so if two caches (from differents applications usually) have the same name, the second cache will not start.

I've already experienced this problem using Hibernate inside JBoss, in my case it was because I deployed twice the same app.
Maybe you can solve your problem by creating your own cache region names so they do not overlap with the regions used by Jboss Portal.

Jboss tree cache would be a solution to but if you don't need clustering or transactionnal cache, it's a bit overengineered

you mean,I give different name of the Cache Name when using ehcache?
That will be the solution?

thanks
.

I will try it after work.

I think the issue is about two Session Factories using trying to use a cache with the same region name (the query cache). So Query.setCacheRegion() would solve the problem.

Thanks for your help.

I solve this problem by using Oscache instead of ehcache.

<!-- Second-level caching -->
<attribute name="SecondLevelCacheEnabled">true</attribute>
<attribute name="CacheProviderClass">org.hibernate.cache.OSCacheProvider</attribute>
<attribute name="QueryCacheEnabled">true</attribute>