Hi

I was able to confirm the same behavior on Kubuntu 19.04 on Oracle JDK
1.8.0_181. I had originally run it on Windows 10 using the same version of
the JDK. Jetty is 9.4.5v20170502.

On Sat, 25 May 2019 at 09:20, Olivier Lamy <[email protected]> wrote:

> Hi
> Do you have same issue when using an other OS (i.e not windows)?
> I remember some issues with selector on windows.
> What are jetty version and jdk version?
>
> On Sat, 25 May 2019 at 2:36 am, Abhyudaya Sharma <
> [email protected]> wrote:
>
>> Hi everyone!
>>
>> I was debugging through JenkinsRule from Jenkins Test Harness. After the
>> Jetty server and Jenkins have both been terminated in JenkinsRule#after() 
>> (line
>> 488
>> <https://github.com/jenkinsci/jenkins-test-harness/blob/2281a68194604c983e7a8d1e7822379b262f153d/src/main/java/org/jvnet/hudson/test/JenkinsRule.java#L488>
>> and line 502
>> <https://github.com/jenkinsci/jenkins-test-harness/blob/2281a68194604c983e7a8d1e7822379b262f153d/src/main/java/org/jvnet/hudson/test/JenkinsRule.java#L502>,
>> respectively) stray threads keep running. Attached is the dump of the
>> running threads. Is it possible to terminate these threads to allow the JVM
>> to exit gracefully?
>>
>> This issue may already have been reported before in this Stack Overflow
>> question:
>> https://stackoverflow.com/questions/13769007/jetty-server-leaves-behind-threads-after-stop
>>
>> A minimal example would be following test code and setting a breakpoint
>> at the System.gc() call on line 517:
>>
>> import org.junit.Rule;
>> import org.junit.Test;
>> import org.jvnet.hudson.test.JenkinsRule;
>>
>> public class RandomTest {
>>     @Rule
>>     public JenkinsRule jenkinsRule = new JenkinsRule();
>>
>>     @Test
>>     public void randomTest() {
>>         System.out.println("Hello world");
>>     }
>> }
>>
>>
>> Thanks
>> Abhyudaya Sharma
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/69803027-2066-4650-837e-b922f86d7531%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/69803027-2066-4650-837e-b922f86d7531%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/7yL0MKjxQwA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPoyBqTUvauHOU3xBN0Obgn75ukvkGhad68N2Lvrcc3rH33LxA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPoyBqTUvauHOU3xBN0Obgn75ukvkGhad68N2Lvrcc3rH33LxA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPBRr8fC0yMpHaEh-Sxi--V%3DzCz56YQWiN5nBix5MSLqTZJrcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to