Hi Greg,
Yes, it's "normal". Let me explain. To avoid an infinite loop when you
are logged in via ssh, log:* commands (log:tail and log:display for
instance) are changing default org.ops4j.pax.logging configuration.
So, if the config files are read only, configadmin won't be able to update.
It's
Hi all,
We are looking at upgrading from Karaf 3.4.3 to 3.4.6, and noticed an odd
behaviour. If your Karaf config files are read only (say, in a docker
container) and you try to run log:tail you get an immediate stack
trace[1]. Is this intended behaviour? It's not blocking our ability to
HI,
Are Blueprint reference listeners bind/unbind methods thread safe? If my
reference listener listens on multiple references of the service, should it
take care about concurrent invocations?
Regards
--
Daniel Łaś
