Hi,
if your Pax Exam @Config provides all featuresBoot to avoid the refresh,
the refresh should not happen.
Did you identify the optional import in cause ?
Thanks,
Regards
JB
On 12/12/2018 11:32, Martin Lichtin wrote:
It happens during a Pax-Exam test, so all features are loaded via
"featuresBoot".
What I can see is that the pax-logging-log4j2 bundle has a lot of
optional Imports. So when more bundles are loaded, re-wiring is happening.
On 11.12.2018 19:41, Jean-Baptiste Onofré wrote:
Hi,
Can you please provide your feature or do a feature:install -v to see
the cause of the refresh ?
A simple workaround is to set your feature as featuresBoot, you won't
have the refresh.
Regards
JB
On 11/12/2018 18:47, Martin Lichtin wrote:
When loading features, I have the problematic situation of
2018-12-11T18:16:00,189 | INFO | features-1-thread-1 |
FeaturesServiceImpl | FeaturesServiceImpl 1286 | karaf.features.core -
4.1.7 | Stopping bundles:
2018-12-11T18:16:00,189 | INFO | features-1-thread-1 |
FeaturesServiceImpl | FeaturesServiceImpl 1286 | karaf.features.core -
4.1.7 | org.ops4j.pax.logging.pax-logging-log4j2/1.10.1
It therefore goes into a blind flight (no more logging) and only a
couple of seconds later (usually 10-20s), the logging returns (when that
bundle gets started again).
Any way to avoid this log4j2 bundle refresh/re-wiring?
- Martin
