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.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.