Re: EventAdmin RejectedExecutionException

2023-03-25 Thread Steven Huypens
Hi JB, Do you need any more info to be able to answer my questions? Kind regards, Steven On Wed, Mar 22, 2023 at 10:48 AM Steven Huypens wrote: > Hi JB, > > Thanks for your answer. > > From my debug.log (see below) I can only see a lot of config updates > before the exceptio

Re: Custom Karaf hangs on first boot if containing folder is renamed

2023-03-23 Thread Steven Huypens
For what it's worth, we faced an issue which this reminded me of. We concluded that the start order of bundles with the same start level depends on the full path of each bundle. As a result, renaming the karaf folder will have an impact on the boot procedure of your Karaf distro. We experienced

Re: EventAdmin RejectedExecutionException

2023-03-22 Thread Steven Huypens
Can you please share the karaf.log and eventually your assembly pom.xml ? > > Thanks > Regards > JB > > On Tue, Mar 21, 2023 at 11:31 AM Steven Huypens > wrote: > > > > Hi, > > > > When starting our custom Karaf distribution, we regularly see the error >

EventAdmin RejectedExecutionException

2023-03-21 Thread Steven Huypens
distribution true Kind regards, Steven Huypens

Re: Problems with logging to karaf.log from liquibase >3

2022-08-14 Thread Steven Huypens
ltiple, osgi.serviceloader; filter:="(osgi.serviceloader=liquibase.sqlgenerator.SqlGenerator)"; cardinality:=multiple org.apache.maven.plugins

Re: Problems with logging to karaf.log from liquibase >3

2022-08-14 Thread Steven Huypens
Hi Steinar, The xsd stacktrace can be explained by this liquibase-issue I think : https://github.com/liquibase/liquibase/issues/2817 They closed it incorrectly imho Kind regards, Steven On Sun, Aug 14, 2022 at 8:31 AM Steinar Bang wrote: > >>>>> Steven Huypens : >

Re: Problems with logging to karaf.log from liquibase >3

2022-08-13 Thread Steven Huypens
Hi Steinar, 1) The exception "No Common Superclass:javax/crypto/SecretKey javax/crypto/SecretKeyFactory" is from the liquibase pro package, as you can see in the stacktrace. But I do not understand that, because that package is not part of the 4.9.1 liquibase-core.jar. It might be however that we

Re: Problems with logging to karaf.log from liquibase >3

2022-08-10 Thread Steven Huypens
be ignored.If you manage to fix the other exception, I think you get a little closer to the solution. Kind regards, Steven On Tue, Aug 9, 2022 at 12:51 PM Steinar Bang wrote: > >>>>> Steven Huypens : > > > Hi Steinar, > > As far as I can tell, there is a spi

Re: Problems with logging to karaf.log from liquibase >3

2022-08-08 Thread Steven Huypens
Steinar Bang wrote: > >>>>> Steven Huypens : > > > Hi Steinar, > > I tried the liquibase-karaf-feature/use-liquibase-slf4j-410 branch. After > > changing the liquibase version to 4.9.1 in the pom.xml, the build is > > successful. > > Yes, but if

Re: Problems with logging to karaf.log from liquibase >3

2022-08-07 Thread Steven Huypens
Hi Steinar, I tried the liquibase-karaf-feature/use-liquibase-slf4j-410 branch. After changing the liquibase version to 4.9.1 in the pom.xml, the build is successful. Best regards, Steven On Sat, Aug 6, 2022 at 10:44 PM Steinar Bang wrote: > >>>>> Steven Huypens

Re: Problems with logging to karaf.log from liquibase >3

2022-08-06 Thread Steven Huypens
einar Bang wrote: > >>>>> Steven Huypens : > > > Hi Steinar, > > I tried to build the project, but ran into several issues. If you can > > update it, also updating the liquibase version, I'd be happy to take a > look. > > Ah, right! Sorry about th

Re: Problems with logging to karaf.log from liquibase >3

