Autosys Job Failed : Error Java.io.IOException: Connection Reset By Peer
(Doc ID 2951424.1)
Last updated on MAY 30, 2023
Applies to:
Oracle Financial Services Compliance Studio - Version 8.1.2 and laterInformation in this document applies to any platform.
Symptoms
Steps to reproduce:
1. Run the ER job.
Expected result:
Job should be successful.
Actual Result:
Job failed with Connection reset by peer.
Error encountered:
2023-05-09 22:33:10.910 [tp-nio-7053-exec-1] INFO oadToElasticSearch.service.IndicesOperationsImpl - Index creation:: DeltaLoad on LoadDay-2
2023-05-09 22:33:10.942 [tp-nio-7053-exec-1] WARN org.elasticsearch.client.RestClient - request [POST https://<HOSTNAME>:<PORT>/<INDEX_NAME>/_count?ignore_throttled=true&ignore_unavailable=false&expand_wildcards=open&allow_no_indices=true] returned 1 warnings: [299 Elasticsearch-7.17.0-bee86328705acaa9a6daede7140defd4d9ec56bd "[ignore_throttled] parameter is deprecated because frozen indices have been deprecated. Consider cold or frozen tiers in place of frozen indices."]
2023-05-09 22:38:13.751 [tp-nio-7053-exec-1] ERROR sticSearch.controller.IndexDataLoadingController - Exception occurred
java.io.IOException: Connection reset by peer
Changes
Recently introduced the LB between the Compliance studio and Elastic search server. Also, Index creation with high volume was not tested after LB is added.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |