[Bug 65408] tomcat8.5.X occurs an AssertionError occationally after running for a period of time

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=65408

--- Comment #10 from jiangyangyang <73...@qq.com> ---
(In reply to Mark Thomas from comment #9)
> Both the stack traces in the bug description are consistent with attempting
> to use a request object that has already been recycled. While that might be
> a Tomcat bug, it is typically cased by applications retaining references to
> requests, responses etc and attempting to use the objects after they are no
> longer valid.
> 
> Unless a test case is provided that can be used to recreate this bug, it
> will eventually get resolved as WORKSFORME.


At present, we have four application clusters that both use websocket and http
have AssertionError! But we did not find the inevitable scene.It does not
reache the application logic when the 500 AssertionError occured in the
catalina.out. And we can not prove application used a request object that has
already been recycled or memory cache recycle failed.

1. What is the purpose of this code, can it be cancelled ?

739    if (mappingData.host != null) {
744            throw new AssertionError();
        }

2.Which debug logs should be added to tomcat,and how to do it?

3.Why does the http method of OPTION requests also have AssertionError and 500
? 



Thanks for your reply!!

-- 
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