Bug 880544 – Declare InnoDB as default MySQL engine in schema generation scripts

Bug 880544 - Declare InnoDB as default MySQL engine in schema generation scripts

Summary:	Declare InnoDB as default MySQL engine in schema generation scripts

Status:	NEW

Aliases:	None

Product:	JBoss Enterprise SOA Platform 5
Classification:	JBoss
Component:	JBossESB (Show other bugs)
Sub Component:
Version:	5.3.0 GA
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	kconner
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2012-11-27 04:50 EST by Martin Weiler
Modified:	2012-11-27 08:39 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	Task
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Martin Weiler 2012-11-27 04:50:49 EST

Description of problem:
If MySQL is configured with MYISAM as default engine, the tables in the SOA-P schema will be mixed, as not all components explicitly declare the engine type in the schema creation scripts:

* jBPM -> InnoDB
* BPEL -> InnoDB
* jUDDI -> MYISAM (not defined)

In addition, jUDDI won't deploy as at least one of the tables is hitting the MYISAM restriction of 1000 bytes for keys:

com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 1000 bytes

All MySQL schema generation scripts inside the platform should declare the engine type.

Note You need to log in before you can comment on or make changes to this bug.