A2A Client error, "Stopping Acceptor ServerSocket"
search cancel

A2A Client error, "Stopping Acceptor ServerSocket"


Article ID: 275029


Updated On:


CA Privileged Access Manager (PAM)


The A2A Client is returning error 445 whenever trying to pull credential.

A2A Client logs:

INFO: Sat August 12 01:17:41.033 EDT 2023 ScriptService::doGet. errorCode: 400, accountId: ClientTest, password: XXXXXXXXXXXXXXXXXX, XML block length: 4
Aug 12, 2023 1:25:16 AM org.mortbay.util.ThreadedServer$Acceptor run
INFO: Stopping Acceptor ServerSocket[addr=,port=0,localport=28888]======================>
Aug 12, 2023 1:25:16 AM org.mortbay.http.SocketListener stop
INFO: Stopped SocketListener on>
Aug 14, 2023 6:57:56 AM org.mortbay.util.LogSupport <clinit>
INFO: Log instance is class org.apache.commons.logging.impl.Jdk14Logger
Aug 14, 2023 6:57:56 AM org.mortbay.http.HttpServer start
INFO: Starting Jetty/5.0.alpha2


PAM: 4.1

Any A2A Client version


 The JRE could not establish the https connection to the PAM server because of a problem with the /var/tmp file system.

This issue is causing JRE to hang trying to use /var/tmp while looking for the configured cipher suites on the server. 


To resolve this issue: 

1. Make sure that /var/tmp on the server which A2A client is configured is performing well to any commands run, such as "ls -l /var/tmp".

2. Restart A2A Client service

3. The main suggestion is to reboot the server.