Failed to start the Gateway server: ERROR #5023: Remote Gateway Error: Communication failure on port: 5000 > ERROR #5001: External Language Server: invalid ping response

Question

Question

#InterSystems IRIS for Health #Ensemble #Health Connect

Our client getting sometimes this error and we need to change port number on JavaGateway process to continue,

Failed to start the Gateway server: ERROR #5023: Remote Gateway Error: Communication failure on port: 5000
> ERROR #5001: External Language Server: invalid ping response

Can you tell as why it is happenning? intersystems runtime is under linux.

Product version: IRIS 2023.1

Discussion (6)3

Log in or sign up to continue

score 0 · Answer 1 · 2024-07-05T09:17:04-04:00

I would start by checking if some other process is already using port 5000 (or whatever port JavaGateway is trying to run on). It would also be good to check the JavaGateway

Since you're on Linux you can check this with netstat:

netstat --listening --numeric-ports

score 0 · Answer 2 · 2024-07-16T04:06:40-04:00

Hallo Marc,

We have tryed to chage the ports the problem persists. hier is a logging: First we get warning from Javagateway. And when BO trying to execute sql we get Error and we need to change port to continue.

1221819
Type:	Warning
Text:	Gateway Server did not respond to PING request: ERROR #5023: Remote Gateway Error: Communication failure on port: 5003
Logged:	2024-07-11 14:33:31.468

235962
Type:	Error
Text:	Failed to stop the Gateway Server: ERROR #5023: Remote Gateway Error: Connection cannot be established
Logged:	2024-07-12 10:20:02.649
Source:	JavaGateway InsertACK
Session:	(none)
Job:	137646
Class:	EnsLib.JavaGateway.Service
Method:	OnTearDown
Trace:	(none)
Stack When Logged:	$$^OnTearDown+4^EnsLib.Gateway.Service.1 +1 DO^%OnClose+16^Ens.Host.1 +1 DO^%Destruct+1^Ens.Host.1 +1 DO^Start+85^Ens.Job.1 +1

score 0 · Answer 3 · 2024-07-16T06:18:58-04:00

Did you try what @Marc Mundt told you? Check if there is a process that is using the port dedicated for the JDBC conenction (in your warning the port 5003).

score 0 · Answer 4 · 2024-07-16T14:25:50-04:00

Have you checked to see if there is another app using the Port? I know that sometimes the Shutdown doesn't always shutdown the Java Gateways properly, especially if you failover, and fail back to the primary. We have it scripted to make sure that if a Shutdown occurs or if the mirror fails over that the Java Gateways are properly shutdown.

score 0 · Answer 5 · 2024-07-18T03:42:51-04:00

It is working for a week and than it stops. We changed the port and changed the timeout of BO SQL adapter from 60 to -1.

We wait now if problem persists.

score 0 · Answer 6 · 2024-07-18T08:57:31-04:00

Does your Java Gateway stop or your BO? Is something scanning the ports and causing a blockage, or failure perhaps? Try enabling the Java Gateway log file, I know it's hard to read, but it may give you a clue to what is going on.

Also make sure that the External Language %JDBC Server isn't crashing for some unknown reason. I found that if the %JDBC Server starts having issues that the Java Gateways within your Namespaces start having issues as well.