https://bz.apache.org/bugzilla/show_bug.cgi?id=63087
--- Comment #4 from Steven <[email protected]> --- Hi, I will apply the logging changes and provide them soonest. To answer the relation to inActive() question... I have created a service which iterates a hash table of known agents/clients executing tests. In this hash table I can pull out per key, and get access to he DistributedRunner(DR) in order to see which agents are still executing. When I call the isActive() on the engines provided by the DR(which is debugged and listed as correct) calling the isActive() function returns true, even though my view on the agent states the test has finished executing(As per the stdout). I suspected this may be timing but after waiting over an hour to eliminate this possibility the isActive still returns true. If this is not the isActive function, as your query suggests, please advise what could be wrong? I am using vanilla API so not sure where the fault could be. Infrastructure - This is being executed in a OpenShift environment. I have the controller wrapped in a springboot application. When a call is made to my endpoint I fire off a new thread which instantiates my DR and fires off the tests on the relevant addresses(trying to be which aren't busy). This all works perfectly, apart from the isActive issues I'm currently seeing. JMX - We script locally in order to get functioning tests. After which we upload to the server via different services and then start the DR programmatically. So we pass the JMX file into the service/server/ I then manually change the JMX to reflect correct paths for CSV datasets and sampler result location and then launch the test. JMeter properties/User.properties. These are all vanilla apart from the ssl rmi set to disabled. This is within a secured cluster so Ssl isn't required for these agents. Regards, Steven (In reply to Philippe Mouawad from comment #3) > 1/ A first step is to put JMeter in debug, add this to log4j2.xml: > > <Logger name="org.apache.jmeter.engine" level="debug" /> > > on both client and server > > 2/ Then provide: > > - jmeter.log for all > - jmeter.properties and user.properties for all servers > - detail how you are proceeding > - provide information on your infrastructure > > Also , how do you know issue is due to isActive() ? > Are you using JMX or Java generated JMX or any other approach ? > > > 3/ Try using nightly build , there is a fix on Distributed Testing > https://ci.apache.org/projects/jmeter/nightlies/ > > > Thank you -- You are receiving this mail because: You are the assignee for the bug.
