| Summary: | ModeShape unit tests are failing with DB2 9.7 (DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null, DRIVER=4.9.78 ) | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Petr Široký <psiroky> |
| Component: | Modeshape | Assignee: | Van Halbert <vhalbert> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.1.0.ER4 | CC: | lcarlon |
| Target Milestone: | --- | ||
| Target Release: | BRMS 5.2.0.GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/BRMS-469 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
brms standalone 5.1.0 ER4
DB2 9.7
|
|
| Last Closed: | 2011-07-18 20:21:45 UTC | 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
Petr Široký
2010-11-29 12:40:41 UTC
Link: Added: This issue is related to MODE-1024 Link: Removed: This issue is related to MODE-1024 Link: Added: This issue is a dependency of MODE-1015 Link: Added: This issue is related to SOA-2570 Triaged by BRMS PM team for 5.2. ModeShape committed a fix to 2.5.0 GA: project comment: As noted in the accompanying JIRA, the root cause of this issue is that DB2 (and Derby) use a binary data type for JPA LOBs with a maximum size of 255 unless a different size is explicitly provided. Most, if not all, non-trivial uses of ModeShape require a larger value for the two LOB fields in the JPA Simple model. This patch addresses the problem in several ways. First, it provides larger default values for the two LOB columns (MODE_SIMPLE_NODE.DATA and MODE_LARGE_VALUES.DATA) that ModeShape uses. Second, it adds comments in the model classes for the JPA entities that contain these fields. Third, it adds a detailed note in the JPA Connector of the Reference Guide explaining how to address these issues in a production environment. Fourth, it modifies the DDL generator utility to output a warning when DDL is generated for the DB2 or Derby dialects. |