Hi Zahid, How below link is going to help me out to know the root cause of the problem?
Thanks and Regards, Rajendra Rathore 9922701491 -----Original Message----- From: Zahid Rahman <zahidr1...@gmail.com> Sent: Thursday, January 9, 2020 10:53 AM To: Tomcat Users List <users@tomcat.apache.org> Subject: Re: BLOCKING: performance issue with Tomcat 8.5.35 in org.apache.tomcat.util.net.NioBlockingSelector.write API External email from: users-return-269283-rarathore=ptc....@tomcat.apache.org https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.codota.com%2Fcode%2Fjava%2Fmethods%2Forg.apache.tomcat.util.net.NioBlockingSelector%2Fopen&data=02%7C01%7Crarathore%40ptc.com%7C02a8c62f96c84b8ea63c08d794c40c25%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637141442053995621&sdata=E666bJmF4N1wxBhm%2Fa%2BY29lvLlA32tQ%2B4F3lwBnLM2g%3D&reserved=0 On Thu, 9 Jan 2020, 04:49 Rathore, Rajendra, <rarath...@ptc.com> wrote: > Hi Team, > > If someone know how to check whether proper read/write operation done > or not or it will caused by network please let me know because it is > blocking for me. > > Thanks and Regards, > Rajendra Rathore > 9922701491 > > -----Original Message----- > From: Rathore, Rajendra > Sent: Wednesday, January 8, 2020 11:43 AM > To: 'Tomcat Users List' <users@tomcat.apache.org> > Subject: RE: performance issue with Tomcat 8.5.35 in > org.apache.tomcat.util.net.NioBlockingSelector.write API > > Can someone please help me to find out the root cause for below issue. > > Thanks and Regards, > Rajendra Rathore > 9922701491 > > -----Original Message----- > From: Rathore, Rajendra > Sent: Tuesday, January 7, 2020 4:16 PM > To: Tomcat Users List <users@tomcat.apache.org> > Subject: RE: performance issue with Tomcat 8.5.35 in > org.apache.tomcat.util.net.NioBlockingSelector.write API > > Hi Remy, > > Thanks for the reply, > > As you mention below points > > "There's a problem only if things are blocked improperly, for example > if the client is correctly reading the data and/or there's no network backlog. > Also the timeout configured on the connector must be respected by the > operation." > > 1. how can we check the network backlog or data read/write not working > properly, if any tool pls let us know 2. how can we set connector timeout. > > Thanks and Regards, > Rajendra Rathore > 9922701491 > > -----Original Message----- > From: Rémy Maucherat <r...@apache.org> > Sent: Tuesday, January 7, 2020 4:11 PM > To: Tomcat Users List <users@tomcat.apache.org> > Subject: Re: performance issue with Tomcat 8.5.35 in > org.apache.tomcat.util.net.NioBlockingSelector.write API > > External email from: users-return-269207-rarathore= > ptc....@tomcat.apache.org > > On Tue, Jan 7, 2020 at 6:33 AM Rathore, Rajendra <rarath...@ptc.com> > wrote: > > > Hi Rémy/ Christopher, > > > > It will stuck there for 10-15 minutes, so it will take time to load > > simple Web UI, there is no WebSocket call. I am giving you one of > > the sample where it will take 90% time in write operation, sometime > > it will > reach to 100%. > > > > > > | | > > > > O-org.apache.coyote.ajp.AjpProcessor.writeData(AjpProcessor.java:133 > > 1) > > count=1669(%92.877) > > | | > > > > O-org.apache.tomcat.util.net.SocketWrapperBase.write(SocketWrapperBa > > se > > .java:385) > > count=1669(%92.877) > > | | > > > > O-org.apache.tomcat.util.net.SocketWrapperBase.writeBlocking(SocketW > > ra > > pperBase.java:462) > > count=1669(%92.877) > > | | > > > > O-org.apache.tomcat.util.net.SocketWrapperBase.doWrite(SocketWrapper > > Ba > > se.java:726) > > count=1669(%92.877) > > | | > > > > O-org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.doWrite(Ni > > oE > > ndpoint.java:1316) > > count=1669(%92.877) > > | | > > > > O-org.apache.tomcat.util.net.NioSelectorPool.write(NioSelectorPool.j > > av > > a:157) > > count=1669(%92.877) > > | | > > > > O-org.apache.tomcat.util.net.NioBlockingSelector.write(NioBlockingSe > > le > > ctor.java:114) > > count=1667(%92.766) > > | | > > | > > O-org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.awaitWrite > > La > > tch(NioEndpoint.java:1160) > > count=1667(%92.766) > > | | > > | O-org.apache.tomcat.util.net > .NioEndpoint$NioSocketWrapper.awaitLatch(NioEndpoint.java:1157) > > count=1667(%92.766) > > | | > > | > > O-java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) > > count=1667(%92.766) > > > > > It's a normal blocking write, and the await does not consume CPU (it > sits there however and a profiler will count that but it doesn't matter). > There's a problem only if things are blocked improperly, for example > if the client is correctly reading the data and/or there's no network backlog. > Also the timeout configured on the connector must be respected by the > operation. > > Rémy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
