| Summary: | Document that Sybase cuts the payload according to pagesize by deafult | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Jiri Pechanec <jpechane> |
| Component: | Documentation, JBoss Messaging | Assignee: | Joshua Wulf <jwulf> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2 CP01 | CC: | jwulf, lcarlon |
| Target Milestone: | --- | ||
| Target Release: | 4.2 CP02 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-554 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-06-10 09:28:39 UTC | Type: | Feature Request |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jiri Pechanec
2008-05-22 12:48:51 UTC
Link: Added: This issue depends JBMESSAGING-1293 Question - are we seeing a related issue with MS-SQL Server DB - where the limit is 8K? These two links contain information on changing the pagesize: http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.ase_15.0.utility/html/utility/utility203.htm http://infocenter.sybase.com/help/topic/com.sybase.help.ase_15.0.omni_ug/html/omni_ug/omni_ug101.htm 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. Can you check tha value of @@TEXTSIZE parameter? * 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. 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? 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. 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 Verified in CR1 |