Hi, As per your notes you appear to be using View Results Tree in GUI mode , so you most probably end up with an OOM or huge GC.
This is bad practices as per: http://jmeter.apache.org/usermanual/best-practices.html http://www.ubik-ingenierie.com/blog/jmeter_performance_tuning_tips/ So switch ton NON GUI mode testing and see what you get. Regards Philippe M. @philmdot On Thu, Dec 31, 2015 at 6:52 PM, Himanshu Ghai <[email protected]> wrote: > On Thu, Dec 31, 2015 at 1:15 AM, vidhi vinchhi <[email protected]> > wrote: > > > Hi Himanshu, > > > > please below my answers insline. > > > > 1) Does it start if you change the ramp up time to be longer say 60 > > seconds? > > Nope > > 2) Do you see any errors in jmeter.log? > > Same error. Socket closed it shows. > > 3) Do the 7 working threads execute the requests fine? How fast > > Send request fine if i see in View results tree listener. > > > > I have one question, when jmeter says socket closed what does it mean out > > of below two: > > > > 1. Socket closed at server end so jmeter is not able to communicate any > > more with server? Thats why it stucks in whichever state it is? > > > > If the socket closed error in log/view results tree shows up after you > pressed the stop button. It should be client side. > > > > 2. Socket closed at client end ( My system ) so that jmeter can not more > > send/receive any requests? in this case, jmeter should end the execution > > based on timeout value configured and should not stuck. > > > > Yes it should can you take a thread dump and either look through/send it > here. Take 2 thread dumps when you see 7/60 started threads and send those > along. > > > > > > Thanks, > > Vidhi. > > > > On Thu, Dec 31, 2015 at 2:35 PM, Himanshu Ghai <[email protected]> > > wrote: > > > >> 1) Does it start if you change the ramp up time to be longer say 60 > >> seconds? > >> 2) Do you see any errors in jmeter.log? > >> 3) Do the 7 working threads execute the requests fine? How fast > >> > >> Himanshu > >> > >> > >> On Wed, Dec 30, 2015 at 10:41 PM, vidhi vinchhi <[email protected]> > >> wrote: > >> > >>> Hi Himashu, > >>> > >>> Thank you for your reply. > >>> > >>> 1. The run is stuck means, say i have started run for 60 users with > ramp > >>> up period of 1 sec, Jmeter shows 7/60 and no progress after that even > if I > >>> wait for 1 hr. When I click on Stop button, all the pending ( 7) > requests > >>> are shown socket closed. > >>> > >>> Thanks, > >>> Vidhi. > >>> > >>> On Thu, Dec 31, 2015 at 12:05 PM, Himanshu Ghai < > [email protected]> > >>> wrote: > >>> > >>>> socket closed after pressing stop button may be okay. What do you > >>>> mean when you say your run is stuck? are threads waiting on server > >>>> to respond > >>>> > >>>> Himanshu > >>>> > >>>> On Wed, Dec 30, 2015 at 9:20 PM, vidhi vinchhi <[email protected]> > >>>> wrote: > >>>> > >>>> > Hi All, > >>>> > > >>>> > I am trying to perform load test for a website of my project. > >>>> > > >>>> > I am trying with 50 users with ramp up period of 1 sec. > >>>> > > >>>> > The isssue is that, after some time, my jmeter run stucks, and 6 yo > 7 > >>>> > thread remains unfinished. if I press stop button, The "View Results > >>>> Tree" > >>>> > listener says > >>>> > > >>>> > "Socket closed". > >>>> > > >>>> > Can anybody help me to resolve this issue? Developer says every is > >>>> set to > >>>> > unlimited on server side, then why Jmeter is reporting socket > closed, > >>>> it > >>>> > should report completed response with connection timeout. but it > >>>> stucks. > >>>> > > >>>> > Note: i have already implemented what is mentioned for > >>>> > > >>>> > httpclient4.retrycount=1 > >>>> > hc.parameters.file=hc.parameters > >>>> > > >>>> > http.connection.stalecheck$Boolean=true > >>>> > > >>>> > But did not help. > >>>> > > >>>> > Can anybody help to resolve this?I am using Jmeter 2.13. > >>>> > > >>>> > > >>>> > Thanks, > >>>> > > >>>> > Vidhi. > >>>> > > >>>> > >>> > >>> > >> > > > -- Cordialement. Philippe Mouawad.
