[
https://issues.jboss.org/browse/TEIID-2750?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2750.
-----------------------------------
Resolution: Done
Ensured proper server side logging (which means adding the message for detail/warning
level).
Increased the default max message size to 2 mb.
Added a system property and documented it in the admin guide - org.teiid.maxMessageSize
can adjust the max message size in bytes.
And probably most important allows for these type of exceptions to be communicated to the
client (8.6.0.Beta3/CR1+) without causing the connection to be dropped.
Improve handling of messages that are too large
-----------------------------------------------
Key: TEIID-2750
URL:
https://issues.jboss.org/browse/TEIID-2750
Project: Teiid
Issue Type: Quality Risk
Components: JDBC Driver
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.6
It is often unclear when a client message is too large. There is also no mechanism to
allow for larger messages.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira