When attempting to execute an information link, it may be observed that the data is unable to be opened. Furthermore the following error may be seen in the Spotfire server.log
response message does not match thecontent type of the binding (text/xml; charset=utf-8).
If using a custom encoder, be sure that the IsContentTypeSupported method is implemented
properly.
The first 146 bytes of the response were: '{"httpErrorCode":500,
"errorType":"Server.InternalError","errorMessage":"Internal server error",
"errorCode":"47ff5683-8576-4d7d-857a-2bd43abb9e05"}' (HRESULT: 80131500)
This error occurs when the QueryManagerService (The SOAP service responsible for executing JDBC queries and sending the result back to the client) receives an error when obtaining data.
This could have a variety of causes but the most common are:
1.) Heap exhaustion
One possibility is that the Information Services Java process has run out of heap. This needs to be assessed by Revvity staff, refer to the following article for further information.
https://support.revvitysignals.com/hc/en-us/articles/30143380527252-Spotfire-Server-OutOfMemoryException-error-when-running-Information-Links-after-upgrading-to-Spotfire-14
2.) HTTP Long timeout exceeded
When the QueryManger service attempts to get a data block, the client also waits for a block of data to be returned. But, due to long-connect-timeout of 10 sec, the connection is reset prior to that.
Increasing the http long timeout may solve the error.
1. Export server config using:
2. Alter the timeout using:
3. Import the config using:
4. Then restart the Spotfire server service and test the behaviour.
Comments
0 comments
Article is closed for comments.