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 183804 - Distributing to Glassfish failing in Netbeans 6.8
Summary: Distributing to Glassfish failing in Netbeans 6.8
Status: RESOLVED INCOMPLETE
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-09 18:56 UTC by mrollis
Modified: 2011-01-28 20:00 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Netbeans Log (189.79 KB, application/octet-stream)
2010-04-09 21:25 UTC, mrollis 		Details
glassfish log (1014.74 KB, application/octet-stream)
2010-04-09 21:27 UTC, mrollis 		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 mrollis 2010-04-09 18:56:23 UTC 
Distributing to Glassfish 3.0 is inconsistent. Many times the following error comes up. If Netbeans crashes then the next time I deploy it works. I have tried resetting permissions and have checked ant. 

-run-deploy-nb:
Distributing D:\StrategicBudgetingWeb\dist\StrategicBudgetingWeb.ear to [GlassFish v3]
Initializing...
deploy?path=D:\StrategicBudgetingWeb\dist\StrategicBudgetingWeb.ear&name=StrategicBudgetingWeb&force=true failed on GlassFish v3
D:\StrategicBudgetingWeb\nbproject\build-impl.xml:283: The module has not been deployed.
        at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:134)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
        at sun.reflect.GeneratedMethodAccessor180.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:498)
        at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
BUILD FAILED (total time: 12 seconds)
Comment 1 Vince Kraemer 2010-04-09 19:26:07 UTC 
Can you attach the server and ide log files that when this happens again?

Is the server that you are deploying to a 'remote' domain?
Comment 2 mrollis 2010-04-09 21:25:59 UTC 
Created attachment 96992 [details]
Netbeans Log
Comment 3 mrollis 2010-04-09 21:27:13 UTC 
Created attachment 96993 [details]
glassfish log
Comment 4 mrollis 2010-04-09 21:36:10 UTC 
The server is a remote server.
Comment 5 Vince Kraemer 2010-04-29 05:20:41 UTC 
do you think we should close this issue as a dup of bug 178471, based on your comment http://netbeans.org/bugzilla/show_bug.cgi?id=178471#c3
Comment 6 Vince Kraemer 2010-04-29 05:21:27 UTC 
disregard comment 5...
Comment 7 Vince Kraemer 2010-05-13 00:03:17 UTC 
the stack traces in the server log look like they are coming from the monitoring code...

Do you have monitoring set to LOW or HIGH for some of the components like the EJB Container?

Do you have a stand-alone project that demonstrates the issue?

Can you outline the steps that you use to recreate this?
Comment 8 Vince Kraemer 2011-01-28 20:00:43 UTC 
info request not answered.

Reopen this issue with the requested info and current NetBeans and GlassFish logs if this is still an issue that you encounter with recent builds of NetBeans 7.0