App Connect

I connected to Remote Integration Node from toolkit that's installed locally and trying to turn on debugger to test the message flow in Dev environment. But I'm getting below error message : "Can not communicate with the flow engine". I tried to change the debugger port to new one and tested, but unfortunately getting same error. Interesting thing is I'm seeing same error while trying to turn on debugger for existing IS/EG whose debugger port was set long back

I cross checked the JVM debugger port to see if it was set correctly by running: mqsireportproperties <IntegrationNode> -e <IntegrationServer> -o ComIbmJVMManager -r, and also made sure the JVM min and max heap sizes were set with some numbers. The firewall is opened for the specific port that I'm trying by N/W team and I see that port is listening. What else needs to be cross checked so that I can turn on debugger from toolkit, and I also made sure that this specific port is not used by any other EG

Below is the error message.

Attach to server at <server _name>:4009 failed.
Connection could not be established.
This can occur for one or more of these reasons:
The host name and/or port are incorrect.
The server on <server_name> is not started in debug mode.
Communication timeouts in the Debug preferences (under the Java node in the Preferences dialog box) are not long enough.
The state of port 4009 on <server_name> must be LISTENING. If the state of the port is ESTABLISHED, then another debug session is already connected to the port.
The "netstat" command line tool can be used to determine port status.
A firewall is interfering with the connection.
Ensure that these settings are properly made before attempting to attach to the server.

------------------------------
Prathyusha Yedupati
Software Lead
------------------------------

Hello Prathyusha,  
 The usual issue for this is a firewall blocking the port.  
I would check the following: 
1) you can ping the server from the toolkit channel ( I would suspect this works since you are probably  showing the server in the toolkit explorer view.  
2) The Toolkit debugger connects using the java debugger so try configuring a debug session to the server by clicking on debug and creating a remote java application and set the host and port to your sever.  


See if that connects.  
If that does not connect then there must be something blocking the connection or that the port at the other end is not running an integration server.    e.g another application .  
If it does connect  then there is something wrong with the server at the other end and you would need to get IBM support involved.  
3. Try getting an iptrace and see if that actually connects.

------------------------------
Paul Lacy
------------------------------

Original Message:
Sent: Mon December 13, 2021 03:44 PM
From: Prathyusha Yedupati
Subject: Java Debug Channel - Cannot communicate with the flow engine

I connected to Remote Integration Node from toolkit that's installed locally and trying to turn on debugger to test the message flow in Dev environment. But I'm getting below error message : "Can not communicate with the flow engine". I tried to change the debugger port to new one and tested, but unfortunately getting same error. Interesting thing is I'm seeing same error while trying to turn on debugger for existing IS/EG whose debugger port was set long back

I cross checked the JVM debugger port to see if it was set correctly by running: mqsireportproperties <IntegrationNode> -e <IntegrationServer> -o ComIbmJVMManager -r, and also made sure the JVM min and max heap sizes were set with some numbers. The firewall is opened for the specific port that I'm trying by N/W team and I see that port is listening. What else needs to be cross checked so that I can turn on debugger from toolkit, and I also made sure that this specific port is not used by any other EG

Below is the error message.

Attach to server at <server _name>:4009 failed.
Connection could not be established.
This can occur for one or more of these reasons:
The host name and/or port are incorrect.
The server on <server_name> is not started in debug mode.
Communication timeouts in the Debug preferences (under the Java node in the Preferences dialog box) are not long enough.
The state of port 4009 on <server_name> must be LISTENING. If the state of the port is ESTABLISHED, then another debug session is already connected to the port.
The "netstat" command line tool can be used to determine port status.
A firewall is interfering with the connection.
Ensure that these settings are properly made before attempting to attach to the server.

------------------------------
Prathyusha Yedupati
Software Lead
------------------------------

Hello Prathyusha, How did you manage to get this issue resolved ? Any help is appreciated. 

------------------------------
Sony Xavier
------------------------------

Original Message:
Sent: Mon December 13, 2021 03:44 PM
From: Prathyusha Yedupati
Subject: Java Debug Channel - Cannot communicate with the flow engine

I connected to Remote Integration Node from toolkit that's installed locally and trying to turn on debugger to test the message flow in Dev environment. But I'm getting below error message : "Can not communicate with the flow engine". I tried to change the debugger port to new one and tested, but unfortunately getting same error. Interesting thing is I'm seeing same error while trying to turn on debugger for existing IS/EG whose debugger port was set long back

I cross checked the JVM debugger port to see if it was set correctly by running: mqsireportproperties <IntegrationNode> -e <IntegrationServer> -o ComIbmJVMManager -r, and also made sure the JVM min and max heap sizes were set with some numbers. The firewall is opened for the specific port that I'm trying by N/W team and I see that port is listening. What else needs to be cross checked so that I can turn on debugger from toolkit, and I also made sure that this specific port is not used by any other EG

Below is the error message.

Attach to server at <server _name>:4009 failed.
Connection could not be established.
This can occur for one or more of these reasons:
The host name and/or port are incorrect.
The server on <server_name> is not started in debug mode.
Communication timeouts in the Debug preferences (under the Java node in the Preferences dialog box) are not long enough.
The state of port 4009 on <server_name> must be LISTENING. If the state of the port is ESTABLISHED, then another debug session is already connected to the port.
The "netstat" command line tool can be used to determine port status.
A firewall is interfering with the connection.
Ensure that these settings are properly made before attempting to attach to the server.

------------------------------
Prathyusha Yedupati
Software Lead
------------------------------

I would first check your firewall (either windows or network). That is usually the culprit here.

------------------------------
Regards
Matthias Blomme
------------------------------

Original Message:
Sent: Wed February 14, 2024 01:06 PM
From: Sony Xavier
Subject: Java Debug Channel - Cannot communicate with the flow engine

Hello Prathyusha, How did you manage to get this issue resolved ? Any help is appreciated. 

------------------------------
Sony Xavier

Original Message:
Sent: Mon December 13, 2021 03:44 PM
From: Prathyusha Yedupati
Subject: Java Debug Channel - Cannot communicate with the flow engine

I connected to Remote Integration Node from toolkit that's installed locally and trying to turn on debugger to test the message flow in Dev environment. But I'm getting below error message : "Can not communicate with the flow engine". I tried to change the debugger port to new one and tested, but unfortunately getting same error. Interesting thing is I'm seeing same error while trying to turn on debugger for existing IS/EG whose debugger port was set long back

I cross checked the JVM debugger port to see if it was set correctly by running: mqsireportproperties <IntegrationNode> -e <IntegrationServer> -o ComIbmJVMManager -r, and also made sure the JVM min and max heap sizes were set with some numbers. The firewall is opened for the specific port that I'm trying by N/W team and I see that port is listening. What else needs to be cross checked so that I can turn on debugger from toolkit, and I also made sure that this specific port is not used by any other EG

Below is the error message.

Attach to server at <server _name>:4009 failed.
Connection could not be established.
This can occur for one or more of these reasons:
The host name and/or port are incorrect.
The server on <server_name> is not started in debug mode.
Communication timeouts in the Debug preferences (under the Java node in the Preferences dialog box) are not long enough.
The state of port 4009 on <server_name> must be LISTENING. If the state of the port is ESTABLISHED, then another debug session is already connected to the port.
The "netstat" command line tool can be used to determine port status.
A firewall is interfering with the connection.
Ensure that these settings are properly made before attempting to attach to the server.

------------------------------
Prathyusha Yedupati
Software Lead
------------------------------