You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2011/09/23 15:30:13 UTC
DO NOT REPLY [Bug 51883] NullPointerException in
StandardContextValve.invoke
https://issues.apache.org/bugzilla/show_bug.cgi?id=51883
Konstantin Kolinko <kn...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS/Version| |All
--- Comment #1 from Konstantin Kolinko <kn...@gmail.com> 2011-09-23 13:30:13 UTC ---
In TOMCAT_7_0_19: (The code is the same in the current trunk)
It is inside the following method:
public final void invoke(Request request, Response response)
throws IOException, ServletException {
122 // Wait if we are reloading
123 boolean reloaded = false;
124 while (context.getPaused()) {
125 reloaded = true;
126 try {
127 Thread.sleep(1000);
128 } catch (InterruptedException e) {
129 // Ignore
130 }
131 }
The only reason that I see why context can be null on line 124 is that the
webapp has been stopped.
In that case you would not be able to process the request anyway. The NPE is
unexpected, but it saves you from infinite looping there.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org