Issue uploading large files to site protected by Secure Proxy Server
Article ID: 115175
Updated On:
Products
CA Single Sign On Secure Proxy Server (SiteMinder)
CA Single Sign On SOA Security Manager (SiteMinder)
CA Single Sign-On
Issue/Introduction
We got the following error for the SPS Proxy used in transferring a large file:
[07/12/2018][13:54:20][4004][5132][201e0a0f-eb03e732-3b16b37e-12f22427-4e63f7b3-782][Noodle::doGet][java.io.IOException: Resetting to invalid mark at java.io.BufferedInputStream.reset(BufferedInputStream.java:448)]
Initially, CA suggested, in server.conf , to raise the size of the setting as follows.
maxcachedpostdata="1024" to the transferred file size; say : maxcachedpostdata="9024" for a test.
But that does not appear to have helped.
Next. the recommended general tuning was followed per this KB article:
https://comm.support.ca.com/kb/ca-access-gateway-formerly-secure-proxy-server-commonly-tuned-parameters/kb000043275
But it didn't help.
[07/12/2018][13:54:20][4004][5132][201e0a0f-eb03e732-3b16b37e-12f22427-4e63f7b3-782][Noodle::doGet][java.io.IOException: Resetting to invalid mark at java.io.BufferedInputStream.reset(BufferedInputStream.java:448)]
Initially, CA suggested, in server.conf , to raise the size of the setting as follows.
maxcachedpostdata="1024" to the transferred file size; say : maxcachedpostdata="9024" for a test.
But that does not appear to have helped.
Next. the recommended general tuning was followed per this KB article:
https://comm.support.ca.com/kb/ca-access-gateway-formerly-secure-proxy-server-commonly-tuned-parameters/kb000043275
But it didn't help.
Environment
Access Gateway - AG (a.k.a. Secure Proxy Sever - SPS) R12.7.2
Policy Server R12.7.2
Policy Server R12.7.2
Resolution
The traditional approaches to find what is causing the SPS to file to not upload may not help after reviewing SPS logs and traces and trying to tune per CA's general guidelines.
In the situation (as it was discovered later in this particular case) where two machines (e.g. Windows-based) in the same sub-net differ in behavior for the large upload of files across SPS to the back end; e,g, one can upload large files, the other cannot and fails with an error (as above), the web.config in the may be the difference. The problem may be unrelated to CA SSO components as in this instance.
Depending on which version of Windows, there might be some difference in the web.config construct. But, please search the Internet accordingly. Or, take assistance from Microsoft Support.
For example, in IIS/ASP.NET environment:
In the situation (as it was discovered later in this particular case) where two machines (e.g. Windows-based) in the same sub-net differ in behavior for the large upload of files across SPS to the back end; e,g, one can upload large files, the other cannot and fails with an error (as above), the web.config in the may be the difference. The problem may be unrelated to CA SSO components as in this instance.
Depending on which version of Windows, there might be some difference in the web.config construct. But, please search the Internet accordingly. Or, take assistance from Microsoft Support.
For example, in IIS/ASP.NET environment:
To increase the upload limit, one can add appropriate section to your web.config file and specify the limit. CA recommends consulting Microsoft Support when taking such action.
In the case of IIS 7.x and later, both Integrated and Classic mode:
| 1 2 3 4 5 6 7 | <system.webServer> <security> <requestFiltering> <requestLimits maxAllowedContentLength="<set_a_large_file_size_here" /> </requestFiltering> </security></system.webServer> |
According to MSDN, maxAllowedContentLength has type uint, its maximum value is 4,294,967,295 bytes = 3,99 GB.
|
maxAllowedContentLength |
Optional uint attribute. Specifies the maximum length of content in a request, in bytes. The default value is 30000000. |
Feedback
Yes
No
Powered by
