Re: webconsole event presentation

Hi Scott, it's a change to do in the Felix EventAdmin WebConsole plugin. Regards JB On 10/20/2016 08:22 PM, Scott Lewis wrote: Hi, In the Karaf webconsole (with EventAdmin installed/running) the menu has an OSGi->Events page that shows the events received by EventAdmin. Is there a way to

webconsole event presentation

Hi, In the Karaf webconsole (with EventAdmin installed/running) the menu has an OSGi->Events page that shows the events received by EventAdmin. Is there a way to filter the presentation of events in this UI? There are a number of events that appear frequently/automatically (e.g.

Re: Best practice for context-specific service instances?

Why not exposing your service with the interface, but instead of exposing directly an instance, use a per-thread pooling mechanism ? 2016-10-20 13:10 GMT+02:00 cniehues : > Hi Tim, > > You are right, maybe the thread node was a little bit too confusing. > > Here

Re: Best practice for context-specific service instances?

Hi, It sounds as though the OSGi Async service would be helpful for you in doing asynchronous work (i.e. thread offloading) into services. Where those services need access to objects with state they can make use of prototype scoped services to do so. It could also be interesting to use

Re: Issue with "kar:install" redirecting from "http" to "https"

OK, it's what I thought: it comes from Pax URL. We are preparing improvements on Pax URL. Let me try with Pax URL SNAPSHOT. Regards JB On 10/20/2016 03:30 PM, Jens Reimann wrote: A bundle installation with such a redirect actually fails (see below) It looks a bit like that the download

Re: Issue with "kar:install" redirecting from "http" to "https"

A bundle installation with such a redirect actually fails (see below) It looks a bit like that the download either doesn't download or dosn download and empty file but keeps on working on that. --- 2016-10-20 10:34:52,247 | ERROR | nsole user karaf | ShellUtil| 22 -

Re: Issue with "kar:install" redirecting from "http" to "https"

Hi Jens, kar:install relays on Pax URL, so it could something there. Does it happen with another URL or resource (like a bundle) ? Regards JB On 10/20/2016 12:27 PM, Jens Reimann wrote: I just tried to install a KAR using: kar:install

Re: Best practice for context-specific service instances?

Hi Tim, You are right, maybe the thread node was a little bit too confusing. Here is a concrete example: I am receiving SOAP messages with camel cxf endpoints that will result in some complex operations lasting some time. To reach a quick processing of the messages I use camel:seda with

Issue with "kar:install" redirecting from "http" to "https"

I just tried to install a KAR using: kar:install http://dentrassi.de/camel-milo/milo-0.1.0-SNAPSHOT.kar That looked like it went fine. Registering the KAR, but not installing anything. However it works issuing this with the direct HTTPS URL instead: kar:install

Re: Best practice for context-specific service instances?

Hi Christian, What is it that you’re trying to achieve? > is it possible to have multiple equal instances of a service or is this > breaking the principle rules of OSGI? Yes, you can have multiple service registrations for the same object instance, but this doesn’t make a whole lot of sense.

Re: Decanter - Bigger issue with the ElasticSearch Rest appender

Good to know, but weird anyway (especially, as it works when using "locally" or on docker). Thanks, Regards JB On 10/20/2016 09:53 AM, Achim Nierbeck wrote: Ok .. my latest fix seems to fix it. The default seems to be true which does have some strange effects. regards, Achim 2016-10-20

Re: Decanter - Bigger issue with the ElasticSearch Rest appender

Ok .. my latest fix seems to fix it. The default seems to be true which does have some strange effects. regards, Achim 2016-10-20 9:48 GMT+02:00 Jean-Baptiste Onofré : > OK, let me look for one ;) > > Regards > JB > > On 10/20/2016 09:44 AM, Achim Nierbeck wrote: > >> Very

Re: Decanter - Bigger issue with the ElasticSearch Rest appender

And I did configure it via code ... that's the main difference to the standard configuration. But that shouldn't be much of an issue. As only one configuration is present in Karaf. regards, Achim 2016-10-20 9:44 GMT+02:00 Achim Nierbeck : > Very simple just let it

Re: Decanter - Bigger issue with the ElasticSearch Rest appender

OK, let me look for one ;) Regards JB On 10/20/2016 09:44 AM, Achim Nierbeck wrote: Very simple just let it connect to a ES run by Amazon :D regards, Achim 2016-10-20 9:39 GMT+02:00 Jean-Baptiste Onofré >: Hi Achim, No problem to disable

Re: Decanter - Bigger issue with the ElasticSearch Rest appender

Very simple just let it connect to a ES run by Amazon :D regards, Achim 2016-10-20 9:39 GMT+02:00 Jean-Baptiste Onofré : > Hi Achim, > > No problem to disable the checker and improve the discovery. > > For 1. I never had this issue with elasticsearch on docker (with Mesos). >

Decanter - Bigger issue with the ElasticSearch Rest appender

Hi, right now we do have an issue with the ElasticSearch Rest appender when using a an amazon based ES instance. this results in two rather stange effects I'd like to discuss 1) we do get an Exception by DS (SCR) that it's not able to obtain a lock on a service ... don't know where this is

Re: See root exception cause in log?

Thanks! That should help at least for shell commands. On Wed, Oct 19, 2016 at 11:11 AM, Jean-Baptiste Onofré wrote: > It's a command. > > Regards > JB > > On 10/19/2016 11:09 AM, Jens Reimann wrote: > >> Thanks for the help. Is this a command? Or a configuration option in >>

Re: Could/should OsgiConfiguration for JAAS fallback to default configuration

Hi JB, thanks for looking into it. I already created a jira: https://issues.apache.org/jira/browse/KARAF-4784 The workaround with an own login module ain't that easy, because we do not know the names of all current jaas configurations customers have today (can be multiple per installation).

Re: Best practice for context-specific service instances?

I am still asking me the question: is it possible to have multiple equal instances of a service or is this breaking the principle rules of OSGI? Because beside my wish of context specific instances I also see the need of parallel processing of messages. How do you do this with a single service