Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

AES server intermittently throws Connection refused errors

SA-42975

Summary



Autonomic Event Services (AES) server intermittently throws Connection refused errors. The errors go away on their own.

These errors are sometimes preceded by 'AxisFault: Transport error: 401 Error: Unauthorized' errors.


Error Messages



####<Aug 14, 2017 11:02:32 AM CDT> <Notice> <Stdout> <XXXXXXXXXX9296> <AES10> <Dispatcher-Thread-33> <<WLS Kernel>> <> <> <1502726552184> <BEA-000000> <2017-08-14 11:02:32,184 [fault (self-tuning)'] [ STANDARD] [ AES:07.14] ( internal.mgmt.Executable) ERROR XXXXXXXXXX9296|your_ip|SOAP|PegaAES|Events|logAlert|A616B21E5C3260BF9C6268211302FDBBC|Rule-Connect-SOAP.PegaAES-Data-Nodes.ExecuteMBeanOperation - Exception
com.pega.pegarules.pub.services.ResourceUnavailableException: SOAP service failed
at com.pegarules.generated.activity.ra_action_invokeaxis2_58dbca272054d891f3559ad0fb53c832.step15_circum0(ra_action_invokeaxis2_58dbca272054d891f3559ad0fb53c832.java:3795)
...
com.pegarules.generated.activity.ra_action_parsealertlinesoap_7a26e04c4a9359d23c155291fc34db0b.step4_circum0(ra_action_parsealertlinesoap_7a26e04c4a9359d23c155291fc34db0b.java:314)
at com.pegarules.generated.activity.ra_action_parsealertlinesoap_7a26e04c4a9359d23c155291fc34db0b.perform(ra_action_parsealertlinesoap_7a26e04c4a9359d23c155291fc34db0b.java:104)
...
java.net.ConnectException: Connection refused: connect
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)

Steps to Reproduce



Use Weblogic Server to host AES and Monitored nodes.


Root Cause



A defect or configuration issue in the operating environment.
The errors are a result of WebLogic tcp buffer pool filling up intermittently.

Monitored nodes send Alert SOAP messages to AES server logAlert SOAP Service, which in turn makes webservice callbacks to the monitored server and tries to get correlation information.

This second service call fails because the monitored Pega node refuses to accept new socket connection, as its queue is already full.


Resolution



Make the following change to the monitored Pega nodes:

As rule of thumb raise the Accept Backlog value from the default by 25 percent.

Continue increasing the value by 25 percent until the messages cease to appear.


Refer to Oracle Weblogic WLSTuning guide for ConnectionBacklogBuffering.

Suggest Edit

Published November 4, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us