Hello Lakshani,

thank you for the confirmation.

Regards

Panos Konstantinidis
Consultant
*Cognity
42 Kifissias Av.
151 25 Marousi, Athens, Greece
Tel:   +30-210-6194400
Fax:  +30-210-6194019
Email: pkonstantini...@cognity.gr<mailto:mlaourd...@cognity.gr>

From: Lakshani Gamage [mailto:laksh...@wso2.com]
Sent: Thursday, November 17, 2016 9:38 AM
To: Panagiotis Konstantinidis
Cc: dev@wso2.org; Niranjan Karunanandham; Kishanthan Thangarajah
Subject: Re: [Dev] How to increase the maximum thread timeout.

Hi Panon,
Sorry, It should be seconds accordning to this[1]

[1] 
https://svn.wso2.org/repos/wso2/trunk/carbon/core/org.wso2.carbon.tomcat.ext/src/main/java/org/wso2/carbon/tomcat/ext/valves/CarbonStuckThreadDetectionValve.java
Regards,
Lakshani


On Thu, Nov 17, 2016 at 12:43 PM, Panagiotis Konstantinidis 
<pkonstantini...@cognity.gr<mailto:pkonstantini...@cognity.gr>> wrote:
Hello Lakshani

>  I said minutes not seconds.
yes, sorry, my mistake, so the value in the Valve element in tomcat’s 
configuration file is in minutes, not in seconds. Can you confirm? I am asking 
you since the default value is

<Valve 
className="org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve" 
threshold="600"/>

which, according to you, means 600 minutes (10 hours). But the transactions was 
failing after about 10’ from the start of the request, which would seem is just 
about right since 600’’ is 10’.

Can you confirm that it is indeed minutes and not seconds?

Regards

Panos Konstantinidis
Consultant
*Cognity
42 Kifissias Av.
151 25 Marousi, Athens, Greece
Tel:   +30-210-6194400<tel:%2B30-210-6194400>
Fax:  +30-210-6194019<tel:%2B30-210-6194019>
Email: pkonstantini...@cognity.gr<mailto:mlaourd...@cognity.gr>

From: Lakshani Gamage [mailto:laksh...@wso2.com<mailto:laksh...@wso2.com>]
Sent: Wednesday, November 16, 2016 6:32 PM
To: Panagiotis Konstantinidis
Cc: dev@wso2.org<mailto:dev@wso2.org>; Niranjan Karunanandham; Kishanthan 
Thangarajah

Subject: Re: [Dev] How to increase the maximum thread timeout.

Hi Panos,

On Wed, Nov 16, 2016 at 9:44 PM, Panagiotis Konstantinidis 
<pkonstantini...@cognity.gr<mailto:pkonstantini...@cognity.gr>> wrote:
Hello Lakshani,

thank you for your suggestion, I have already tried it before I read your 
message and it worked. The key was to change the threshold value in the 
catalina-server.xml instead.

Just a couple of questions if you may.


1)      What is the meaning of the MaxThreadExecutionTime if we need to change 
Tomcat’s configuration file?
I don't have a clear idea  of the MaxThreadExecutionTime. I'll cc a member of 
Kernal team.

2)      Is the threshold in minutes or in seconds (you said seconds, this is 
why I am asking).
 I said minutes not seconds.
Thanks,
Lakshani

Regards

Panos

From: Lakshani Gamage [mailto:laksh...@wso2.com<mailto:laksh...@wso2.com>]
Sent: Wednesday, November 16, 2016 5:33 PM
To: Panagiotis Konstantinidis
Cc: dev@wso2.org<mailto:dev@wso2.org>
Subject: Re: [Dev] How to increase the maximum thread timeout.

Hi Panos,

Can you please try changing threshold value of <Valve 
className="org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve" 
threshold="600"/> in <AS_HOME>/repository/conf/tomcat/catalina-server.xml 
accordingly to your task completance time. Threshold is in minutes.
Regards,
Lakshani.

On Wed, Nov 16, 2016 at 8:38 PM, Panagiotis Konstantinidis 
<pkonstantini...@cognity.gr<mailto:pkonstantini...@cognity.gr>> wrote:
Hello,

we are using WSO2 AS Server 5.3. We have a long running task in the database 
which takes more than 20 minutes to complete. During this time the server 
throws a ThreadDeath exception (since it detects a stuck thread) and is killing 
the thread that deals with the database.

How can I increase the maximum thread timeout? I have tried to modify the 
carbon.xml and change the

    <!-- The Max time a thread should take for execution in seconds -->
    <MaxThreadExecutionTime>600</MaxThreadExecutionTime>

to 1800 (half an hour) but it seems that this makes no difference whatsoever to 
the thread timeout. The server keeps killing the thread before this timeout is 
reached.

Is there any other flag I can use? I would appreciate any help on this issue.

Regards

Panos
_______________________________________________
Dev mailing list
Dev@wso2.org<mailto:Dev@wso2.org>
http://wso2.org/cgi-bin/mailman/listinfo/dev



--
Lakshani Gamage
Software Engineer, WSO2

Mobile : +94 71 5478184<tel:%2B94%20%280%29%20773%20451194>
Blog : http://lakshanigamage.blogspot.com/



--
Lakshani Gamage
Software Engineer, WSO2

Mobile : +94 71 5478184<tel:%2B94%20%280%29%20773%20451194>
Blog : http://lakshanigamage.blogspot.com/



--
Lakshani Gamage
Software Engineer, WSO2

Mobile : +94 71 5478184<tel:%2B94%20%280%29%20773%20451194>
Blog : http://lakshanigamage.blogspot.com/
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to