DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Please enter at least three characters to search
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Zones

Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Because the DevOps movement has redefined engineering responsibilities, SREs now have to become stewards of observability strategy.

Apache Cassandra combines the benefits of major NoSQL databases to support data management needs not covered by traditional RDBMS vendors.

The software you build is only as secure as the code that powers it. Learn how malicious code creeps into your software supply chain.

Generative AI has transformed nearly every industry. How can you leverage GenAI to improve your productivity and efficiency?

Related

  • Resolving Parameter Sensitivity With Parameter Sensitive Plan Optimization in SQL Server 2022
  • Comparing Managed Postgres Options on The Azure Marketplace
  • Useful System Table Queries in Relational Databases
  • Introducing Graph Concepts in Java With Eclipse JNoSQL

Trending

  • The Ultimate Guide to Code Formatting: Prettier vs ESLint vs Biome
  • How Large Tech Companies Architect Resilient Systems for Millions of Users
  • Navigating Double and Triple Extortion Tactics
  • Simplifying Multi-LLM Integration With KubeMQ
  1. DZone
  2. Data Engineering
  3. Databases
  4. Increase the Default Process Variable Size in jBPM

Increase the Default Process Variable Size in jBPM

In this article, see how to increase the default process variable size in jBPM.

By 
Amit Nijhawan user avatar
Amit Nijhawan
·
Dec. 09, 20 · Tutorial
Likes (3)
Comment
Save
Tweet
Share
4.4K Views

Join the DZone community and get the full member experience.

Join For Free

Process variables in jBPM are limited to 255 characters by default. The number of characters in turn are also dependent on the character set that is being followed. So, it is always better to have an option to increase the default value.

This article is just an extension of the solution provided in the above link; simplifying things a little more for beginners.

To increase the variable size, two configuration changes are needed to be one.

Change the Column Data Type in jBPM Database

Variable information is stored in “VariableInstanceLog” table in jBPM database. Find the table in the jBPM schema and increase the VARCHAR size of the column “value” to the desired size (lets say 20000)

Ask jBPM to Use the New Size

Even if we increase the size of the value column in the database, jBPM will still truncate any value bigger than 255 before saving it to the database. We need to set the following system property to let jBPM know the new size.

Java
 




x


 
1
-Dorg.jbpm.var.log.length=20000


where 20000 is the desired size of the variable value.

As jBPM includes ant script to start the jboss (now wildfly) server, we can configure the system property in the standalone.xml file. ant task will read this file and set the system properties while starting the server.

To do this, open standalone.xml file located in the jBPM configuration directory and open it with a text editor. Look for target by name and add the following line under the exec tag along with the other properties.       

XML
xxxxxxxxxx
1
 
1
 <property name="org.jbpm.var.log.length" value="20000"/>


The final exec tag should look like the following under standalone.xml target.

XML
xxxxxxxxxx
1
 
1
<system-properties>
2
3
        <property name="org.jbpm.var.log.length" value="20000"/>
4
5
    </system-properties
Database

Opinions expressed by DZone contributors are their own.

Related

  • Resolving Parameter Sensitivity With Parameter Sensitive Plan Optimization in SQL Server 2022
  • Comparing Managed Postgres Options on The Azure Marketplace
  • Useful System Table Queries in Relational Databases
  • Introducing Graph Concepts in Java With Eclipse JNoSQL

Partner Resources

×

Comments
Oops! Something Went Wrong

The likes didn't load as expected. Please refresh the page and try again.

ABOUT US

  • About DZone
  • Support and feedback
  • Community research
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • support@dzone.com

Let's be friends:

Likes
There are no likes...yet! 👀
Be the first to like this post!
It looks like you're not logged in.
Sign in to see who liked this post!