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 118164 - Runtime error when using Web Module deployment
Summary: Runtime error when using Web Module deployment
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P2 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-08 23:45 UTC by Chris Webster
Modified: 2008-06-20 20:28 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
NetBeans projects which are causing the deployment issue (37.72 KB, application/octet-stream)
2007-10-08 23:48 UTC, Chris Webster
Details
NetBeans projects with updated servlet code (38.18 KB, application/octet-stream)
2007-10-30 03:07 UTC, Chris Webster
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Webster 2007-10-08 23:45:56 UTC
The attached NetBeans projects have a problem the second time a deployment occurs. The exact sequence which causes the
problem is as follows:

1. Open the web module project and deploy the project, verify that WebApplication1/NewServlet context works as expected,
the url should be similar to (http://localhost:8080/WebApplication1/NewServlet). 

2. Open the dependent project test and edit the file org.acme.impl.Executor, can be anything the easiest is to change
the toString method. 

3. Deploy using NetBeans.

4. Now visit the same URL as in 1 and you will notice an exception which is similar to the following:

Caused by: java.io.FileNotFoundException: JAR entry META-INF/services/org.api.ExecutorFactory not found in
C:\NetBeansProjects\WebApplication1\build\web\WEB-INF\lib\test.jar

This problem requires restarting the Server, where the app will continue to work as expected. The problem also seems to
occur if the test project is changed. 

This was using JSE 1.6_02 with NetBeans 6 beta1 and the glassfish installed with the NetBeans installation. I have only
verified this on windows, haven't tried with other platforms.
Comment 1 Chris Webster 2007-10-08 23:48:02 UTC
Created attachment 50448 [details]
NetBeans projects which are causing the deployment issue
Comment 2 Vince Kraemer 2007-10-09 22:26:20 UTC
work-around: put the web app into an Enterprise Application project. Secondary runs are fine then.

This work-around indicates that there may be a pretty easy fix.
Comment 3 Vince Kraemer 2007-10-09 23:20:58 UTC
And the easy fix will probably break the "save and reload" development style for JSP's that so many enjoy...  

Comment 4 Vince Kraemer 2007-10-11 19:19:40 UTC
I could not reproduce this on Solaris.
Comment 5 Vince Kraemer 2007-10-11 21:07:13 UTC
another possible work-around.  turn off directory deployment. use 'undeploy and deploy' item.
Comment 6 Girish Balachandran 2007-10-11 21:53:49 UTC
Could you please elaborate on the workaround you mentioned? What you mean "by turn off directory deployment." I do not
see that option anywhere.
Comment 8 Vince Kraemer 2007-10-15 05:13:24 UTC
parallel GF issue: https://glassfish.dev.java.net/issues/show_bug.cgi?id=3767
Comment 9 Vince Kraemer 2007-10-16 16:24:43 UTC
this may require a server side fix. V2 update 1 would be the release vehicle for those fixes.
Comment 10 Vince Kraemer 2007-10-24 17:35:29 UTC
the parallel GF issue has been updated... the GF engineers have the issue isolated in ServiceLocator...
Comment 11 Vince Kraemer 2007-10-25 17:10:16 UTC
There is an updated version of the NewServlet.java file in the parallel GF issue which resolves this... I think.

https://glassfish.dev.java.net/issues/show_bug.cgi?id=3767

The engineers that worked the issue are claiming that there is a bug in ServiceLocator.
Comment 12 Vince Kraemer 2007-10-25 23:24:44 UTC
Here is the JDK bug http://bugs.sun.com/view_bug.do?bug_id=6587593
Comment 13 Vince Kraemer 2007-10-25 23:26:10 UTC
Here is the JDK bug http://bugs.sun.com/view_bug.do?bug_id=6587593
Comment 14 Vince Kraemer 2007-10-25 23:44:35 UTC
The root cause appears to be a bug in the JDK.  The work-around is to avoid the ServiceLocator or stop using directory
deployment.
Comment 15 Chris Webster 2007-10-30 03:07:31 UTC
Created attachment 51960 [details]
NetBeans projects with updated servlet code
Comment 16 Petr Jiricka 2007-10-30 10:01:37 UTC
The waiver for 6.0 is approved.
Comment 17 Chris Webster 2007-10-30 16:56:22 UTC
The suggested patch doesn't appear to be effective. I have tried the project with the updated servlet code and I am
seeing the same issue described in the original bug report. The attached project url is slightly different
http://localhost:8080/WebApplication1/Servlet. 
Comment 18 Chris Webster 2007-10-30 18:11:02 UTC
I also just tried to go the Glassfish server options and uncheck the directory deployment enabled checkbox. I am getting
a similar error message, although the reference is in the glassfish domain area instead of the NetBeans project. 
Comment 19 Vince Kraemer 2008-02-01 21:13:39 UTC
starting to work with a jdk team member to resolve the root cause.
Comment 20 Vince Kraemer 2008-02-14 19:33:41 UTC
a jdk engineer has started on the fix for this, but the deliver "vehicle" for their change is undetermined at this point.
Comment 21 Vince Kraemer 2008-02-20 16:17:39 UTC
past the 48 hour mark
Comment 22 Vince Kraemer 2008-06-20 20:28:33 UTC
I have a 6.5 dev build from 20080616.

i have jdk 6 update 6

I have gf v2 ur 2.

I am not able to reproduce this issue on Windows Vista.

Please reopen and clarify the directions on how to reproduce this issue if you are still running into this.