Bug 880544

Summary:	Declare InnoDB as default MySQL engine in schema generation scripts
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Martin Weiler <mweiler>
Component:	JBossESB	Assignee:	Nobody <nobody>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.3.0 GA	CC:	soa-p-jira
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:27:02 UTC	Type:	Task
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Weiler 2012-11-27 09:50:49 UTC

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.

Comment 2 Red Hat Bugzilla 2025-02-10 03:27:02 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.