ACNS wait 120 seconds for reply not long enough

Unanswered Question
Sep 19th, 2008

Hello

Using CE-7305A-K9 with ACNS 5.5.5 for outgoing proxy towards the Internet. A POST is send via the proxy and TCP ack'd by the application provider. The HTTP reply comes back from the application almost 4 minutes later. ACNS only waits for 120 seconds (I think) and then sends an error message to the client browser. The browser waits for 5 minutes so this works when the proxy is not there.

Can this max time that the proxy waits for a reply be increased ?

Thanks

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
sachinga.hcl Tue, 09/23/2008 - 06:11

Hi CHRISTIAN,

Can you send me the output of the following commnad:

show statistics http requests

show statistics http monitor

show statistics content-routing summary

show statistics content-routing history

show statistics content-routing website

so as to know about why delay is happening.

Sachin Garg

Senior Specialist Security

HCL Comnet Ltd.

A-10, Sector 3, Noida- 201301

sachinga.hcl Tue, 09/23/2008 - 06:33

one more thing are you using Websense Enterprise Manager or Websense Policy Server along with your CE and if the version at the websense does not math then also you face a resonable latency.

If all components are not in the same LAN, you might experience communication latency between Websense Enterprise Manager and other components. A significant increase in latency may lead to a communication failure.

ACNS Software Release =ACNS 5.5.5

martFilter Version Supported =Version 4.1.1

Websense Version Supported=Version 5.5.2

sachinga.hcl Tue, 09/23/2008 - 06:37

This problem occurs when the first configured name server is down and replies with ICMP unreachable for the DNS queries.

or

CSCef67934

Symptom: The proxy autoconfiguration file is missing from the Content Engine after you switch from group settings to device settings, and then switch back to group settings.

Condition: This problem occurs in the following circumstances:

a. You have specified values in the Client Proxy Autoconfig Device Group window of the Content Distribution Manager GUI.

b. You override these values through the Client Proxy Autoconfig Device window of the Content Distribution Manager GUI.

c. You revert the Content Engine back to the device group settings (you click the Force device group settings button in the device group window or you select the device group from the drop-down menu in the device window).

The autoconfiguration file is not found, but the proxy autoconfiguration feature is shown as enabled.

Workaround: Return to the device window in the Content Distribution Manager GUI, delete the values from the proxy autoconfiguration fields in the device window, and then select device group from the drop-down menu.

Actions

This Discussion