Deploying AET containers in a locked down environment without access to the internet can be a challange:
upon AET start there's quite a few calls to Central Maven repo and that produces a lot of errors, which makes debugging a bit harder than it should be. It'd be great to remove those errors/warnings or at least provide an option to control that behaviour
ERROR [FelixDispatchQueue] Unable to update deployed features for bundle: healthcheck-features.xml - 0.0.0
ERROR [activator-1-thread-2] Error notifying listener about the current state
ERROR [activator-1-thread-2] Unable to update deployed features for bundle: aet-features.xml - 0.0.0
ERROR [activator-1-thread-2] Unable to update deployed features for bundle: aet-webconsole.xml - 0.0.0
WARN [FelixDispatchQueue] Can't load features repository mvn:org.apache.activemq/activemq-karaf/5.15.2/xml/features
WARN [FelixDispatchQueue] Can't load features repository mvn:org.apache.cxf.karaf/apache-cxf/3.2.0/xml/features
WARN [FelixDispatchQueue] Can't load features repository mvn:org.apache.karaf.features/spring-legacy/4.2.0/xml/features
WARN [FelixDispatchQueue] Error resolving artifact org.apache.activemq:activemq-karaf:xml:features:5.15.2: [Could not transfer artifact org.apache.activemq:activemq-karaf:xml:features:5.15.2 from/to central (https://repo1.maven.org/maven2/): Connection reset]
WARN [FelixDispatchQueue] Error resolving artifact org.apache.cxf.karaf:apache-cxf:xml:features:3.2.0: [Could not transfer artifact org.apache.cxf.karaf:apache-cxf:xml:features:3.2.0 from/to central (https://repo1.maven.org/maven2/): Connection reset]
WARN [FelixDispatchQueue] Error resolving artifact org.apache.karaf.features:spring-legacy:xml:features:4.2.0: [Could not transfer artifact org.apache.karaf.features:spring-legacy:xml:features:4.2.0 from/to central (https://repo1.maven.org/maven2/): Connection reset]
WARN [activator-1-thread-2] Can't load features repository mvn:org.apache.activemq/activemq-karaf/5.15.2/xml/features
WARN [activator-1-thread-2] Can't load features repository mvn:org.apache.cxf.karaf/apache-cxf/3.2.0/xml/features
WARN [activator-1-thread-2] Can't load features repository mvn:org.apache.karaf.features/enterprise/4.2.0/xml/features
WARN [activator-1-thread-2] Can't load features repository mvn:org.apache.karaf.features/framework/4.2.0/xml/features
WARN [activator-1-thread-2] Can't load features repository mvn:org.apache.karaf.features/spring-legacy/4.2.0/xml/features
WARN [activator-1-thread-2] Can't load features repository mvn:org.apache.karaf.features/spring/4.2.0/xml/features
WARN [activator-1-thread-2] Can't load features repository mvn:org.apache.karaf.features/standard/4.2.0/xml/features
WARN [activator-1-thread-2] Error resolving artifact org.apache.activemq:activemq-karaf:xml:features:5.15.2: [Could not transfer artifact org.apache.activemq:activemq-karaf:xml:features:5.15.2 from/to central (https://repo1.maven.org/maven2/): Connection reset]
WARN [activator-1-thread-2] Error resolving artifact org.apache.cxf.karaf:apache-cxf:xml:features:3.2.0: [Could not transfer artifact org.apache.cxf.karaf:apache-cxf:xml:features:3.2.0 from/to central (https://repo1.maven.org/maven2/): Connection reset]
WARN [activator-1-thread-2] Error resolving artifact org.apache.karaf.features:enterprise:xml:features:4.2.0: [Could not transfer artifact org.apache.karaf.features:enterprise:xml:features:4.2.0 from/to central (https://repo1.maven.org/maven2/): Connection reset]
WARN [activator-1-thread-2] Error resolving artifact org.apache.karaf.features:framework:xml:features:4.2.0: [Could not transfer artifact org.apache.karaf.features:framework:xml:features:4.2.0 from/to central (https://repo1.maven.org/maven2/): Connection reset]
WARN [activator-1-thread-2] Error resolving artifact org.apache.karaf.features:spring-legacy:xml:features:4.2.0: [Could not transfer artifact org.apache.karaf.features:spring-legacy:xml:features:4.2.0 from/to central (https://repo1.maven.org/maven2/): Connection reset]
WARN [activator-1-thread-2] Error resolving artifact org.apache.karaf.features:spring:xml:features:4.2.0: [Could not transfer artifact org.apache.karaf.features:spring:xml:features:4.2.0 from/to central (https://repo1.maven.org/maven2/): Connection reset]
WARN [activator-1-thread-2] Error resolving artifact org.apache.karaf.features:standard:xml:features:4.2.0: [Could not transfer artifact org.apache.karaf.features:standard:xml:features:4.2.0 from/to central (https://repo1.maven.org/maven2/): Connection reset]
WARN [downloader-4-thread-1] Error resolving artifact org.apache.servicemix.bundles:org.apache.servicemix.bundles.xmlbeans:jar:2.6.0_2: [Could not transfer artifact org.apache.servicemix.bundles:org.apache.servicemix.bundles.xmlbeans:jar:2.6.0_2 from/to central (https://repo1.maven.org/maven2/): Connection reset]
WARN [downloader-5-thread-1] Error resolving artifact org.apache.servicemix.bundles:org.apache.servicemix.bundles.xmlbeans:jar:2.6.0_2: [Could not transfer artifact org.apache.servicemix.bundles:org.apache.servicemix.bundles.xmlbeans:jar:2.6.0_2 from/to central (https://repo1.maven.org/maven2/): Connection reset]
WARN [downloader-6-thread-1] Error resolving artifact org.apache.servicemix.bundles:org.apache.servicemix.bundles.xmlbeans:jar:2.6.0_2: [Could not transfer artifact org.apache.servicemix.bundles:org.apache.servicemix.bundles.xmlbeans:jar:2.6.0_2 from/to central (https://repo1.maven.org/maven2/): Connection reset]
example-aet-swarm/features/healthcheck-features.xml implicitly requires access to the internet to download fabric8-karaf-checks bundle, which is strictly required for Apache Karaf to start (see #20). It's a vicious cycle - Apache Karaf container is constantly restarted, as healtcheck it waits for does not and will never work in such environment. To work that around I decided to put fabric8-karaf-checks in the bundles directory and remove healthcheck-features.xml file entirely.
malaskowski
commented
4 years ago
Deploying AET containers in a locked down environment without access to the internet can be a challange:
example-aet-swarm/features/healthcheck-features.xmlimplicitly requires access to the internet to downloadfabric8-karaf-checksbundle, which is strictly required for Apache Karaf to start (see #20). It's a vicious cycle - Apache Karaf container is constantly restarted, as healtcheck it waits for does not and will never work in such environment. To work that around I decided to putfabric8-karaf-checksin thebundlesdirectory and removehealthcheck-features.xmlfile entirely.