Hi Thanh,

You might want to use the Stuck thread detection
value<http://tomcat.apache.org/tomcat-6.0-doc/config/valve.html#Stuck_Thread_Detection_Valve>for
logging, if there is some threads that get stuck.
And these might never complete their requests to return back to nginx.

---
Regards,
Saptarshi PURKAYASTHA

My Tech Blog:  http://sunnytalkstech.blogspot.com
You Live by CHOICE, Not by CHANCE


On 19 July 2013 20:11, Ngoc Thanh Nguyen <thanh.hispviet...@gmail.com>wrote:

> Thanks Bob. That's definitely the case. However, do you think this can
> affect the performance? In other words, will it cause server memory or cpu
> problem?
>
> Thanh
>
>
> On Fri, Jul 19, 2013 at 7:24 PM, Bob Jolliffe <bobjolli...@gmail.com>wrote:
>
>> I am sure you have a proxy (nginx or apache?) on the same machine.  So
>> the users access the proxy and the proxy accesses tomcat (which sees the
>> request as a local one).
>>
>> You need to add a directive to your proxy to preserve the name of the
>> requesting host.  On nginx this is:
>>
>> see http://ashberlin.co.uk/blog/nginx-proxy-host-header
>>
>> On apache2:
>>
>> http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypreservehost
>>
>> Bob
>>
>>
>>
>>
>>
>> On 19 July 2013 13:39, <jeromesha...@gmail.com> wrote:
>>
>>> **
>>> Hi Ngoc, no my server is not public
>>> Sent from my BlackBerry wireless device from MTN
>>> ------------------------------
>>> *From: * Ngoc Thanh Nguyen <thanh.hispviet...@gmail.com>
>>> *Date: *Fri, 19 Jul 2013 18:36:20 +0700
>>> *To: *jerome shaguy<jeromesha...@gmail.com>
>>> *Cc: *dhis2-devs<dhis2-devs@lists.launchpad.net>
>>> *Subject: *Re: [Dhis2-devs] Strange request from 127.0.0.1
>>>
>>> Hi Jerome,
>>>
>>> Is your server public? In my case, I am guessing that some bad guys have
>>> hacked into the system by exploiting some security holes of the system or
>>> probably dhis2 itself.
>>>
>>> Thanh
>>>
>>>
>>> On Fri, Jul 19, 2013 at 5:05 PM, jerome shaguy 
>>> <jeromesha...@gmail.com>wrote:
>>>
>>>> Hi,
>>>>
>>>> I have also been experiencing the same problem with my tomcat as
>>>> reported by Ngoc (but in my case it was only after I upgraded my war file
>>>> to 2.12) I am seeing a lot of requests in the log even though I am on
>>>> 127.0.0.1 and its constantly exceeding memory and completely halting simple
>>>> processes... I have tried to adjust memory to tomcat but this has not
>>>> helped. I join Ngoc in asking is there anyone out there with a solution?
>>>>
>>>>
>>>> On Fri, Jul 19, 2013 at 10:20 AM, Ngoc Thanh Nguyen <
>>>> thanh.hispviet...@gmail.com> wrote:
>>>>
>>>>> In our server tomcat access log, there are lots of requests from
>>>>> 127.0.0.1 which is obviously local request. However, no one from our team
>>>>> actually working from the server so it must be automatic requests. This
>>>>> might be the reason for our server problems last several days as the 
>>>>> system
>>>>> always results in full CPU or exceeding memory.
>>>>>
>>>>> Any one have ideas on how to kill these process?
>>>>>
>>>>> Thanks
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list: https://launchpad.net/~dhis2-devs
>>>>> Post to     : dhis2-devs@lists.launchpad.net
>>>>> Unsubscribe : https://launchpad.net/~dhis2-devs
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~dhis2-devs
>>> Post to     : dhis2-devs@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~dhis2-devs
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>
_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to     : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Reply via email to