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.
This bug was originally marked as duplicate of bug 186968, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related. Build: NetBeans IDE 8.0.1 (Build 201408251540) VM: Java HotSpot(TM) 64-Bit Server VM, 25.25-b02, Java(TM) SE Runtime Environment, 1.8.0_25-b18 OS: Windows 7 User Comments: terje7601: I guess it occurred when starting Tomcat (which failed btw, because Tomcat failed to stop before) Stacktrace: java.lang.IllegalStateException: Output file has been disposed! at org.netbeans.core.output2.OutWriter.getStorage(OutWriter.java:129) at org.netbeans.core.output2.OutWriter$LinesImpl.getStorage(OutWriter.java:765) at org.netbeans.core.output2.AbstractLines.getByteSize(AbstractLines.java:220) at org.netbeans.core.output2.AbstractLines.getCharCount(AbstractLines.java:351) at org.netbeans.core.output2.OutputDocument.getLength(OutputDocument.java:150) at javax.swing.text.DefaultCaret.handleSetDot(DefaultCaret.java:1162)
Created attachment 150350 [details] stacktrace
I'm sorry, I cannot reproduce this bug. Did you try to close Output Window (or some output tab), or was it closed automatically? Thank you for reporting.
(In reply to Jaroslav Havlin from comment #2) > I'm sorry, I cannot reproduce this bug. > > Did you try to close Output Window (or some output tab), or was it closed > automatically? > > Thank you for reporting. To be honest, I can't remember what I did exactly. I was messing around with Tomcat & suddenly this error appeared. I probably did "Close all output tabs" right before starting Tomcat though. And I remember deleting all Tomcat log files outside of NetBeans (i.e. using Windows Explorer) at some point, so maybe NetBeans got confused that it suddenly couldn't find those files anymore. Anyway, none of this isn't very helpful, I guess. I will try to reproduce it next week at work. But I haven't had this error before & haven't had it since, so it's a very particular bug.
I've been trying to reproduce this, but failed to do so...
Thank you very much for help. It seems that this bug occurs quite seldom, and under specific conditions, so we can set lower priority.
*** Bug 250405 has been marked as a duplicate of this bug. ***