[
http://jira.jboss.com/jira/browse/JBESB-1435?page=comments#action_12394485 ]
Kevin Conner commented on JBESB-1435:
-------------------------------------
Tom, the logs show that the issue is with the definition of the JBPM_VARIABLEINSTANCE
table in that it restricts STRINGVALUE_ to 255 characters.
Here is the definition from the db/jbpm.jpdl.mysql.sql file.
create table JBPM_VARIABLEINSTANCE (ID_ bigint not null auto_increment, CLASS_ char(1) not
null, VERSION_ integer not null, NAME_ varchar(255), CONVERTER_ char(1), TOKEN_ bigint,
TOKENVARIABLEMAP_ bigint, PROCESSINSTANCE_ bigint, BYTEARRAYVALUE_ bigint, DATEVALUE_
datetime, DOUBLEVALUE_ double precision, LONGIDCLASS_ varchar(255), LONGVALUE_ bigint,
STRINGIDCLASS_ varchar(255), STRINGVALUE_ varchar(255), TASKINSTANCE_ bigint, primary key
(ID_)) type=InnoDB
This seems to be different from the hibernate settings.
Message longer than 255 chrs cannot be passed to jBPM
-----------------------------------------------------
Key: JBESB-1435
URL:
http://jira.jboss.com/jira/browse/JBESB-1435
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow, Rosetta
Affects Versions: 4.2.1 CP1
Reporter: Jiri Pechanec
Assigned To: Kurt Stam
Priority: Blocker
Fix For: 4.2.1 CP1
Attachments: server.mysql.log.gz, server.oracle10g.log.gz
If message is String it and passed to jBPM then it is stored in variable instance that is
limited by 255 chars length.
This should either be fixed or clearly stated in the dosumentation and removed from
quickstarts not to support antippaterns.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira