Re: https redirect failed for POST request when behind a load balancer

2017-01-18 Thread Konstantin Kolinko
2017-01-19 9:32 GMT+03:00 Bin Chen : > Hi, I've been looking for a solution to this question. We have a setup of a > couple api servers running tomcat 7.0.65. For both servers we had http > redirect to https set up so when people access to > http://my-api1:8080, it is

https redirect failed for POST request when behind a load balancer

2017-01-18 Thread Bin Chen
Hi, I've been looking for a solution to this question. We have a setup of a couple api servers running tomcat 7.0.65. For both servers we had http redirect to https set up so when people access to http://my-api1:8080, it is automatically redirect to https://my-api1:8443 The redirect works fine

RE: FW: tomcat 8080 thread not reduced

2017-01-18 Thread smith
Hi, Christopher I don't care if the threads will be reduced, I just want to know why. And we want to use the account to determine when the tomcat capacity is not enough that we need to add max configuration or add new tomcat servers. Since not use the , the busy thread account also cannot tell

Re: Suggested doc change for Connectors

2017-01-18 Thread Mark Thomas
On 18/01/2017 13:02, André Warnier (tomcat) wrote: > On 18.01.2017 13:00, Mark Thomas wrote: >> Maybe change the first sentence to: >> >> The number of idle threads Tomcat keeps available to handle new >> requests. Note that excess idle threads are not stopped. The total >> number of threads

Re: TomcatCon @ ApacheCon

2017-01-18 Thread Terence M. Bandoian
On 1/17/2017 4:04 PM, Mark Thomas wrote: On 09/01/2017 11:57, Mark Thomas wrote: I look forward to hearing your topic ideas. Thanks for all the great ideas so far. I've tried to pull them all together here: https://cwiki.apache.org/confluence/display/TOMCAT/TomcatCon+NA+2017 I'm waiting to

Re: SEVERE: Servlet.service() for servlet [Jersey Web Application] in context with path [/grocerystore] threw exception [java.lang.IllegalArgumentException: Property 'dataSource' is required] with roo

2017-01-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Kunal, On 1/18/17 9:10 AM, kunal.parn...@wissen.com wrote: > I am using Jersey to develop REST Services in Java using Spring > JdbcTemplate. > > I have posted my query on StackOverflow You sure have. - -chris -BEGIN PGP SIGNATURE-

Re: Suggested doc change for Connectors

2017-01-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, On 1/18/17 8:02 AM, André Warnier (tomcat) wrote: > So what you are saying above, is that the "minSpareThreads" > attribute in a Connector (without Executor) is not really being > ignored. Right. > It is just the "shrinking" part of it

ApacheCon CFP closing soon (11 February)

2017-01-18 Thread Rich Bowen
Hello, fellow Apache enthusiast. Thanks for your participation, and interest in, the projects of the Apache Software Foundation. I wanted to remind you that the Call For Papers (CFP) for ApacheCon North America, and Apache: Big Data North America, closes in less than a month. If you've been

Re: FW: tomcat 8080 thread not reduced

2017-01-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Smith, On 1/18/17 12:47 AM, smith wrote: > So the tomcat default executor will not reduce the thread count > until it reach to the max configuration? By default, you get a thread pool that isn't as smart as an executor. > Will it reduce when it

Re: FW: tomcat 8080 thread not reduced

2017-01-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Smith, On 1/18/17 7:42 AM, Smith Hua wrote: > our monitor is getting the result from the tomcat manager page > which provides the busy threads count and totol threads count, i'm > not sure if tomcat manager treat the keepAlived thread as free. If

Re: Tomcat Version 7.0.34 + jdk 1.6 is not supporting TLS Protocol TLS1.2

2017-01-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dhanesh, On 1/18/17 6:03 AM, dhanesh1212121212 wrote: > Thanks for the support. This meets our requirement. We are going > with stable java 1.8 version (default TLSv1.2) which has support > for tomcat 7.0.34 + TLSv1.2. I would recommend upgrading

Re: Cannot Allocate Memory errno=12

2017-01-18 Thread tomcat
On 18.01.2017 15:13, Fady Haikal wrote: Thank You Andre so much will check the below now quick fix, without guarantee : in your setenv.sh file, just replace JAVA_OPTS=.. by CATALINA_OPTS=.. and you will probably be ok. On Wed, Jan 18, 2017 at 4:10 PM, André Warnier (tomcat)

SEVERE: Servlet.service() for servlet [Jersey Web Application] in context with path [/grocerystore] threw exception [java.lang.IllegalArgumentException: Property 'dataSource' is required] with root ca

2017-01-18 Thread kunal.parn...@wissen.com
I am using Jersey to develop REST Services in Java using Spring JdbcTemplate. I have posted my query on StackOverflow Here's the link http://stackoverflow.com/questions/41706267/exception-java-lang-illegalargumentexception-property-datasource-is-required

Re: Cannot Allocate Memory errno=12

2017-01-18 Thread Fady Haikal
Thank You Andre so much will check the below now On Wed, Jan 18, 2017 at 4:10 PM, André Warnier (tomcat) wrote: > On 18.01.2017 14:51, André Warnier (tomcat) wrote: >> >> Actually, I think that you need to look closer at the tomcat shutdown >> scripts on your >> system, and

Re: Cannot Allocate Memory errno=12

2017-01-18 Thread tomcat
On 18.01.2017 14:51, André Warnier (tomcat) wrote: Actually, I think that you need to look closer at the tomcat shutdown scripts on your system, and their settings. If I remember correctly, when you call the tomcat shutdown script, it actually starts another java JVM instance, just to send a

Re: Cannot Allocate Memory errno=12

2017-01-18 Thread tomcat
Actually, I think that you need to look closer at the tomcat shutdown scripts on your system, and their settings. If I remember correctly, when you call the tomcat shutdown script, it actually starts another java JVM instance, just to send a shutdown message to the running tomcat's JVM. And with

Re: Cannot Allocate Memory errno=12

2017-01-18 Thread tomcat
On 18.01.2017 14:20, Fady Haikal wrote: plz find it on the below link https://drive.google.com/file/d/0By0Z6xkBVBFHVGJKVkRqM2hwUVE/view?usp=sharing Hmm, that's a nice logfile. It also starts with a number of hints and recommendations, did you see ? Very generically : When tomcat is shutting

Re: Cannot Allocate Memory errno=12

2017-01-18 Thread Fady Haikal
plz find it on the below link https://drive.google.com/file/d/0By0Z6xkBVBFHVGJKVkRqM2hwUVE/view?usp=sharing On Wed, Jan 18, 2017 at 3:16 PM, André Warnier (tomcat) wrote: > On 18.01.2017 14:08, Fady Haikal wrote: >> >> Yes log already sent, anw attached > > > Well no. Only the

Re: Cannot Allocate Memory errno=12

2017-01-18 Thread tomcat
On 18.01.2017 14:08, Fady Haikal wrote: Yes log already sent, anw attached Well no. Only the "setenv.sh" was attached. This list server strips many attachments. Maybe you need to paste the content directly into your message (if not too long), or post it somewhere where we can look at it.

Re: Cannot Allocate Memory errno=12

2017-01-18 Thread Fady Haikal
Yes log already sent, anw attached On Wed, Jan 18, 2017 at 3:07 PM, André Warnier (tomcat) wrote: > On 18.01.2017 13:49, Fady Haikal wrote: >> >> Guys, We are facing the below error (attached also) while trying to >> shutdown tomcat server >> >> Java HotSpot(TM) 64-Bit Server VM

Re: Cannot Allocate Memory errno=12

2017-01-18 Thread tomcat
On 18.01.2017 13:49, Fady Haikal wrote: Guys, We are facing the below error (attached also) while trying to shutdown tomcat server Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0xd555, 715849728, 0) failed; error='Cannot allocate memory' (errno=12) # # There is

Re: Suggested doc change for Connectors

2017-01-18 Thread tomcat
On 18.01.2017 13:00, Mark Thomas wrote: On 18/01/2017 11:34, André Warnier (tomcat) wrote: Hi. This is a partial recap of the theme discussed on the list, in this thread : http://marc.info/?l=tomcat-user=148473249120783=2 I would sugest a documentation change, basically in all pages related

Cannot Allocate Memory errno=12

2017-01-18 Thread Fady Haikal
Guys, We are facing the below error (attached also) while trying to shutdown tomcat server Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0xd555, 715849728, 0) failed; error='Cannot allocate memory' (errno=12) # # There is insufficient memory for the Java Runtime

Re[2]: FW: tomcat 8080 thread not reduced

2017-01-18 Thread Smith Hua
thanks, our monitor is getting the result from the tomcat manager page which provides the busy threads count and totol threads count, i'm not sure if tomcat manager treat the keepAlived thread as free. if the tomcat manager treat the keepAlived thread as free, seems we can't kown what's the

Re[2]: FW: tomcat 8080 thread not reduced

2017-01-18 Thread Smith Hua
thanks, our monitor is getting the result from the tomcat manager page which provides the busy threads count and totol threads count -- 从myMail的Android专用app所发送 星期三, 18 一月 2017, 06:08下午 +08:00 发件人 André Warnier (tomcat) a...@ice-sa.com : >On 18.01.2017 10:56, smith wrote: >> Hi, André >> >>

Re: Suggested doc change for Connectors

2017-01-18 Thread Mark Thomas
On 18/01/2017 11:34, André Warnier (tomcat) wrote: > Hi. > > This is a partial recap of the theme discussed on the list, in this > thread : > http://marc.info/?l=tomcat-user=148473249120783=2 > > I would sugest a documentation change, basically in all pages related to > Connector's

Suggested doc change for Connectors

2017-01-18 Thread tomcat
Hi. This is a partial recap of the theme discussed on the list, in this thread : http://marc.info/?l=tomcat-user=148473249120783=2 I would sugest a documentation change, basically in all pages related to Connector's configurations, from 9.0, and I believe all the way back to 6.0. The change

Re: Tomcat Version 7.0.34 + jdk 1.6 is not supporting TLS Protocol TLS1.2

2017-01-18 Thread dhanesh1212121212
Hi All, Thanks for the support. This meets our requirement. We are going with stable java 1.8 version (default TLSv1.2) which has support for tomcat 7.0.34 + TLSv1.2. Need one more information. Question is mentioned below. Suppose my web server (Apache) and application (Tomcat) is using TLS1.2

Re: FW: tomcat 8080 thread not reduced

2017-01-18 Thread tomcat
On 18.01.2017 10:56, smith wrote: Hi, André Thanks for the great explanation. So the current thread count will grow always until it reaches to the max configuration. I have another strange thing: We never monitored tomcat busy thread count high (we monitored one minutes interval through

RE: FW: tomcat 8080 thread not reduced

2017-01-18 Thread smith
Hi, André Thanks for the great explanation. So the current thread count will grow always until it reaches to the max configuration. I have another strange thing: We never monitored tomcat busy thread count high (we monitored one minutes interval through Nagios to get tomcat manager result,

RE: FW: tomcat 8080 thread not reduced

2017-01-18 Thread smith
Hi, André My case is same, my tomcat also has load balancer in front and it has health check to tomcat -Original Message- From: André Warnier (tomcat) [mailto:a...@ice-sa.com] Sent: Wednesday, January 18, 2017 9:41 AM To: users@tomcat.apache.org Subject: Re: FW: tomcat 8080 thread not

Re: FW: tomcat 8080 thread not reduced

2017-01-18 Thread tomcat
Hi. I believe that what Philippe mentions below is somewhat different : in his configuration, there is apparently a front-end httpd server, which communicates with Tomcat via AJP and the tomcat AJP Connector. In such a case, the "mod_jk" or "mod_proxy_ajp" connector module inside of httpd,