javax.naming.CommunicationException: XXXXXXXX.XXXX:389 [Root exception is java.net.ConnectException: Connection refused: connect]

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

Do you know how to solve this issue? Write a tip to help other users and build your expert profile.

Solutions on the web

via Oracle Community by 846590, 1 year ago
XXXXXXXX.XXXX:389 [Root exception is java.net.ConnectException: Connection refused: connect]
via Oracle Community by 843793, 1 year ago
storedom.net:389 [Root exception is java.net.BindException: Address already in use: connect]
via Oracle Community by 925694, 1 year ago
mediwebtst.aphp.fr:389 [Root exception is java.net.UnknownHostException: mediwebtst.aphp.fr]
via Coderanch by Hisham Farahat, 11 months ago
name.com:389 [Root exception is java.net.ConnectException: Connection refused: connect]
via Jenkins JIRA by Justinas Urbanavicius, 1 year ago
my.domainserver.xx:389 [Root exception is java.net.ConnectException: Connection refused]
via Jenkins JIRA by Justinas Urbanavicius, 1 year ago
my.domainserver.xx:389 [Root exception is java.net.ConnectException: Connection refused]
javax.naming.CommunicationException: XXXXXXXX.XXXX:389 [Root exception is java.net.ConnectException: Connection refused: connect]
at com.sun.jndi.ldap.LdapReferralContext.(LdapReferralContext.java:74)
at com.sun.jndi.ldap.LdapReferralException.getReferralContext(LdapReferralException.java:132)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.