Portal 2.2.1RC1 and Oracle9i Issue

[dmiklancic]

I downloaded the bundled 2.2.1RC1. With no changes, the portal works fine. When the portal-hsqldb-ds.xml is replaced with portal-oracle-ds.xml all works the first run. Subsequent runs yield an error deploying the CMS service:

--- MBeans waiting for other MBeans ---
ObjectName: portal:service=CMS
 State: FAILED
 Reason: org.hibernate.TransactionException: Transaction not successfully started
 I Depend On:
 jboss.jca:service=DataSourceBinding,name=PortalDS
 portal:service=JAASLoginModule
 Depends On Me:
 portal:mapper=CMSObject

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: portal:service=CMS
 State: FAILED
 Reason: org.hibernate.TransactionException: Transaction not successfully started
 I Depend On:
 jboss.jca:service=DataSourceBinding,name=PortalDS
 portal:service=JAASLoginModule
 Depends On Me:
 portal:mapper=CMSObject

Earlier in the log:

2006-01-19 13:07:03,840 DEBUG [org.jboss.portal.cms.impl.jcr.JCRCMS] Starting failed portal:service=CMS
org.hibernate.TransactionException: Transaction not successfully started
 at org.hibernate.transaction.JDBCTransaction.rollback(JDBCTransaction.java:149)
 at org.jboss.portal.cms.hibernate.HibernateStore.getInputStream(HibernateStore.java:1069)
 at org.apache.jackrabbit.core.fs.BasedFileSystem.getInputStream(BasedFileSystem.java:128)
 at org.apache.jackrabbit.core.fs.FileSystemResource.getInputStream(FileSystemResource.java:147)
 at org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.loadCustomNodeTypeDefs(NodeTypeRegistry.java:1504)
 at org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.<init>(NodeTypeRegistry.java:196)
 at org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.create(NodeTypeRegistry.java:128)
 at org.apache.jackrabbit.core.RepositoryImpl.createNodeTypeRegistry(RepositoryImpl.java:411)
 at org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:192)
 at org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:424)
 at org.apache.jackrabbit.core.jndi.BindableRepository.init(BindableRepository.java:124)
 at org.apache.jackrabbit.core.jndi.BindableRepository.create(BindableRepository.java:110)
 at org.apache.jackrabbit.core.jndi.RegistryHelper.registerRepository(RegistryHelper.java:57)
 at org.jboss.portal.cms.util.RepositoryUtil.registerRepository(RepositoryUtil.java:82)
 at org.jboss.portal.cms.impl.jcr.JCRCMS.startService(JCRCMS.java:235)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274)
 at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:181)
 at org.jboss.portal.common.system.AbstractJBossService.start(AbstractJBossService.java:86) ....

What would cause a subsequent run to generate such an error?

If one drops the database tables and restarts, everything works fine again the first run. If one stops JBoss and restarts, all subsequent runs generate the above error.

I have been struggling with the Portal 2.2.x and Oracle for a couple months now. JIRA reports the Oracle issue has been resolved. Yet, I am unable to get a stable installation. If someone has been successful, please clue me in. If not, I am willing to invest some time if someone can point me in the right direction.

[roy.russo]

I remember seeing this problem with MS SQL before the 2.2Final release. I will look at Oracle again tonight and post here with my findings.

[roy.russo]

I have tested again and its working..

JBoss AS 4.0.3SP1
RDBMS: Oracle, version: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Beta
driver: Oracle JDBC driver, version: 10.2.0.1.0
Using dialect: org.hibernate.dialect.Oracle9Dialect

Start/restart works fine.

[dmiklancic]

Thanks for your feedback. I upgraded the Oracle JDBC driver to 10.2.0.1.0. Problem solved.

It's interesting that I use a 9i database, an Oracle9Dialect, but need a 10g JDBC driver. Perhaps it has something to do with Java 1.5 or with changes in the handling of BLOB datatypes used by CMS.

[roy.russo]

The Blob handling wasnt changed in this release... the change was something simple, trying to set null on a column that didn't allow it. Funny how all the other databases didn't seem to mind.

It could be the way the driver deals with Blobs, in fact.