Saving jBPM process variables exceeding 4000 characters fails in SOA-P

Solution Verified - Updated -

Issue

Using jBPM to orchestrate services in the SOA Platform, we ran into a problem related to jBPM variables. The message body we put into a jBPM variable is about 6k. But the size of the variable instance in the jbpm-jpdl.jar (org.jbpm.context.exe.variableinstance.StringInstance.hbm.xml) and inside the corresponding create table statements (in jbpm-sql) is set to varchar2(4000). As a result, the following exception is thrown:

 [JDBCExceptionReporter] Value too long for column STRINGVALUE_:

This means that orchestrating XML documents over 4000 characters is not possible. How can we work around this limitation?

Environment

  • JBoss Enterprise SOA Platform (SOA-P)

    • 4.3
    • 5.0

  • jBPM

    • 3.2.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.