asfimport
commented
8 years ago Sebb (migrated from Bugzilla): 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?
Open asfimport opened 8 years ago
asfimport
commented
8 years ago Sebb (migrated from Bugzilla): 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?
asfimport
commented
8 years ago Shivansh (migrated from Bugzilla): I am Testing it on my Local server , so no such link is available for it.
asfimport
commented
8 years ago Shivansh (migrated from Bugzilla): In Jmeter Log file no such message is displayed.
asfimport
commented
8 years ago Shivansh (migrated from Bugzilla): Can i help you by providing some other details.
asfimport
commented
8 years ago Sebb (migrated from Bugzilla): (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.
asfimport
commented
8 years ago Shivansh (migrated from Bugzilla): Created attachment Text output on Error Page.txt: Text Output for Error Page
asfimport
commented
8 years ago Shivansh (migrated from Bugzilla): 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.
asfimport
commented
8 years ago @FSchumacher (migrated from Bugzilla): 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.
asfimport
commented
8 years ago Shivansh (migrated from Bugzilla): 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 .
asfimport
commented
8 years ago Sebb (migrated from Bugzilla): (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.
asfimport
commented
8 years ago Sebb (migrated from Bugzilla): (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.
asfimport
commented
8 years ago @FSchumacher (migrated from Bugzilla): Created attachment bug59632-example.jmx: Example jmx with minimal html code to reproduce issue
true
asfimport
commented
8 years ago @FSchumacher (migrated from Bugzilla): Created attachment bug59632-emptystackexc.log: Stacktrace of the exception, that jmeter can catch
asfimport
commented
8 years ago @FSchumacher (migrated from Bugzilla): Created attachment bug59632-quote-stack.log: Stacktrace that gets written to stdout by jdk
asfimport
commented
8 years ago @pmouawad (migrated from Bugzilla): Shouldn't we report a bug to Oracle ?
Shivansh (Bug 59632): 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.
Created attachment Jmeter Issue.png: Failed to Parse HTML : NULL error message is displayed.
Severity: major OS: All