Loading...

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XML

Word

Printable

Steps to Reproduce:

Hide

1. Switch the SOA Database implementation to MSSQL, Postgres or Sybase.

2. Deploy the attached example project.

3. Send a message with a large 4000+ character value in <x></x>.

Show
1. Switch the SOA Database implementation to MSSQL, Postgres or Sybase. 2. Deploy the attached example project. 3. Send a message with a large 4000+ character value in <x></x>.
Workaround Description:

Hide

Change the datatype of the MESSAGE field to 'TEXT' in bpel-sql/<database>.sql

Show
Change the datatype of the MESSAGE field to 'TEXT' in bpel-sql/<database>.sql
Bugzilla References:
https://bugzilla.redhat.com/show_bug.cgi?id=804866

For SQLServer the BPEL_FAULT table has a MESSAGE datatype of VARCHAR(4000). This has proven inadequate in at least one case.

We suggest changing the datatype of this field to varchar(max), TEXT is deprecated as of MSSQL 2005

It also appears to be an issue for Postgres, and Sybase.

I have attached a stacktrace for SQLServer

The MESSAGE field from table BPEL_FAULT table is too small, for at least SQLServer