On Aug 17, 2012, at 1:18 PM, Manidhar gudavalli wrote:

> Paul
> Thank you. Currently thread max is at 1400. Strange thing is, this happens on 
> two pages where the user posts data repeatedly. Some of these IP addresses 
> also repeating in the log. And, there are no issues with the page java code. 
> In my previous setup, I did not gave this problem. I moved to new box and I 
> keep the same resin configuration. However, I  switched to worker RPM in 
> apache and using JDK 1.7 . I dont see any errors in resin log.

Hi Mani,

The fact that the issue is occurring with Resin 4 also leads me to think it's 
not an issue related to Resin at all.  

It could be something related to Apache.  It would help you can take that out 
of the equation but accessing Resin directly.

The only other possibility that occurs to me right now is database lock 
contention for the same rows, since you say it's occurring when the same users 
connect. 

Thanks,
Paul


> 
> 
> I tried to migrate 4.x version and getting the same problem.
> thanks
> Mani
> 
> 
> On Fri, Aug 17, 2012 at 12:09 PM, Paul Cowan <co...@caucho.com> wrote:
> 
> On Aug 17, 2012, at 11:58 AM, Manidhar gudavalli wrote:
> 
>> HI
>> I am seeing a strange 503 error  on the server. When the repeated requests 
>> coming from the clients with the same IP address, after some time, I am 
>> seeing 503 error in apache logs. These requests are all valid requests from 
>> valid ips.
>> 
>> I am using resin 3.1.12. and apache 2.2.3 and JDK 7.
>>  Is resin considering, the repeated request from same IP as spam?
>>  Is there any parameter that I can set to force resin to accepts the 
>> requests and not consider as spam?
> 
> Hi Mani,
> 
> A 503 error usually indicates Resin was unavailable to Apache (ie restarting) 
> or overloaded.  The client IP address should not matter.
> 
> You need to examine the Resin logs to see what is it doing during that time 
> and if there are any errors reported.
> 
> Resin may be running out of resources or paused for a long garbage 
> collection.  Often simply increasing thread-max to a larger number like 2048 
> helps, since the default is rather low for Resin 3.1.
> 
> Thanks,
> Paul
> 
> 
> 
>> 
>> 
>> Please help.
>> 
>> thanks
>> Mani
>> 
>> 
>> _______________________________________________
>> resin-interest mailing list
>> resin-interest@caucho.com
>> http://maillist.caucho.com/mailman/listinfo/resin-interest
> 
> ===============================
> Paul Cowan, Software Engineer
> Caucho Technology
> co...@caucho.com
> http://blog.caucho.com
> http://twitter.com/cauchoresin
> 
> 
> _______________________________________________
> resin-interest mailing list
> resin-interest@caucho.com
> http://maillist.caucho.com/mailman/listinfo/resin-interest
> 
> 
> 
> 
> 
> 
> _______________________________________________
> resin-interest mailing list
> resin-interest@caucho.com
> http://maillist.caucho.com/mailman/listinfo/resin-interest

===============================
Paul Cowan, Software Engineer
Caucho Technology
co...@caucho.com
http://blog.caucho.com
http://twitter.com/cauchoresin

_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Reply via email to