Thank you for catching my typo and for the information
On Mon, Mar 2, 2015 at 2:55 PM, Konstantin Kolinko
wrote:
> 2015-03-03 1:45 GMT+03:00 Eric :
> > I am trying to change the ciphers that my Tomcat 7 server supports. I am
> > using the APR connector. Here's the connector information in server
2015-03-03 1:45 GMT+03:00 Eric :
> I am trying to change the ciphers that my Tomcat 7 server supports. I am
> using the APR connector. Here's the connector information in server.xml
> with the line saying which ciphers to support:
>
> enableLookups="false" disableUploadTimeout="
I am trying to change the ciphers that my Tomcat 7 server supports. I am
using the APR connector. Here's the connector information in server.xml
with the line saying which ciphers to support:
SSLCipherSuite="ECDHE-RSA-AES128-GCM-SHA256"
I shut down and started Tomcat back up.
For an explanation of what we mean by "please do not top post", see here :
http://www.idallen.com/topposting.html
Got it ?
Rajesh Cherukuri wrote:
Yes it is always 20 sec always the case when the MOD_jk assigns the request
to the tomcat that was down
using Mod_jk 1.2.37 version
On Mon, Mar 2
Please dont top post.
On 03/02/2015 04:07 PM, Rajesh Cherukuri wrote:
Yes it is always 20 sec always the case when the MOD_jk assigns the request
to the tomcat that was down
Are you sure that there's not some other tomcat in the same load
balanced worker that's in hang? Didnt had time to chec
Yes it is always 20 sec always the case when the MOD_jk assigns the request
to the tomcat that was down
using Mod_jk 1.2.37 version
On Mon, Mar 2, 2015 at 8:27 PM, Rainer Jung wrote:
> Please don't top post, it makes following the communication very hard.
>
> Am 02.03.2015 um 12:48 schrieb Raje
Please don't top post, it makes following the communication very hard.
Am 02.03.2015 um 12:48 schrieb Rajesh Cherukuri:
for telnet immediateconnection refused is given
telnet 10.xxx.xxx.xx 8911
Trying 10.xx.xx.x...
telnet: connect to address 10.xx.x.xx: Connection refused
Then I would
Am 02.03.2015 um 13:34 schrieb Umesh Sehgal:
On Mon, Mar 2, 2015 at 5:25 PM, Umesh Sehgal wrote:
On Mon, Mar 2, 2015 at 3:52 PM, Rainer Jung
wrote:
Am 02.03.2015 um 11:02 schrieb Umesh Sehgal:
Thanks for the quick reply, I tried using the maxSwallowSize with
increased
value but to no eff
On Mon, Mar 2, 2015 at 5:25 PM, Umesh Sehgal wrote:
>
>
>
> On Mon, Mar 2, 2015 at 3:52 PM, Rainer Jung
> wrote:
>
>> Am 02.03.2015 um 11:02 schrieb Umesh Sehgal:
>>
>>> Thanks for the quick reply, I tried using the maxSwallowSize with
>>> increased
>>> value but to no effect. The max size that
On Mon, Mar 2, 2015 at 3:52 PM, Rainer Jung wrote:
> Am 02.03.2015 um 11:02 schrieb Umesh Sehgal:
>
>> Thanks for the quick reply, I tried using the maxSwallowSize with
>> increased
>> value but to no effect. The max size that I have been able to upload is
>> ~16
>> KB. I also see that the maxSwa
for telnet immediateconnection refused is given
telnet 10.xxx.xxx.xx 8911
Trying 10.xx.xx.x...
telnet: connect to address 10.xx.x.xx: Connection refused
here is the error log for the specifed time
[Fri Feb 27 02:26:14.463 2015] [31713:140059770595072] [error]
ajp_service::jk_ajp_common
Am 02.03.2015 um 11:34 schrieb Rajesh Cherukuri:
rainer
looks like what you said is correct , but not sure why the Mod_jk has to
wait for 10 seconds when the backend tomcat servers is down
Because your network layer behaves like that. It simply hangs for (more
than) 10 seconds. You should be
rainer
looks like what you said is correct , but not sure why the Mod_jk has to
wait for 10 seconds when the backend tomcat servers is down
here is the error log i don't see that any place where it is aitng for 20
sec
error log
[Thu Feb 26 01:28:35.432 2015] [19535:140214433396480] [error]
ajp
Am 02.03.2015 um 11:02 schrieb Umesh Sehgal:
Thanks for the quick reply, I tried using the maxSwallowSize with increased
value but to no effect. The max size that I have been able to upload is ~16
KB. I also see that the maxSwallowSize got introduced with update 55 but
the behavior I'm seeing is
Am 02.03.2015 um 10:45 schrieb Rajesh Cherukuri:
here is what i can see in modJk log file , we have stopped tomcat 11 a week
back ,
172.x [27/Feb/2015:*02:28:14* +] "GET /xx/deal-finder
HTTP/1.1"200 15172 20 *lb* tomcat--11** 0 26712 12118 **tomcat-03**
0 820679 4 *20.35284
Thanks for the quick reply, I tried using the maxSwallowSize with increased
value but to no effect. The max size that I have been able to upload is ~16
KB. I also see that the maxSwallowSize got introduced with update 55 but
the behavior I'm seeing is 50 update onwards, is there any other param too
here is what i can see in modJk log file , we have stopped tomcat 11 a week
back ,
172.x [27/Feb/2015:*02:28:14* +] "GET /xx/deal-finder
HTTP/1.1"200 15172 20 *lb* tomcat--11** 0 26712 12118 **tomcat-03**
0 820679 4 *20.352845* –
worker configuration
*here is my work.prop
On 02/03/2015 09:21, Yuanxianhu (Tiger, Secospace) wrote:
> My friend,
> Can you give me the bug ID for JVM?
To repeat what I said previously.
We can't help. You'll have to speak yo your JVM vendor.
Mark
>
> Best Regards
>
>
>
>
>
> -邮件原件-
> 发件人: Mark Thomas [mailto:ma...@a
My friend,
Can you give me the bug ID for JVM?
Best Regards
-邮件原件-
发件人: Mark Thomas [mailto:ma...@apache.org]
发送时间: 星期一 2015年3月2日 17:20
收件人: Tomcat Users List
主题: Re: Tomcat 6.0.37 EXCEPTION_ACCESS_VIOLATION Crash
On 02/03/2015 07:47, Yuanxianhu (Tiger, Secospace) wrote:
> D
On 02/03/2015 07:47, Yuanxianhu (Tiger, Secospace) wrote:
> Dear:
>
> I use Tomcat NIO to deal with web request, but tomcat crashed
> frequently because of NIO EXCEPTION_ACCESS_VIOLATION. Attachments are
> crash logs.
>
>
>
> I need you help how to analyze this problem.
We c
Am 02.03.2015 um 09:34 schrieb Umesh Sehgal:
Hi,
We recently upgraded our application's tomcat from 7.0.30 to 7.0.59. After
upgrade the file upload feature has broken. I have been able to nail it
down to the point that the problem manifests 7.0.50 onwards. Here is the
exception that I see inside
Hi,
We recently upgraded our application's tomcat from 7.0.30 to 7.0.59. After
upgrade the file upload feature has broken. I have been able to nail it
down to the point that the problem manifests 7.0.50 onwards. Here is the
exception that I see inside logs:
Caused by: java.net.SocketException:
22 matches
Mail list logo