IBM Support

JR60354: YOU NOTICE A LOT OF CPU IS USED IN IBM RPA V11.3 AFTER YOU UPGRADE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When IBM Robotic Process Automation with Automation Anywhere
    services are started, you might notice heavy CPU usage from a
    Java process started by the ElasticSearch
    service. In addition, you might also get errors logging into the
    Control Room because the ElasticSearch JVM is not running
    because of this error:
    
    "Failed to connect to Elasticsearch server."
    
    This error occurs because the JVM constantly restarts. The JVM
    constantly restarts because the following error is being logged
    in the aa_cr_elasticsearch.log file:
    
    [2018-11-15T00:00:19,098][ERROR][o.e.b.Bootstrap ] [3cZWpWG]
    Exception org.elasticsearch.transport.BindTransportException:
    Failed to resolve publish address
    at
    org.elasticsearch.transport.TcpTransport.createBoundTransportAdd
    ress(TcpTransport.java:825)
    at
    org.elasticsearch.transport.TcpTransport.bindServer(TcpTransport
    .java:761)
    ...
    Caused by: java.lang.IllegalArgumentException: No up-and-running
    site-local (private) addresses found, got [...
    
    This error occurs because no local/private IP addresses is found
    on the local system.
    

Local fix

  • LOCAL FIX:Ø
    Edit the following entry in the C:\Program Files\Automation
    Anywhere\Enterprise\elasticsearch\config\elasticsearch.yml file:
    network.host: _site_
    to
    network.host: _local_
    

Problem summary

  • No additional information is available.
    

Problem conclusion

  • A fix is included in IBM Robotic Process Automation with
    Automation Anywhere V11.0.0.4 interim fix 001.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR60354

  • Reported component name

    RPA WITH AA

  • Reported component ID

    5737E8100

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-11-27

  • Closed date

    2019-02-05

  • Last modified date

    2019-02-05

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    RPA WITH AA

  • Fixed component ID

    5737E8100

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSMGNY","label":"IBM Robotic Process Automation with Automation Anywhere"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
05 February 2019