Kbase P159627: Error 8373 calling Appserver after upgrade
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/16/2010 |
|
Status: Unverified
SYMPTOM(s):
Error 8373 calling AppServer after upgrade
Failure reading response from Application Server. (14810)
The maximum size of input or output data is 32K. If you need more than that then please use input or output TEMP-TABLES. (8373)
FACT(s) (Environment):
The AppServer procedure is being called with an input output temp table with many fields. In this case in the order of 1200.
All Supported Operating Systems
OpenEdge 10.x
Progress 9.1x
CHANGE:
Upgraded from Progress 9.1E to OpenEdge 10.2A02
CAUSE:
In this respect Progress 9.x and OpenEdge 10 cannot be compared with regard to how context is passed back and forth to the AppServer. In OpenEdge 10 this has changed considerably.
In version 9 the table schema is sent as a bulk message with a 32K limit. In OpenEdge this is done with tables and due to additional requirements/enhancements for OE10 this results in more data passed as context. This context still has a 32K limit, and is what causes the error. The fact that this error appears in OpenEdge 10 suggests that the code was very close to the 32K limit in Progress 9.x, and could have resulted in a similar error even in this version.
FIX:
To work around the issue there are two choices:
1. The best solution would be to reduce the number of fields in the temp table.
2. The other alternative is to reduce the schema transfer with the temp-table:MIN-SCHEMA-MARSHALL attribute on the sending side. This should suppress the sending of validation expressions and column labels, etc. If the receiving side has a definition (i.e. is not a NULL handle) then NO-SCHEMA-MARSHALL can be used.