I can’t guess anything about which extenders you might be using, but….
compliant consumers of config admin Configurations only look at configurations
whose bundle location is compatible with the bundle being configured. It’s
recommended that configuration management agents (such as IIUC felix
Noted. Thanks.
Regards,
Allan C.
On Tue, Jul 5, 2016 at 3:40 AM, Jean-Baptiste Onofré
wrote:
> Thanks Allan,
>
> jetty is an alias feature on top of pax-jetty (for backward compatibility).
>
> Definitely, we upgraded in pax-web, but forgot to update the jetty alias
> feature.
>
> Let me create
I encountered this issue when I was installing some of my bundles. I've
narrowed it down to I think what is the cause of the issue.
For instance, bundle A and B contains the following:
When first bundle is installed, it works fine. But when second bundle is
installed, it will restart indefinite
Thanks Allan,
jetty is an alias feature on top of pax-jetty (for backward compatibility).
Definitely, we upgraded in pax-web, but forgot to update the jetty alias
feature.
Let me create a Jira to fix that.
Thanks !
Regards
JB
On 07/04/2016 10:20 AM, Allan C. wrote:
I am playing around with
Another theory: Looking at the stack trace this seems to be triggered by a
configuration update. Could the problem be that Pax-logging is trying to
load the DLL again and failing since it is already loaded? Perhaps the
initial load works but subsequent configuration updates does not?
I tried to ve
A theory: Could one of the bundles installed by feature pax-jetty be using
log4j 2.x directly without using Pax-logging? If so, would it too try to
read the log4j configuration file? I guess it would fail to load the DLL
since it is probably not compatible with log4j 2.x.
Could this happen? If so,
hm, I'm not quite getting this.
when I enter feature:install -v -t bundle1
then I get the following output:
2016-07-04 12:36:50,137 | INFO | ool-791-thread-1 |
FeaturesServiceImpl | 9 - org.apache.karaf.features.core -
4.0.5 | Bundles to refresh:
Bundles to refresh:
2016-07
hm, I'm not quite getting this.
when I enter feature:install -v -t bundle1
then I get the following output:
2016-07-04 12:36:50,137 | INFO | ool-791-thread-1 |
FeaturesServiceImpl | 9 - org.apache.karaf.features.core -
4.0.5 | Bundles to refresh:
Bundles to refresh:
2016-07
I am playing around with 4.0.5 and I noticed that the versions for the
jetty and pax-jetty are different. In Fuse 6.2.1 (I think it is based on
Karaf 2.4.0), the versions are the same.
JBossFuse:karaf@root> features:list | grep jetty
[installed ] [*8.1.17.v20150415* ] jetty
karaf-2.
