Karaf 2.4.0 with Pax-Logging-Logback

Hi All, after getting pax-logging-logback implementation running in ServiceMix 5.1.x, based on Karaf 2.3.x, I face issues again in ServiceMix 5.3.0 using Karaf 2.4.0 I replaced the pax-logging-service bundle inside etc/startup.properties (as before) but was surprised to see a pax-logging-service

Re: Karaf 2.4.0 with Pax-Logging-Logback

Hi All, as a workaround I removed karaf-framework from the featuresBoot in etc/org.apache.karaf.features.cfg and the container runs nicely with no duplicate logging provider. Still curios why karaf-framework replicates the entries from etc/startup.properties ?! Best Regards, Michael 2014-11-21

Re: Karaf 2.4.0 with Pax-Logging-Logback

Well actually it's the other way round. The never version of Karaf which is build by the karaf-maven-plugin you'll need a feature to describe the Karaf container, allas the karaf-framework feature. On a related note: it would be extremely helpful if we had some kind of reverse search for

Karaf 3.0.2 refuses to run with Jdk8u40b15 (i586)

Dear Karaf-ers, I just updated Java to 8u40-b15. Karaf was ok with b12 but refuses to start with b15. Starting karaf just leads to a quick end of it without any message, no log at all (the file is not created), and no core dump. Where to start investigation? Kind regards, JP [@@ OPEN @@]

Deployment error with the Karaf Maven plugin

Hi, I work on a project that provides Karaf features and even custom Karaf distributions. To achieve this, I use the Karaf Maven plugin (3.0.2). The build and the platform work fine. However, when I run *mvn deploy* on my project, the Maven modules that use the Karaf plugin cannot be

restarting Karaf after uninstalling bundles or features

Karaf 3.0.1 is it necessary to restart Karaf after uninstalling bundles or features to avoid a missing bundles problem we've been seeing? Sometimes and suddenly, some bundles disappear when you type 'list'. Has anybody else seen this and what is the best practice when uninstalling then

Upgrading Karaf 2.3.5 to 2.4.0 (or 3.0.2)

Hi, Our application (Cytoscape) runs on top of a custom Karaf distribution that is currently based on Karaf 2.3.5. As this is a desktop application used by many end-users, we need to upgrade our Karaf release to one that fully supports Java 8. As such, we had a few questions: 1) What reasons are

The Karaf 3.0.x “Programmatically Connect” Developers Guide[1] uses some deprecated sshd APIs.

The example in the Karaf 3.0.x “Programmatically Connect” Developers Guide[1] uses some deprecated sshd APIs. I have detailed code using the deprecated APIs and suggested replacement code. *** Connect() changed From: ConnectFuture future = client.connect(host, port); To: ConnectFuture

AW: Deployment error with the Karaf Maven plugin

Hi! I had exactly the same problem. Build is working fine when I revert back to karaf-maven-plugin version 3.0.1 Best, Lukas Von: Vincent Zurczak [mailto:vincent.zurc...@linagora.com] Gesendet: Freitag, 21. November 2014 19:06 An: user@karaf.apache.org Betreff: Deployment error with the Karaf

Karaf 3.0.x and Bouncy Castle

I do some encryption stuff and use Bouncy Castle as the provider. In one of my classes I do: static { Security.addProvider(new BouncyCastleProvider()); } This works fine when running standalone - but when I deploy it to Karaf I get (of course) an unresolved constraint

Re: Karaf 3.0.2 refuses to run with Jdk8u40b15 (i586)

Hi JP, an another user reported the same issue after the update. I will investigate this during the week end. Regards JB On 11/21/2014 06:35 PM, CLEMENT Jean-Philippe wrote: Dear Karaf-ers, I just updated Java to 8u40-b15. Karaf was ok with b12 but refuses to start with b15. Starting karaf

Re: restarting Karaf after uninstalling bundles or features

Hi, no, normally it's not necessary to restart Karaf (it depends of the bundles, but generally speaking), and I didn't see such kind of issue. Is it only with ouyr own bundles, or with Karaf bundles as well ? Regards JB On 11/21/2014 08:07 PM, asookazian2 wrote: Karaf 3.0.1 is it necessary

Re: Upgrading Karaf 2.3.5 to 2.4.0 (or 3.0.2)

Hi, see my comments inline: 1) What reasons are there to pick Karaf 2.4.0 vs 3.0.2? Based on the versioning, it seems that Karaf 2.4.0 would be the safer option for 2.x users - though it does seem that 2.4 is using a newer version of OSGi than 3.0.2 (5.0 vs 4.3). I would say go directly to

Re: The Karaf 3.0.x “Programmatically Connect” Developers Guide[1] uses some deprecated sshd APIs.

Hi Paul, good point. I will create a Jira to update the documentation. Thanks, Regards JB On 11/21/2014 08:48 PM, Paul Spencer wrote: The example in the Karaf 3.0.x “Programmatically Connect” Developers Guide[1] uses some deprecated sshd APIs. I have detailed code using the deprecated APIs

Re: Deployment error with the Karaf Maven plugin

Hi, it's a known issue with karaf-maven-plugin 3.0.2. I have a Jira about that, it will be fix for 3.0.3. Regards JB On 11/21/2014 07:05 PM, Vincent Zurczak wrote: Hi, I work on a project that provides Karaf features and even custom Karaf distributions. To achieve this, I use the Karaf

Re: Karaf 3.0.x and Bouncy Castle

Hi, normally, bouncycastle should be in the system package (so startup.properties). So, your way should be fine too. Regards JB On 11/22/2014 01:27 AM, Richard Snowden wrote: I do some encryption stuff and use Bouncy Castle as the provider. In one of my classes I do: static {

Re: restarting Karaf after uninstalling bundles or features

I've only seen this happen with our custom bundles... jbonofre wrote Hi, no, normally it's not necessary to restart Karaf (it depends of the bundles, but generally speaking), and I didn't see such kind of issue. Is it only with ouyr own bundles, or with Karaf bundles as well ? Regards