@ClassRule
public static PaxExamServer exam = new PaxExamServer();
to launch karaf 4.0.6. Most of the time, everything works as expected, but when it goes wrong, it just gets stuck, sitting there. We're on the verge of implementing a thread waiting for a connection that will just stop the OSGi framework forcibly. That's pretty ugly. Can anyone suggest a debugging strategy? The non-reproducibility of this is, of course, a barrier.
--
--
------------------
OPS4J - http://www.ops4j.org - op...@googlegroups.com
---
You received this message because you are subscribed to the Google Groups "OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
>> email to ops4j+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> Niclas Hedhman, Software Developer
> http://zest.apache.org - New Energy for Java
>
> --
> --
> ------------------
> OPS4J - http://www.ops4j.org - op...@googlegroups.com
>
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "OPS4J" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/ops4j/GlyXQeXcwmY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
--
------------------
OPS4J - http://www.ops4j.org - op...@googlegroups.com
---
You received this message because you are subscribed to the Google Groups "OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscribe@googlegroups.com.
>> email to ops4j+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> Niclas Hedhman, Software Developer
> http://zest.apache.org - New Energy for Java
>
> --
> --
> ------------------
> OPS4J - http://www.ops4j.org - op...@googlegroups.com
>
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "OPS4J" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/ops4j/GlyXQeXcwmY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
--
------------------
OPS4J - http://www.ops4j.org - op...@googlegroups.com
---
You received this message because you are subscribed to the Google Groups "OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscribe@googlegroups.com.
Here are some thread dumps:
I don't have a lot of data, but we're seeing similar behavior, but integrating with Karaf 4.0.5. If I run a suite of tests, many of them fail with "Address in use" errors, and when the tests are all completed, I see several leftover karaf instances that I have to manually kill. Some of the tests are also failing for other reasons (dependencies, other details). I don't know if it's possible for those errors to cause the shutdown to fail.
On Monday, October 17, 2016 at 12:39:40 PM UTC-7, Benson Margulies wrote:Using pax-exam 4.9.1, we suffer from unpredictable hangs on shutdown. We've seen this with the exam-maven-plugin and when using@ClassRule
public static PaxExamServer exam = new PaxExamServer();to launch karaf 4.0.6. Most of the time, everything works as expected, but when it goes wrong, it just gets stuck, sitting there. We're on the verge of implementing a thread waiting for a connection that will just stop the OSGi framework forcibly. That's pretty ugly. Can anyone suggest a debugging strategy? The non-reproducibility of this is, of course, a barrier.
--
--
------------------
OPS4J - http://www.ops4j.org - op...@googlegroups.com
---
You received this message because you are subscribed to a topic in the Google Groups "OPS4J" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ops4j/GlyXQeXcwmY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ops4j+unsubscribe@googlegroups.com.
You received this message because you are subscribed to the Google Groups "OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Mon, Oct 24, 2016 at 11:26 AM, David Karr <davidmic...@gmail.com> wrote:I don't have a lot of data, but we're seeing similar behavior, but integrating with Karaf 4.0.5. If I run a suite of tests, many of them fail with "Address in use" errors, and when the tests are all completed, I see several leftover karaf instances that I have to manually kill. Some of the tests are also failing for other reasons (dependencies, other details). I don't know if it's possible for those errors to cause the shutdown to fail.I was hoping that posting the thread dumps would shed light. Our team has given up, and plans to replace pax-exam with launching the app with Docker for testing.
On Thu, Oct 27, 2016 at 12:50 PM, David Karr <davidmic...@gmail.com> wrote:
On Monday, October 24, 2016 at 8:48:15 AM UTC-7, Benson Margulies wrote:On Mon, Oct 24, 2016 at 11:26 AM, David Karr <davidmic...@gmail.com> wrote:I don't have a lot of data, but we're seeing similar behavior, but integrating with Karaf 4.0.5. If I run a suite of tests, many of them fail with "Address in use" errors, and when the tests are all completed, I see several leftover karaf instances that I have to manually kill. Some of the tests are also failing for other reasons (dependencies, other details). I don't know if it's possible for those errors to cause the shutdown to fail.I was hoping that posting the thread dumps would shed light. Our team has given up, and plans to replace pax-exam with launching the app with Docker for testing.
That isn't a practical option for us. Our desktops are Windows7. The CI server is Linux, but our developers need to be able to run the suite locally.Docker works on Windows.