This content has been marked as final. Show 3 replies
There are 2 possibilities:
1. As you can see from the event log messages, a request's POST body length was longer than the max. cacheable size. This might have lead to this error.
2. You see that a client connection at the listen port has been dropped. This dropping of client connection might have lead to this error msg.
1. Are you sure that this error corresponds to the access log msg of HTTP 202?
2. What is returned (to the end--user) for this request (for which the network error is seen)?
Hope this helps.
I have a similar error. Do you have a solution to this yet? It hangs the page and users gets incomplete pages or browser just hangs. I have to restart webcache to resolve issue. Does it have anything to do with keep alive settings or firewall timeouts?
The cacheable response size limit may have to be increased. Get in touch with Oracle Support. They will be able to advice.