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 125433 - HTTP Monitor seems to be causing some warnings in output window
Summary: HTTP Monitor seems to be causing some warnings in output window
Status: REOPENED
Alias: None
Product: javaee
Classification: Unclassified
Component: HTTP Monitor (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker with 1 vote (vote)
Assignee: Petr Jiricka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-16 20:44 UTC by rdelaplante
Modified: 2017-09-27 19:50 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rdelaplante 2008-01-16 20:44:33 UTC
I stopped Glassfish from within the IDE, closed the IDE, then opened the IDE again.  I used Plugins manager to install 
the new woodstock 4.1.1 upgrade, then restarted the IDE again (it wanted to).  I started GlassFish from the Services 
tab, then redeployed my app.
Whenever I access a page, I now get this error in my output window:

WARNING *********** NetBeans HTTP Monitor ************
The request cannot be recorded most likely because the NetBeans HTTP Server is not running. Go to the IDE and start 
the HTTP Server from within the Runtime window to fix this problem.


In Tools --> Servers --> Sun Java System Application Server 9.1, I see  that "Enable HTTP Monitor" is not checked -- I 
did that a few days ago because it can be annoying when I do not need to use it.  This error message in the output 
window didn't happen until just now after upgrading Woodstock. 


I re-enabled the HTTP Monitor in Servers tab, then restarted the app server within NetBeans.  No more of those 
messages, but I do get the following on every page:

> PWC4011: Unable to set request character encoding to UTF-8 from context , because request parameters have already 
been read, or ServletRequest.getReader() has already been called


This has been happening for so many months that I've been ignoring it.
Next I turned HTTP Monitor off again in servers tab, restarted the app server again, and no no errors whatsoever when 
accessing pages.

Next I re-enabled the HTTP Monitor in servers tab, restarted app server again,  and get the following warnings again 
for each page:

> PWC4011: Unable to set request character encoding to UTF-8 from context , because request parameters have already 
been read, or ServletRequest.getReader() has already been called
Comment 1 Milan Kuchtiak 2008-01-18 11:48:19 UTC
The first warning is strange. The HTTP Monitor behaves like it cannot open connection to the small IDE's local HTTP
server, that is used to log requests to the server (e.g. GlassFish).
It might have happened, there was a port colision - IDE's local HTTP server is defaultly running on port 8082.

The second warning comes from GlassFish application server.
It's likely related to request.setCharacterEncoding() method.
(see also https://glassfish.dev.java.net/issues/show_bug.cgi?id=3551)

Most likely the monitor filter (part of HTTP Monitor) does something that triggers the warning.
The monitor filter reads the request parameters and sends them to IDE's local HTTP server.
Thare might be a problem that character encoding is set afterwards.

Comment 2 _ gtzabari 2008-12-01 20:09:12 UTC
Just a thought: is it possible to read the request parameters after the request ends (when control returns to your
filter)? Or is it possible the underlying application will modify them?
Comment 3 Petr Jiricka 2009-11-02 14:35:43 UTC
The first issue happens typically whenever the server is started outside of the IDE. There was a related issue 109175,
that the warning about the inability to connect to NetBeans was logged on every request. That is now fixed, and this
(otherwise harmless) warning is only printed once.

The second issue was fixed on the GlassFish side in GF 2.1 (this report was originally against GF 2.0, right?). So can
you please try with the latest GlassFish? Thanks.

Comment 4 rdelaplante 2009-11-02 14:40:04 UTC
I haven't seen this problem for a long time.  I'm now using NB 6.7.1 and GF 2.1 on OpenSolaris and do not have this
problem. 
Comment 5 Petr Jiricka 2009-11-02 14:46:28 UTC
Hi Ryan, thanks for a prompt reply, I am marking as fixed.
Comment 6 thaotor 2011-06-22 12:56:55 UTC
I have the same error with tomcat7.0.11 using netbeans 7.0

22-giu-2011 14.43.53 org.zkoss.util.resource.impl.LabelLoader loadLabels:229
INFO: Loading labels for it
22-giu-2011 14.43.53 org.zkoss.util.resource.impl.LabelLoader load:366
INFO: Opening jndi:/localhost/gbs/WEB-INF/i3-label_it.properties
22-giu-2011 14.43.53 org.zkoss.util.resource.impl.LabelLoader load:366
INFO: Opening jndi:/localhost/gbs/WEB-INF/i3-label.properties
WARNING *********** NetBeans HTTP Monitor ************
The request cannot be recorded most likely because the NetBeans HTTP Monitor module is disabled.
Comment 7 Martin Balin 2016-07-07 08:56:32 UTC
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss
Comment 8 JohaKlotz 2017-05-28 12:37:43 UTC
Still getting this warning on 8.2 (64bits, with tomcat).
Comment 9 JohaKlotz 2017-05-28 12:38:13 UTC
Still getting this warning on 8.2 (64bits, with tomcat).
Comment 10 stanleyshi 2017-09-27 19:50:27 UTC
Today I got the same warning on GlassFish 4.1.1 as follows:

Info:   mClaimDBtest17092701 was successfully deployed in 1,796 milliseconds.
Info:   WARNING *********** NetBeans HTTP Monitor ************
The request cannot be recorded most likely because the NetBeans HTTP Monitor module is disabled.