Bug 1051487
| Summary: | Multiple failures with Oracle DB schema as configured with installer - value too large for column (re-opened) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | Pavel Macik <pmacik> | ||||||
| Component: | Installer | Assignee: | Julian Coleman <jcoleman> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavel Macik <pmacik> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.0.0 GA | CC: | atangrin, jcoleman, jsedlace, psrna, soa-p-jira | ||||||
| Target Milestone: | CR1 | Keywords: | Regression | ||||||
| Target Release: | 6.0.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | Type: | Bug | |||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Pavel Macik
2014-01-10 12:09:38 UTC
The issue is introduced in 6.0.0.ER8 build Regression - not seen in ER7 This looks like it is probably fixed in the community by: https://github.com/Governance/s-ramp/pull/328 (SRAMP-241) which explicitly configures the Infinispan tables. For the product, an AS CLI script to add this configuration is required. Is this problem unique to Oracle? In MySQL 5.5 seeing this: mysql> describe ispn_bucket_sramp; +---------+------------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +---------+------------------+------+-----+---------+-------+ | id | varchar(500) | NO | PRI | NULL | | | datum | varbinary(60000) | YES | | NULL | | | version | bigint(20) | YES | | NULL | | +---------+------------------+------+-----+---------+-------+ 3 rows in set (0.00 sec) The server configuration contains following cache configuration where the "datum" column is set to 2000 in case of Oracle but 60000 in case of MySQL.
Oracle:
...
<cache-container name="modeshape">
<local-cache name="sramp">
<locking isolation="NONE"/>
<transaction mode="NON_XA"/>
<string-keyed-jdbc-store datasource="java:jboss/datasources/srampDS" passivation="false" purge="false">
<string-keyed-table prefix="ispn_bucket">
<id-column name="id" type="varchar2(500 char)"/>
<data-column name="datum" type="raw(2000)"/>
<timestamp-column name="version" type="number(19,0)"/>
</string-keyed-table>
</string-keyed-jdbc-store>
</local-cache>
</cache-container>
...
MySQL:
...
<cache-container name="modeshape">
<local-cache name="sramp">
<locking isolation="NONE"/>
<transaction mode="NON_XA"/>
<string-keyed-jdbc-store datasource="java:jboss/datasources/srampDS" passivation="false" purge="false">
<string-keyed-table prefix="ispn_bucket">
<id-column name="id" type="VARCHAR(500)"/>
<data-column name="datum" type="VARBINARY(60000)"/>
<timestamp-column name="version" type="BIGINT"/>
</string-keyed-table>
</string-keyed-jdbc-store>
</local-cache>
</cache-container>
...
Fixed with commit 25a440ddfb9c28a5d38bc4b0de221d4d4c56cac0 to ip (6.0.0-fsw branch): BZ-1051487 Replace raw(2000) with blob, as we store data larger than 2000 bytes. I don't see the original issues reported, but maybe something new was introduced? This is my log: javax.persistence.PersistenceException: [PersistenceUnit: gadget-core] Unable to build EntityManagerFactory at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:103) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] at org.jboss.threads.JBossThread.run(JBossThread.java:122) Caused by: javax.persistence.PersistenceException: [PersistenceUnit: gadget-core] Unable to build EntityManagerFactory at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:930) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:904) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:92) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:200) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$600(PersistenceUnitServiceImpl.java:57) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:99) ... 4 more Caused by: org.hibernate.HibernateException: Missing sequence or table: hibernate_sequence at org.hibernate.cfg.Configuration.validateSchema(Configuration.java:1289) at org.hibernate.tool.hbm2ddl.SchemaValidator.validate(SchemaValidator.java:155) at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:508) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1762) at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:94) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:920) ... 9 more Created attachment 850953 [details]
another-server-log.txt
I can't reproduce this. The hibernate_sequence is created correctly, and the server starts without errors. (tested using oracle11gR2 via DBALLO01) I can't reproduce either. I'll reopen or file another bug if seen in the future. |