Using the latest daily builds with the integrated Tomcat 7.0.22, I receive the following message many, many times in the log output of the webapp (which I have never received):
"MonitorFilter::WARNING: the monitor filter must be the first filter in the chain."
I cannot detect any exception message besides that in NB nor have I done any configuration changes (I am aware off) neither to NB nor my web app.
How can I help to make you able to reporduce?
I'm having the same problem. I think it begun when add Spring Security filters.
Do you have HTTP monitor option enabled in server properties? Do you use it?
Since I opened the bug, I have been changing my environment to a clean NetBeans dailies installation (for NetCAT) as well as to a clean Tomcat installation, and the error currently does not appear anymore. Before, when the bug did appear, I had created a new Tomcat server instance in the services tab and added "-Xmx1024m -XX:MaxPermsize=256m" as runtime arguments for the server.
I also see this in logs, Tomcat 7.0.32
HTTP monitor is enabled in options, neither of colleague who uses eclipse has this warning, so i suppose there is something wrong with netbeans
Product Version: NetBeans IDE Dev (Build 201211010001)
Java: 1.7.0_05; Java HotSpot(TM) 64-Bit Server VM 23.1-b03
Runtime: Java(TM) SE Runtime Environment 1.7.0_05-b06
System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
Well AFAIK monitor is implemented as javax.servlet.Filter. Perhaps you have some other filter deployed before this one. And message is warning about that. If you do not use HTTP monitor just disable it in server properties.