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

  1. ,

    Check if your MongoDB is available.

  2. ,

    Check if your MariaDB is running and available.

java.net.ConnectException: Connection refused	at java.net.PlainSocketImpl.socketConnect(Native Method)	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)	at java.net.Socket.connect(Socket.java:579)	at java.net.Socket.connect(Socket.java:528)	at java.net.Socket.(Socket.java:425)	at java.net.Socket.(Socket.java:208)	at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)	at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:147)	at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)	at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619)	at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)	at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)	at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:341)	at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)	at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:114)