Connection Refused and Cannot connect to Controller Error - jboss

I am getting an error when i try to stop services
Failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to http-remoting://localhost:9990. The connection failed: Connection refused
when i try to start services, i get below error and need to restart the server multiple times to resolve it. need a solution to avoid errors during start and stop services. we use keycloack sercurity as well
2020-02-11 19:21:01,191 WARNING [com.lgc.dsl.admin.security.controllers.DSSecurity] (default task-12) Connect to localhost:8880 [localhost/IP] failed: Connection refused (Connection refused)
2020-02-11 19:21:09,462 WARN [org.kie.server.services.impl.controller.DefaultRestControllerImpl] (KieServer-ControllerConnect) Exception encountered while syncing with controller at http:localhost:port/dsbpm-console/rest/controller/server/dsbpm-kieserver error Error while sending PUT request to localhost:port/dsbpm-console/rest/controller/server/dsbpm-kieserver response code 405

Default kie server is not showing up in the server section
2020-02-11 19:21:01,191 WARNING [com.lgc.dsl.admin.security.controllers.DSSecurity] (default task-12) Connect to localhost:8880 [localhost/IP] failed: Connection refused (Connection refused)
2020-02-11 19:21:09,462 WARN [org.kie.server.services.impl.controller.DefaultRestControllerImpl] (KieServer-ControllerConnect) Exception encountered while syncing with controller at http:localhost:port/dsbpm-console/rest/controller/server/dsbpm-kieserver error Error while sending PUT request to localhost:port/dsbpm-console/rest/controller/server/dsbpm-kieserver response code 405
Check if you have 'dsbpm-console' for 'org.kie.server.controller' property, like as:

Related

kie server in Jboss EAP 7.4.0 localhost:8080/kie-server/services/rest/server' as failed due to Connection refused (Connection refused)

On running the command $EAP_HOME/bin/standalone.sh -c standalone-full.xml -b I'm getting error like
12:06:15,197 INFO
[org.kie.server.controller.websocket.client.WebSocketKieServerControllerImpl]
(KieServer-ControllerConnect) Kie Server points to non Web Socket
controller 'http://localhost:8080/business-central/rest/controller',
using default REST mechanism 12:06:15,198 WARN
[org.kie.server.services.impl.controller.DefaultRestControllerImpl]
(KieServer-ControllerConnect) Exception encountered while syncing with
controller at
http://localhost:8080/business-central/rest/controller/server/default-kieserver
error Connection refused (Connection refused) 12:06:19,805 WARN
[org.kie.server.client.impl.AbstractKieServicesClientImpl]
(Thread-125) Marking endpoint
'http://localhost:8080/kie-server/services/rest/server' as failed due
to Connection refused (Connection refused) 12:06:19,805 WARN
[org.kie.server.client.impl.AbstractKieServicesClientImpl]
(Thread-125) Cannot invoke request - 'No available endpoints found'
12:06:24,812 WARN
[org.kie.server.client.impl.AbstractKieServicesClientImpl]
(Thread-125) Marking endpoint
'http://localhost:8080/kie-server/services/rest/server' as failed due
to Connection refused (Connection refused) 12:06:24,812 WARN
[org.kie.server.client.impl.AbstractKieServicesClientImpl]
(Thread-125) Cannot invoke request - 'No available endpoints found'
on bind address, business central is running but I cannot find any execution server
but when I run the same command without bind address like
./standalone.sh -c standalone-full.xml
All are working properly
What would be the issue when using bind address
I'm using
rhpam 7.12.0
jboss eap 7.4.0
I've done default configuration. And I didn't change any configuration

How to access JMX metrics using kafka.tools.JmxTool?

I am unable to get JMX metrics using bin/kafka-run-class.sh kafka.tools.JmxTool script. However, I am able to connect to process using Jconsole.
I have set following properties:
com.sun.management.jmxremote = true
com.sun.management.jmxremote.authenticate = false
com.sun.management.jmxremote.local.only = false
com.sun.management.jmxremote.port = 9145
com.sun.management.jmxremote.ssl = false
Exception:
? kafka_2.11-2.1.0/bin/kafka-run-class.sh kafka.tools.JmxTool --jmx-url service:jmx:rmi:///jndi/rmi://kafkatest-01:9154/jmxrmi
Trying to connect to JMX url: service:jmx:rmi:///jndi/rmi://kafkatest-01:9154/jmxrmi.
Could not connect to JMX url: service:jmx:rmi:///jndi/rmi://kafkatest-01:9154/jmxrmi. Exception Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: kafkatest-01; nested exception is:
java.net.ConnectException: Connection refused (Connection refused)].
java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: kafkatest-01; nested exception is:
java.net.ConnectException: Connection refused (Connection refused)]
at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:369)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
at kafka.tools.JmxTool$.main(JmxTool.scala:120)
at kafka.tools.JmxTool.main(JmxTool.scala)
Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: kafkatest-01; nested exception is:
java.net.ConnectException: Connection refused (Connection refused)]
at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:136)
at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:205)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1955)
at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1922)
at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:287)
... 3 more
Trying to connect to JMX url: service:jmx:rmi:///jndi/rmi://kafkatest-01:9154/jmxrmi.
but your port is 9145
com.sun.management.jmxremote.port = 9145
Want to know what properties are actually set on your running JVM (useful for checking stuff like this)
prompt> jcmd $pid VM.system_properties

