Hi,
what’s the new “framework” feature for? Would it have consequences if we
remove this from the boot features?
When I compare the startup.properties and the framework features file I
find that the framework feature only contains bundles which are already
listed and started by the startup.properties.
And because the bundles attributes are set to start=true I would not be
surprised if this leads to core restarts when fragments are there.
Regards,
Volker
*Von:*Althaus, Volker
*Gesendet:* Mittwoch, 11. Mai 2016 13:36
*An:* [email protected]
*Betreff:* AW: [Karaf 4.0.5] Strange console log messages when using
custom log appenders
Hi JB,
yes, it's a vanilla Karaf 4.0.5 with only the fragment bundle named in
startup.properties.
Without the "framework" feature as in 4.0.4 it works correct.
Log with DEBUG (the relevant parts):
---------------------------------------------
Mai 11, 2016 1:29:45 PM org.apache.karaf.main.Main launch
INFORMATION: Installing and starting initial bundles
Mai 11, 2016 1:29:45 PM org.apache.karaf.main.Main launch
INFORMATION: All initial bundles installed and set to start
Mai 11, 2016 1:29:45 PM org.apache.karaf.main.lock.SimpleFileLock lock
INFORMATION: Trying to lock D:\apache-karaf-4.0.5\lock
Mai 11, 2016 1:29:45 PM org.apache.karaf.main.lock.SimpleFileLock lock
INFORMATION: Lock acquired
Mai 11, 2016 1:29:45 PM org.apache.karaf.main.Main$KarafLockCallback
lockAquired
INFORMATION: Lock acquired. Setting startlevel to 100
2016-05-11 13:29:46,503 | DEBUG | FelixStartLevel |
configadmin | 8 - org.apache.felix.configadmin -
1.8.8 | getProperties()
…
2016-05-11 13:29:46,678 | DEBUG | FelixStartLevel |
fileinstall | 9 - org.apache.felix.fileinstall -
3.5.4 | BundleEvent STARTED - org.apache.felix.fileinstall
2016-05-11 13:29:46,692 | DEBUG | FelixStartLevel |
core | 10 - org.apache.karaf.features.core -
4.0.5 | BundleEvent RESOLVED - org.apache.karaf.features.core
2016-05-11 13:29:46,692 | DEBUG | FelixStartLevel | core
| 10 - org.apache.karaf.features.core - 4.0.5 |
BundleEvent STARTING - org.apache.karaf.features.core
2016-05-11 13:29:46,705 | DEBUG | FelixStartLevel |
core | 10 - org.apache.karaf.features.core -
4.0.5 | BundleEvent STARTED - org.apache.karaf.features.core
…
2016-05-11 13:29:46,912 | DEBUG | pool-7-thread-1 |
OptimizedAccessorFactory | - - | Using optimized Accessor for
protected java.lang.String
org.apache.karaf.features.internal.model.Features.name
2016-05-11 13:29:47,105 | DEBUG | pool-7-thread-1 |
Blacklist | 10 - org.apache.karaf.features.core -
4.0.5 | Unable to load overrides bundles list
java.io.FileNotFoundException:
D:\apache-karaf-4.0.5\bin\..\etc\blacklisted.properties (Das System kann
die angegebene Datei nicht finden)
at java.io.FileInputStream.open0(Native Method)[:1.8.0_77]
at java.io.FileInputStream.open(FileInputStream.java:195)[:1.8.0_77]
at
java.io.FileInputStream.<init>(FileInputStream.java:138)[:1.8.0_77]
…
2016-05-11 13:29:47,456 | DEBUG | pool-9-thread-1 |
Overrides | 10 - org.apache.karaf.features.core -
4.0.5 | Unable to load overrides bundles list
java.io.FileNotFoundException:
D:\apache-karaf-4.0.5\bin\..\etc\overrides.properties (Das System kann
die angegebene Datei nicht finden)
at java.io.FileInputStream.open0(Native Method)[:1.8.0_77]
at java.io.FileInputStream.open(FileInputStream.java:195)[:1.8.0_77]
at
java.io.FileInputStream.<init>(FileInputStream.java:138)[:1.8.0_77]
…
2016-05-11 13:29:48,597 | INFO | pool-9-thread-1 |
FeaturesServiceImpl | 10 - org.apache.karaf.features.core -
4.0.5 | mvn:org.ops4j.pax.url/pax-url-aether/2.4.7
2016-05-11 13:29:48,597 | INFO | pool-9-thread-1 |
FeaturesServiceImpl | 10 - org.apache.karaf.features.core -
4.0.5 | mvn:org.ops4j.pax.url/pax-url-wrap/2.4.7/jar/uber
2016-05-11 13:29:48,621 | DEBUG | pool-9-thread-1 |
wrap | 52 - org.ops4j.pax.url.wrap - 2.4.7 |
BundleEvent INSTALLED - org.ops4j.pax.url.wrap
2016-05-11 13:29:48,647 | INFO | pool-9-thread-1 |
FeaturesServiceImpl | 10 - org.apache.karaf.features.core -
4.0.5 | Stopping bundles:
2016-05-11 13:29:48,647 | DEBUG | pool-9-thread-1 |
Deployer | 10 - org.apache.karaf.features.core -
4.0.5 | Usage for bundle org.ops4j.pax.logging.pax-logging-service [7] is 0
2016-05-11 13:29:48,648 | DEBUG | pool-9-thread-1 |
Deployer | 10 - org.apache.karaf.features.core -
4.0.5 | Selected bundles [org.ops4j.pax.logging.pax-logging-service [7]]
for destroy (no services in use)
2016-05-11 13:29:48,648 | INFO | pool-9-thread-1 |
FeaturesServiceImpl | 10 - org.apache.karaf.features.core -
4.0.5 | org.ops4j.pax.logging.pax-logging-service/1.8.5
2016-05-11 13:29:48,648 | DEBUG | pool-9-thread-1 |
pax-logging-service | 7 -
org.ops4j.pax.logging.pax-logging-service - 1.8.5 | BundleEvent STOPPING
- org.ops4j.pax.logging.pax-logging-service
Mai 11, 2016 1:29:48 PM org.apache.karaf.main.lock.SimpleFileLock lock
INFORMATION: Trying to lock D:\apache-karaf-4.0.5\lock
Mai 11, 2016 1:29:48 PM org.apache.karaf.main.lock.SimpleFileLock lock
INFORMATION: Lock acquired
2016-05-11 13:29:49,372 | DEBUG | FelixStartLevel |
configadmin | 8 - org.apache.felix.configadmin -
1.8.8 | getProperties()
…
2016-05-11 13:29:49,408 | DEBUG | FelixStartLevel |
fileinstall | 9 - org.apache.felix.fileinstall -
3.5.4 | BundleEvent STARTED - org.apache.felix.fileinstall
2016-05-11 13:29:49,418 | DEBUG | FelixStartLevel |
core | 10 - org.apache.karaf.features.core -
4.0.5 | BundleEvent RESOLVED - org.apache.karaf.features.core
2016-05-11 13:29:49,418 | DEBUG | FelixStartLevel |
core | 10 - org.apache.karaf.features.core -
4.0.5 | BundleEvent STARTING - org.apache.karaf.features.core
2016-05-11 13:29:49,433 | DEBUG | FelixStartLevel | core
| 10 - org.apache.karaf.features.core - 4.0.5 |
BundleEvent STARTED - org.apache.karaf.features.core
…
2016-05-11 13:29:51,230 | DEBUG | FelixStartLevel |
BlueprintExtender | 14 - org.apache.aries.blueprint.core
- 1.6.1 | Starting BlueprintContainer destruction process for bundle
my.logging/1.0
2016-05-11 13:29:51,230 | DEBUG | FelixStartLevel |
BlueprintExtender | 14 - org.apache.aries.blueprint.core
- 1.6.1 | Not a blueprint bundle or destruction of BlueprintContainer
already finished for my.logging/1.0
…
Regards,
Volker
> -----Ursprüngliche Nachricht-----
> Von: Jean-Baptiste Onofré [mailto:[email protected]]
> Gesendet: Mittwoch, 11. Mai 2016 11:18
> An: [email protected] <mailto:[email protected]>
> Betreff: Re: [Karaf 4.0.5] Strange console log messages when using custom
> log appenders
>
> Hi Volker,
>
> it's weird: I don't think the framework feature trigger a whole refresh.
>
> Do you use the default featuresBoot in
etc/org.apache.karaf.features.cfg ?
>
> Regards
> JB
>
> On 05/11/2016 09:47 AM, Althaus, Volker wrote:
> > Hi,
> >
> > we upgraded from Karaf 4.0.4 to 4.0.5 and now we have a
> > non-deterministic start behavior with our custom log appenders which
> > lead to multiple error-like output on the console.
> >
> > We implemented our appender regarding to
> >
> > http://blog.nanthrax.net/2012/12/create-custom-log4j-appender-for-kara
> > f-and-pax-logging/
> > and
> >
> > http://karaf.apache.org/manual/latest/#_advanced_configuration
> (Custom
> > appenders section)
> >
> > startup.properties:
> >
> > -----------------------
> >
> > mvn\:org.ops4j.pax.logging/pax-logging-api/1.8.5 = 8
> >
> > mvn\:org.ops4j.pax.logging/pax-logging-service/1.8.5 = 8
> >
> > mvn\:my.group/my.logging.fragment/1.0 = 8
> >
> > (No behavior change if the fragment is moved before the service bundle
> > as mentioned in the second link).
> >
> > MANIFEST.MF:
> >
> > ------------------
> >
> > …
> >
> > Bundle-SymbolicName: my.logging.fragment
> >
> > Fragment-Host: org.ops4j.pax.logging.pax-logging-service
> >
> > …
> >
> > Now an example first start output is:
> >
> > $ > karaf.bat
> >
> > The specified feature: 'instance' version '4.0.5' is already installed
> >
> > The specified feature: 'package' version '4.0.5' is already installed
> >
> > The specified feature: 'log' version '4.0.5' is already installed
> >
> > The specified feature: 'ssh' version '4.0.5' is already installed
> >
> > The specified feature: 'aries-blueprint' version '4.0.5' is already
> > installed
> >
> > The specified feature: 'framework' version '4.0.5' is already
> > installed
> >
> > The specified feature: 'system' version '4.0.5' is already installed
> >
> > The specified feature: 'feature' version '4.0.5' is already installed
> >
> > The specified feature: 'shell' version '4.0.5' is already installed
> >
> > The specified feature: 'management' version '4.0.5' is already
> > installed
> >
> > The specified feature: 'service' version '4.0.5' is already installed
> >
> > The specified feature: 'jaas' version '4.0.5' is already installed
> >
> > The specified feature: 'shell-compat' version '4.0.5' is already
> > installed
> >
> > The specified feature: 'deployer' version '4.0.5' is already installed
> >
> > The specified feature: 'diagnostic' version '4.0.5' is already
> > installed
> >
> > The specified feature: 'wrap' version '0.0.0' is already installed
> >
> > The specified feature: 'bundle' version '4.0.5' is already installed
> >
> > The specified feature: 'config' version '4.0.5' is already installed
> >
> > The specified feature: 'kar' version '4.0.5' is already installed
> >
> > The specified feature: 'instance' version '4.0.5' is already installed
> >
> > The specified feature: 'package' version '4.0.5' is already installed
> >
> > The specified feature: 'log' version '4.0.5' is already installed
> >
> > The specified feature: 'ssh' version '4.0.5' is already installed
> >
> > The specified feature: 'aries-blueprint' version '4.0.5' is already
> > installed
> >
> > The specified feature: 'framework' version '4.0.5' is already
> > installed
> >
> > The specified feature: 'system' version '4.0.5' is already installed
> >
> > The specified feature: 'feature' version '4.0.5' is already installed
> >
> > The specified feature: 'shell' version '4.0.5' is already installed
> >
> > The specified feature: 'management' version '4.0.5' is already
> > installed
> >
> > The specified feature: 'service' version '4.0.5' is already installed
> >
> > The specified feature: 'jaas' version '4.0.5' is already installed
> >
> > The specified feature: 'shell-compat' version '4.0.5' is already
> > installed
> >
> > The specified feature: 'deployer' version '4.0.5' is already installed
> >
> > The specified feature: 'diagnostic' version '4.0.5' is already
> > installed
> >
> > The specified feature: 'wrap' version '0.0.0' is already installed
> >
> > The specified feature: 'bundle' version '4.0.5' is already installed
> >
> > The specified feature: 'config' version '4.0.5' is already installed
> >
> > The specified feature: 'kar' version '4.0.5' is already installed
> >
> > __ __ ____
> >
> > / //_/____ __________ _/ __/
> >
> > / ,< / __ `/ ___/ __ `/ /_
> >
> > / /| |/ /_/ / / / /_/ / __/
> >
> > /_/ |_|\__,_/_/ \__,_/_/
> >
> > Apache Karaf (4.0.5)
> >
> > Hit '<tab>' for a list of available commands
> >
> > and '[cmd] --help' for help on a specific command.
> >
> > Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> >
> > karaf@root()>
> >
> > __ __ ____
> >
> > / //_/____ __________ _/ __/
> >
> > / ,< / __ `/ ___/ __ `/ /_
> >
> > / /| |/ /_/ / / / /_/ / __/
> >
> > /_/ |_|\__,_/_/ \__,_/_/
> >
> > Apache Karaf (4.0.5)
> >
> > Hit '<tab>' for a list of available commands
> >
> > and '[cmd] --help' for help on a specific command.
> >
> > Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> >
> > karaf@root()>
> >
> > Not a copy’n’paste mistake – really duplicated output.
> >
> > As this did not happen in Karaf 2, 3 and 4.0.4 I think this could be
> > bug in the new boot feature “framework” which has been added in 4.0.5.
> >
> > It seems that the whole core is restarted when the custom logging
> > fragment is there.
> >
> > Do you agree with me and should I raise a Jira issue for that? And in
> > case this is a bug – do you have an idea for a workaround? Or could it
> > be an implementation mistake of the appender?
> >
> > We ship a custom distribution to our customers and this behavior is a
> > no-go because they could think that something failed even at the end
> > the application has started correctly.
> >
> > It does not make a good impression when the customers are faced with
> > some strange messages even at the first start.
> >
> > TIA & Regards
> >
> > Volker
> >
> >
> > CENIT AG, Industriestrasse 52-54, 70565 Stuttgart, Tel.: +49 711
> > 7825-30, Fax: +49 711 7825-4000, Internet: www.cenit.com
<http://www.cenit.com>
> > Geschaeftsstellen: Berlin, Frankfurt, Hamburg, Hannover, Muenchen,
> > Oelsnitz, Ratingen, Saarbruecken
> > Vorstandsmitglieder: Kurt Bengel, Matthias Schmidt
> > Aufsichtsratsmitglieder: Andreas Schmidt (Vorsitzender des
> > Aufsichtsrats), Hubert Leypoldt, Andreas Karrer
> > Bankverbindungen:
> > Deutsche Bank (BLZ 600 700 70) Kto. 1661 040 IBAN : DE85 6007 0070
> > 0166
> > 1040 00 SWIFT-CODE : DEUTDESS,
> > Commerzbank (BLZ 600 400 71) Kto. 532 015 500 IBAN : DE83 6004 0071
> > 0532
> > 0155 00 SWIFT-Code : COBADEFF600,
> > Registergericht: Amtsgericht Stuttgart
> > Handelsregister: HRB Nr. 19117
> > Umsatzsteuer: ID-Nr. DE 147 862 777
>
> --
> Jean-Baptiste Onofré
> [email protected] <mailto:[email protected]>
> http://blog.nanthrax.net
> Talend - http://www.talend.com
CENIT AG, Industriestrasse 52-54, 70565 Stuttgart, Tel.: +49 711
7825-30, Fax: +49 711 7825-4000, Internet: www.cenit.com
<http://www.cenit.com>
Geschaeftsstellen: Berlin, Frankfurt, Hamburg, Hannover, Muenchen,
Oelsnitz, Ratingen, Saarbruecken
Vorstandsmitglieder: Kurt Bengel, Matthias Schmidt
Aufsichtsratsmitglieder: Andreas Schmidt (Vorsitzender des
Aufsichtsrats), Hubert Leypoldt, Andreas Karrer
Bankverbindungen:
Deutsche Bank (BLZ 600 700 70) Kto. 1661 040 IBAN : DE85 6007 0070 0166
1040 00 SWIFT-CODE : DEUTDESS,
Commerzbank (BLZ 600 400 71) Kto. 532 015 500 IBAN : DE83 6004 0071 0532
0155 00 SWIFT-Code : COBADEFF600,
Registergericht: Amtsgericht Stuttgart
Handelsregister: HRB Nr. 19117
Umsatzsteuer: ID-Nr. DE 147 862 777
CENIT AG, Industriestrasse 52-54, 70565 Stuttgart, Tel.: +49 711
7825-30, Fax: +49 711 7825-4000, Internet: www.cenit.com
Geschaeftsstellen: Berlin, Frankfurt, Hamburg, Hannover, Muenchen,
Oelsnitz, Ratingen, Saarbruecken
Vorstandsmitglieder: Kurt Bengel, Matthias Schmidt
Aufsichtsratsmitglieder: Andreas Schmidt (Vorsitzender des
Aufsichtsrats), Hubert Leypoldt, Andreas Karrer
Bankverbindungen:
Deutsche Bank (BLZ 600 700 70) Kto. 1661 040 IBAN : DE85 6007 0070 0166
1040 00 SWIFT-CODE : DEUTDESS,
Commerzbank (BLZ 600 400 71) Kto. 532 015 500 IBAN : DE83 6004 0071 0532
0155 00 SWIFT-Code : COBADEFF600,
Registergericht: Amtsgericht Stuttgart
Handelsregister: HRB Nr. 19117
Umsatzsteuer: ID-Nr. DE 147 862 777
