tx subsystem: CAUAJM_E_10062 Failed

book

Article ID: 7804

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) CA Workload Automation Agent

Issue/Introduction

Customer may encounter WAAE Application Server outage due to error "Error initializing tx subsystem: CAUAJM_E_10062 Failed to get initial configuration from CA WAAE Application Server(s)."

Cause

This can be caused by an exorbitant number of API calls into the AE application. The API traffic is generally from WCC where users are interacting with the system. Customer will see messages similar to the following in the as_server.<instance> log file:

[08/08/2017 00:00:01]      CAUAJM_I_30031 Client [CA WAAE API JNI:5470][9][sys1.ca.com:49364:xxx.xxx.xxx.xxx] [0x35181960][08/08/2017 00:00:01.1433][1:autosys<@sys1,sys2> 1] API ID [300] execution started.

[08/08/2017 00:00:01]      CAUAJM_I_30032 Client [CA WAAE API JNI:5470][9][sys1.ca.com:49364:xxx.xxx.xxx.xxx] [0x35181960][08/08/2017 00:00:01.1433][1:autosys<@sys1,sys2> 1] API ID [300] execution completed. Total time: 0.07 seconds.

[08/08/2017 00:00:02]      CAUAJM_I_30031 Client [CA WAAE API JNI:11034][9][sys2.ca.com:49254:xxx.xxx.xxx.xxx] [0x35e089e8][08/08/2017 00:00:02.3597][1:autosys<@sys1,sys2> 1] API ID [348] execution started.

[08/08/2017 00:00:02]      CAUAJM_I_30032 Client [CA WAAE API JNI:11034][9][sys2.ca.com:49254:xxx.xxx.xxx.xxx] [0x35e089e8][08/08/2017 00:00:02.3597][1:autosys<@sys1,sys2> 1] API ID [348] execution completed. Total time: 0.035 seconds.

[08/08/2017 00:00:02]      CAUAJM_I_30031 Client [CA WAAE API JNI:11034][9][sys2.ca.com:49254:xxx.xxx.xxx.xxx] [0x35024598][08/08/2017 00:00:02.4273][1:autosys<@sys1,sys2> 1] API ID [299] execution started.

[08/08/2017 00:00:03]      CAUAJM_I_30032 Client [CA WAAE API JNI:11034][9][sys2.ca.com:49254:xxx.xxx.xxx.xxx] [0x35024598][08/08/2017 00:00:02.4273][1:autosys<@sys1,sys2> 1] API ID [299] execution completed. Total time: 0.807 seconds.

Environment

Any OS typeAny Database type

Resolution

A resolution to this issue is to decrease the number of API JNI calls at any given time. Executing jobs that run scripts where Autosys client utilities are being called contribute to the number of API JNI calls. A large number of API JNI calls can bring down the application server. While the application server is down, customer will notice that new job executions are not occurring. Start the application server back up to resume normal operations. If you have an HA environment, then the system will check to see if another application server is online and available. If so, then there will be no delay in batch processing as the alternate application server takes over.