Wildfly 15.0.1 Final: The controller is not available at localhost:9990

I am trying to use Wildfly/JBoss to deploy a war of a program I made, but I keep receiving the following errors when I try to connect:
[disconnected /] connect 127.0.0.1:9990
The controller is not available at 127.0.0.1:9990: java.net.ConnectException: WFLYPRT0053: Could not connect
to remote+http://127.0.0.1:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990
. The connection failed: Connection refused: no further information
[disconnected /] connect localhost:9990
The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect
to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990
. The connection failed: Connection refused: no further information
[disconnected /] connect localhost:9991
The controller is not available at localhost:9991: java.net.ConnectException: WFLYPRT0053: Could not connect
to remote+http://localhost:9991. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9991
. The connection failed: Connection refused: no further information
[disconnected /] connect localhost:10000
The controller is not available at localhost:10000: java.net.ConnectException: WFLYPRT0053: Could not connec
t to remote+http://localhost:10000. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:10
000. The connection failed: Connection refused: no further information
[disconnected /] connect 127.0.0.1:9999
The controller is not available at 127.0.0.1:9999: java.net.ConnectException: WFLYPRT0053: Could not connect
to remoting://127.0.0.1:9999. The connection failed: WFLYPRT0053: Could not connect to remoting://127.0.0.1:9999. The
connection failed: Connection refused: no further information
[disconnected /] connect 127.0.0.1:10000
The controller is not available at 127.0.0.1:10000: java.net.ConnectException: WFLYPRT0053: Could not connec
t to remote+http://127.0.0.1:10000. The connection failed: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:10
000. The connection failed: Connection refused: no further information
[disconnected /]
What I did were the following steps
1)Went to the Wildfly site
2)Downloaded the latest version of the standalone
3)Unpacked from the archive
4)Run on Windows the file jboss-cli.bat by double clicking on it
5)Typed what you can see above (and before that I also typed only "connect", without anything else. Still didn't work, same error for localhost:9990)
I must specify this is a clean download with no configuration changed, no file deleted, nothing modified at all. Not even the war was deployed. I also tried to add a rule to the Windows firewall to unlock the port 9990, still the same error. On port 9990 nothing is listening, I already checked in cmd. And I also restarted my PC before trying the connect commands, so nothing would be opened by me on that port.
I have the latest versions of JDK and JRE installed on my PC if that helps.
What is going on with this error, I am really lost.
In the end I fixed the problem, and the solution was pretty straightforward. I forgot to open standalone.sh so wildfly can run, this being the reason jboss didn't connect.

Login Failure: Pool is empty and connection creation failed

when I tried to SSO using Shibboleth IDP, a login Error occured, when username and password was submitted as, Login Failure: Pool is empty and connection creation failed.
My error logs are as follows
==> /opt/shibboleth-idp/logs/idp-warn.log <==
at org.ldaptive.provider.jndi.JndiConnectionFactory.createInternal(JndiConnectionFactory.java:102)
Caused by: javax.naming.CommunicationException: localhost:10389
at com.sun.jndi.ldap.Connection.<init>(Connection.java:216)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
2018-08-13 09:32:53,752 - WARN [org.ldaptive.pool.BlockingConnectionPool:600] - unable to create active connection
2018-08-13 09:32:53,753 - ERROR [org.ldaptive.pool.BlockingConnectionPool:197] - Could not service check out request
2018-08-13 09:32:53,754 - WARN [net.shibboleth.idp.authn.impl.ValidateUsernamePasswordAgainstLDAP:192] - Profile Action ValidateUsernamePasswordAgainstLDAP: Login by admin produced exception
org.ldaptive.pool.PoolExhaustedException: Pool is empty and connection creation failed
at org.ldaptive.pool.BlockingConnectionPool.getConnection(BlockingConnectionPool.java:198)
Can anyone suggest me a way to solve this?
Old question, answer for google.
Check /opt/shibboleth-idp/conf/ldap.properties if your domain/IP and port are correct.
In my case i missed out that the image bitnami/openldap uses port 1389 by default.

Connection timed out: connect

When i am trying to deploy my application from Eclipse am getting the following error
Deploying frontend ------------
java.net.ConnectException: Connection timed out: connect
Any idea on how to remove this ?