2022-08-06 Thread Steven Huypens
Hi Steinar, I tried to build the project, but ran into several issues. If you can update it, also updating the liquibase version, I'd be happy to take a look. Kind regards, Steven On Fri, Aug 5, 2022 at 5:22 PM Steinar Bang wrote: > >>>>> Steinar Bang : > >>&

Re: Problems with logging to karaf.log from liquibase >3

2022-08-05 Thread Steven Huypens
by: liquibase.exception.UnexpectedLiquibaseException: Cannot find default log service at liquibase.Scope.getCurrentScope(Scope.java:87) at liquibase.database.DatabaseFactory.(DatabaseFactory.java:20) ... 21 more Best regards, Steven On Fri, Aug 5, 2022 at 2:23 PM Steinar Bang wrote: > >>>>&

Re: Problems with logging to karaf.log from liquibase >3

2022-08-05 Thread Steven Huypens
I'm sure there are better ways nowadays, but this is how we got it to work so many years ago. Steven On Wed, Aug 3, 2022 at 3:25 PM Steinar Bang wrote: > >>>>> Steinar Bang : > >>>>> Steven Huypens : > > >> I had a brief look at your repo and I see yo

Re: Problems with logging to karaf.log from liquibase >3

2022-06-29 Thread Steven Huypens
Hi Steinar, I finally found some time to check our setup. We are currently using liquibase-core 4.9.1 (be it with some patches we required) on Karaf 4.3.7 and logging is working fine with Pax Logging, nothing special required, only the correct Slf4j configuration. I had a brief look at your repo

Re: Problems with logging to karaf.log from liquibase >3

2022-03-10 Thread Steven Huypens
Hi Steinar, We're using liquibase 3.8.0 in Karaf, higher 3.x versions are missing 'javax.activation' import. We have no liquibase-logging like you mention. Waiting for Liquibase 4.8.1 with Jakub's fix.. Kind regards, Steven On Wed, Mar 9, 2022 at 10:38 PM Steinar Bang wrote: > I've been

Re: Decanter and JMX

2021-09-22 Thread Steven Huypens
Thanks, that would be great ! Steven On Wed, Sep 22, 2021 at 4:21 PM JB Onofré wrote: > Oh yes. It just has to be exposed. I will do that. > > I forgot, sorry for the inconvenience. > > Regards > JB > > Le 22 sept. 2021 à 15:50, Steven Huypens a > écrit : >

Re: Decanter and JMX

2021-09-22 Thread Steven Huypens
Sep 19, 2021 at 3:33 PM Steven Huypens wrote: > > Great ! > > Anyway, thanks for the 2.8.0 release. Decanter now offers a prometheus > endpoint with the properties we need out-of-the-box. > > Steven > > On Sun, Sep 19, 2021 at 1:58 PM JB Onofré wrote: &g

Re: Decanter and JMX

2021-09-19 Thread Steven Huypens
st use property names provided by the collectors. > > I think it makes sense to use full object name and collector prefix to > differentiate the properties name. > > I will do that for next decanter release. > > Thanks for pointing this. > > Regards > JB > > Le 19 sep

Re: Decanter and JMX

2021-09-19 Thread Steven Huypens
prometheus/PrometheusServlet.java#L69 > > I hope it helps. > > Regards > JB > > > Le 19 sept. 2021 à 10:16, Steven Huypens a > écrit : > > > > Hi JB, > > > > I've tested the new 2.8.0 decanter release and I'm pleased to say your > fix for https://issue

Re: Significance of featuresBootAsynchronous - can you explain?

2021-09-19 Thread Steven Huypens
Hi JB, Still interested ;-) Kind regards, Steven On Tue, Sep 14, 2021 at 8:32 AM Stefan Günst wrote: > Hi JB, > > we would also be very interested on this > > Regards > Stefan > > > Am 13.09.2021 um 21:30 schrieb Steven Huypens : > > Hi JB, > > Thanks f

Re: Decanter and JMX

