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 214679 - java.util.concurrent.TimeoutException at java.util.concurrent.FutureTask$Sync.innerGet
Summary: java.util.concurrent.TimeoutException at java.util.concurrent.FutureTask$Sync...
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-25 04:02 UTC by Exceptions Reporter
Modified: 2012-10-18 18:23 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 190008

Attachments
stacktrace (430 bytes, text/plain)
2012-06-25 04:02 UTC, Exceptions Reporter 		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 Exceptions Reporter 2012-06-25 04:02:39 UTC 
This bug was originally marked as duplicate of bug 210062, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 6.8 Beta (Build 200910212001)
VM: Java HotSpot(TM) Client VM, 20.7-b02, Java(TM) SE Runtime Environment, 1.6.0_32-b05
OS: Windows 7

User Comments:
GUEST: compiling




Stacktrace: 
java.util.concurrent.TimeoutException
   at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:228)
   at java.util.concurrent.FutureTask.get(FutureTask.java:91)
   at org.netbeans.modules.glassfish.javaee.ide.UpdateContextRoot$1.run(UpdateContextRoot.java:90)
   at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:602)
   at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1084)
Comment 1 Exceptions Reporter 2012-06-25 04:02:45 UTC 
Created attachment 121268 [details]
stacktrace
Comment 2 TomasKraus 2012-10-18 18:23:02 UTC 
This should be simply ignored.
Exception is correctly handled and logged in 7.3 so it's no more an issue.
Looks like GlassFish was just not running when this was invoked.