Problem: We were not able to login into Desktop client

Document ID:  TEC1373095
Last Modified Date:  08/08/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Workload Automation DE

Releases

  • CA Workload Automation DE:Release:11.3 SP1
  • CA Workload Automation DE:Release:11.3
  • CA Workload Automation DE:Release:11.3 SP2

Components

  • CA DSERIES WORKLOAD AUTOMATION:DSRIES
Question:

We were not able to login into Desktop client. The agent and server were running on the server but desktop was not able to connect. 
The error message that we have found in the trace log is provided below. 

Error Message: 

20170801 05:55:16.972 [essential] [INFO] WSS_reactor_4: [2017-08-01_05:55:16.971] Session created: 10.10.11.11:57264->10.10.13.13:7500 (id=16952) 
20170801 05:55:16.972 [ws:connections] [INFO] WSS_reactor_4: [2017-08-01_05:55:16.972] Connection closed (10.10.11.11:57264->10.10.13.13:7500) 
java.io.EOFException 
at cybermation.workstationserver.nio.ReadExpert.read(ReadExpert.java:164) 
at cybermation.workstationserver.nio.ReadWriteHandler.handleRead(ReadWriteHandler.java:159) 
at cybermation.workstationserver.nio.Reactor.dispatchEvents(Reactor.java:184) 
at cybermation.workstationserver.nio.Reactor.access$000(Reactor.java:39) 
at cybermation.workstationserver.nio.Reactor$3.run(Reactor.java:403) 
at java.lang.Thread.run(Thread.java:745)

Environment:
11.3
Answer:

This problem is fixed in 11.3 SP3 and is documented in the release notes


https://support.ca.com/cadocs/7/CA%20Workload%20Automation%20DE%20r11%203%20SP3%20-%20Customer%20Access%20Only-ENU/Bookshelf_Files/HTML/Release_Notes_11_3_SP3/index.htm?toc.htm?Unable_to_Add_a_New_Server_Connection_in_CA_WA_Desktop_Client_Due_to_Deadlock.html


Unable to Add a New Server Connection in CA WA Desktop Client Due to Deadlock

When you add a new server connection in CA WA Desktop Client, the connection gets timed-out after 30 seconds with the following error message:

20140708 13:54:01.157 [ws:connections] [INFO] WSS_reactor_8: Connection
closed 
java.io.EOFException

In this issue, the scheduler thread acquired a lock on the RelationalDatabaseManager object and waited for the database connection. At the same time, the workload processing thread held the database connection and waited for the RelationalDatabaseManager object. Hence, the server moved into a deadlock and the database connection could not be released to the database connection pool.

This issue is fixed.

 

If you are not at SP3 the Upgrade patch 11.3 SP3 RO76709 
then follow by the 11.3 SP3 Cumulative patch RO89278 
and Also, the Desktop Client patch WIN-CUMULATIVE R11.3SP3 RO89279 . 

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >