You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Jan Vávra <va...@602.cz> on 2018/12/04 15:10:57 UTC
manager app, Complete Server Status, not shown list of NIO threads
Hello,
I'm using Apache Tomcat/8.5.35, jvm 1.8.0_192-b12, Windows Server 2012
R2 and at Complete Server Status page I can see list of all http-nio
threads and I can see a header of ajp-nio threads. But there is
displayed only a label Max threads:
and nothing more.
In the localhost.log is an exception:
04-Dec-2018 10:31:38.109 SEVERE [96]
org.apache.catalina.core.StandardHostValve.invoke Exception Processing null
java.lang.NullPointerException
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:236)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:493)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
at
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:650)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
at org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:479)
at
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:806)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
at
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
At the version Apache Tomcat/8.5.34 this problem doesn't occur.
Did I found a bug?
Jan.
Re: manager app, Complete Server Status, not shown list of NIO
threads
Posted by Mark Thomas <ma...@apache.org>.
On 04/12/2018 15:10, Jan Vávra wrote:
> Hello,
> I'm using Apache Tomcat/8.5.35, jvm 1.8.0_192-b12, Windows Server 2012
> R2 and at Complete Server Status page I can see list of all http-nio
> threads and I can see a header of ajp-nio threads. But there is
> displayed only a label Max threads:
> and nothing more.
That matches this:
https://bz.apache.org/bugzilla/show_bug.cgi?id=62918
> In the localhost.log is an exception:
> 04-Dec-2018 10:31:38.109 SEVERE [96]
> org.apache.catalina.core.StandardHostValve.invoke Exception Processing null
> java.lang.NullPointerException
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:236)
although the exception is different. Odd.
I'll echo Chris's comments about the exception.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Incomplete list of handle types
Posted by Mark Thomas <ma...@apache.org>.
Please don't hijack threads. Please start a new thread for a new topic.
Mark
On 08/12/2018 15:25, Stephane Passignat wrote:
> Hi
> I've seen this non compliancy. In TC 7.042 and 7.0.72. How, who can fix this ?
>
> @HandlesTypes classes implementations. The mecanism in place only accept classes implementing an the type but doesn't accept classes inheriting from class implementing the @HandlesTypes classes. The
> (Servlet 3.0 spec 8.2.4: ServletContainerInitializer’sonStartup method get's a Set of Classes that either extend / implement the classes that the initializer expressed interest in or if it is annotated with any of the classes specified via the @HandlesTypes annotation)
>
> Thanks
> Stephane
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Incomplete list of handle types
Posted by Stephane Passignat <pa...@hotmail.com>.
Hi
I've seen this non compliancy. In TC 7.042 and 7.0.72. How, who can fix this ?
@HandlesTypes classes implementations. The mecanism in place only accept classes implementing an the type but doesn't accept classes inheriting from class implementing the @HandlesTypes classes. The
(Servlet 3.0 spec 8.2.4: ServletContainerInitializer’sonStartup method get's a Set of Classes that either extend / implement the classes that the initializer expressed interest in or if it is annotated with any of the classes specified via the @HandlesTypes annotation)
Thanks
Stephane
Re: Duplicate web fragment
Posted by Mark Thomas <ma...@apache.org>.
Please don't hijack threads. Please start a new thread for a new topic.
Mark
On 08/12/2018 15:12, Stephane Passignat wrote:
> Hello,
>
> I've seen this non compliancy. In TC 7.042 and 7.0.72. How, who can fix this ?
>
> Servlet 3.0 spec 8.2.2 2b: Duplicate name exception: if, when traversing the web-fragments, multiple members with the same <name> element are encountered, the application must log an informative error message including information to help fix the problem, and must fail to deploy.
>
> TC doesn't do it.
>
>
> Thanks
> Stephane
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Duplicate web fragment
Posted by Stephane Passignat <pa...@hotmail.com>.
Hello,
I've seen this non compliancy. In TC 7.042 and 7.0.72. How, who can fix this ?
Servlet 3.0 spec 8.2.2 2b: Duplicate name exception: if, when traversing the web-fragments, multiple members with the same <name> element are encountered, the application must log an informative error message including information to help fix the problem, and must fail to deploy.
TC doesn't do it.
Thanks
Stephane
Re: Sci and web fragment initialization
Posted by Mark Thomas <ma...@apache.org>.
Please don't hijack threads. Please start a new thread for a new topic.
Mark
On 08/12/2018 15:18, Stephane Passignat wrote:
>
> Hello,
>
> I've seen this non compliancy. In TC 7.042 and 7.0.72. How, who can fix this ?
>
> The case is related to web-fragment loading and SCI initialization.
> In Tomcat 7.0.42 and 7.0.72 at least, SCI (with @HandlesTypes annotation) are initialized web-fragments per web-fragments, with the classes previously discovered (in the WEB-INF/classes and previous processed jars). This means @HandlesTypes classes implementation located in web-fragments loaded after the one having the SCI are not provided to the SCI:onStartup method.
> The specification (8.2.4: onStartup method get's a Set of Classes) here is not clear, but we would expect having all classes, not only an "undefined" set of classes.
> A possible solution is a three steps initialization:
> - discover all SCI classes and their @HandlesTypes in all web-fragments
> - discover all @HandlesTypes implementation classes in all web-fragments
> - initialize SCI
>
> Thanks
> Stephane
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Sci and web fragment initialization
Posted by Stephane Passignat <pa...@hotmail.com>.
Hello,
I've seen this non compliancy. In TC 7.042 and 7.0.72. How, who can fix this ?
The case is related to web-fragment loading and SCI initialization.
In Tomcat 7.0.42 and 7.0.72 at least, SCI (with @HandlesTypes annotation) are initialized web-fragments per web-fragments, with the classes previously discovered (in the WEB-INF/classes and previous processed jars). This means @HandlesTypes classes implementation located in web-fragments loaded after the one having the SCI are not provided to the SCI:onStartup method.
The specification (8.2.4: onStartup method get's a Set of Classes) here is not clear, but we would expect having all classes, not only an "undefined" set of classes.
A possible solution is a three steps initialization:
- discover all SCI classes and their @HandlesTypes in all web-fragments
- discover all @HandlesTypes implementation classes in all web-fragments
- initialize SCI
Thanks
Stephane
Re: manager app, Complete Server Status, not shown list of NIO
threads
Posted by Jan Vávra <va...@602.cz>.
Hi,
Dne 05.12.2018 v 16:39 Christopher Schultz napsal(a):
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Jan,
>
> On 12/5/18 06:59, Jan Vávra wrote:
>> Hi,
>>
>> Dne 04.12.2018 v 17:49 Christopher Schultz napsal(a): Jan,
>>
>> On 12/4/18 10:10, Jan Vávra wrote:
>>>>> Hello, I'm using Apache Tomcat/8.5.35, jvm 1.8.0_192-b12,
>>>>> Windows Server 2012 R2 and at Complete Server Status page I
>>>>> can see list of all http-nio threads and I can see a header
>>>>> of ajp-nio threads. But there is displayed only a label Max
>>>>> threads: and nothing more.
>>>>>
>>>>> In the localhost.log is an exception: 04-Dec-2018
>>>>> 10:31:38.109 SEVERE [96]
>>>>> org.apache.catalina.core.StandardHostValve.invoke Exception
>>>>> Processing null java.lang.NullPointerException at
>>>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrappe
> rVa
> lve.java:236)
>>>>> at
>>>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContex
> tVa
> lve.java:96)
>>>>> at
>>>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenti
> cat
> orBase.java:493)
>>>>> at
>>>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve
> .ja
> va:140)
>>>>> at
>>>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve
> .ja
> va:81)
>>>>> at
>>>>> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAc
> ces
> sLogValve.java:650)
>>>>> at
>>>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineV
> alv
> e.java:87)
>>>>> at
>>>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.j
> ava
> :342)
>> at
>> org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:479)
>>>>> at
>>>>> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorL
> igh
> t.java:66)
>>>>> at
>>>>> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(Abstra
> ctP
> rotocol.java:806)
>>>>> at
>>>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEnd
> poi
> nt.java:1498)
>>>>> at
>>>>> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorB
> ase
> .java:49)
>>>>> at
>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecuto
> r.j
> ava:1149)
>>>>> at
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecut
> or.
> java:624)
>>>>> at
>>>>> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(Task
> Thr
> ead.java:61)
>>>>> at java.lang.Thread.run(Thread.java:748)
>>>>>
>>>>> At the version Apache Tomcat/8.5.34 this problem doesn't
>>>>> occur. Did I found a bug?
>> Something looks seriously broken if you got an NPE on that line of
>> code. Either the Valve doesn't have a Container or the Container
>> doesn't have a logger, neither of which should ever happen.
>>
>> What's your use-case? Is this embedded, or using Tomcat "normally"
>> like starting-up from a script/service and deploying web
>> applications to it?
>>> The tomcat is started as a Windows service tomcat7.exe. The
>>> services was installed using service.bat install. User
>>> connections are received in Apache Server and reverse proxied
>>> using mod_ajp. The manager app I've opened locally at RDP at url
>>> http://localhost:8080/manager/html.
>>
>> Did you upgrade from 8.5.34 and then it broke? How did you perform
>> the upgrade?
>>> I upgraded from 8.5.9 to 8.5.35 just copying from
>>> apache-tomcat-8.5.35-windows-x64.zip. I didn't copy only the
>>> conf/server.xml If I copied files from 8.5.34 the problem didn't
>>> occur.
> So you took files from the ZIP file and dropped them on top of your
> existing Tomcat installation?
Yes.
Before that I've made a directory synchronization to view what files are
new, modified and same.
> Which files? All of them?
And then I've copied all of them except server.xml where I have my
customizations.
> Generally,
> conf/server.xml is customized for a particular environment. If you
> copied everything, you will probably have lost something important.
I do not understand how I can lost something important, if I've copied
everything.
There could be a jar hell when in the zip would be jar with newer
version numbers in name. But this is not this issue for upgrade from
8.5.9 to 8.5.39.
No new jar is in the zip.
I've also text compared source a my server.xml to inspect some new
sections in source server.xml and have nothing found.
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwH8UUACgkQHPApP6U8
> pFgD+BAAwoP66vzrt5yMgiEPW9h8iUc3c8C7TXVTBLcPB1zGhjlE0r+OEhpDv2u/
> nvtlLOHMJKfqDKmDsRL8CN/qjdieZaGS4jGgDmISgBlUAMskzKf0KO5IFTqME/1p
> VKd74+cPaEZTOBqS0iwJ3iEuUczy5ArxyHeCwe7gtKLecUJot9p8MmAZ3vbVZfs+
> wKHYvz2TgI4DW6LHYlVVkzE5fxsJcJXMZj0DoDIjvzy1IGfMbsIYgnUpPtqh4neC
> uGBc1GaOIjH4uK81jr6A9CxtFaSpsek+1cZzXKDZwn0LKaY6hzAieXc+EH+22Cp3
> DjPqOzwJA2fBW5ZuOUpSnCpxvtZtz8HhuouzZA8HgsgZdXhfGiBv980CigMUoOoh
> 71gXSi5AgOcsarD3R+mwu5UAgmYKEtIcslfrpQEE7CziRCLJhyuEZvSt6Yz48v/B
> q5Jpd2/FT/qf91C/X/l1Ndd21kApQYZw6C4AAOIuxP7ZLdtUjlme2dKIB46w88pq
> zwluTi3Rnk2qFBYfTlaK5TCINj3d1r0kguzMwxoEyDbK86FOOqX9qlEKnty3JdBw
> ieOpQ4+t+O1/ogLfqFwX2Tce9MdWtDFMkWS/FLW1O4LdLklvKElb6Q75ZUmRqrrQ
> FS4IvMfXaMWkOr53MM/G7Zs37kp7F5k4MF7yyafNTjFP3yK8/Og=
> =R5+S
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
Jan.
Re: manager app, Complete Server Status, not shown list of NIO
threads
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Jan,
On 12/5/18 06:59, Jan Vávra wrote:
> Hi,
>
> Dne 04.12.2018 v 17:49 Christopher Schultz napsal(a): Jan,
>
> On 12/4/18 10:10, Jan Vávra wrote:
>>>> Hello, I'm using Apache Tomcat/8.5.35, jvm 1.8.0_192-b12,
>>>> Windows Server 2012 R2 and at Complete Server Status page I
>>>> can see list of all http-nio threads and I can see a header
>>>> of ajp-nio threads. But there is displayed only a label Max
>>>> threads: and nothing more.
>>>>
>>>> In the localhost.log is an exception: 04-Dec-2018
>>>> 10:31:38.109 SEVERE [96]
>>>> org.apache.catalina.core.StandardHostValve.invoke Exception
>>>> Processing null java.lang.NullPointerException at
>>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrappe
rVa
>
>>>>
lve.java:236)
>>>> at
>>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContex
tVa
>
>>>>
lve.java:96)
>>>> at
>>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenti
cat
>
>>>>
orBase.java:493)
>>>> at
>>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve
.ja
>
>>>>
va:140)
>>>> at
>>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve
.ja
>
>>>>
va:81)
>>>> at
>>>> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAc
ces
>
>>>>
sLogValve.java:650)
>>>> at
>>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineV
alv
>
>>>>
e.java:87)
>>>> at
>>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.j
ava
>
>>>>
:342)
>>>>
> at
> org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:479)
>>>> at
>>>> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorL
igh
>
>>>>
t.java:66)
>>>> at
>>>> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(Abstra
ctP
>
>>>>
rotocol.java:806)
>>>> at
>>>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEnd
poi
>
>>>>
nt.java:1498)
>>>> at
>>>> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorB
ase
>
>>>>
.java:49)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecuto
r.j
>
>>>>
ava:1149)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecut
or.
>
>>>>
java:624)
>>>> at
>>>> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(Task
Thr
>
>>>>
ead.java:61)
>>>> at java.lang.Thread.run(Thread.java:748)
>>>>
>>>> At the version Apache Tomcat/8.5.34 this problem doesn't
>>>> occur. Did I found a bug?
> Something looks seriously broken if you got an NPE on that line of
> code. Either the Valve doesn't have a Container or the Container
> doesn't have a logger, neither of which should ever happen.
>
> What's your use-case? Is this embedded, or using Tomcat "normally"
> like starting-up from a script/service and deploying web
> applications to it?
>> The tomcat is started as a Windows service tomcat7.exe. The
>> services was installed using service.bat install. User
>> connections are received in Apache Server and reverse proxied
>> using mod_ajp. The manager app I've opened locally at RDP at url
>> http://localhost:8080/manager/html.
>
>
> Did you upgrade from 8.5.34 and then it broke? How did you perform
> the upgrade?
>> I upgraded from 8.5.9 to 8.5.35 just copying from
>> apache-tomcat-8.5.35-windows-x64.zip. I didn't copy only the
>> conf/server.xml If I copied files from 8.5.34 the problem didn't
>> occur.
So you took files from the ZIP file and dropped them on top of your
existing Tomcat installation? Which files? All of them? Generally,
conf/server.xml is customized for a particular environment. If you
copied everything, you will probably have lost something important.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwH8UUACgkQHPApP6U8
pFgD+BAAwoP66vzrt5yMgiEPW9h8iUc3c8C7TXVTBLcPB1zGhjlE0r+OEhpDv2u/
nvtlLOHMJKfqDKmDsRL8CN/qjdieZaGS4jGgDmISgBlUAMskzKf0KO5IFTqME/1p
VKd74+cPaEZTOBqS0iwJ3iEuUczy5ArxyHeCwe7gtKLecUJot9p8MmAZ3vbVZfs+
wKHYvz2TgI4DW6LHYlVVkzE5fxsJcJXMZj0DoDIjvzy1IGfMbsIYgnUpPtqh4neC
uGBc1GaOIjH4uK81jr6A9CxtFaSpsek+1cZzXKDZwn0LKaY6hzAieXc+EH+22Cp3
DjPqOzwJA2fBW5ZuOUpSnCpxvtZtz8HhuouzZA8HgsgZdXhfGiBv980CigMUoOoh
71gXSi5AgOcsarD3R+mwu5UAgmYKEtIcslfrpQEE7CziRCLJhyuEZvSt6Yz48v/B
q5Jpd2/FT/qf91C/X/l1Ndd21kApQYZw6C4AAOIuxP7ZLdtUjlme2dKIB46w88pq
zwluTi3Rnk2qFBYfTlaK5TCINj3d1r0kguzMwxoEyDbK86FOOqX9qlEKnty3JdBw
ieOpQ4+t+O1/ogLfqFwX2Tce9MdWtDFMkWS/FLW1O4LdLklvKElb6Q75ZUmRqrrQ
FS4IvMfXaMWkOr53MM/G7Zs37kp7F5k4MF7yyafNTjFP3yK8/Og=
=R5+S
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: manager app, Complete Server Status, not shown list of NIO
threads
Posted by Jan Vávra <va...@602.cz>.
Hi,
Dne 04.12.2018 v 17:49 Christopher Schultz napsal(a):
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Jan,
>
> On 12/4/18 10:10, Jan Vávra wrote:
>> Hello, I'm using Apache Tomcat/8.5.35, jvm 1.8.0_192-b12, Windows
>> Server 2012 R2 and at Complete Server Status page I can see list of
>> all http-nio threads and I can see a header of ajp-nio threads. But
>> there is displayed only a label Max threads: and nothing more.
>>
>> In the localhost.log is an exception: 04-Dec-2018 10:31:38.109
>> SEVERE [96] org.apache.catalina.core.StandardHostValve.invoke
>> Exception Processing null java.lang.NullPointerException at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVa
> lve.java:236)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextVa
> lve.java:96)
>> at
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticat
> orBase.java:493)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.ja
> va:140)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.ja
> va:81)
>> at
>> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAcces
> sLogValve.java:650)
>> at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValv
> e.java:87)
>> at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java
> :342)
>>
> at org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:479)
>> at
>> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLigh
> t.java:66)
>> at
>> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractP
> rotocol.java:806)
>> at
>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoi
> nt.java:1498)
>> at
>> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase
> .java:49)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.j
> ava:1149)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
> java:624)
>> at
>> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThr
> ead.java:61)
>> at java.lang.Thread.run(Thread.java:748)
>>
>> At the version Apache Tomcat/8.5.34 this problem doesn't occur. Did
>> I found a bug?
> Something looks seriously broken if you got an NPE on that line of
> code. Either the Valve doesn't have a Container or the Container
> doesn't have a logger, neither of which should ever happen.
>
> What's your use-case? Is this embedded, or using Tomcat "normally"
> like starting-up from a script/service and deploying web applications
> to it?
The tomcat is started as a Windows service tomcat7.exe. The services was
installed using service.bat install.
User connections are received in Apache Server and reverse proxied using
mod_ajp.
The manager app I've opened locally at RDP at url
http://localhost:8080/manager/html.
>
> Did you upgrade from 8.5.34 and then it broke? How did you perform the
> upgrade?
I upgraded from 8.5.9 to 8.5.35 just copying from
apache-tomcat-8.5.35-windows-x64.zip. I didn't copy only the conf/server.xml
If I copied files from 8.5.34 the problem didn't occur.
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwGsBUACgkQHPApP6U8
> pFg7RxAAvmaaNGfOSGut8l5xHktCpf7B8Uy4/nChr/gAeGuY6Vk0vKcB88cdecGU
> q70+atyU6r03sUWuIbfM9OQc7DhPS5mZHifCOM8Yn77ZK6pJERYg+tz4m/f7M979
> Cj7QUIHl8/i21qULL6Y5OQyV/N5U9lAnKzGRJrVcDghcl+pYrEBE3P+VyOXduTvr
> rOjYxNq2NP+D0B4JTy1D+Wa7+BFsqrAwm3TjQ7vxCg3wW4OWwDUM7SKYCCDMCYHV
> kLHIgJFRSwoZIGhDI4HYGjssY1H1q4DCTJPduQi0RZI/IcvrHNjRff3S9HXnzs5n
> 86efvPHh8SUmp42dFwWzlXq6E7O9tzoCOTbAn+SEr3EQG8H2m2cQ8Y66zaoXZGMY
> hN+cPtMfimwCpI3bO46yEB6YipZbf4fjn6MXIbJk+GWEafuviEg0t/uIUGRslBpl
> CpzJb1lgZZUIdmn3xvdPsCzo1Ot5saC2lEJbzCnBjjR8d9RqlrGZKBn5L6h43zxV
> QlEK8YfF11YckXKSM/Kr8/AorYzmifcd6aAQJJtCPkQWE49YDzbCOIAqy6ooR7Br
> fCpfs1cUsemNn0nfUYWMN/4X/NDfrsFhdxLveI8/bjMCFfYCxyH0V5wYN69oZaWL
> N8Vt74TrJ4gqukQTwvq85xdgVdLj9zQgTtVci5+AamjDe6ydTjI=
> =Wtha
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
Jan.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: manager app, Complete Server Status, not shown list of NIO
threads
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Jan,
On 12/4/18 10:10, Jan Vávra wrote:
> Hello, I'm using Apache Tomcat/8.5.35, jvm 1.8.0_192-b12, Windows
> Server 2012 R2 and at Complete Server Status page I can see list of
> all http-nio threads and I can see a header of ajp-nio threads. But
> there is displayed only a label Max threads: and nothing more.
>
> In the localhost.log is an exception: 04-Dec-2018 10:31:38.109
> SEVERE [96] org.apache.catalina.core.StandardHostValve.invoke
> Exception Processing null java.lang.NullPointerException at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVa
lve.java:236)
>
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextVa
lve.java:96)
>
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticat
orBase.java:493)
>
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.ja
va:140)
>
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.ja
va:81)
>
> at
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAcces
sLogValve.java:650)
>
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValv
e.java:87)
>
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java
:342)
>
>
at org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:479)
> at
> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLigh
t.java:66)
>
> at
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractP
rotocol.java:806)
>
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoi
nt.java:1498)
>
> at
> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase
.java:49)
>
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.j
ava:1149)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
java:624)
>
> at
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThr
ead.java:61)
>
> at java.lang.Thread.run(Thread.java:748)
>
> At the version Apache Tomcat/8.5.34 this problem doesn't occur. Did
> I found a bug?
Something looks seriously broken if you got an NPE on that line of
code. Either the Valve doesn't have a Container or the Container
doesn't have a logger, neither of which should ever happen.
What's your use-case? Is this embedded, or using Tomcat "normally"
like starting-up from a script/service and deploying web applications
to it?
Did you upgrade from 8.5.34 and then it broke? How did you perform the
upgrade?
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwGsBUACgkQHPApP6U8
pFg7RxAAvmaaNGfOSGut8l5xHktCpf7B8Uy4/nChr/gAeGuY6Vk0vKcB88cdecGU
q70+atyU6r03sUWuIbfM9OQc7DhPS5mZHifCOM8Yn77ZK6pJERYg+tz4m/f7M979
Cj7QUIHl8/i21qULL6Y5OQyV/N5U9lAnKzGRJrVcDghcl+pYrEBE3P+VyOXduTvr
rOjYxNq2NP+D0B4JTy1D+Wa7+BFsqrAwm3TjQ7vxCg3wW4OWwDUM7SKYCCDMCYHV
kLHIgJFRSwoZIGhDI4HYGjssY1H1q4DCTJPduQi0RZI/IcvrHNjRff3S9HXnzs5n
86efvPHh8SUmp42dFwWzlXq6E7O9tzoCOTbAn+SEr3EQG8H2m2cQ8Y66zaoXZGMY
hN+cPtMfimwCpI3bO46yEB6YipZbf4fjn6MXIbJk+GWEafuviEg0t/uIUGRslBpl
CpzJb1lgZZUIdmn3xvdPsCzo1Ot5saC2lEJbzCnBjjR8d9RqlrGZKBn5L6h43zxV
QlEK8YfF11YckXKSM/Kr8/AorYzmifcd6aAQJJtCPkQWE49YDzbCOIAqy6ooR7Br
fCpfs1cUsemNn0nfUYWMN/4X/NDfrsFhdxLveI8/bjMCFfYCxyH0V5wYN69oZaWL
N8Vt74TrJ4gqukQTwvq85xdgVdLj9zQgTtVci5+AamjDe6ydTjI=
=Wtha
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org