Project

General

Profile

Image Support #3675

JBOSS EAP 7.2.9 : Unable to connect to jboss using jboss-cli remotely

Added by Shweta 2 months ago. Updated about 2 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Due date:
% Done:

0%

Operating System:
Linux
JRE:
Not Applicable
Instance Type:
Not Applicable
Your Marketplace Account ID:
2872-5568-4589
Marketplace:
Amazon Web Services
Customer State:
Sydney
Customer Country:
New South Wales

Description

Hi Team,

We are using below command to connect from /opt/jboss-eap-7.2/bin
java -jar jboss-cli-client.jar --connect --controller=10.54.154.220:443 --user=***** --password=***** locally it connects but remotely from other ec2 server it was not connecting and getting below error :
error :
Failed to connect to the controller: The controller is not available at 10.54.154.220:443: java.net.ConnectException: WFLYPRT0053: Could not connect to https-remoting://10.54.154.220:443. The connection failed: WFLYPRT0053: Could not connect to https-remoting://10.54.154.220:443. The connection failed: Connection refused

Please help us understand the issue here.

Thanks & Regards,
Shweta Hegade

#1

Updated by Shweta 2 months ago

We are trying to connect to the jboss from remote server using jboss-cli.xml , jboss-cli-client.jar and the below controller using which are able to connect locally but getting error while trying to connect remotely.

Command used : /opt/jboss-eap-7.2/bin
java -jar jboss-cli-client.jar --connect --controller=10.54.154.220:443 --user=***** --password=*****

#2

Updated by Mariusz 2 months ago

  • Status changed from New to In Progress
  • Assignee set to Shweta

Hi Shweta,

I will contact Red Hat support team, but it actually looks like there is no connection between two ec2 servers. Could you possibly make sure that you can telnet port 443 from the other ec2 instance?
Is your security group open on port 443?

Thanks,
Mariusz Chwalek

#3

Updated by Shweta 2 months ago

Hi Mariusz,
Yes. We are able to telnet port 443 from other ec2 instance.

Regards,
Shweta Hegade

#4

Updated by Mariusz 2 months ago

  • Assignee changed from Shweta to Mariusz

Hi,

We are now waiting for a reply from Red Hat support team.
I will let you know when I have more information.
Thanks,
Mariusz Chwalek

#5

Updated by Mariusz 2 months ago

  • Assignee changed from Mariusz to Red Hat Support
#6

Updated by Mariusz 2 months ago

  • Status changed from In Progress to Feedback
  • Assignee changed from Red Hat Support to Shweta

Reply from IBM:

"Hi,

Thank you for contacting Red Hat, my name is Abhijeet and I am taking ownership of this case.
As per issue description you are encountering below error while connecting jboss-cli : 
~~~~~~~~~~
Failed to connect to the controller: The controller is not available at 10.54.154.220:443: java.net.ConnectException: WFLYPRT0053: Could not connect to https-remoting://10.54.154.220:443. The connection failed: WFLYPRT0053: Could not connect to https-remoting://10.54.154.220:443. The connection failed: Connection refused
~~~~~~~~~~
- I have reviewed the command you are using to connect to jboss cli and found that you arr using "443", is this correct port you have configured in your server configuration, by default https port is 8443. To confirm can you please share your server configuration standalone*.xml which ever you are using to start the server with us to review.
- Also please share your complete server.log file with us to review the server bootup logs, it will help us to understand on what host/port the EAP has registered.

Thanks
Abhijeet." 
#7

Updated by Mariusz about 2 months ago

  • Status changed from Feedback to Marked for Closure

Hi,
We noticed there hasn't been an update to this ticket for some time. Can we consider this ticket closed from support point of view? Is this still an issue or is there anything further that we can do for you in this regard? If not we will be timing out this ticket and will be closed in a few days time. If you have any other queries, please do not hesitate to ask us.

Regards,
Mariusz Chwalek

#8

Updated by Mariusz about 2 months ago

  • Status changed from Marked for Closure to Closed

Also available in: Atom PDF