Bug 778031 (SOA-554) - Document that Sybase cuts the payload according to pagesize by deafult
Summary: Document that Sybase cuts the payload according to pagesize by deafult
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-554
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation, JBoss Messaging
Version: 4.2 CP01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CP02
Assignee: Joshua Wulf
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-22 12:48 UTC by Jiri Pechanec
Modified: 2014-10-19 23:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-10 09:28:39 UTC
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-554 0 None None None Never

Description Jiri Pechanec 2008-05-22 12:48:51 UTC
Date of First Response: 2008-05-22 11:34:51
project_key: SOA

See JBMESSAGING-1293

Comment 1 Jiri Pechanec 2008-05-22 12:49:03 UTC
Link: Added: This issue depends JBMESSAGING-1293


Comment 2 Len DiMaggio 2008-05-22 15:34:51 UTC
Question - are we seeing a related issue with MS-SQL Server DB - where the limit is 8K? 


Comment 4 Martin Vecera 2008-05-27 13:48:35 UTC
I was able to pass 5MB TextMessage to queue/A and read it whole back. It was stored in the database before receiving. So it doesn't seem to me that the limit applies here.

Comment 6 Jiri Pechanec 2008-05-27 19:31:32 UTC
Can you check tha value of @@TEXTSIZE parameter?

Comment 7 Martin Vecera 2008-05-28 08:56:09 UTC
* When I connected through MSSQL Management studio, TEXTSIZE was set to 2GB. I could set it to 4kB for instance, but after reconnecting the size was again 2GB. I found this on the web:
"The SQL Server ODBC driver and Microsoft OLE DB Provider for SQL Server automatically set TEXTSIZE to 2147483647 when connecting." I didn't found anything similar for JDBC.

* I tried additional parameter in connection URL (textsize=4096) but it didn't work.

* According to the docs, TEXTSIZE limits the number of bytes returned from SELECT for columns of type TEXT, NTEXT, IMAGE. We definitely should put such a notice in our docs.

Comment 8 Joshua Wulf 2008-05-30 01:32:09 UTC
Release notes:

7.1. Sybase database cuts the payload according to pagesize by default

When a database is created Sybase sets the maximum size of text and image datatypes to the default page size of 2 KB. The longer message payload is truncated without any information or warning. The database parameters have to be updated to change the page size.

Further information: http://jira.jboss.com/jira/browse/SOA-554 | http://jira.jboss.com/jira/browse/SOA-553 


Is this ok? Or do you want something about MS SQL Server, as well?

Comment 9 Jiri Pechanec 2008-05-30 09:26:51 UTC
This issue is fixed by setting  @@TEXTSIZE config parameter not by changing page size
Also I would include the note that the issue can occur even on SQL Server if explicetly set but by default it should not.

Comment 10 Joshua Wulf 2008-06-02 06:59:10 UTC
7.1. Sybase database truncates message payload according to pagesize

When a database is created in Sybase the maximum size of text and image datatypes is set to the default page size of 2 KB. Any longer message payload is truncated without any information or warning. The database parameters have to be updated to set the @@TEXTSIZE parameter to a higher value.

The truncation behaviour may also be observed in MSSQL Server if @@TEXTSIZE is changed from its default value to a smaller one.

Further information: http://jira.jboss.com/jira/browse/SOA-554 | http://jira.jboss.com/jira/browse/SOA-553 

Comment 11 Jiri Pechanec 2008-06-10 09:28:39 UTC
Verified in CR1


Note You need to log in before you can comment on or make changes to this bug.