Yes, ehcache is included in Portal, just a previous version.
We are testing with ehcache 1.2, per Emmanuel's comment.
If it works, we can document the workaround for now, and possibly
release Portal 2.2.1.SP1 shortly after 4.0.4?
-----Original Message-----
From: Adrian Brock
Sent: Friday, May 12, 2006 1:42 PM
To: Ryan Campbell
Cc: Steve Ebersole; Julien Viet; Roy Russo;
jboss-development@lists.sourceforge.net; QA
Subject: Re: FW: jboss-4.0.4 portal-2.2 issue
Actually (2) is not an option because it looks like
Portal/Hibernate in 2.2 is expecting a different/incompatible
version of EhCache?
On Fri, 2006-05-12 at 20:34 +0200, Adrian Brock wrote:
Why isn't portal using JBoss's hibernate-int session factory?
The solutions are:
1) JBoss Portal's session factory is configured to use JBoss Cache
not EhCache
2) JBossAS's installer should include EhCache as an optional
part of the install
3) JBoss Portal includes EhCache itself (since it is not a part of the
JBossAS install)
On a related issue, why does Portal have its own transaction
demarcation? :-)
org.jboss.portal.common.transaction.Transactions.notSupported(Transactio
ns.java:245)
Looks like too much "not invented here" in the Portal code
that JBossAS can do nothing about.
On Fri, 2006-05-12 at 13:05 -0500, Ryan Campbell wrote:
Portal 2.2.1 fails to deploy on 4.0.4. Is this a bug in Hibernate?
______________________________________________________________________
From:[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of
Rali Genova
Sent: Friday, May 12, 2006 12:00 PM
To: Ryan Campbell
Subject: jboss-4.0.4 portal-2.2 issue
Attached is the server log, but here is the relevant exception. I
was
using the Hypersonic DB and then MySQL, repeats with both. The AS is
built from source, I am working on verifying this with the installer
that Scott created as well.
2006-05-12 11:22:16,353 DEBUG
[org.hibernate.impl.SessionFactoryImpl]
instantiating session factory with properties:...(I took those off)
2006-05-12 11:22:16,363 WARN [org.jboss.system.ServiceController]
Problem starting service portal:service=Hibernate
java.lang.IllegalAccessError: tried to access method
net.sf.ehcache.CacheManager.<init>()V from class
org.hibernate.cache.EhCacheProvider
at
org.hibernate.cache.EhCacheProvider.start(EhCacheProvider.java:124)
at
org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:180
)
at
org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1
213)
at org.jboss.portal.core.hibernate.SessionFactoryBinder
$3.run(SessionFactoryBinder.java:509)
at
org.jboss.portal.common.transaction.Transactions.apply(Transactions.java
:199)
at
org.jboss.portal.common.transaction.Transactions.notSupported(Transactio
ns.java:245)
at
org.jboss.portal.core.hibernate.SessionFactoryBinder.createSessionFactor
y(SessionFactoryBinder.java:505)
at
org.jboss.portal.core.hibernate.SessionFactoryBinder.startService(Sessio
nFactoryBinder.java:291)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupp
ort.java:289)
at
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
at
org.jboss.portal.common.system.AbstractJBossService.start(AbstractJBossS
ervice.java:86)
at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.
java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.
java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBea
nOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav
a:264)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController
$ServiceProxy.invoke(ServiceController.java:995)
at $Proxy0.start(Unknown Source)
--
Bug? That's not a bug, that's a feature.
