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 230302 - java.io.IOException: Periodo di timeout del semaforo scaduto
Summary: java.io.IOException: Periodo di timeout del semaforo scaduto
Status: RESOLVED INCOMPLETE
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Jan Lahoda
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-27 08:07 UTC by williambacchi
Modified: 2013-05-27 10:47 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 200940

Attachments
stacktrace (2.65 KB, text/plain)
2013-05-27 08:07 UTC, williambacchi 		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 williambacchi 2013-05-27 08:07:29 UTC 
Build: NetBeans IDE Dev (Build 201305232300)
VM: Java HotSpot(TM) Client VM, 23.21-b01, Java(TM) SE Runtime Environment, 1.7.0_21-b11
OS: Windows XP

User Comments:
williambacchi: running a web application




Stacktrace: 
java.io.IOException: Periodo di timeout del semaforo scaduto
   at java.io.FileOutputStream.writeBytes(FileOutputStream.java:0)
   at java.io.FileOutputStream.write(FileOutputStream.java:318)
   at org.openide.filesystems.FileUtil.copy(FileUtil.java:549)
   at org.netbeans.modules.java.source.usages.BuildArtifactMapperImpl.copyFile(BuildArtifactMapperImpl.java:451)
   at org.netbeans.modules.java.source.usages.BuildArtifactMapperImpl.classCacheUpdated(BuildArtifactMapperImpl.java:410)
   at org.netbeans.modules.java.source.usages.ClassIndexEventsTransaction.commit(ClassIndexEventsTransaction.java:218)
Comment 1 williambacchi 2013-05-27 08:07:32 UTC 
Created attachment 134932 [details]
stacktrace
Comment 2 Tomas Zezula 2013-05-27 10:47:28 UTC 
Please if you are able to reproduce we need to know who holds the loch or opened handler on the file.
This can be easily find out by MS Process Monitor, http://technet.microsoft.com/en-us/sysinternals/bb896645