[jbpm-issues] [JBoss JIRA] Reopened: (JBPM-701) Do not truncate long messages/exceptions

[Thomas Diesler (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBPM-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler reopened JBPM-701:
---------------------------------



Martin sais,

FYI, I've asked Goldman which issues they are still facing with getting jBPM to work on Sybase, and this was their reply:

"All the JIRA items [see below] are necessary. The database version we are using are Sybase 12.5 and UDB version is 9.1.5. We are using jconn2.jar and jconn3.jar for Sybase, db2jcc.jar for UDB."

Sybase related JIRA items:
1. Usage of 'CLOB' columns instead of 'VARCHAR(4000)' [JBPM-701]
2. Usage of 'BINARY NOT NULL' columns instead of 'VARBINARY' [JBPM-702]
3. Avoid truncation of large context data by using the JCONNECT_VERSION=6 option [JBPM-703]
4. Increase the default page size [JBPM-1176] 

> Do not truncate long messages/exceptions
> ----------------------------------------
>
>                 Key: JBPM-701
>                 URL: https://jira.jboss.org/jira/browse/JBPM-701
>             Project: JBoss jBPM
>          Issue Type: Sub-task
>         Environment: Sybase/DB2
>            Reporter: Ryan Campbell
>            Assignee: Tom Baeyens
>         Attachments: sybase.build.xml
>
>
> For sybase, a "text" column should be used instead of the current varchar(4000)
> This will prevent the truncation of stack traces.
> Similarly, a CLOB or equivalent should be used on DB2.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira