As it seems the problem is related to the exposure of the JMX management server via the Karaf management bundle.
My firewall prevents the opening of a port for it, hence the bundle is stuck in start() and in turn its stop() method is stuck either. If I disable my firewall it works as expected. Is there any way for preventing the management bundle from starting? It's not needed for my testing via Pax Exam anyways. Thanks, --Gunnar Am Mittwoch, 30. November 2016 14:57:17 UTC+1 schrieb Gunnar Morling: > > Yes, it's using Surefire via Maven, but I see the same issue when running > that test from within Eclipse. > > It's happening in this pull request towards Hibernate Validator: > https://github.com/hibernate/hibernate-validator/pull/521. On master > (with Karaf 3.x) the OsgiIntegrationTest completes within a few seconds, > with that PR (and using Karaf 4.0.7) it takes > 30 sec. I tried to narrow > down the exact version and it happens when using 4.0.4 or later. > > Something seems to prevent the container shutdown to complete. When remote > debugging, I see that the "FelixShutdown" thread is waiting at > Felix#stopBundle() / FrameworkStartLevelImpl#setStartLevelAndWait() which I > assume to be related, but I don't know enough about the inner workings of > Felix to understand the deeper cause behind it. > > --Gunnar > > Am Mittwoch, 30. November 2016 14:03:38 UTC+1 schrieb Toni Menzel: >> >> Is this using Surefire? Or in an IDE? If so which one? >> >> *Toni Menzel* >> >> >> *Developer Advocates - The Rebaze Way * >> >> *www.rebaze.de <http://www.rebaze.de/> | www.rebaze.com >> <http://www.rebaze.com/> | @rebazeio <https://twitter.com/rebazeio>* >> >> On Wed, Nov 30, 2016 at 12:54 PM, 'Gunnar Morling' via OPS4J < >> [email protected]> wrote: >> >>> Hi, >>> >>> I'm using PaxExam to execute some JUnit tests on Karaf. The tests >>> succeed, but the Karaf VM fails to shutdown after test execution for >>> approximately 30 seconds. >>> >>> This is happening with Karaf 4.0.4 and beyond. Using 4.0.3 will cause >>> the container to shutdown as expected right after all tests have been >>> executed. >>> >>> Does that ring a bell with anyone? Any pointers for addressing the issue >>> would be more than welcome. >>> >>> Thanks, >>> >>> --Gunnar >>> >>> -- >>> -- >>> ------------------ >>> OPS4J - http://www.ops4j.org - [email protected] >>> >>> --- >>> 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 [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
