Exception: "Maximum attribute size limit (65536) exceeded"

[Bernd Welter]

Hello out there,

today a colleague mentioned the following generic issue:

I ran into an issue with a customer where the 1.20 version of xMap can no longer handle big WKB string. You will get a error that the "Maximum attribute size limit (65536) exceeded".

I reproduced the error and the complete message looks like this:

Code: Select all

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Client</faultcode>
<faultstring>Unmarshalling Error: Maximum attribute size limit (65536) exceeded </faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>

It occurs when you try to use a property (string, wkb, ...) that exceeds the length 65536 which is the implicit default value.
The workaround for this is quite simple:
Add the following key into the /conf/wrapper.conf and restart the service:

• wrapper.java.additional.21=-Dorg.apache.cxf.stax.maxAttributeSize=99999999

Works fine!

Thanks to Joost Claessen for the hint,

Best regards Bernd

[Bernd Welter]

just looked into an actual xserver 1.36:

wrapper.java.additional.23=-Dorg.apache.cxf.stax.maxAttributeSize=33554432

Looks like we already increased the size of that parameter value.
By the way: current xServer 2.27 uses the same threshold value.

[Bernd Welter]

Quick side note: last week I had a partner who had been running into this error though the PTV servers in use were already updated to way more than 65kb message size. It turned out that his middleware infrastructure (=xserver CLIENT) wasn't able to handle the communication, not the PTV servers.

After increasing the relevant keys in the middleware communication the error was gone