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.
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.
Created attachment 50448 [details] NetBeans projects which are causing the deployment issue
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.
And the easy fix will probably break the "save and reload" development style for JSP's that so many enjoy...
I could not reproduce this on Solaris.
another possible work-around. turn off directory deployment. use 'undeploy and deploy' item.
Could you please elaborate on the workaround you mentioned? What you mean "by turn off directory deployment." I do not see that option anywhere.
http://blogs.sun.com/vkraemer/entry/new_glassfish_integration_feature_new
parallel GF issue: https://glassfish.dev.java.net/issues/show_bug.cgi?id=3767
this may require a server side fix. V2 update 1 would be the release vehicle for those fixes.
the parallel GF issue has been updated... the GF engineers have the issue isolated in ServiceLocator...
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.
Here is the JDK bug http://bugs.sun.com/view_bug.do?bug_id=6587593
The root cause appears to be a bug in the JDK. The work-around is to avoid the ServiceLocator or stop using directory deployment.
Created attachment 51960 [details] NetBeans projects with updated servlet code
The waiver for 6.0 is approved.
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.
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.
starting to work with a jdk team member to resolve the root cause.
a jdk engineer has started on the fix for this, but the deliver "vehicle" for their change is undetermined at this point.
past the 48 hour mark
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.