date:20160412

Re: Help needed

2016-04-12 Thread Sajin S

Nullpointerexception
On 13-Apr-2016 12:38 am, "David kerber"  wrote:

>
> On 4/12/2016 2:56 PM, Sajin S wrote:
>
>> Expection :
>>
>> at org.apache.coyote.http11.InternalAprOutputBuffer.addToBB(
>> *InternalAprOutputBuffer.java:186*)
>>
>
> You still missed the exception itself; you need what's before the "at" in
> the above lines.
>
>
>
>
>> at org.apache.coyote.http11.InternalAprOutputBuffer.access$000(
>> *InternalAprOutputBuffer.java:40*)
>>
>> at
>>
>> org.apache.coyote.http11.InternalAprOutputBuffer$SocketOutputBuffer.doWrite(
>> *InternalAprOutputBuffer.java:349*)
>>
>> at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(
>> *ChunkedOutputFilter.java:116*)
>>
>> at org.apache.coyote.http11.AbstractOutputBuffer.doWrite(
>> *AbstractOutputBuffer.java:256*)
>>
>> at org.apache.coyote.Response.doWrite(*Response.java:501*)
>>
>> at org.apache.catalina.connector.OutputBuffer.realWriteBytes(
>> *OutputBuffer.java:388*)
>>
>> at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(
>> *ByteChunk.java:426*)
>>
>> at
>> org.apache.tomcat.util.buf.ByteChunk.append(*ByteChunk.java:339*)
>>
>> at org.apache.catalina.connector.OutputBuffer.writeBytes(
>> *OutputBuffer.java:418*)
>>
>> at org.apache.catalina.connector.OutputBuffer.write(
>> *OutputBuffer.java:406*)
>>
>> at org.apache.catalina.connector.CoyoteOutputStream.write(
>> *CoyoteOutputStream.java:97*)
>>
>> at
>>
>> jp.co.hitachi_ul.mvspf.restbase.service.RestVoiceService$1$1.onChunkReceived(
>> *RestVoiceService.java:170*)
>>
>> at
>> jp.co.hitachi_ul.mvspf.middleware.base.SessionContainer.onChunkReceived(
>> *SessionContainer.java:106*)
>>
>> at jp.co.hitachi_ul.mvspf.middleware.util.IpThread.callback(
>> *IpThread.java:188*)
>>
>> at
>> jp.co.hitachi_ul.mvspf.middleware.util.IpAdapter$ReadThread.run(
>> *IpAdapter.java:193*)
>> On 12-Apr-2016 11:55 pm, "Mark Thomas"  wrote:
>>
>> On 12/04/2016 18:42, Sajin S wrote:
>>>
   I am using tomcat 8.0.33 and getting this issue. Kindly help me.


 While doing asynchronous call back and write the output using

>>> outputstream
>>>
 am getting this issue.


 Current protocol is bio. Please help.

>>>
>>> You've removed the exception information that would let us help you.
>>>
>>> What you have left clearly shows you are not using BIO.
>>>
>>> It looks like you need to read this:
>>> http://www.catb.org/esr/faqs/smart-questions.html
>>>
>>> Mark
>>>
>>>


 Expection :

 at org.apache.coyote.http11.InternalAprOutputBuffer.addToBB(
 *InternalAprOutputBuffer.java:186*)

 at org.apache.coyote.http11.InternalAprOutputBuffer.access$000(
 *InternalAprOutputBuffer.java:40*)

 at


>>> org.apache.coyote.http11.InternalAprOutputBuffer$SocketOutputBuffer.doWrite(
>>>
 *InternalAprOutputBuffer.java:349*)

 at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(
 *ChunkedOutputFilter.java:116*)

 at org.apache.coyote.http11.AbstractOutputBuffer.doWrite(
 *AbstractOutputBuffer.java:256*)

 at org.apache.coyote.Response.doWrite(*Response.java:501*)

 at org.apache.catalina.connector.OutputBuffer.realWriteBytes(
 *OutputBuffer.java:388*)

 at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(
 *ByteChunk.java:426*)

 at

>>> org.apache.tomcat.util.buf.ByteChunk.append(*ByteChunk.java:339*)
>>>

 at org.apache.catalina.connector.OutputBuffer.writeBytes(
 *OutputBuffer.java:418*)

 at org.apache.catalina.connector.OutputBuffer.write(
 *OutputBuffer.java:406*)

 at org.apache.catalina.connector.CoyoteOutputStream.write(
 *CoyoteOutputStream.java:97*)

 at


>>> jp.co.hitachi_ul.mvspf.restbase.service.RestVoiceService$1$1.onChunkReceived(
>>>
 *RestVoiceService.java:170*)

 at
 jp.co.hitachi_ul.mvspf.middleware.base.SessionContainer.onChunkReceived(
 *SessionContainer.java:106*)

 at jp.co.hitachi_ul.mvspf.middleware.util.IpThread.callback(
 *IpThread.java:188*)

 at

>>> jp.co.hitachi_ul.mvspf.middleware.util.IpAdapter$ReadThread.run(
>>>
 *IpAdapter.java:193*)
 Thanks & Regards,
 Sajin S
 +919995047208


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

Re: users Digest 12 Apr 2016 18:54:12 -0000 Issue 12577

2016-04-12 Thread Lyndon Samson

Windows env often have 'virus scanners' that make large numbers of HTTP
calls to known vunerable endpoints. Do the access logs show anything OOTO?
On 13 Apr 2016 4:54 am,  wrote:

