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 169260 - Exception occurs when dedploy JMS Web Project
Summary: Exception occurs when dedploy JMS Web Project
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
: 169596 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-07-27 19:55 UTC by davisn
Modified: 2009-09-14 22:57 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
messages.log (55.75 KB, text/plain)
2009-07-27 19:56 UTC, davisn
Details
server.log (7.94 KB, text/plain)
2009-07-27 19:57 UTC, davisn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description davisn 2009-07-27 19:55:35 UTC
-java.util.concurrent.TimeoutException occurs when deploy a Web Project which has JMS Resource
-This problem happens on winXP and Mac OSX platforms

Steps To Reproduce:
1. Install NB trunk 07/27/2009 build
2. Start IDE -> expand the Server node to activate Java EE component (do not start the server)
3. Create a Web Module (use all default)
4. Right-click at the web project, select new -> other -> Glassfish -> JMS Resource -> Next -> Next -> enter 123 value
for Name field -> Finish
5. Right-click at the web proejct, select Run menu
BUG:
    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.db.ResourcesHelper.registerResourceDir(ResourcesHelper.java:241)
	at
org.netbeans.modules.glassfish.javaee.Hk2MessageDestinationManager.deployMessageDestinations(Hk2MessageDestinationManager.java:111)
	at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.deployMessageDestinations(ServerInstance.java:764)
	at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deployMessageDestinations(Deployment.java:300)
	at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:190)
	at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:135)
	at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:103)
	at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
	at sun.reflect.GeneratedMethodAccessor76.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
	at org.apache.tools.ant.Task.perform(Task.java:348)
	at org.apache.tools.ant.Target.execute(Target.java:357)
	at org.apache.tools.ant.Target.performTasks(Target.java:385)
	at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
	at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
	at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
	at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
	at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:278)
	at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:497)
[catch] at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
Comment 1 davisn 2009-07-27 19:56:09 UTC
Created attachment 85271 [details]
messages.log
Comment 2 davisn 2009-07-27 19:57:13 UTC
Created attachment 85272 [details]
server.log
Comment 3 Nitya Doraisamy 2009-07-30 19:17:45 UTC

*** This issue has been marked as a duplicate of 169596 ***
Comment 4 davisn 2009-07-30 23:28:41 UTC
This bug is opened earlier than #169596 and beside it's a P2? 
Comment 5 Nitya Doraisamy 2009-07-31 00:02:08 UTC
OK. Marking 169596 as duplicate of this. I had thought both were P2's
Comment 6 Nitya Doraisamy 2009-07-31 00:02:31 UTC
Register of resources needs to wait for server startup completion when deploy is initiated on stopped server. 
Comment 7 Nitya Doraisamy 2009-07-31 00:02:37 UTC
*** Issue 169596 has been marked as a duplicate of this issue. ***
Comment 8 Vince Kraemer 2009-09-14 22:57:19 UTC
I could not reproduce this with a recent trunk build.

The most likely reason is the changes that I did in this commit: http://hg.netbeans.org/web-main/rev/442c42bf3b87

I am going to mark this as FIXED.

Reopen if you run into it again.