This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 253679 - java.net.ConnectException: Connection refused
Summary: java.net.ConnectException: Connection refused
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WildFly (show other bugs)
Version: -FFJ-
Hardware: All All
: P3 normal (vote)
Assignee: ehsavoie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-23 10:44 UTC by abien
Modified: 2015-09-25 12:14 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 218715

Attachments
stacktrace (4.04 KB, text/plain)
2015-07-23 10:44 UTC, abien 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description abien 2015-07-23 10:44:05 UTC 
Build: NetBeans IDE Dev (Build 201507160001)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.45-b02, Java(TM) SE Runtime Environment, 1.8.0_45-b14
OS: Mac OS X

User Comments:
abien: happened during deployment




Stacktrace: 
java.net.ConnectException: Connection refused
   at sun.nio.ch.SocketChannelImpl.checkConnect(SocketChannelImpl.java:0)
   at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
   at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:319)
   at org.xnio.nio.WorkerThread.run(WorkerThread.java:539)
   at ...asynchronous invocation...(.java:0)
   at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272)
Comment 1 abien 2015-07-23 10:44:07 UTC 
Created attachment 154815 [details]
stacktrace
Comment 2 ehsavoie 2015-07-23 11:07:21 UTC 
Which version of the server ?
Seems like it couldn't access it.
Comment 3 Petr Hejl 2015-09-25 10:02:37 UTC 
Awaiting user response.
Comment 4 ehsavoie 2015-09-25 12:14:53 UTC 
Adam Bien <abien@adam-bien.com>
	
Jul 25
		
to ehsavoie
It was the WF 8.2. But the problem was misconfigured server. The data source pointed to a not-existing DB.

Hence I’m working with NB DEV builds, I just pushed the button to report the bug. Nothing serious.