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 109891 - Fatal Error when bundled GlassFish starts
Summary: Fatal Error when bundled GlassFish starts
Status: RESOLVED WONTFIX
Alias: None
Product: ide
Classification: Unclassified
Component: Schema2Beans (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P4 blocker (vote)
Assignee: schema2beans-issues@ide
URL:
Keywords:
: 112584 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-07-16 18:39 UTC by Roman Mostyka
Modified: 2009-12-21 06:03 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
IDE's log (50.21 KB, text/plain)
2007-07-16 18:40 UTC, Roman Mostyka 		Details
Ziped $NB_USERDIR/config/HTTPMonitor folder. (3.27 KB, application/octet-stream)
2007-07-17 13:26 UTC, Roman Mostyka 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Mostyka 2007-07-16 18:39:37 UTC 
1. Install 'Standard' package.
2. Start IDE.
3. Start GlassFish.

Result: There is exception in message.log:
"[Fatal Error] :2:123: The character reference must end with the ';' delimiter.
INFO [global]
java.io.IOException".
Comment 1 Roman Mostyka 2007-07-16 18:40:15 UTC 
Created attachment 45154 [details]
IDE's log
Comment 2 Vince Kraemer 2007-07-17 01:53:31 UTC 
Is there something the plugin can do to resolve this?  Reassign with advice.
Comment 3 Sherold Dev 2007-07-17 09:44:11 UTC 
The 'fatal error' message comes from schema2beans. It seems that one of the recorded HTTP requests cannot be loaded from
XML.

Changing the priority to P3.

Roman, can you please zip and attach the $NB_USERDIR/config/HTTPMonitor folder after this issue occurs again?
Comment 4 Roman Mostyka 2007-07-17 13:25:08 UTC 
$NB_USERDIR/config/HTTPMonitor in attach.
And this issue is always reproducible.
Comment 5 Roman Mostyka 2007-07-17 13:26:04 UTC 
Created attachment 45206 [details]
Ziped $NB_USERDIR/config/HTTPMonitor folder.
Comment 6 Sherold Dev 2007-07-17 15:25:15 UTC 
It looks like the culprit is most likely the GlassFish server.

HTTP Monitor filter obtains the request method by calling HttpServletRequest.getMethod(). Expected value is GET, POST,
etc., but the real value provided by the server is a mess, see the value of the method attribute of the MonitorData
element in the recorded request (HTTPMonitor.zip/HTTPMonitor/current/1184674996187.xml).

Reassign to Vince, just to make sure that the GlassFIsh plugin is not involved in this.
Comment 7 Vince Kraemer 2007-07-17 21:18:32 UTC 
The request that is causing this comes from the plugin.  The strange request is used to determine if the server at the
address and port given is speaking http or https.  If the server's admin port is "secured", the message doesn't get
logged, since the networking code figures out that needs to respond to this strangeness BEFORE the data gets sent into
the HTTP layer and gets intercepted by the monitor...  If the port is not secured, the request makes it into the http
layer... and we end up with this strange error.

1. turn off autodetection - would need to add user interaction to pick the http flavor associated with a server... BAD

2. find a way to not associate the http monitor with the admin listener... this looks like it requires an extension to
the monitor.

3. extend the http monitor to not barf when it gets some strange data...
Comment 8 Vince Kraemer 2007-07-17 21:25:14 UTC 
The request that is causing this comes from the plugin.  The strange request is used to determine if the server at the
address and port given is speaking http or https.  If the server's admin port is "secured", the message doesn't get
logged, since the networking code figures out that needs to respond to this strangeness BEFORE the data gets sent into
the HTTP layer and gets intercepted by the monitor...  If the port is not secured, the request makes it into the http
layer... and we end up with this strange error.

1. turn off autodetection - would need to add user interaction to pick the http flavor associated with a server... BAD

2. find a way to not associate the http monitor with the admin listener... this looks like it requires an extension to
the monitor.

3. extend the http monitor to not barf when it gets some strange data...
Comment 9 Sherold Dev 2007-07-18 13:11:26 UTC 
Please note that there is no real user impact of this issue, the only side effect are the error messages in the log.
Those messages can be ignored.


The proper place for fixing this issue is schema2beans, illegal characters stored in the model should be automatically
escaped.

Reassigning the issue....
Comment 10 Sherold Dev 2007-08-13 09:15:15 UTC 
*** Issue 112584 has been marked as a duplicate of this issue. ***
Comment 11 Erno Mononen 2007-10-16 14:07:29 UTC 
I'm setting the target milestone to future as this has no impact on functionality and doing changes in schema2beans at 
this point is a bit risky.
Comment 12 Erno Mononen 2008-06-20 15:40:31 UTC 
Downgrading to P4 as the issue has no user impact.
Comment 13 Quality Engineering 2009-12-21 06:03:49 UTC 
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. 

We apologize for any inconvenience.


Thank you.
The NetBeans Team