Unexpected Server received stop signal in CA Access Gateway (SPS)
Article ID: 244103
Updated On:
Products
Issue/Introduction
When starting CA Access Gateway (SPS), this one doesn't start, and the mod_jk connector reports:
mod_jk.log:
[Mon Jun 13 10:40:21.394 2022] [3772:2068] [error] ajp_send_request::jk_ajp_common.c (1724):
(ajp13) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
[Mon Jun 13 10:40:22.515 2022] [3772:2068] [error] ajp_send_request::jk_ajp_common.c (1724):
(ajp13) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
[Mon Jun 13 10:40:22.515 2022] [3772:2068] [error] ajp_service::jk_ajp_common.c (2795):
(ajp13) connecting to tomcat failed (rc=-3, errors=382, client_errors=0).
This happens as the CA Access Gateway (SPS) shuts down automatically just after having fully started up:
server.log:
[15/Jun/2022:11:25:37-145] [INFO] - {/authapp=sessionassuranceapp, /chs=chs, /affwebservices=affwebservices}
[15/Jun/2022:11:25:37-160] [INFO] - Server received stop signal.
Environment
CA Access Gateway (SPS) 12.8SP6a on Windows 2016;
AdoptOpenJDK 1.8.0_322;
Cause
Another process using port 8005 already on the system causes this issue.
The Application Event Viewer reports the error:
SPS Proxy Engine process could not be started. Retried three times. Command used :
"C:\myApps\Java\jdk8u322-b06\bin\java.exe"
-Xms512m -Xmx1024m -XX:MaxMetaspaceSize=256M
-Dcatalina.base="c:\myApps\CA\secure-proxy\Tomcat"
-Dcatalina.home="c:\myApps\CA\secure-proxy\Tomcat"
-Djava.endorsed.dirs="c:\myApps\CA\secure-proxy\Tomcat\endorsed"
-Djava.endorsed.dirs="c:\myApps\CA\secure-proxy\Tomcat\endorsed"
-Djava.io.tmpdir="c:\myApps\CA\secure-proxy\Tomcat\temp"
-DHTTPClient.log.mask=0
-DHTTPClient.Modules="HTTPClient.RetryModule|org.tigris.noodle.NoodleCookieModule|HTTPClient.DefaultModule"
-DSM_AGENT_LOG_CONFIG="" -Dfile.encoding=UTF8
-DIWACONFIGHOME="c:\myApps\CA\secure-proxy\proxy-engine\conf\sts-config\globalconfig"
-Dlogger.properties="c:\myApps\CA\secure-proxy\Tomcat\properties\logger.properties"
-classpath
"c:\myApps\CA\secure-proxy\Tomcat\bin\proxybootstrap.jar;
c:\myApps\CA\secure-proxy\Tomcat\properties;C:\myApps\Java\jdk8u322-b06\lib\tools.jar;
C:\myApps\Java\jdk8u322-b0
Running the command in the DOS console:
"C:\myApps\Java\jdk8u322-b06\bin\java.exe"
-Xms512m -Xmx1024m -XX:MaxMetaspaceSize=256M
-Dcatalina.base="c:\myApps\CA\secure-proxy\Tomcat"
-Dcatalina.home="c:\myApps\CA\secure-proxy\Tomcat"
-Djava.endorsed.dirs="c:\myApps\CA\secure-proxy\Tomcat\endorsed"
-Djava.endorsed.dirs="c:\myApps\CA\secure-proxy\Tomcat\endorsed"
-Djava.io.tmpdir="c:\myApps\CA\secure-proxy\Tomcat\temp"
-DHTTPClient.log.mask=0
-DHTTPClient.Modules="HTTPClient.RetryModule|org.tigris.noodle.NoodleCookieModule|HTTPClient.DefaultModule"
-DSM_AGENT_LOG_CONFIG="" -Dfile.encoding=UTF8
-DIWACONFIGHOME="c:\myApps\CA\secure-proxy\proxy-engine\conf\sts-config\globalconfig"
-Dlogger.properties="c:\myApps\CA\secure-proxy\Tomcat\properties\logger.properties"
-classpath
"c:\myApps\CA\secure-proxy\Tomcat\bin\proxybootstrap.jar;
c:\myApps\CA\secure-proxy\Tomcat\properties;C:\myApps\Java\jdk8u322-b06\lib\tools.jar;
C:\myApps\Java\jdk8u322-b0
It shows that port 8005 was already used when Tomcat tried to bind it.
In DOS console, running netstat command, the PID 4 uses the port 8005 already:
c:\> netstat -ano -p tcp| findstr 8005
TCP 127.0.0.1:8005 127.0.0.1:8005 ESTABLISHED 4
In Task Manager, PID 4 properties show it's related to process: ntoskml.exe.
According to that post, this is an issue with the SMS service (1), and it's recommended the disable the service or force it to use another port.
Resolution
- Get in touch with the Windows System administrator to disable the "SMS Agent Host" service, or configure it to use another port than 8005 to fix this issue.
Additional Information
(1)
Port 8005 is used By Windows 10 System Process
check the file c:\Windows\CCM\Logs\DeltaDownload.log for port 8005
stop the service "SMS Agent Host"
Feedback
