DRM Web Service Custom .NET Client: The number of bytes available is inconsistent with the HTTP Content-Length header. There may have been a network error or the client may be sending invalid requests
Last updated on MARCH 08, 2017
Applies to:Hyperion Data Relationship Management - Version 18.104.22.168.504 and later
Information in this document applies to any platform.
When invoking a DRM webservice method which retrieves a lot of data from a custom .NET web service client the following error is being seen:
The log for the managed server where the DRM web service has been deployed also shows evidence of the StuckThreadMaxTime parameter having been exceeded due to requests to the DRM web service having taken longer than 600 seconds:
####<Aug 31, 2015 3:28:34 AM EDT> <Error> <WebLogicServer> <US1SAWN02774> <FoundationServices0> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <
POST /oracle-epm-drm-webservices/DrmService HTTP/1.1
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
If this has not been seen before and worked in the past then the volume of data being retrieved via the web service call or the stress on the DRM application server may have increased.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms