You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2016/05/25 11:31:58 UTC
[Bug 59632] New: HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
Bug ID: 59632
Summary: HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Product: JMeter
Version: 2.13
Hardware: PC
Status: NEW
Severity: major
Priority: P2
Component: HTTP
Assignee: issues@jmeter.apache.org
Reporter: Shivanshshah.shah94@gmail.com
Created attachment 33888
--> https://bz.apache.org/bugzilla/attachment.cgi?id=33888&action=edit
Failed to Parse HTML : NULL error message is displayed.
When trying to LOGIN into the application , the user is navigated to the
Dashboard of the application ,but when trying to view the response in HTML
format the "Failed to Parse HTML : NULL" error message is displayed.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59632] HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
--- Comment #6 from Shivansh <Sh...@gmail.com> ---
Created attachment 33900
--> https://bz.apache.org/bugzilla/attachment.cgi?id=33900&action=edit
Text Output for Error Page
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59632] HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
Shivansh <Sh...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS| |All
--- Comment #2 from Shivansh <Sh...@gmail.com> ---
I am Testing it on my Local server , so no such link is available for it.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59632] HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
--- Comment #12 from Felix Schumacher <fe...@internetallee.de> ---
Created attachment 33902
--> https://bz.apache.org/bugzilla/attachment.cgi?id=33902&action=edit
Example jmx with minimal html code to reproduce issue
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59632] HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
--- Comment #13 from Felix Schumacher <fe...@internetallee.de> ---
Created attachment 33903
--> https://bz.apache.org/bugzilla/attachment.cgi?id=33903&action=edit
Stacktrace of the exception, that jmeter can catch
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59632] HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
--- Comment #5 from Sebb <se...@apache.org> ---
(In reply to Shivansh from comment #4)
> Can i help you by providing some other details.
Can you attach the HTML page for the URL that fails?
If that page contains sensitive information, feel free to redact it first, so
long as the updated page still causes the issue.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59632] HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
--- Comment #11 from Sebb <se...@apache.org> ---
(In reply to Shivansh from comment #9)
> If your point is correctly then can you please tell me that how come the
> application is working correctly on Google chrome and other Browsers .
Browsers are generally very lenient when parsing HTML.
There's nothing that JMeter can do here other than display better info about
the error. It relies on the Java runtime for parsing the HTML.
Note that lenient parsing relies on making assumptions about what the causes of
errors are and how to fix them. If the browser makes the wrong assumptions, the
page may still look OK, but may have subtle incorrect behaviour changes.
The proper solution is to fix the page so that the HTML is valid.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59632] HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
--- Comment #4 from Shivansh <Sh...@gmail.com> ---
Can i help you by providing some other details.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59632] HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
--- Comment #9 from Shivansh <Sh...@gmail.com> ---
If your point is correctly then can you please tell me that how come the
application is working correctly on Google chrome and other Browsers .
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59632] HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
--- Comment #14 from Felix Schumacher <fe...@internetallee.de> ---
Created attachment 33904
--> https://bz.apache.org/bugzilla/attachment.cgi?id=33904&action=edit
Stacktrace that gets written to stdout by jdk
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59632] HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
--- Comment #8 from Felix Schumacher <fe...@internetallee.de> ---
The attached HTML Page has a few syntax errors. One is an unbalanced quote (").
That leads to an RuntimeException, that is thrown in
javax.swing.text.html.CSSParser#readTill. That exception bubbles up the
callstack and is caught by javax.swing.text.html.Parser#parse by the following
construct:
} catch (IOException e) {
errorContext();
error("ioexception");
throw e;
} catch (Exception e) {
errorContext();
error("exception", e.getClass().getName(), e.getMessage());
e.printStackTrace();
} catch (ThreadDeath e) {
errorContext();
error("terminated");
e.printStackTrace();
throw e;
As you can see, the RuntimeException gets caught as an Exception and it is
printed on the console, but does not get propagated - which is probably an
error in the jdk.
The parsing continues and leads now to another Exception in
java.util.Stack#peek. An EmptyStackException gets thrown, which has no message.
That exceptions message (null) is printed.
We could change the jmeter code to display the full exception when the message
is null, but I think the real culprit is the jdk.
The OP should probably correct the HTML and all is well (for him at least).
I will attach the two stacktraces and a simple test to reproduce the issue.
Just run it in jmeter, got to the tree view and try to display the sample as
html.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59632] HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
--- Comment #3 from Shivansh <Sh...@gmail.com> ---
In Jmeter Log file no such message is displayed.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59632] HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
Sebb <se...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #33903|text/x-log |text/plain
mime type| |
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59632] HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
--- Comment #7 from Shivansh <Sh...@gmail.com> ---
I have attached a Text File with containing the output in Text Format kindly
check & Tell if it provides any help to u in understanding the source of
problem.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59632] HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |p.mouawad@ubik-ingenierie.c
| |om
--- Comment #15 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Shouldn't we report a bug to Oracle ?
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59632] HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
Sebb <se...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #33904|text/x-log |text/plain
mime type| |
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59632] HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
--- Comment #1 from Sebb <se...@apache.org> ---
Comment on attachment 33888
--> https://bz.apache.org/bugzilla/attachment.cgi?id=33888
Failed to Parse HTML : NULL error message is displayed.
This is impossible to debug without further info.
Are there any related messages in the jmeter.log file?
What is the URL for the page?
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59632] HTML format the "Failed to Parse HTML : NULL" error
message is displayed.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59632
--- Comment #10 from Sebb <se...@apache.org> ---
(In reply to Felix Schumacher from comment #8)
> We could change the jmeter code to display the full exception when the
> message is null, but I think the real culprit is the jdk.
>
Agreed, we should display more info in this case.
Probably sensible to log the stack trace as well.
Also agree that the JVM implementation is broken as it does not propagate the
error.
--
You are receiving this mail because:
You are the assignee for the bug.