Yes, that is correct. -----Original Message----- From: Bob Nance [mailto:[email protected]] Sent: Friday, June 10, 2016 8:52 AM To: JMeter Users List Subject: Re: Jmeter pausing when running
The original post said that there were 75 thread groups but they were still only running one thread at a time. --- Bob Nance Novation Systems 256-534-4620 (iPhone-flavored) > On Jun 9, 2016, at 4:07 PM, Deepak Shetty <[email protected]> wrote: > > Hi > you mentioned you had something like 75 threads ? The dump you are > including only shows 1 ?Hence are you sure this is the complete threaddump ? > In which case it looks like all your other threads did finish / terminate ? > > regards > deepak > > On Thu, Jun 9, 2016 at 1:44 PM, Janine DeBeradinis < > [email protected]> wrote: > >> I think this is it (I didn't check with the developer but looked at >> the >> dump): >> >> "CSUNPROD_pay 69-1" #108 prio=6 os_prio=0 tid=0x0000000019d08000 >> nid=0x74c runnable [0x00000000253ae000] >> java.lang.Thread.State: RUNNABLE >> at java.net.SocketInputStream.socketRead0(Native Method) >> at java.net.SocketInputStream.socketRead(Unknown Source) >> at java.net.SocketInputStream.read(Unknown Source) >> at java.net.SocketInputStream.read(Unknown Source) >> at sun.security.ssl.InputRecord.readFully(Unknown Source) >> at sun.security.ssl.InputRecord.read(Unknown Source) >> at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source) >> - locked <0x000000008ca85708> (a java.lang.Object) >> at sun.security.ssl.SSLSocketImpl.readDataRecord(Unknown Source) >> at sun.security.ssl.AppInputStream.read(Unknown Source) >> - locked <0x000000008ca86488> (a sun.security.ssl.AppInputStream) >> at >> org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:166) >> at >> org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:90) >> at >> org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:281) >> at >> org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:92) >> at >> org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:61) >> at >> org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:254) >> at >> org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHead >> er(AbstractHttpClientConnection.java:289 >> ) >> at >> org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:252) >> at >> org.apache.http.impl.conn.ManagedClientConnectionImpl.receiveResponseHeader(ManagedClientConnectionImpl.java: >> 191) >> at >> org.apache.jmeter.protocol.http.sampler.MeasuringConnectionManager$Me >> asuredConnection.receiveResponseHeader(M >> easuringConnectionManager.java:201) >> at >> org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:300) >> at >> org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:127) >> at >> org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:715) >> at >> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:520) >> at >> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906) >> at >> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805) >> at >> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.executeRequest(HTTPHC4Impl.java:517) >> at >> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.sample(HTTPHC4Impl.java:331) >> at >> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:74) >> at >> org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1146) >> at >> org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1135) >> at >> org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:434) >> at >> org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:261) >> at java.lang.Thread.run(Unknown Source) >> >> >> "AWT-EventQueue-0" #15 prio=6 os_prio=0 tid=0x0000000019fff000 >> nid=0x1260 waiting on condition [0x000000001b7de000] >> java.lang.Thread.State: WAITING (parking) >> at sun.misc.Unsafe.park(Native Method) >> - parking to wait for <0x000000008001aa50> (a >> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionOb >> ject) >> at java.util.concurrent.locks.LockSupport.park(Unknown Source) >> at >> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject >> .await(Unknown >> Source) >> at java.awt.EventQueue.getNextEvent(Unknown Source) >> at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown >> Source) >> at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) >> at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown >> Source) >> at java.awt.EventDispatchThread.pumpEvents(Unknown Source) >> at java.awt.EventDispatchThread.pumpEvents(Unknown Source) >> at java.awt.EventDispatchThread.run(Unknown Source) >> >> >> >> >> -----Original Message----- >> From: Felix Schumacher [mailto:[email protected]] >> Sent: Thursday, June 09, 2016 4:30 PM >> To: JMeter Users List >> Subject: RE: Jmeter pausing when running >> >> Can you post the complete threaddump? The part you posted does not >> seem to match the bugs you cited. >> >> >> Regards, >> Felix >> >> Am 9. Juni 2016 21:39:30 MESZ, schrieb Janine DeBeradinis < >> [email protected]>: >>> Thanks for the suggestion. I was able to get a thread dump and >>> passed the information onto one of our developers. It looks like he >>> found the issue. >>> >>> - locked <0x000000008ce895b8> (a java.lang.Object) >>> at sun.security.ssl.SSLSocketImpl.readDataRecord(Unknown Source) >>> at sun.security.ssl.AppInputStream.read(Unknown Source) >>> - locked <0x000000008ce8a338> (a >>> sun.security.ssl.AppInputStream) at >>> org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(Abstra >>> ctS >>> essionInputBuffer.java:166) >>> ... >>> "AWT-EventQueue-0" #15 prio=6 os_prio=0 tid=0x0000000019fff000 >>> nid=0x1260 waiting on condition [0x000000001b7de000] >>> java.lang.Thread.State: WAITING (parking) >>> at sun.misc.Unsafe.park(Native Method) >>> - parking to wait for <0x000000008001aa50> (a >>> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionOb >>> ject) >>> >>> >>> He suggested a few things to me: >>> >>> 1. Try using IP addresses instead of hostnames or vice versa (this >>> cuts down on DNS lookups or reverse name lookups). >>> >>> 2. Perhaps JMeter is trying to download embedded resources within >>> the SSL page - perhaps try switching this off (if it isnt already) - >>> as per this old bug report >>> https://urldefense.proofpoint.com/v2/url?u=https-3A__bz.apache.org_b >>> ugz >>> illa_show-5Fbug.cgi-3Fid-3D31832&d=DQIDaQ&c=G2J7obiPomkpMVl1prtGFw&r >>> =1O >>> gbcP-oUjBUH-3H8avzbUL8Jplqf3JrZ0J8DHFWVZE&m=Cs-iQY2E1maRYYpNsVozCrvy >>> RQw >>> -lg_FuY6HtiickVA&s=sYvb6OwRtnL2LjqVrGXWv6t4AU5B_1Q8qyOHgLMessU&e= >>> >>> 3. This is related to #1. >>> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.o >>> rg_ >>> jira_browse_HTTPCLIENT-2D1302&d=DQIDaQ&c=G2J7obiPomkpMVl1prtGFw&r=1O >>> gbc >>> P-oUjBUH-3H8avzbUL8Jplqf3JrZ0J8DHFWVZE&m=Cs-iQY2E1maRYYpNsVozCrvyRQw >>> -lg _FuY6HtiickVA&s=RmnWHb9ckyRd1MEy9se28OvNGIFe_H7eeyWPTzqEuIY&e= >>> Essentially they are saying that we should turn off hostname >>> verification. Not sure where that option is in Jmeter. See if you >>> can find it. >>> >>> >>> I was going to start and look into these. I can let you know how I >>> make out. >>> >>> Thanks. >>> >>> >>> -----Original Message----- >>> From: Deepak Shetty [mailto:[email protected]] >>> Sent: Wednesday, June 08, 2016 3:36 PM >>> To: JMeter Users List >>> Subject: Re: Jmeter pausing when running >>> >>> Hi >>> you could be having >>> a. Problems in the JMeter java VM >>> b. Problems in your test itself (like a synchronizing timer or a >>> throughput >>> controller) - This is something you have probably eliminated ? >>> c. Problems in the system being tested (i.e. JMeter is generating >>> the load , but your system under test paused so Jmeter isnt doing >>> anything other than waiting) - Sounds like you have eliminated this >>> possibility >>> >>> For a) you probably have no way out of looking at the java VM when >>> it is paused (take a thread dump - or hook up something like >>> jconsole or run a profiler - look at GC running , memory usage etc) >>> and then take it from there. >>> >>> Since you mentioned you are using Jmeter distributed mode , try >>> eliminating that first - i.e. running a single machine test (perhaps >>> with half the >>> load) and seeing whether you see same behavior or not - if you do >>> then you can probably take a thread dump (ctrl+break or kill -3 and >>> see what JMeter is doing at that time - you can also enable GC logs >>> to see what the memory usage looks and whether GC is running or not). >>> >>> >>> >>> On Wed, Jun 8, 2016 at 12:05 PM, Janine DeBeradinis < >>> [email protected]> wrote: >>> >>>> Sorry, I'm not exactly sure what you mean. Run both the server and >>>> client in non-gui mode on the same machine? >>>> >>>> -----Original Message----- >>>> From: sebb [mailto:[email protected]] >>>> Sent: Wednesday, June 08, 2016 2:56 PM >>>> To: JMeter Users List >>>> Subject: Re: Jmeter pausing when running >>>> >>>> The JMeter GUI takes a lot more resources than running in non-Gui >>> mode. >>>> Also client-server mode takes more resources as it has to send back >>>> the results. >>>> >>>> Since you only have two machines actually running the test, it >>>> should >>> >>>> be easy enough to try running them stand-alone in non-GUI mode in >>> parallel. >>>> >>>> >>>> >>>> >>>> On 8 June 2016 at 19:41, Janine DeBeradinis >>>> <[email protected]> >>>> wrote: >>>>> We are using 3 machines. >>>>> >>>>> 1 is running JMeter GUI to distribute the load. (also trying to >>> see >>>>> if the pausing issue goes away) The other 2 are running JMeter >>> server. >>>>> >>>>> They are all Windows Server 2012 R2 machines. >>>>> >>>>> Thanks. >>>>> Janine >>>>> >>>>> -----Original Message----- >>>>> From: Deepak Goel [mailto:[email protected]] >>>>> Sent: Wednesday, June 08, 2016 12:47 PM >>>>> To: JMeter Users List >>>>> Subject: Re: Jmeter pausing when running >>>>> >>>>> What machine are you running the test from? Is it a laptop or a >>>>> desktop >>>> for personal use? >>>>> >>>>> Hey >>>>> >>>>> Namaskara~Nalama~Guten Tag~Bonjour >>>>> >>>>> >>>>> -- >>>>> Keigu >>>>> >>>>> Deepak >>>>> 73500 12833 >>>>> www.simtree.net, [email protected] [email protected] >>>>> >>>>> LinkedIn: www.linkedin.com/in/deicool >>>>> Skype: thumsupdeicool >>>>> Google talk: deicool >>>>> Blog: >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__loveandfearless. >>>>> wo >>> rdpress.com&d=DQIFaQ&c=G2J7obiPomkpMVl1prtGFw&r=1OgbcP-oUjBUH-3H8avz >>>>> bU >>> L8Jplqf3JrZ0J8DHFWVZE&m=Q7QdXYQGe-rZwgYG-F0UQuBOUV8fVsyteZl_FEcZ5fU& >>>>> s= Au4_yzYoutDa59LBgoqwvraAw3A_W4bhaXyB6azgyCM&e= >>>>> Facebook: >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com >>>>> _d >>> eicool&d=DQIFaQ&c=G2J7obiPomkpMVl1prtGFw&r=1OgbcP-oUjBUH-3H8avzbUL8J >>>>> pl >>> qf3JrZ0J8DHFWVZE&m=Q7QdXYQGe-rZwgYG-F0UQuBOUV8fVsyteZl_FEcZ5fU&s=sC3 >>>>> 4g I9c7G5kALpTSm-Np-s7lFURlfsjH_Zh4zbnbPs&e= >>>>> >>>>> "Contribute to the world, environment and more : >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.gridrepublic >>>>> .o >>> rg&d=DQIFaQ&c=G2J7obiPomkpMVl1prtGFw&r=1OgbcP-oUjBUH-3H8avzbUL8Jplqf >>>>> 3J >>> rZ0J8DHFWVZE&m=Q7QdXYQGe-rZwgYG-F0UQuBOUV8fVsyteZl_FEcZ5fU&s=U_jTZpf >>>>> YA Z4lWmjZkzSVlkxPqhktjUtJP2vvEIInJ6s&e= >>>>> " >>>>> >>>>> On Wed, Jun 8, 2016 at 10:09 PM, Bob Nance >>>>> <[email protected]> >>>>> wrote: >>>>> >>>>>> I've been having an issue with JMeter periodically pausing when >>>>>> running a load test and am not sure how to resolve this. We have >>>>>> tried several things, but nothing seems to be working. The >>>>>> behavior is I start a JMeter load test. The test will run fine >>>>>> for >>> >>>>>> a few >>>> minutes, then pause, then pick >>>>>> back up, then pause, etc. I've tried upping the heap size when >>>> starting >>>>>> JMeter, running in distributed mode and non distributed mode, >>>>>> even >>> >>>>>> turning off our Anti-Virus software, but the issue still persists. >>>>>> The amount of load being generated isn't that much either. My >>> test >>>>>> has >>>> about 75 >>>>>> different thread groups, but we are only using 1 thread per group. >>> The >>>>>> last thing I tired was adding -XX:+DisableExplicitGC to >>>>>> jmeter.bat >>> >>>>>> file, but that didn't work either. >>>>>> >>>>>> Does anyone have any other suggestions or thoughts? >>>>>> >>>>>> Do the logs reflect the delay? (or could it just be a delayed >>>>>> display >>>>>> issue) >>>>>> Do you have any data visualizations/listeners running during the >>> tests? >>>>>> (they can eat up a lot of CPU cycles) Do you have anything else >>>>>> running on the computer that might be stealing the network card? >>>>>> Is there a pattern that might point you somewhere (like it >>>>>> happens >>> >>>>>> nearly at the same test, or every 12.5 seconds or something)? >>>>>> >>>>>> No direct help, but those are all things that I have seen affect >>> my >>>> tests. >>>>>> >>>>>> -Bob >>>>>> >>>>>> >>>>>> --- >>>>>> Bob Nance >>>>>> Novation Systems >>>>>> [email protected]<mailto:[email protected]> >>>>>> 256-534-4620 >>> -------------------------------------------------------------------- >>>>> - To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>> >>>> ------------------------------------------------------------------- >>>> -- To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>>> ------------------------------------------------------------------- >>>> -- To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
