Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1154655

Summary: Using new database logging extension, getting error that indicates column isn't long enough
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Andrej Smigala <asmigala>
Component: TeiidAssignee: Van Halbert <vhalbert>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: atangrin, dlesage, jstastny, vhalbert
Target Milestone: ER4Keywords: QA-Closed
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
When running an XA transaction, an org.h2.jdbc.JdbcSQLException error was logged in the console whether the actual transaction succeeded or not. This was because the column size was not large enough. It has now been increased to 256. As a result, these exceptions are no longer recorded in the log.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-10 08:55:06 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:
Embargoed:

Description Andrej Smigala 2014-10-20 12:44:43 UTC 
When running an XA transaction, the following error is logged in the console (whether the actual transaction succeeds or not):

org.h2.jdbc.JdbcSQLException: Value too long for column "TRANSACTIONID VARCHAR(100)": "'TransactionImple < ac, BasicAction: 0:ffff0a221e8b:29f70065:54450202:1a status: ActionStatus.RUNNING >' (102)"; SQL statement:
insert into commandlog (applicationname, executionid, modelname, principal, queryplan, requestid, rowcount, sessionid, sourcecommand, sourcerequestid, sqlcmd, eventtype, logtim
e, transactionid, translatorname, vdbname, vdbversion, id) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [22001-168]


This is with XA transaction involving Oracle 11g and DB2 8.1 datasources
Comment 2 JBoss JIRA Server 2014-10-20 13:34:21 UTC 
Ramesh Reddy <rareddy> updated the status of jira TEIID-2976 to Resolved
Comment 3 JBoss JIRA Server 2015-10-08 14:39:56 UTC 
Steven Hawkins <shawkins> updated the status of jira TEIID-2976 to Closed