2021-09-19 Thread Steven Huypens
which MBean the properties are (or as you put it 'allow user to define the "exported" event properties by configuration'). Can you please explain how I can achieve this ? Kind regards, Steven On Wed, May 12, 2021 at 6:57 PM Steven Huypens wrote: > Hi Jean-Baptist, >

Re: Significance of featuresBootAsynchronous - can you explain?

2021-09-13 Thread Steven Huypens
che.org/jira/browse/KARAF-7246), the workaround is to > use a template file. > > Regards > JB > > On 13/09/2021 19:03, Steven Huypens wrote: > > Hi JB, > > > > I could not find how to implement such a 'stage' using the > > from the karaf-maven-plugin. Do y

Re: Significance of featuresBootAsynchronous - can you explain?

2021-09-13 Thread Steven Huypens
Hi JB, I could not find how to implement such a 'stage' using the from the karaf-maven-plugin. Do you know where I can find an example ? Kind regards, Steven On Mon, Sep 13, 2021 at 6:22 PM Jean-Baptiste Onofre wrote: > Exactly, you are in the case where stage can help ;) > > Regards > JB >

Re: Decanter and JMX

2021-06-01 Thread Steven Huypens
ject.name.karaf=org.apache.karaf:type=http,name=* > object.name.3=org.apache.activemq:* > > > Regards > JB > > Le 1 juin 2021 à 12:50, Steven Huypens a écrit > : > > Hi François, > > Thanks, I will try that ! > > Best regards, > Steven > &

Re: Decanter and JMX

2021-06-01 Thread Steven Huypens
karaf-decanter/blob/main/collector/jmx/src/main/cfg/org.apache.karaf.decanter.collector.jmx-camel.cfg > > regards, > > Françoisfpa...@apache.org > > Le 01/06/2021 à 11:07, Steven Huypens a écrit : > > Hi, > > Enabling the JMX-collector leads to a very high CPU load in our &g

Re: Decanter and JMX

2021-06-01 Thread Steven Huypens
Hi, Enabling the JMX-collector leads to a very high CPU load in our application, making it impossible to use. I'm not sure, but I think especially the org.apache.karaf MBeans are expensive to harvest, maybe because of the size of our application (>900 bundles). It would be very useful if we

Re: bootFeature with leading zero in version does not get state STARTED

2021-05-25 Thread Steven Huypens
https://issues.apache.org/jira/browse/KARAF-7163 Regards Steven On Tue, May 25, 2021 at 10:06 AM Jean-Baptiste Onofre wrote: > Ok, > > Can you please create a Jira about that, I will fix/improve that. > > Regards > JB > > Le 25 mai 2021 à 09:08, Steven Huy

Re: bootFeature with leading zero in version does not get state STARTED

2021-05-25 Thread Steven Huypens
Hi, Apparently our customer needs the version numbers to be alphanumerically sortable, so we cannot remove the leading zeroes. I'm looking forward to a solution, let me know how I can help. Best regards, Steven On Tue, May 25, 2021 at 6:19 AM Jean-Baptiste Onofre wrote: > Hi Daniel, > > I

Re: bootFeature with leading zero in version does not get state STARTED

2021-05-24 Thread Steven Huypens
Hi Daniel, No problem, I'm glad you sorted it out. I will still try to change our version numbers, but now I do consider this to be a little bug ;-) Kind regards, Steven On Mon, May 24, 2021 at 6:46 PM Daniel Krügler wrote: > Am 24.05.2021 um 18:25 schrieb Steven Huypens: > >

Re: bootFeature with leading zero in version does not get state STARTED

2021-05-24 Thread Steven Huypens
Hi Daniel, If that's clearly stated, I'll try to have our version numbers changed. Can you tell me where to find this statement ? I did try to look for it myself, but couldn't find it. Best regards, Steven On Mon, May 24, 2021 at 5:16 PM Daniel Krügler wrote: > Am 24.05.2021 um 17:10 schrieb

Re: bootFeature with leading zero in version does not get state STARTED

