>>>>> Grzegorz Grzybek <gr.grzybek-re5jqeeqqe8avxtiumw...@public.gmane.org>:
> Hello > Sorry, but I didn't have time to check/run your integration tests. > You've mentioned that the test may be run twice - that's possible depending > on the configuration of maven-surefire/failsafe-plugin. I don't know. > Usually in such cases I turn on quite detailed logging, so I can see how > all the threads interact. For example in Pax Web I use this logging > configuration: > https://github.com/ops4j/org.ops4j.pax.web/blob/web-8.0.20/pax-web-itest/pax-web-itest-karaf/src/test/resources/log4j2-test.properties#L38 > appender.file.layout.pattern = %d{HH:mm:ss.SSS} [%thread] %-5level (%F:%L) > %logger - %msg%n Thanks! Where does the log affected by this config end up? I assume it isn't the karaf.log of the started karaf instance, and it doesn't seem to affect the console log format? > The most important part is to ensure you have full thread name (%thread), > so you can see how the threads interact. I've detected many deadlocks and > thread synchronization problems in last years simply by looking at the logs. > If the green tests are fine, you're half way to success ;) True. :-) -- -- ------------------ OPS4J - http://www.ops4j.org - ops4j@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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ops4j/87edm1ulm7.fsf%40dod.no.
