[jboss-user] [JBoss Portal] - deploy of 2.4.1 SP1 portal over 2.4.0 DB
hello,
in our current configuration we use JBoss AS 4.0.5 GA and Portal 2.4.0 GA. Portal DB is
persisted inside Oracle 10g.
We tried to upgrade Portal up to 2.4.1 SP1 version. We pointed new installation with new
Portal into same DB instance 2.4 used. And on Server start up we get following exception:
007-11-04 18:29:06,468 ERROR
[org.jboss.portal.cms.hibernate.state.JBossCachePersistenceManager] failed to read node
state from cache: deadbeef-face-babe-cafe-babecafebabe
java.io.UTFDataFormatException
at java.io.DataInputStream.readUTF(DataInputStream.java:674)
at java.io.DataInputStream.readUTF(DataInputStream.java:610)
at org.apache.jackrabbit.core.state.util.Serializer.deserialize(Serializer.java:123)
at
org.jboss.portal.cms.hibernate.state.JBossCachePersistenceManager.load(JBossCachePersistenceManager.java:477)
at
org.apache.jackrabbit.core.state.SharedItemStateManager.loadItemState(SharedItemStateManager.java:857)
at
org.apache.jackrabbit.core.state.SharedItemStateManager.getNonVirtualItemState(SharedItemStateManager.java:784)
at
org.apache.jackrabbit.core.state.SharedItemStateManager.getItemState(SharedItemStateManager.java:207)
at
org.apache.jackrabbit.core.state.LocalItemStateManager.getNodeState(LocalItemStateManager.java:86)
at
org.apache.jackrabbit.core.state.LocalItemStateManager.getItemState(LocalItemStateManager.java:141)
at org.apache.jackrabbit.core.version.VersionManagerImpl.(VersionManagerImpl.java:160)
at
org.apache.jackrabbit.core.RepositoryImpl.createVersionManager(RepositoryImpl.java:291)
at org.apache.jackrabbit.core.RepositoryImpl.(RepositoryImpl.java:234)
at org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:483)
at
org.jboss.portal.cms.impl.jcr.jackrabbit.JackrabbitJCRService.start(JackrabbitJCRService.java:103)
at org.jboss.portal.cms.impl.jcr.JCRCMS.startJCR(JCRCMS.java:206)
at org.jboss.portal.cms.impl.jcr.JCRCMS.startService(JCRCMS.java:176)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
at
org.jboss.portal.common.system.AbstractJBossService.start(AbstractJBossService.java:73)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
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)
If needed i can provide a full stack trace. it is very important for us to preserve the
original portal DB from version 2.4 when running 2.4.1 SP1.
We do not experience problems when 2.4.1 SP1 pointed into empty DB schema.
Please advise.
Dmitry.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101602#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...