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.
1. Create Visual Web Application. 2. Deploy it to Apache Tomcat 5.5.20 or higher. Note: The same was with applications created in Creator 2 and VWP 5.5. Result: Exception arises: "type: Exception report message description: The server encountered an internal error () that prevented it from fulfilling this request. exception: javax.servlet.ServletException: Servlet.init() for servlet Faces Servlet threw exception org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConn ection(Http11BaseProtocol.java:665) org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:5 28) org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorke rThread.java:81) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:6 85) java.lang.Thread.run(Unknown Source) root cause: java.lang.NullPointerException javax.faces.webapp.FacesServlet.init(FacesServlet.java:144) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConn ection(Http11BaseProtocol.java:665) org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:5 28) org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorke rThread.java:81) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:6 85) java.lang.Thread.run(Unknown Source)".
> Note: The same was with applications created in Creator 2 and VWP 5.5. Do you mean the same error also happened in Creator 2 and VWP 5.5? I.e., Creator2 and VWP 5.5 cannot deploy to Tomcat 5.5.20 or higher? Can you deploy NetBeans web project (with or without NetBeans JSF framework) to Tomcat 5.5.20? If you got the same issue, then this error should belong to either NetBeans web project or Tomcat.
Yes, I mean that applications, which was created in "Creator 2 Update 1" and in "NetBeans 5.5 + VWP" are also failed on Tomcat 5.5.20 or higher. I created web application with NetBeans JSF framework and then deploy it. I opened application in browser and first page (index.jsp) was opened, but when I had clicked link to JSP page with JSF, I got the same exception.
> but when I had clicked link to JSP page with JSF, I got the same exception. Looks like a general NetBeans server plugin issue.
Could this be a JSF version issue?
Roman, Is this a Java EE 5 project or a J2EE 1.4 project ? JSF 1.2 apps will not work on Tomcat 5.5.x
I think it's not the JSF version issue. When you select Tomcat as the target server, the J2EE version is restricted to 1.4 and hence JSF 1.1. The other reason I think so is, the created web application is working on Tomcat 5.5.17 that currently NetBeans bundled, but not the 5.5.20 mentioned.
> The other reason I think so is, the created web application is working on Tomcat 5.5.17 that currently NetBeans bundled, but not the 5.5.20 mentioned. Unless Tomcat 5.5.20 changes to J2EE 5 and only support JSF 1.2. Then the web project may need to update the New Project Wizard. (*.*.17 to *.*.20 should be minor that I don't think the above is true)
I have tested deployment do Tomcat 5.5.17, 5.5.20 and 5.5.23. All these servers seem to work correctly, please note that there is no difference in how the IDE accesses these servers. I have also tested the described scenario with the latest build of NetBeans with Visual Web Pack but I was not able to reproduce the issue. Reassigning back to visualweb for further evaluation since it seems that the Tomcat module is not the culprit in this case. to: romanmostyka It would be useful if you could provide more info. Please specify which version of JSF do you use and whether deployment to the bundled Tomcat 5.5.17 works or not. Thanks
1) Please specify which version of JSF do you use. I created standard J2EE 1.4 Visual Web Application and hence version of JSF have to be 1.1. 2) Whether deployment to the bundled Tomcat 5.5.17 works or not. Deployment to the bundled Tomcat 5.5.17 and to standalone Tomcat 5.5.17 ol lower works fine.
OK, then it looks like the issue was already fixed, since I am not able to reproduce it. Roman or Poting, could you please verify that the issue is not reproducible in the latest builds?
sherold wrote > Reassigning back to visualweb for further evaluation since it seems that the Tomcat module is not the culprit in this case. romanmostyka wrote: >> I created web application with NetBeans JSF framework and then deploy it. I opened application in browser and first page (index.jsp) was opened, but when I had clicked link to JSP page with JSF, I got the same exception. This is not a visual web specific issue. romanmostyka has the same issue when just using NetBeans web project + NetBeans JSF framework (without touching any visual web). sherold wrote > OK, then it looks like the issue was already fixed, since I am not able to reproduce it. No, romanmostyka said it works for Tomcat 5.5.17 and lower, but NOT higher (e.g., 5.5.20).
I talked about latest build of NetBeans not Tomcat. The issue was failed against NetBeans 5.5 and I am not able to reproduce the issue in the latest dev builds. Can you please verify that the issue is still reproducible?
> I talked about latest build of NetBeans not Tomcat. The issue was failed against NetBeans 5.5 and I am not able to reproduce the issue in the latest dev builds.
I installed NetBeans 5.5 (build 200611140100) + VWP 5.5 (build 070322_1), NetBeans 5.5.1 (build 200703050600) + VWP 5.5.1 (build 070321_1) and NetBeans 6.0 (build 200703211900) + VWP 6.0 (build 070322_11). I also installed Apache Tomcat 5.5.23 and added it to all of installed NetBeans versions. I used Java 1.5.0_08 for all of them. Then: 1) Start NetBeans 5.5, create Visual Web Application, set J2EE 1.4 and target server Tomcat 5.5.23, add 'Button' component to the page and deploy application. And got the same exception. 2) Start NetBeans 5.5.1, create Visual Web Application, set J2EE 1.4 and target server Tomcat 5.5.23, add 'Button' component to the page and deploy application. And got the same exception. 3) Start NetBeans 6.0, create Web Application, set J2EE 1.4 and target server Tomcat 5.5.23 and check only "Visual Web JSF" framework, add 'Button' component to the page and deploy application. And also got the same exception.
Created attachment 39859 [details] Logs
Roman, can you please verify what Poting says that this issue is not Visual Web Pack specific? Are you able to reproduce this issue with NetBeans without the Visual Web Pack?
I installed NetBeans 6.0 (build 200703221900) without VWP, started it, create Web Application, set J2EE 1.4 and target server Tomcat 5.5.23 and check only "JavaServer Faces" framework, deploy application. index.jsp was successfully loaded in browser, but when I click "JavaServer Faces Welcome Page" link, I got the same exception.
Can't reproduce neither in NB 5.5.1 with 5.5.23 nor in NB 6.0.
Roman, can you please attach Tomcat server output and Tomcat server log? The output and the log are opened automatically in the NB output window after the server is started. Please, do not forget to reproduce the issue before attaching the logs so that the exceptions will be logged there.
Created attachment 39884 [details] Tomcat Output and Tomcat Log
romanmostyka wrote: > I installed NetBeans 6.0 (build 200703221900) without VWP, started it, create > Web Application, set J2EE 1.4 and target server Tomcat 5.5.23 and check only > "JavaServer Faces" framework, deploy application. > index.jsp was successfully loaded in browser, but when I click "JavaServer Faces > Welcome Page" link, I got the same exception. Since it's a general NetBeans+JSF issue, reassign to tomcatint.
This is Tomcat issue http://issues.apache.org/bugzilla/show_bug.cgi?id=40809 . Decreasing priority to P2 and assigning keyword.
Setting the TM to 6.0, hopefully Tomcat will fix it in time..
Marking the issue as WONTFIX, since it must be fixed in the server itself. You can track the status of this issue in bugzilla http://issues.apache.org/bugzilla/show_bug.cgi?id=40809.