Bug 1037571

Summary: BPEL riftsaw-ode - IBM DB2 SQL schema fails to load. Column (BPEL_FAULT.MESSAGE) larger than allowable value.
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Steve Johnson <stejohns>
Component: BPEL IntegrationAssignee: Steve Johnson <stejohns>
Status: CLOSED CURRENTRELEASE QA Contact: lvaskova
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.0 GACC: atangrin, ncross, soa-p-jira
Target Milestone: ER7   
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:

Description Steve Johnson 2013-12-03 11:52:35 UTC
Description of problem:

The IBM DB2 generated SQL for riftsaw-ode fails due to column size being larger than column max allowable value.

See BPEL_FAULT.MESSAGE mapped from class dao-jpa/src/main/java/org/apache/ode/dao/jpa/bpel/FaultDAOImpl.java

The value is set to 102400 and the largest acceptable column size for varchar type is 32 672 bytes long.

The solution is to apply @Lob annotation and map the java attribute to clob type.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Steve Johnson 2013-12-03 16:31:03 UTC
IBM DB2 now maps this column to "clob" type that supports 102400 bytes.

Patch applied at productisation build time and generated SQL ran into db2 database instance.  Needs to be pushed back to community team at the next appropriate point.

Comment 2 lvaskova 2013-12-18 12:36:03 UTC
Verified on ER7

Comment 3 JBoss JIRA Server 2014-05-12 09:06:10 UTC
Gary Brown <gary> updated the status of jira RIFTSAW-550 to Resolved