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 217249 - java.net.SocketException: Software caused connection abort: socket write error
Summary: java.net.SocketException: Software caused connection abort: socket write error
Status: RESOLVED FIXED
Alias: None
Product: web
Classification: Unclassified
Component: HTML Project (show other bugs)
Version: 7.3
Hardware: All All
: P2 normal (vote)
Assignee: David Konecny
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-22 20:26 UTC by John Jullion-ceccarelli
Modified: 2012-09-03 12:54 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 191442

Attachments
stacktrace (611 bytes, text/plain)
2012-08-22 20:27 UTC, John Jullion-ceccarelli 		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 John Jullion-ceccarelli 2012-08-22 20:26:59 UTC 
This issue was reported manually by pjiricka.
It already has 2 duplicates 


Build: NetBeans IDE Dev (Build EaselCSS-537-on-20120822)
VM: Java HotSpot(TM) Client VM, 23.0-b21, Java(TM) SE Runtime Environment, 1.7.0_04-b20
OS: Windows 7

User Comments:
johnjullion: changed a property in the CSS, the change was applied but then connection with browser is broken. CSS styles view no longer populates, selection in chrome doesn't update DOM, etc.

GUEST: changing the value of an H1 element in the index.html file.  This error was thrown when I pressed Ctrl-S to save the changes.




Stacktrace: 
java.net.SocketException: Software caused connection abort: socket write error
   at java.net.SocketOutputStream.socketWrite0(SocketOutputStream.java:0)
   at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
   at java.net.SocketOutputStream.write(SocketOutputStream.java:132)
   at java.io.DataOutputStream.writeBytes(DataOutputStream.java:276)
   at org.netbeans.modules.web.clientproject.spi.webserver.WebServer$Server.read(WebServer.java:288)
   at org.netbeans.modules.web.clientproject.spi.webserver.WebServer$Server.run(WebServer.java:240)
Comment 1 John Jullion-ceccarelli 2012-08-22 20:27:02 UTC 
Created attachment 123426 [details]
stacktrace
Comment 2 Petr Jiricka 2012-08-22 20:58:55 UTC 
The exception itself may be harmless, but if all the features break, then that's something to worry about. 

The fact that everything is reloaded from scratch may be caused by Honza B's fix for 216988 - now if your CSS file is not open in the editor, it will be auto-saved after every change via the property sheet. As a workaround, can you try opening the CSS file in the editor before modifying it via the property sheet?
Comment 3 John Jullion-ceccarelli 2012-08-22 21:13:58 UTC 
Yup, if the CSS file is open the page does not autorefresh.
Comment 4 David Konecny 2012-08-22 21:45:07 UTC 
Re. CSS  - that's a different issue.

Re. SocketException - give me more info how to reproduce it. I'm 90% that problem happens when browser (WebView?) is "stacked" and is not accepting the data from web server it asked for. In any case the proper fix is to ignore this exception which I'm doing as web-main#1410773b764b.
Comment 5 Jan Becicka 2012-08-23 07:32:43 UTC 
(In reply to comment #3)
> Yup, if the CSS file is open the page does not autorefresh.

Autorefresh is invoked on save of any file. Not specific for CSS.
Comment 6 Quality Engineering 2012-09-03 12:54:55 UTC 
Integrated into 'main-golden', will be available in build *201209031048* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/1410773b764b
User: David Konecny <dkonecny@netbeans.org>
Log: #217249 - java.net.SocketException: Software caused connection abort: socket write error