AutoSys Workload Automation

Hi

Actually I have encountered  I could'nt connect to WCC as url (http://wcc01:8080/wcc/ui/login.html).

and I found any message on the as_server.BAT as below at the same time..

-------------------------------------------------------------------------------

[10/30/2017 03:45:06]  ispUtil  

       ERROR: [0x00001071] ispUtil.HttpPostRequest: select failed or timedout on recv [timeout : 120]

       ERROR: [0x00001071] +_+_+_ispUtil::ReleasePC: peer closed

---------------------------------------------------------------------------------

So I have restarted WCC server, but still have the problem.

Eventually I solved the problem after I restart manager service (as_server, scheduler) first and then continuoulsy restart wcc server.

Actually we have been encounting the phenomenon that we can not connect to WCC via CROM every couple of week, so we periodically restart WCC server every monday.

Why is this phenomenon happening ?

What is the reason for this? (Java, tomcat in WCC? or any other cause ?)

What are some things we can do to solve this problem? (upgrade or patch ??)

- Manager : autosys 11.3.6 sp5 on AIX 6.1

- WCC : wcc 11.4 sp4 on WIndows 2012

shouldn't it be https: and 8443? 

i certainly hope your firm is using https .. 

open a ticket it appears  you may have set something up incorrectly. 

Steve C.

I agree with Steve in that you should probably open a ticket on this one. Here are some of the things we will be asking you when you do...

What specific error do you get in your browser when you are unable to connect with that URL?

Have you tried clearing browser cache when this occurs?

Does it only occur in Chrome, or does it occur with any type of browser?

A failure to connect with the WCC URL would not log anything in the as_server log. However, the error you are seeing in the as_server log when this occurs is typically associated with a problem between the Application Server and EEM. That is a common thread between the App Server and a WCC login. Both would be interacting with EEM. It is possible you have an intermittent EEM issue behind this.

Hi Han,

The very fact that your WCC needs restarting to work looks lke it is running out of resources. You can tune the WCC performance to resolve the bottlenecks.

You can increase Java max memory of the tomcat

You can consider using external database if your load is more than that is specified for Derby

Optimize EEM policies.

For more details please refer the following documentation

https://docops.ca.com/ca-workload-automation-ae/11-4-2/en/installing/ca-wcc-installation/tune-component-performance