Automation Studio Slow or Times Out

Products

• CA Release Automation - Release Operations Center (Nolio)
• CA Release Automation - DataManagement Server (Nolio)

Issue/Introduction

Users working with the Automation Studio application experience either consistent or intermittent slowdowns in application responsiveness, such as periodic freezes or delays.  

When logs are checked, some or all of the following message may be found:

 

In the user's workstation's nolio_profiling.log:

[SwingWorker-pool-9584327-thread-121] INFO (ProfilingAspect.java:47) - exceeded 1000 ms threshold 

public abstract com.nolio.platform.server.dataservices.api.model.ApplicationPermissionsAdminBean com.nolio.platform.server.dataservices.api.model.UserAccessRightsService.getOverallApplicationPermissions(java.lang.Long) 

took 29091 millis (29.091 sec) 

 

In the user's workstation's nolio_app_all.log:

(Note: The following example error is specific to environments running Microsoft SQL Server, so the error may vary depending on what database is utilized.)

[SwingWorker-pool-790517696-thread-1] ERROR (BasicLoginHandler.java:137) - Could not deserialize result from HTTP invoker remote service [http://localhost:8080/datamanagement/remoting/AuthorizationService]; nested exception is java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerException 

org.springframework.remoting.RemoteAccessException: Could not deserialize result from HTTP invoker remote service [http://localhost:8080/datamanagement/remoting/AuthorizationService]; nested exception is java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerException 

[...] 

Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerException 

 

In the NAC's nolio_dm_all.log:

[http-nio-8080-exec-37] ERROR (com.nolio.releasecenter.utils.MessagesDataUtils:177) - Unexpected error [1487865142541] 

org.apache.catalina.connector.ClientAbortException: java.io.IOException: An established connection was aborted by the software in your host machine

 

 

Environment

Release Automation - All Versions.

Cause

This behavior usually occurs due to network-related problems outside of Release Automation.  Slow performance and the example errors cited indicate network latency issues, possibly occurring between the NAC and the database server (indicated by the error "Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerException").

Resolution

Since this problem is likely caused by environment issues instead of a problem within Release Automation, the issue can usually be resolved by identifying where the network issue is occurring.  Test the following items (which may require your network administrator to check):

• Network latency between the user's workstation and the server.
• Network latency between the NAC and the database server.
• Geographical distance between the NAC and database server.

Regarding the last item above, Studio slowdowns/freezes may occur if the database server and NAC are far apart from each other.  If this is the case, consider moving the NAC closer to the database server, such as moving servers so that they are in the same data center.