2021-05-24 Thread Steven Huypens
: wiring = resolver.resolve(context); Kind regards, Steven On Mon, May 24, 2021 at 1:27 PM Jean-Baptiste Onofre wrote: > Hi, > > Does it mean that you are using features repository in json format ? > > Regards > JB > > Le 24 mai 2021 à 12:44, Steven Huypens a écrit >

Re: bootFeature with leading zero in version does not get state STARTED

2021-05-24 Thread Steven Huypens
. > > Let me check in Felix. > > Regards > JB > > Le 23 mai 2021 à 19:47, Steven Huypens a écrit > : > > Hi JB, > > Thanks for your response. I guess we'll have to change our versioning > scheme then. Do you have a reference to the OSGi spec stating leadi

Re: bootFeature with leading zero in version does not get state STARTED

2021-05-23 Thread Steven Huypens
; I would consider as "works as designed" ;) > > The OSGi version parser expects "flat" versioning. > > Regards > JB > > > Le 23 mai 2021 à 11:06, Steven Huypens a > écrit : > > > > Hi All, > > > > When using a bootFeature with a le

bootFeature with leading zero in version does not get state STARTED

2021-05-23 Thread Steven Huypens
Hi All, When using a bootFeature with a leading zero in the version number (eg. 1.01.1-SNAPSHOT), the feature gets state UNINSTALLED after starting Karaf. All my bundles are OK, it's only the state of the feature that seems wrong. When I remove the leading zero (1.1.1-SNAPSHOT), the feature gets

Re: Decanter and JMX

2021-05-19 Thread Steven Huypens
Thanks ! On Wed, May 19, 2021 at 9:02 AM Jean-Baptiste Onofre wrote: > Hi Steven, > > Yes: https://issues.apache.org/jira/browse/KARAF-7154 > > I will work on Decanter release tonight. > > Regards > JB > > Le 19 mai 2021 à 08:19, Steven Huypens a écrit > :

Re: Decanter and JMX

2021-05-19 Thread Steven Huypens
fferent data > structure. > > However I think we can improve the Prometheus appender to recursive on > array/complex type down to numeric data that we can expose. > > I will create the Jira. > > Regards > JB > > Le 12 mai 2021 à 18:58, Steven Huypens a > écr

Re: instance:list causes warning

2021-05-14 Thread Steven Huypens
t; > - Eric L > > > On Wed, May 12, 2021 at 7:05 PM JB Onofré wrote: > >> Hi >> >> Forgot to check, sorry about that. I will keep you posted. >> >> Regards >> JB >> >> Le 12 mai 2021 à 19:01, Steven Huypens a >> écrit : >

Re: instance:list causes warning

2021-05-12 Thread Steven Huypens
Hi Jean-Baptiste, Did you manage to reproduce this ? Kind regards, Steven On Tue, May 4, 2021 at 2:10 PM Jean-Baptiste Onofre wrote: > Hi > > Thanks for the update. Let me try to reproduce it. I keep you posted. > > Regards > JB > > Le 4 mai 2021 à 14:07, Steven H

Re: Decanter and JMX

2021-05-12 Thread Steven Huypens
Hi Jean-Baptist, 1) You mention the Prometheus appender only exposes the numeric metrics. I believe it would be a minor but very useful addition to also expose the Objects in a CompositeDataSupport. For example java.lang.memory has a HeapMemoryUsage-object which contains 4 values (committed,

Re: instance:list causes warning

2021-05-04 Thread Steven Huypens
appeared. Best regards, Steven On Tue, May 4, 2021 at 1:43 PM Jean-Baptiste Onofre wrote: > Hi, > > What do you have in etc/org.apache.karaf.shell.cfg or etc/users.properties > ? > > Regards > JB > > Le 4 mai 2021 à 12:18, Steven Huypens a écrit : > > H

instance:list causes warning

2021-05-04 Thread Steven Huypens
Hi, When executing the command "instance:list" on our custom Karaf 4.2.11 distro (based on 'standard'), we see the following warning in the logfile. *2021-05-04 12:07:12,138 - [o.a.s.s.s.ServerSessionImpl][sshd-SshServer[44db67ef](port=8101)-nio2-thread-2] WARN -