>
> users Digest 12 Apr 2016 18:54:12 - Issue 12577
>
> Topics (messages 257263 through 257265)
>
> Re: Tomcat 8 uses high CPU
> 257263 by: Christopher Schultz
> 257264 by: Mark Thomas
> 257265 by: Josep M Beleta
>
> Administrivia:
>
> -
> To post to the list, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-digest-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-digest-h...@tomcat.apache.org
>
> --
>
>
>
> -- Forwarded message --
> From: Christopher Schultz 
> To: Tomcat Users List 
> Cc:
> Date: Tue, 12 Apr 2016 14:50:12 -0400
> Subject: Re: Tomcat 8 uses high CPU
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Josep,
>
> On 4/12/16 2:30 PM, Josep M Beleta wrote:
> > I need some help with a problem we have running Tomcat 8, with Java
> > 8 on a Windows 2008 R2 Standard with Service Pack 1 running as a
> > virtual machine on top of ESXi, 5.1.0. The virtual machine has 16
> > GB of memory and 4 CPUs. The physical host computer has lots of
> > memory and is not stressed at all.
> >
> > One week ago our Tomcats, we have two, began to use high CPU. When
> > the problem started we had no made any change we can remember in
> > the preceding week, and no Windows update was installed.
> >
> > We use two Tomcats, one of them with some in-house applications
> > the other one with Jira. Both began to shows the same symptoms
> > roughly at the same time.
> >
> > The Jira Tomcat version is 8.0.17 and runs with  Java 1.8.0_51 64
> > Bit, the other Tomcat is 8.0.33 and runs over Java 1.8.0_77 64 Bit.
> >
> >
> > These are the facts we can summarize:
> >
> > 1. Now we run only the Tomcat for our in-house applications.We
> > stopped the Jira one. 2. We run it as a service. 3. Every time, two
> > hours after launching the Tomcat service, the CPU use jumps to
> > 70-75% and some time after (one hour more) it reaches 100 %. More
> > threads are allocated using lots of CPU. The final result is our
> > entire system being degraded as time goes on. 4. The problems has
> > nothing to do with our applications. We undeployed them with the
> > same result.
>
> So if you start Tomcat with no applications deployed and make no
> requests, Tomcat starts taking 75% of the CPU after 2 hours?
>
> Mark is right: we need to see those thread dumps. It looks like your
> second attempt also didn't work. Please try to re-attach them as plain
> text files.
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlcNQ2QACgkQ9CaO5/Lv0PDJTwCfWuiSiAqrb8hYw5YQLOxE52uX
> isIAnRpR9Vj2GZLjiCMr6+hnFbB7eEPb
> =/3nu
> -END PGP SIGNATURE-
>
>
>
> -- Forwarded message --
> From: Mark Thomas 
> To: Tomcat Users List 
> Cc:
> Date: Tue, 12 Apr 2016 19:53:19 +0100
> Subject: Re: Tomcat 8 uses high CPU
> On 12/04/2016 19:50, Josep M Beleta wrote:
> > I am sorry, I sent the same file twice.
> >
> > Here is the other one.
>
> Nope. They need to be plain text attachments and no larger than 1MB.
>
> Mark
>
>
> >
> > **
> >
> > *Josep M Beleta*
> >
> > /Director de Tecnologia/
> >
> >
> > Carver Advanced Systems, S.L.
> >
> > París, 184. 4º  08036 - Barcelona
> >
> >
> > Tel:  93 238 5880
> >
> > Fax: 93 238 5881
> >
> > */segueix-nos
> > /*<
> http://twitter.com/#%21/carver_as> <
> https://plus.google.com/112583630853594851700?prsrc=3>
> >
> > www.carver-as.com 
> >
> >
> > 2016-04-12 20:49 GMT+02:00 Josep M Beleta  > >:
> >
> > Hi Mark, thanks a lot.
> >
> > here come the dumps:
> >
> > Josep
> >
> >
> > **
> >
> > *Josep M Beleta*
> >
> > /Director de Tecnologia/
> >
> >
> > Carver Advanced Systems, S.L.
> >
> > París, 184. 4º  08036 - Barcelona
> >
> >
> > Tel:  93 238 5880 
> >
> > Fax: 93 238 5881 
> >
> > */segueix-nos
> > /*<
> http://twitter.com/#%21/carver_as> <
> https://plus.google.com/112583630853594851700?prsrc=3>
> >
> > www.carver-as.com 
> >
> >
> > 2016-04-12 20:43 GMT+02:00 Mark Thomas  > >:
> >
> > On 12/04/2016 19:30, Josep M Beleta wrote:
> > > Hi,
> > >
> > > I need some help with a

Re: Tomcat 8 uses high CPU

2016-04-12 Thread Josep M Beleta

Mark,

I tested Tomcat 8.5 and experienced the same problem.

I am enclosing a new dump. I hope it will be useful.

Regards

Josep M Beleta
2016-04-13 01:50:55
Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.77-b03 mixed mode):

"ajp-nio-8209-AsyncTimeout" #26 daemon prio=5 os_prio=0 tid=0x175f5000 
nid=0x1694 waiting on condition [0x19ecf000]
   java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at 
org.apache.coyote.AbstractProtocol$AsyncTimeout.run(AbstractProtocol.java:1076)
at java.lang.Thread.run(Unknown Source)

   Locked ownable synchronizers:
- None

"ajp-nio-8209-Acceptor-0" #25 daemon prio=5 os_prio=0 tid=0x175f4000 
nid=0x114c runnable [0x19eaf000]
   java.lang.Thread.State: RUNNABLE
at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.accept(Unknown Source)
at sun.nio.ch.ServerSocketChannelImpl.accept(Unknown Source)
- locked <0x80022878> (a java.lang.Object)
at 
org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:513)
at java.lang.Thread.run(Unknown Source)

   Locked ownable synchronizers:
- None

"ajp-nio-8209-ClientPoller-1" #24 daemon prio=5 os_prio=0 
tid=0x175f3800 nid=0x1bd4 runnable [0x19e8f000]
   java.lang.Thread.State: RUNNABLE
at sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
at sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(Unknown Source)
at sun.nio.ch.WindowsSelectorImpl$SubSelector.access$400(Unknown Source)
at sun.nio.ch.WindowsSelectorImpl.doSelect(Unknown Source)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(Unknown Source)
- locked <0x80023ae0> (a sun.nio.ch.Util$2)
- locked <0x80023ad0> (a java.util.Collections$UnmodifiableSet)
- locked <0x80023a50> (a sun.nio.ch.WindowsSelectorImpl)
at sun.nio.ch.SelectorImpl.select(Unknown Source)
at 
org.apache.tomcat.util.net.NioEndpoint$Poller.run(NioEndpoint.java:835)
at java.lang.Thread.run(Unknown Source)

   Locked ownable synchronizers:
- None

"ajp-nio-8209-ClientPoller-0" #23 daemon prio=5 os_prio=0 
tid=0x175f2800 nid=0x22e8 runnable [0x19e6f000]
   java.lang.Thread.State: RUNNABLE
at sun.nio.ch.WindowsSelectorImpl.resetWakeupSocket0(Native Method)
at sun.nio.ch.WindowsSelectorImpl.resetWakeupSocket(Unknown Source)
- locked <0x803ac500> (a java.lang.Object)
at sun.nio.ch.WindowsSelectorImpl.doSelect(Unknown Source)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(Unknown Source)
- locked <0x800258d8> (a sun.nio.ch.Util$2)
- locked <0x800258c8> (a java.util.Collections$UnmodifiableSet)
- locked <0x80025848> (a sun.nio.ch.WindowsSelectorImpl)
at sun.nio.ch.SelectorImpl.select(Unknown Source)
at 
org.apache.tomcat.util.net.NioEndpoint$Poller.run(NioEndpoint.java:835)
at java.lang.Thread.run(Unknown Source)

   Locked ownable synchronizers:
- None

"http-nio-8280-AsyncTimeout" #22 daemon prio=5 os_prio=0 tid=0x183c5800 
nid=0x227c waiting on condition [0x19e4f000]
   java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at 
org.apache.coyote.AbstractProtocol$AsyncTimeout.run(AbstractProtocol.java:1076)
at java.lang.Thread.run(Unknown Source)

   Locked ownable synchronizers:
- None

"http-nio-8280-Acceptor-0" #21 daemon prio=5 os_prio=0 tid=0x183c3800 
nid=0x1b5c runnable [0x19e2f000]
   java.lang.Thread.State: RUNNABLE
at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.accept(Unknown Source)
at sun.nio.ch.ServerSocketChannelImpl.accept(Unknown Source)
- locked <0x801009c8> (a java.lang.Object)
at 
org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:513)
at java.lang.Thread.run(Unknown Source)

   Locked ownable synchronizers:
- None

"http-nio-8280-ClientPoller-1" #20 daemon prio=5 os_prio=0 
tid=0x183c3000 nid=0x6ac runnable [0x19e0f000]
   java.lang.Thread.State: RUNNABLE
at sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
at sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(Unknown Source)
at sun.nio.ch.WindowsSelectorImpl$SubSelector.access$400(Unknown Source)
at sun.nio.ch.WindowsSelectorImpl.doSelect(Unknown Source)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(Unknown Source)
- locked <0x80137dc0> (a sun.nio.ch.Util$2)
- locked <0x80137db0> (a java.util.Collections$UnmodifiableSet)
- locked <0x80137c40> (a sun.nio.ch.WindowsSelectorImpl)
at

Re: async servlet, tomcat 8.0.33, behind apache

2016-04-12 Thread Christopher Schultz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

fachhoch,

On 4/12/16 3:01 PM, fachhoch wrote:
> Thank you , In my case there is no cluster, its apache web server
> version 2.2.29 and one tomcat server, the connector is AJP, not
> mod_jk as said earlier.

AJP is a protocol, not software. What software are you actually using?

> does async work only with mod_jk connector?as mentioned in 
> (http://markmail.org/message/5oyqgyjuhfjsf666)

Not quite sure, yet.

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlcNUh0ACgkQ9CaO5/Lv0PAtYQCgoo4pAf3C0G7yKgxD+meQVljN
excAnA389gwggqGayMfm0Mt4kfUtnShP
=TR3L
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 8 uses high CPU

2016-04-12 Thread Mark Thomas

On 12/04/2016 19:53, Josep M Beleta wrote:
> Again,

Thanks. They came thought this time but aren't that helpful as several
key bits of information are missing:
- thread name
- thread ID

There should be an option in Tomcat8w.exe to trigger a thread dump. This
will be written to the log files and should be more complete.

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: async servlet, tomcat 8.0.33, behind apache

2016-04-12 Thread fachhoch

Thank you , In my case there is no cluster, its apache web server version
2.2.29 and one tomcat server, the connector is AJP, not mod_jk as said
earlier.

does async work only with mod_jk connector?as mentioned in
(http://markmail.org/message/5oyqgyjuhfjsf666)










 





--
View this message in context: 
http://tomcat.10.x6.nabble.com/async-servlet-tomcat-8-0-33-behind-apache-tp5049264p5049353.html
Sent from the Tomcat - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Help needed

2016-04-12 Thread David kerber



On 4/12/2016 2:56 PM, Sajin S wrote:

Expection :

at org.apache.coyote.http11.InternalAprOutputBuffer.addToBB(
*InternalAprOutputBuffer.java:186*)


You still missed the exception itself; you need what's before the "at" 
in the above lines.






at org.apache.coyote.http11.InternalAprOutputBuffer.access$000(
*InternalAprOutputBuffer.java:40*)

at
org.apache.coyote.http11.InternalAprOutputBuffer$SocketOutputBuffer.doWrite(
*InternalAprOutputBuffer.java:349*)

at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(
*ChunkedOutputFilter.java:116*)

at org.apache.coyote.http11.AbstractOutputBuffer.doWrite(
*AbstractOutputBuffer.java:256*)

at org.apache.coyote.Response.doWrite(*Response.java:501*)

at org.apache.catalina.connector.OutputBuffer.realWriteBytes(
*OutputBuffer.java:388*)

at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(
*ByteChunk.java:426*)

at org.apache.tomcat.util.buf.ByteChunk.append(*ByteChunk.java:339*)

at org.apache.catalina.connector.OutputBuffer.writeBytes(
*OutputBuffer.java:418*)

at org.apache.catalina.connector.OutputBuffer.write(
*OutputBuffer.java:406*)

at org.apache.catalina.connector.CoyoteOutputStream.write(
*CoyoteOutputStream.java:97*)

at
jp.co.hitachi_ul.mvspf.restbase.service.RestVoiceService$1$1.onChunkReceived(
*RestVoiceService.java:170*)

at
jp.co.hitachi_ul.mvspf.middleware.base.SessionContainer.onChunkReceived(
*SessionContainer.java:106*)

at jp.co.hitachi_ul.mvspf.middleware.util.IpThread.callback(
*IpThread.java:188*)

at jp.co.hitachi_ul.mvspf.middleware.util.IpAdapter$ReadThread.run(
*IpAdapter.java:193*)
On 12-Apr-2016 11:55 pm, "Mark Thomas"  wrote:


On 12/04/2016 18:42, Sajin S wrote:

  I am using tomcat 8.0.33 and getting this issue. Kindly help me.


While doing asynchronous call back and write the output using

outputstream

am getting this issue.


Current protocol is bio. Please help.


You've removed the exception information that would let us help you.

What you have left clearly shows you are not using BIO.

It looks like you need to read this:
http://www.catb.org/esr/faqs/smart-questions.html

Mark





Expection :

at org.apache.coyote.http11.InternalAprOutputBuffer.addToBB(
*InternalAprOutputBuffer.java:186*)

at org.apache.coyote.http11.InternalAprOutputBuffer.access$000(
*InternalAprOutputBuffer.java:40*)

at


org.apache.coyote.http11.InternalAprOutputBuffer$SocketOutputBuffer.doWrite(

*InternalAprOutputBuffer.java:349*)

at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(
*ChunkedOutputFilter.java:116*)

at org.apache.coyote.http11.AbstractOutputBuffer.doWrite(
*AbstractOutputBuffer.java:256*)

at org.apache.coyote.Response.doWrite(*Response.java:501*)

at org.apache.catalina.connector.OutputBuffer.realWriteBytes(
*OutputBuffer.java:388*)

at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(
*ByteChunk.java:426*)

at

org.apache.tomcat.util.buf.ByteChunk.append(*ByteChunk.java:339*)


at org.apache.catalina.connector.OutputBuffer.writeBytes(
*OutputBuffer.java:418*)

at org.apache.catalina.connector.OutputBuffer.write(
*OutputBuffer.java:406*)

at org.apache.catalina.connector.CoyoteOutputStream.write(
*CoyoteOutputStream.java:97*)

at


jp.co.hitachi_ul.mvspf.restbase.service.RestVoiceService$1$1.onChunkReceived(

*RestVoiceService.java:170*)

at
jp.co.hitachi_ul.mvspf.middleware.base.SessionContainer.onChunkReceived(
*SessionContainer.java:106*)

at jp.co.hitachi_ul.mvspf.middleware.util.IpThread.callback(
*IpThread.java:188*)

at

jp.co.hitachi_ul.mvspf.middleware.util.IpAdapter$ReadThread.run(

*IpAdapter.java:193*)
Thanks & Regards,
Sajin S
+919995047208




-
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

Re: Help needed

2016-04-12 Thread Sajin S

Expection :

at org.apache.coyote.http11.InternalAprOutputBuffer.addToBB(
*InternalAprOutputBuffer.java:186*)

   at org.apache.coyote.http11.InternalAprOutputBuffer.access$000(
*InternalAprOutputBuffer.java:40*)

   at
org.apache.coyote.http11.InternalAprOutputBuffer$SocketOutputBuffer.doWrite(
*InternalAprOutputBuffer.java:349*)

   at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(
*ChunkedOutputFilter.java:116*)

   at org.apache.coyote.http11.AbstractOutputBuffer.doWrite(
*AbstractOutputBuffer.java:256*)

   at org.apache.coyote.Response.doWrite(*Response.java:501*)

   at org.apache.catalina.connector.OutputBuffer.realWriteBytes(
*OutputBuffer.java:388*)

   at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(
*ByteChunk.java:426*)

   at org.apache.tomcat.util.buf.ByteChunk.append(*ByteChunk.java:339*)

   at org.apache.catalina.connector.OutputBuffer.writeBytes(
*OutputBuffer.java:418*)

   at org.apache.catalina.connector.OutputBuffer.write(
*OutputBuffer.java:406*)

   at org.apache.catalina.connector.CoyoteOutputStream.write(
*CoyoteOutputStream.java:97*)

   at
jp.co.hitachi_ul.mvspf.restbase.service.RestVoiceService$1$1.onChunkReceived(
*RestVoiceService.java:170*)

   at
jp.co.hitachi_ul.mvspf.middleware.base.SessionContainer.onChunkReceived(
*SessionContainer.java:106*)

   at jp.co.hitachi_ul.mvspf.middleware.util.IpThread.callback(
*IpThread.java:188*)

   at jp.co.hitachi_ul.mvspf.middleware.util.IpAdapter$ReadThread.run(
*IpAdapter.java:193*)
On 12-Apr-2016 11:55 pm, "Mark Thomas"  wrote:

> On 12/04/2016 18:42, Sajin S wrote:
> >  I am using tomcat 8.0.33 and getting this issue. Kindly help me.
> >
> >
> > While doing asynchronous call back and write the output using
> outputstream
> > am getting this issue.
> >
> >
> > Current protocol is bio. Please help.
>
> You've removed the exception information that would let us help you.
>
> What you have left clearly shows you are not using BIO.
>
> It looks like you need to read this:
> http://www.catb.org/esr/faqs/smart-questions.html
>
> Mark
>
> >
> >
> >
> > Expection :
> >
> > at org.apache.coyote.http11.InternalAprOutputBuffer.addToBB(
> > *InternalAprOutputBuffer.java:186*)
> >
> >at org.apache.coyote.http11.InternalAprOutputBuffer.access$000(
> > *InternalAprOutputBuffer.java:40*)
> >
> >at
> >
> org.apache.coyote.http11.InternalAprOutputBuffer$SocketOutputBuffer.doWrite(
> > *InternalAprOutputBuffer.java:349*)
> >
> >at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(
> > *ChunkedOutputFilter.java:116*)
> >
> >at org.apache.coyote.http11.AbstractOutputBuffer.doWrite(
> > *AbstractOutputBuffer.java:256*)
> >
> >at org.apache.coyote.Response.doWrite(*Response.java:501*)
> >
> >at org.apache.catalina.connector.OutputBuffer.realWriteBytes(
> > *OutputBuffer.java:388*)
> >
> >at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(
> > *ByteChunk.java:426*)
> >
> >at
> org.apache.tomcat.util.buf.ByteChunk.append(*ByteChunk.java:339*)
> >
> >at org.apache.catalina.connector.OutputBuffer.writeBytes(
> > *OutputBuffer.java:418*)
> >
> >at org.apache.catalina.connector.OutputBuffer.write(
> > *OutputBuffer.java:406*)
> >
> >at org.apache.catalina.connector.CoyoteOutputStream.write(
> > *CoyoteOutputStream.java:97*)
> >
> >at
> >
> jp.co.hitachi_ul.mvspf.restbase.service.RestVoiceService$1$1.onChunkReceived(
> > *RestVoiceService.java:170*)
> >
> >at
> > jp.co.hitachi_ul.mvspf.middleware.base.SessionContainer.onChunkReceived(
> > *SessionContainer.java:106*)
> >
> >at jp.co.hitachi_ul.mvspf.middleware.util.IpThread.callback(
> > *IpThread.java:188*)
> >
> >at
> jp.co.hitachi_ul.mvspf.middleware.util.IpAdapter$ReadThread.run(
> > *IpAdapter.java:193*)
> > Thanks & Regards,
> > Sajin S
> > +919995047208
> >
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: Tomcat 8 uses high CPU

2016-04-12 Thread Josep M Beleta

Again,
Attaching to process ID 1964, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 25.66-b18
Deadlock Detection:

No deadlocks found.

Thread 124: (state = BLOCKED)
 - sun.misc.Unsafe.park(boolean, long) @bci=0 (Compiled frame; information may 
be imprecise)
 - java.util.concurrent.locks.LockSupport.park(java.lang.Object) @bci=14, 
line=175 (Compiled frame)
 - 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await() 
@bci=42, line=2039 (Compiled frame)
 - java.util.concurrent.LinkedBlockingQueue.take() @bci=29, line=442 (Compiled 
frame)
 - org.apache.tomcat.util.threads.TaskQueue.take() @bci=36, line=103 (Compiled 
frame)
 - org.apache.tomcat.util.threads.TaskQueue.take() @bci=1, line=31 (Compiled 
frame)
 - java.util.concurrent.ThreadPoolExecutor.getTask() @bci=149, line=1067 
(Compiled frame)
 - 
java.util.concurrent.ThreadPoolExecutor.runWorker(java.util.concurrent.ThreadPoolExecutor$Worker)
 @bci=26, line=1127 (Interpreted frame)
 - java.util.concurrent.ThreadPoolExecutor$Worker.run() @bci=5, line=617 
(Interpreted frame)
 - org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run() @bci=4, 
line=61 (Interpreted frame)
 - java.lang.Thread.run() @bci=11, line=745 (Interpreted frame)


Thread 123: (state = BLOCKED)
 - sun.misc.Unsafe.park(boolean, long) @bci=0 (Compiled frame; information may 
be imprecise)
 - java.util.concurrent.locks.LockSupport.park(java.lang.Object) @bci=14, 
line=175 (Compiled frame)
 - 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await() 
@bci=42, line=2039 (Compiled frame)
 - java.util.concurrent.LinkedBlockingQueue.take() @bci=29, line=442 (Compiled 
frame)
 - org.apache.tomcat.util.threads.TaskQueue.take() @bci=36, line=103 (Compiled 
frame)
 - org.apache.tomcat.util.threads.TaskQueue.take() @bci=1, line=31 (Compiled 
frame)
 - java.util.concurrent.ThreadPoolExecutor.getTask() @bci=149, line=1067 
(Compiled frame)
 - 
java.util.concurrent.ThreadPoolExecutor.runWorker(java.util.concurrent.ThreadPoolExecutor$Worker)
 @bci=26, line=1127 (Interpreted frame)
 - java.util.concurrent.ThreadPoolExecutor$Worker.run() @bci=5, line=617 
(Interpreted frame)
 - org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run() @bci=4, 
line=61 (Interpreted frame)
 - java.lang.Thread.run() @bci=11, line=745 (Interpreted frame)


Thread 122: (state = BLOCKED)
 - sun.misc.Unsafe.park(boolean, long) @bci=0 (Compiled frame; information may 
be imprecise)
 - java.util.concurrent.locks.LockSupport.park(java.lang.Object) @bci=14, 
line=175 (Compiled frame)
 - 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await() 
@bci=42, line=2039 (Compiled frame)
 - java.util.concurrent.LinkedBlockingQueue.take() @bci=29, line=442 (Compiled 
frame)
 - org.apache.tomcat.util.threads.TaskQueue.take() @bci=36, line=103 (Compiled 
frame)
 - org.apache.tomcat.util.threads.TaskQueue.take() @bci=1, line=31 (Compiled 
frame)
 - java.util.concurrent.ThreadPoolExecutor.getTask() @bci=149, line=1067 
(Compiled frame)
 - 
java.util.concurrent.ThreadPoolExecutor.runWorker(java.util.concurrent.ThreadPoolExecutor$Worker)
 @bci=26, line=1127 (Interpreted frame)
 - java.util.concurrent.ThreadPoolExecutor$Worker.run() @bci=5, line=617 
(Interpreted frame)
 - org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run() @bci=4, 
line=61 (Interpreted frame)
 - java.lang.Thread.run() @bci=11, line=745 (Interpreted frame)


Thread 121: (state = BLOCKED)
 - sun.misc.Unsafe.park(boolean, long) @bci=0 (Compiled frame; information may 
be imprecise)
 - java.util.concurrent.locks.LockSupport.park(java.lang.Object) @bci=14, 
line=175 (Compiled frame)
 - 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await() 
@bci=42, line=2039 (Compiled frame)
 - java.util.concurrent.LinkedBlockingQueue.take() @bci=29, line=442 (Compiled 
frame)
 - org.apache.tomcat.util.threads.TaskQueue.take() @bci=36, line=103 (Compiled 
frame)
 - org.apache.tomcat.util.threads.TaskQueue.take() @bci=1, line=31 (Compiled 
frame)
 - java.util.concurrent.ThreadPoolExecutor.getTask() @bci=149, line=1067 
(Compiled frame)
 - 
java.util.concurrent.ThreadPoolExecutor.runWorker(java.util.concurrent.ThreadPoolExecutor$Worker)
 @bci=26, line=1127 (Interpreted frame)
 - java.util.concurrent.ThreadPoolExecutor$Worker.run() @bci=5, line=617 
(Interpreted frame)
 - org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run() @bci=4, 
line=61 (Interpreted frame)
 - java.lang.Thread.run() @bci=11, line=745 (Interpreted frame)


Thread 120: (state = BLOCKED)
 - sun.misc.Unsafe.park(boolean, long) @bci=0 (Compiled frame; information may 
be imprecise)
 - java.util.concurrent.locks.LockSupport.park(java.lang.Object) @bci=14, 
line=175 (Compiled frame)
 - 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await() 
@bci=42, line=2039 (Compiled frame)
 - java.util.concurrent.LinkedBlockingQueue.take() @bci=29, line=442

Re: Tomcat 8 uses high CPU

2016-04-12 Thread Mark Thomas

On 12/04/2016 19:50, Josep M Beleta wrote:
> I am sorry, I sent the same file twice.
> 
> Here is the other one.

Nope. They need to be plain text attachments and no larger than 1MB.

Mark


> 
> **
> 
> *Josep M Beleta*
> 
> /Director de Tecnologia/
> 
> 
> Carver Advanced Systems, S.L.
> 
> París, 184. 4º  08036 - Barcelona 
> 
> 
> Tel:  93 238 5880   
> 
> Fax: 93 238 5881 
> 
> */segueix-nos
> /*
>  
> 
> www.carver-as.com 
> 
> 
> 2016-04-12 20:49 GMT+02:00 Josep M Beleta  >:
> 
> Hi Mark, thanks a lot.
> 
> here come the dumps:
> 
> Josep
> 
> 
> **
> 
> *Josep M Beleta*
> 
> /Director de Tecnologia/
> 
> 
> Carver Advanced Systems, S.L.
> 
> París, 184. 4º  08036 - Barcelona 
> 
> 
> Tel:  93 238 5880    
> 
> Fax: 93 238 5881  
> 
> */segueix-nos
> 
> /*
>  
> 
> www.carver-as.com 
> 
> 
> 2016-04-12 20:43 GMT+02:00 Mark Thomas  >:
> 
> On 12/04/2016 19:30, Josep M Beleta wrote:
> > Hi,
> >
> > I need some help with a problem we have running Tomcat 8, with Java 
> 8 on
> > a Windows 2008 R2 Standard with Service Pack 1 running as a virtual
> > machine on top of ESXi, 5.1.0. The virtual machine has 16 GB of 
> memory
> > and 4 CPUs. The physical host computer has lots of memory and is not
> > stressed at all.
> >
> > One week ago our Tomcats, we have two, began to use high CPU. When 
> the
> > problem started we had no made any change we can remember in the
> > preceding week, and no Windows update was installed.
> >
> > We use two Tomcats, one of them with some in-house applications the
> > other one with Jira. Both began to shows the same symptoms roughly 
> at
> > the same time.
> >
> > The Jira Tomcat version is 8.0.17 and runs with  Java 1.8.0_51 64 
> Bit,
> > the other Tomcat is 8.0.33 and runs over Java 1.8.0_77 64 Bit.
> >
> > These are the facts we can summarize:
> >
> >  1. Now we run only the Tomcat for our in-house
> applications.We stopped
> > the Jira one.
> >  2. We run it as a service.
> >  3. Every time, two hours after launching the Tomcat service,
> the CPU
> > use jumps to 70-75% and some time after (one hour more) it 
> reaches
> > 100 %. More threads are allocated using lots of CPU. The final
> > result is our entire system being degraded as time goes on.
> >  4. The problems has nothing to do with our applications. We
> undeployed
> > them with the same result.
> >  5. We tested versions 8.0.23 and 8.0.33 in our internal
> Tomcat with the
> > same results.
> >  6. We tested JVM 1.8.0_66, 1.8.0_71 and 1.8.0_77 with the
> same results.
> >  7. We have changed some JVM parameters, allocating more heap
> memory, or
> > changing GC  methods with always the same result, 100% CPU.
> >  8. Using jstack we take several thread dumps that we are
> enclosing in
> > this message. Dump75 is whe the CPU was at 75 %, the other one,
> > Dump100, the CPU was at 100%.
> >  9. I am attaching the Process Explorer images of the Tomcat
> process
> > showing also the Tomcat threads. I am including a Tomcat manager
> > screenshot showing the status of the server.
> >
> > Any help would be deeply appreciated,
> 
> We really need to see those thread dumps. I've checked the list
> config
> and plain text files should be allowed through. I'm attaching a test
> file to this message to confirm that. If it comes through, please
> provide your thread dumps in plain text form and we can take a look.
> 
> Mark
> 
> 
> 
> -
> 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
>

Re: Tomcat 8 uses high CPU

2016-04-12 Thread Josep M Beleta

I am sorry, I sent the same file twice.

Here is the other one.

*Josep M Beleta*

*Director de Tecnologia*


Carver Advanced Systems, S.L.
París, 184. 4º  08036 - Barcelona


Tel:  93 238 5880
Fax: 93 238 5881

*segueix-nos *



www.carver-as.com


2016-04-12 20:49 GMT+02:00 Josep M Beleta :

> Hi Mark, thanks a lot.
>
> here come the dumps:
>
> Josep
>
>
> *Josep M Beleta*
>
> *Director de Tecnologia*
>
>
> Carver Advanced Systems, S.L.
> París, 184. 4º  08036 - Barcelona
>
>
> Tel:  93 238 5880
> Fax: 93 238 5881
>
> *segueix-nos
> *
> 
> 
>
> www.carver-as.com
>
>
> 2016-04-12 20:43 GMT+02:00 Mark Thomas :
>
>> On 12/04/2016 19:30, Josep M Beleta wrote:
>> > Hi,
>> >
>> > I need some help with a problem we have running Tomcat 8, with Java 8 on
>> > a Windows 2008 R2 Standard with Service Pack 1 running as a virtual
>> > machine on top of ESXi, 5.1.0. The virtual machine has 16 GB of memory
>> > and 4 CPUs. The physical host computer has lots of memory and is not
>> > stressed at all.
>> >
>> > One week ago our Tomcats, we have two, began to use high CPU. When the
>> > problem started we had no made any change we can remember in the
>> > preceding week, and no Windows update was installed.
>> >
>> > We use two Tomcats, one of them with some in-house applications the
>> > other one with Jira. Both began to shows the same symptoms roughly at
>> > the same time.
>> >
>> > The Jira Tomcat version is 8.0.17 and runs with  Java 1.8.0_51 64 Bit,
>> > the other Tomcat is 8.0.33 and runs over Java 1.8.0_77 64 Bit.
>> >
>> > These are the facts we can summarize:
>> >
>> >  1. Now we run only the Tomcat for our in-house applications.We stopped
>> > the Jira one.
>> >  2. We run it as a service.
>> >  3. Every time, two hours after launching the Tomcat service, the CPU
>> > use jumps to 70-75% and some time after (one hour more) it reaches
>> > 100 %. More threads are allocated using lots of CPU. The final
>> > result is our entire system being degraded as time goes on.
>> >  4. The problems has nothing to do with our applications. We undeployed
>> > them with the same result.
>> >  5. We tested versions 8.0.23 and 8.0.33 in our internal Tomcat with the
>> > same results.
>> >  6. We tested JVM 1.8.0_66, 1.8.0_71 and 1.8.0_77 with the same results.
>> >  7. We have changed some JVM parameters, allocating more heap memory, or
>> > changing GC  methods with always the same result, 100% CPU.
>> >  8. Using jstack we take several thread dumps that we are enclosing in
>> > this message. Dump75 is whe the CPU was at 75 %, the other one,
>> > Dump100, the CPU was at 100%.
>> >  9. I am attaching the Process Explorer images of the Tomcat process
>> > showing also the Tomcat threads. I am including a Tomcat manager
>> > screenshot showing the status of the server.
>> >
>> > Any help would be deeply appreciated,
>>
>> We really need to see those thread dumps. I've checked the list config
>> and plain text files should be allowed through. I'm attaching a test
>> file to this message to confirm that. If it comes through, please
>> provide your thread dumps in plain text form and we can take a look.
>>
>> Mark
>>
>>
>>
>> -
>> 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

Re: Tomcat 8 uses high CPU

2016-04-12 Thread Christopher Schultz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Josep,

On 4/12/16 2:30 PM, Josep M Beleta wrote:
> I need some help with a problem we have running Tomcat 8, with Java
> 8 on a Windows 2008 R2 Standard with Service Pack 1 running as a
> virtual machine on top of ESXi, 5.1.0. The virtual machine has 16
> GB of memory and 4 CPUs. The physical host computer has lots of
> memory and is not stressed at all.
> 
> One week ago our Tomcats, we have two, began to use high CPU. When
> the problem started we had no made any change we can remember in
> the preceding week, and no Windows update was installed.
> 
> We use two Tomcats, one of them with some in-house applications
> the other one with Jira. Both began to shows the same symptoms
> roughly at the same time.
> 
> The Jira Tomcat version is 8.0.17 and runs with  Java 1.8.0_51 64
> Bit, the other Tomcat is 8.0.33 and runs over Java 1.8.0_77 64 Bit.
> 
> 
> These are the facts we can summarize:
> 
> 1. Now we run only the Tomcat for our in-house applications.We
> stopped the Jira one. 2. We run it as a service. 3. Every time, two
> hours after launching the Tomcat service, the CPU use jumps to
> 70-75% and some time after (one hour more) it reaches 100 %. More
> threads are allocated using lots of CPU. The final result is our
> entire system being degraded as time goes on. 4. The problems has
> nothing to do with our applications. We undeployed them with the
> same result.

So if you start Tomcat with no applications deployed and make no
requests, Tomcat starts taking 75% of the CPU after 2 hours?

Mark is right: we need to see those thread dumps. It looks like your
second attempt also didn't work. Please try to re-attach them as plain
text files.

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlcNQ2QACgkQ9CaO5/Lv0PDJTwCfWuiSiAqrb8hYw5YQLOxE52uX
isIAnRpR9Vj2GZLjiCMr6+hnFbB7eEPb
=/3nu
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 8 uses high CPU

2016-04-12 Thread Josep M Beleta

Hi Mark, thanks a lot.

here come the dumps:

Josep


*Josep M Beleta*

*Director de Tecnologia*


Carver Advanced Systems, S.L.
París, 184. 4º  08036 - Barcelona


Tel:  93 238 5880
Fax: 93 238 5881

*segueix-nos *



www.carver-as.com


2016-04-12 20:43 GMT+02:00 Mark Thomas :

> On 12/04/2016 19:30, Josep M Beleta wrote:
> > Hi,
> >
> > I need some help with a problem we have running Tomcat 8, with Java 8 on
> > a Windows 2008 R2 Standard with Service Pack 1 running as a virtual
> > machine on top of ESXi, 5.1.0. The virtual machine has 16 GB of memory
> > and 4 CPUs. The physical host computer has lots of memory and is not
> > stressed at all.
> >
> > One week ago our Tomcats, we have two, began to use high CPU. When the
> > problem started we had no made any change we can remember in the
> > preceding week, and no Windows update was installed.
> >
> > We use two Tomcats, one of them with some in-house applications the
> > other one with Jira. Both began to shows the same symptoms roughly at
> > the same time.
> >
> > The Jira Tomcat version is 8.0.17 and runs with  Java 1.8.0_51 64 Bit,
> > the other Tomcat is 8.0.33 and runs over Java 1.8.0_77 64 Bit.
> >
> > These are the facts we can summarize:
> >
> >  1. Now we run only the Tomcat for our in-house applications.We stopped
> > the Jira one.
> >  2. We run it as a service.
> >  3. Every time, two hours after launching the Tomcat service, the CPU
> > use jumps to 70-75% and some time after (one hour more) it reaches
> > 100 %. More threads are allocated using lots of CPU. The final
> > result is our entire system being degraded as time goes on.
> >  4. The problems has nothing to do with our applications. We undeployed
> > them with the same result.
> >  5. We tested versions 8.0.23 and 8.0.33 in our internal Tomcat with the
> > same results.
> >  6. We tested JVM 1.8.0_66, 1.8.0_71 and 1.8.0_77 with the same results.
> >  7. We have changed some JVM parameters, allocating more heap memory, or
> > changing GC  methods with always the same result, 100% CPU.
> >  8. Using jstack we take several thread dumps that we are enclosing in
> > this message. Dump75 is whe the CPU was at 75 %, the other one,
> > Dump100, the CPU was at 100%.
> >  9. I am attaching the Process Explorer images of the Tomcat process
> > showing also the Tomcat threads. I am including a Tomcat manager
> > screenshot showing the status of the server.
> >
> > Any help would be deeply appreciated,
>
> We really need to see those thread dumps. I've checked the list config
> and plain text files should be allowed through. I'm attaching a test
> file to this message to confirm that. If it comes through, please
> provide your thread dumps in plain text form and we can take a look.
>
> Mark
>
>
>
> -
> 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

Re: Tomcat 8 uses high CPU

2016-04-12 Thread Mark Thomas

On 12/04/2016 19:30, Josep M Beleta wrote:
> Hi,
> 
> I need some help with a problem we have running Tomcat 8, with Java 8 on
> a Windows 2008 R2 Standard with Service Pack 1 running as a virtual
> machine on top of ESXi, 5.1.0. The virtual machine has 16 GB of memory
> and 4 CPUs. The physical host computer has lots of memory and is not
> stressed at all.
> 
> One week ago our Tomcats, we have two, began to use high CPU. When the
> problem started we had no made any change we can remember in the
> preceding week, and no Windows update was installed.
> 
> We use two Tomcats, one of them with some in-house applications the
> other one with Jira. Both began to shows the same symptoms roughly at
> the same time.
> 
> The Jira Tomcat version is 8.0.17 and runs with  Java 1.8.0_51 64 Bit,
> the other Tomcat is 8.0.33 and runs over Java 1.8.0_77 64 Bit. 
> 
> These are the facts we can summarize:
> 
>  1. Now we run only the Tomcat for our in-house applications.We stopped
> the Jira one.
>  2. We run it as a service.
>  3. Every time, two hours after launching the Tomcat service, the CPU
> use jumps to 70-75% and some time after (one hour more) it reaches
> 100 %. More threads are allocated using lots of CPU. The final
> result is our entire system being degraded as time goes on.
>  4. The problems has nothing to do with our applications. We undeployed
> them with the same result.
>  5. We tested versions 8.0.23 and 8.0.33 in our internal Tomcat with the
> same results.
>  6. We tested JVM 1.8.0_66, 1.8.0_71 and 1.8.0_77 with the same results.
>  7. We have changed some JVM parameters, allocating more heap memory, or
> changing GC  methods with always the same result, 100% CPU.
>  8. Using jstack we take several thread dumps that we are enclosing in
> this message. Dump75 is whe the CPU was at 75 %, the other one,
> Dump100, the CPU was at 100%.
>  9. I am attaching the Process Explorer images of the Tomcat process
> showing also the Tomcat threads. I am including a Tomcat manager
> screenshot showing the status of the server.
> 
> Any help would be deeply appreciated,

We really need to see those thread dumps. I've checked the list config
and plain text files should be allowed through. I'm attaching a test
file to this message to confirm that. If it comes through, please
provide your thread dumps in plain text form and we can take a look.

Mark

This is a test
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Obsolete cypher suit

2016-04-12 Thread Christopher Schultz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

All,

On 4/12/16 2:32 PM, Christopher Schultz wrote:
> Lyallex,
> 
> On 4/12/16 2:11 PM, Lyallex wrote:
>> On 12 April 2016 at 18:06, Lyallex  wrote:
>>> apache-tomcat-7.0.42 as standalone web server jdk1.7.0_45
>>> Ubuntu 12.10
>>> 
>>> Greetings
>>> 
>>> I'm sure this is an old chestnut but it's got me stumped
>>> 
>>> I just purchased and installed my first ever ssl certificate I 
>>> had it installed and apparently running in no time. I should of
>>>  course have been suspicious that it all went so smoothly but
>>> I though it was about time I got a break ... no such luck.
>>> 
>>> Clicking the padlock in chrome I get
>>> 
>>> Your connection to 192.168.1.68 is encrypted using an obsolete 
>>> cipher suit.
>>> 
>>> The connection uses TLS 1.2.
>>> 
>>> The connection is encrypted using AES_128_CBC with HMAC-SHA1
>>> for message authentication and ECDHE_RSA as the key exchange 
>>> mechanism.
> 
>> jdk1.8.0.77 fixed it
> 
>> Should have know it was a Java (as opposed to Tomcat) problem
> 
> You did have this cipher suite configured in your ,
> though:
> 
> TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
> 
> That's the one Chrome was complaining about. (Though I'm not sure
> why it doesn't like that cipher suite).

Aaaand it's obvious, now. I was only looking at the cipher and hashing
algorithms. I didn't see the "AES + CBC" which is a red flag these days.

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlcNP3kACgkQ9CaO5/Lv0PBx5ACfaz2VUHZNWnFr7QhCrWwLO9Db
e98AnRC4t0Hkz5FTM7jUriXnI8uRhMjG
=Xixo
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Monitoring Tomcat

2016-04-12 Thread Anthony Biacco

On Sat, Apr 2, 2016 at 4:47 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:

>
> What regular expression did you try?
>
> How about this one:
>
> ^OK.*=\s*([0-9.]+)$
>
> -chris
>

sorry it took so long, i've been in dynamodb hell.
that worked as the -r and -R
grazie!

-Tony


>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: Obsolete cypher suit

2016-04-12 Thread Christopher Schultz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Lyallex,

On 4/12/16 2:11 PM, Lyallex wrote:
> On 12 April 2016 at 18:06, Lyallex  wrote:
>> apache-tomcat-7.0.42 as standalone web server jdk1.7.0_45 Ubuntu
>> 12.10
>> 
>> Greetings
>> 
>> I'm sure this is an old chestnut but it's got me stumped
>> 
>> I just purchased and installed my first ever ssl certificate I
>> had it installed and apparently running in no time. I should of 
>> course have been suspicious that it all went so smoothly but I
>> though it was about time I got a break ... no such luck.
>> 
>> Clicking the padlock in chrome I get
>> 
>> Your connection to 192.168.1.68 is encrypted using an obsolete
>> cipher suit.
>> 
>> The connection uses TLS 1.2.
>> 
>> The connection is encrypted using AES_128_CBC with HMAC-SHA1 for 
>> message authentication and ECDHE_RSA as the key exchange
>> mechanism.
> 
> jdk1.8.0.77 fixed it
> 
> Should have know it was a Java (as opposed to Tomcat) problem

You did have this cipher suite configured in your , though:

  TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA

That's the one Chrome was complaining about. (Though I'm not sure why
it doesn't like that cipher suite).

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlcNPyUACgkQ9CaO5/Lv0PCa4ACfUHcftICEAlwB25PExNjgw8CZ
4cEAoJKegblaMMmlFn/7CtH5t76cdWHI
=SocL
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Obsolete cypher suit

2016-04-12 Thread Mark Thomas

On 12/04/2016 19:11, Lyallex wrote:
> On 12 April 2016 at 18:06, Lyallex  wrote:
>> apache-tomcat-7.0.42 as standalone web server
>> jdk1.7.0_45
>> Ubuntu 12.10
>>
>> Greetings
>>
>> I'm sure this is an old chestnut but it's got me stumped
>>
>> I just purchased and installed my first ever ssl certificate
>> I had it installed and apparently running in no time. I should of
>> course have been suspicious that it all went so smoothly
>> but I though it was about time I got a break ... no such luck.
>>
>> Clicking the padlock in chrome I get
>>
>> Your connection to 192.168.1.68 is encrypted using an obsolete cipher suit.
>>
>> The connection uses TLS 1.2.
>>
>> The connection is encrypted using AES_128_CBC with HMAC-SHA1 for
>> message authentication and ECDHE_RSA as the key exchange mechanism.
> 
> jdk1.8.0.77 fixed it
> 
> Should have know it was a Java (as opposed to Tomcat) problem
> 
> as you were

As of the next Tomcat 7 release, the SSL defaults have been improved so
a default configuration should not report any issues.

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Help needed

2016-04-12 Thread Mark Thomas

On 12/04/2016 18:42, Sajin S wrote:
>  I am using tomcat 8.0.33 and getting this issue. Kindly help me.
> 
> 
> While doing asynchronous call back and write the output using outputstream
> am getting this issue.
> 
> 
> Current protocol is bio. Please help.

You've removed the exception information that would let us help you.

What you have left clearly shows you are not using BIO.

It looks like you need to read this:
http://www.catb.org/esr/faqs/smart-questions.html

Mark

> 
> 
> 
> Expection :
> 
> at org.apache.coyote.http11.InternalAprOutputBuffer.addToBB(
> *InternalAprOutputBuffer.java:186*)
> 
>at org.apache.coyote.http11.InternalAprOutputBuffer.access$000(
> *InternalAprOutputBuffer.java:40*)
> 
>at
> org.apache.coyote.http11.InternalAprOutputBuffer$SocketOutputBuffer.doWrite(
> *InternalAprOutputBuffer.java:349*)
> 
>at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(
> *ChunkedOutputFilter.java:116*)
> 
>at org.apache.coyote.http11.AbstractOutputBuffer.doWrite(
> *AbstractOutputBuffer.java:256*)
> 
>at org.apache.coyote.Response.doWrite(*Response.java:501*)
> 
>at org.apache.catalina.connector.OutputBuffer.realWriteBytes(
> *OutputBuffer.java:388*)
> 
>at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(
> *ByteChunk.java:426*)
> 
>at org.apache.tomcat.util.buf.ByteChunk.append(*ByteChunk.java:339*)
> 
>at org.apache.catalina.connector.OutputBuffer.writeBytes(
> *OutputBuffer.java:418*)
> 
>at org.apache.catalina.connector.OutputBuffer.write(
> *OutputBuffer.java:406*)
> 
>at org.apache.catalina.connector.CoyoteOutputStream.write(
> *CoyoteOutputStream.java:97*)
> 
>at
> jp.co.hitachi_ul.mvspf.restbase.service.RestVoiceService$1$1.onChunkReceived(
> *RestVoiceService.java:170*)
> 
>at
> jp.co.hitachi_ul.mvspf.middleware.base.SessionContainer.onChunkReceived(
> *SessionContainer.java:106*)
> 
>at jp.co.hitachi_ul.mvspf.middleware.util.IpThread.callback(
> *IpThread.java:188*)
> 
>at jp.co.hitachi_ul.mvspf.middleware.util.IpAdapter$ReadThread.run(
> *IpAdapter.java:193*)
> Thanks & Regards,
> Sajin S
> +919995047208
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Obsolete cypher suit

2016-04-12 Thread Lyallex

On 12 April 2016 at 18:06, Lyallex  wrote:
> apache-tomcat-7.0.42 as standalone web server
> jdk1.7.0_45
> Ubuntu 12.10
>
> Greetings
>
> I'm sure this is an old chestnut but it's got me stumped
>
> I just purchased and installed my first ever ssl certificate
> I had it installed and apparently running in no time. I should of
> course have been suspicious that it all went so smoothly
> but I though it was about time I got a break ... no such luck.
>
> Clicking the padlock in chrome I get
>
> Your connection to 192.168.1.68 is encrypted using an obsolete cipher suit.
>
> The connection uses TLS 1.2.
>
> The connection is encrypted using AES_128_CBC with HMAC-SHA1 for
> message authentication and ECDHE_RSA as the key exchange mechanism.

jdk1.8.0.77 fixed it

Should have know it was a Java (as opposed to Tomcat) problem

as you were

snip

lyallex

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Help needed

2016-04-12 Thread Sajin S

 I am using tomcat 8.0.33 and getting this issue. Kindly help me.


While doing asynchronous call back and write the output using outputstream
am getting this issue.


Current protocol is bio. Please help.



Expection :

at org.apache.coyote.http11.InternalAprOutputBuffer.addToBB(
*InternalAprOutputBuffer.java:186*)

   at org.apache.coyote.http11.InternalAprOutputBuffer.access$000(
*InternalAprOutputBuffer.java:40*)

   at
org.apache.coyote.http11.InternalAprOutputBuffer$SocketOutputBuffer.doWrite(
*InternalAprOutputBuffer.java:349*)

   at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(
*ChunkedOutputFilter.java:116*)

   at org.apache.coyote.http11.AbstractOutputBuffer.doWrite(
*AbstractOutputBuffer.java:256*)

   at org.apache.coyote.Response.doWrite(*Response.java:501*)

   at org.apache.catalina.connector.OutputBuffer.realWriteBytes(
*OutputBuffer.java:388*)

   at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(
*ByteChunk.java:426*)

   at org.apache.tomcat.util.buf.ByteChunk.append(*ByteChunk.java:339*)

   at org.apache.catalina.connector.OutputBuffer.writeBytes(
*OutputBuffer.java:418*)

   at org.apache.catalina.connector.OutputBuffer.write(
*OutputBuffer.java:406*)

   at org.apache.catalina.connector.CoyoteOutputStream.write(
*CoyoteOutputStream.java:97*)

   at
jp.co.hitachi_ul.mvspf.restbase.service.RestVoiceService$1$1.onChunkReceived(
*RestVoiceService.java:170*)

   at
jp.co.hitachi_ul.mvspf.middleware.base.SessionContainer.onChunkReceived(
*SessionContainer.java:106*)

   at jp.co.hitachi_ul.mvspf.middleware.util.IpThread.callback(
*IpThread.java:188*)

   at jp.co.hitachi_ul.mvspf.middleware.util.IpAdapter$ReadThread.run(
*IpAdapter.java:193*)
Thanks & Regards,
Sajin S
+919995047208

Obsolete cypher suit

2016-04-12 Thread Lyallex

apache-tomcat-7.0.42 as standalone web server
jdk1.7.0_45
Ubuntu 12.10

Greetings

I'm sure this is an old chestnut but it's got me stumped

I just purchased and installed my first ever ssl certificate
I had it installed and apparently running in no time. I should of
course have been suspicious that it all went so smoothly
but I though it was about time I got a break ... no such luck.

Clicking the padlock in chrome I get

Your connection to 192.168.1.68 is encrypted using an obsolete cipher suit.

The connection uses TLS 1.2.

The connection is encrypted using AES_128_CBC with HMAC-SHA1 for
message authentication and ECDHE_RSA as the key exchange mechanism.

I followed the instructions here

https://www.sslshopper.com/article-how-to-disable-weak-ciphers-and-ssl-2-in-tomcat.html
and passed then following when starting tomcat
-Dhttps.protocols=TLSv1,TLSv1.1,TLSv1.2 \

No luck so far

here is server.xml

  



Any pointers to useful resources much appreciated

TIA
Lyallex

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: async servlet, tomcat 8.0.33, behind apache

2016-04-12 Thread Christopher Schultz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

fachhoch,

On 4/12/16 10:00 AM, fachhoch wrote:
> async servlet  with tomcat 8.33,   when behind apache web server is
> causing issues, without apache web server, only tomcat, works fine,
> with apache its not working, to make async servlet work with
> tomcat, and apache   what changes are required?are there any
> recommendations? how to troubleshoot the issue? currently   using
> mod_jk connector. Please advice.

http://tomcat.markmail.org/thread/2jeluyiqjp5hjxg3
http://markmail.org/message/5oyqgyjuhfjsf666

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlcNGlEACgkQ9CaO5/Lv0PC0VwCePzc2d++EhrKJAFWIObOKCciC
w6UAnjW3iI1LjZ/u2OKHHYC4665e60ww
=PIdA
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: async servlet, tomcat 8.0.33, behind apache

2016-04-12 Thread fachhoch

async servlet  with tomcat 8.33,   when behind apache web server is causing
issues, without apache web server, only tomcat, works fine, with apache its
not working, to make async servlet work with tomcat, and apache   what
changes are required?are there any recommendations? how to troubleshoot
the issue?
currently   using mod_jk connector. Please advice.






--
View this message in context: 
http://tomcat.10.x6.nabble.com/async-servlet-tomcat-8-0-33-behind-apache-tp5049264p5049318.html
Sent from the Tomcat - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Help needed

Re: users Digest 12 Apr 2016 18:54:12 -0000 Issue 12577

Re: Tomcat 8 uses high CPU

Re: async servlet, tomcat 8.0.33, behind apache

Re: Tomcat 8 uses high CPU

Re: async servlet, tomcat 8.0.33, behind apache

Re: Help needed

Re: Help needed

Re: Tomcat 8 uses high CPU

Re: Tomcat 8 uses high CPU

Re: Tomcat 8 uses high CPU

Re: Tomcat 8 uses high CPU

Re: Tomcat 8 uses high CPU

Re: Tomcat 8 uses high CPU

Re: Obsolete cypher suit

Re: Monitoring Tomcat

Re: Obsolete cypher suit

Re: Obsolete cypher suit

Re: Help needed

Re: Obsolete cypher suit

Help needed

Obsolete cypher suit

Re: async servlet, tomcat 8.0.33, behind apache

Re: async servlet, tomcat 8.0.33, behind apache

24 matches

Site Navigation

Mail list logo

Footer information