Re: ActiveMQ and Camel 2.17.x on Karaf
Btw, this trick with camel-cxf doesn't help with Camel 2.18.x. I think, there was a change in Camel 2.17.3 which helped with this problem (but not completely yet), but the change is not available in 2.18.x (I tried current snapshot and it didn't help too). It looks like this change has helped in 2.17.3 https://github.com/apache/camel/commit/284cc6780de1e32468ef2ae50ad357a444e79da1 (CAMEL-10153), which introduces [3.2,5) as version range for spring in camel-cxf. In 2.18.x there is still used the version range [4.1,5) Regards Krzysztof On 19.01.2017 01:17, Krzysztof Sobkowiak wrote: > My mistake. This problem still happens in the sample steps below - the > exception still occurs after Karaf restart and broker doesn't start. > But adding camel-cxf seems to fix this problem > > feature:install camel camel-blueprint camel-jms camel-cxf activemq-camel > activemq-broker-noweb activemq-blueprint > > Kindly regards > Krzysztof > > > On 14.01.2017 22:55, Krzysztof Sobkowiak wrote: >> Hi >> >> I could successfully install Camel 2.17.3 and ActiveMQ 5.14.3 on Karaf 4.0.8 >> (also 4.0.7): >> >> >> __ __ >>/ //_/ __ _/ __/ >> / ,< / __ `/ ___/ __ `/ /_ >> / /| |/ /_/ / / / /_/ / __/ >> /_/ |_|\__,_/_/ \__,_/_/ >> >> Apache Karaf (4.0.8) >> >> Hit '' for a list of available commands >> and '[cmd] --help' for help on a specific command. >> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf. >> >> karaf@root()> feature:repo-add camel 2.17.3 >> Adding feature url >> mvn:org.apache.camel.karaf/apache-camel/2.17.3/xml/features >> karaf@root()> feature:repo-add activemq 5.14.3 >> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.14.3/xml/features >> karaf@root()> feature:install camel camel-blueprint camel-jms activemq-camel >> activemq-broker-noweb activemq-blueprint >> karaf@root()> activemq:list >> brokerName = amq-broker >> >> >> Kindly tegards >> Krzysztof >> >> On 30.11.2016 14:11, IODB wrote: >>> Can somebody refer me to the relevant Jira issue, so I can track its >>> progress? >>> >>> Thanks >>> >>> Krzysztof Sobkowiak JEE & OSS Architect, Integration Architect Apache Software Foundation Member (http://apache.org/) Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/) Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
Re: ActiveMQ and Camel 2.17.x on Karaf
My mistake. This problem still happens in the sample steps below - the exception still occurs after Karaf restart and broker doesn't start. But adding camel-cxf seems to fix this problem feature:install camel camel-blueprint camel-jms camel-cxf activemq-camel activemq-broker-noweb activemq-blueprint Kindly regards Krzysztof On 14.01.2017 22:55, Krzysztof Sobkowiak wrote: > Hi > > I could successfully install Camel 2.17.3 and ActiveMQ 5.14.3 on Karaf 4.0.8 > (also 4.0.7): > > > __ __ >/ //_/ __ _/ __/ > / ,< / __ `/ ___/ __ `/ /_ > / /| |/ /_/ / / / /_/ / __/ > /_/ |_|\__,_/_/ \__,_/_/ > > Apache Karaf (4.0.8) > > Hit '' for a list of available commands > and '[cmd] --help' for help on a specific command. > Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf. > > karaf@root()> feature:repo-add camel 2.17.3 > Adding feature url mvn:org.apache.camel.karaf/apache-camel/2.17.3/xml/features > karaf@root()> feature:repo-add activemq 5.14.3 > Adding feature url mvn:org.apache.activemq/activemq-karaf/5.14.3/xml/features > karaf@root()> feature:install camel camel-blueprint camel-jms activemq-camel > activemq-broker-noweb activemq-blueprint > karaf@root()> activemq:list > brokerName = amq-broker > > > Kindly tegards > Krzysztof > > On 30.11.2016 14:11, IODB wrote: >> Can somebody refer me to the relevant Jira issue, so I can track its >> progress? >> >> Thanks >> >> >> >> -- >> View this message in context: >> http://karaf.922171.n3.nabble.com/ActiveMQ-and-Camel-2-17-x-on-Karaf-tp4046427p4048863.html >> Sent from the Karaf - Dev mailing list archive at Nabble.com. > > -- > Krzysztof Sobkowiak (@ksobkowiak) > > JEE & OSS Architect, Integration Architect > Apache Software Foundation Member (http://apache.org/) > Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/) > Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/) -- Krzysztof Sobkowiak (@ksobkowiak) JEE & OSS Architect, Integration Architect Apache Software Foundation Member (http://apache.org/) Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/) Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
ApacheCon CFP closing soon (11 February)
Hello, fellow Apache enthusiast. Thanks for your participation, and interest in, the projects of the Apache Software Foundation. I wanted to remind you that the Call For Papers (CFP) for ApacheCon North America, and Apache: Big Data North America, closes in less than a month. If you've been putting it off because there was lots of time left, it's time to dig for that inspiration and get those talk proposals in. It's also time to discuss with your developer and user community whether there's a track of talks that you might want to propose, so that you have more complete coverage of your project than a talk or two. We're looking for talks directly, and indirectly, related to projects at the Apache Software Foundation. These can be anything from in-depth technical discussions of the projects you work with, to talks about community, documentation, legal issues, marketing, and so on. We're also very interested in talks about projects and services built on top of Apache projects, and case studies of how you use Apache projects to solve real-world problems. We are particularly interested in presentations from Apache projects either in the Incubator, or recently graduated. ApacheCon is where people come to find out what technology they'll be using this time next year. Important URLs are: To submit a talk for Apache: Big Data - http://events.linuxfoundation.org/events/apache-big-data-north-america/program/cfp To submit a talk for ApacheCon - http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp To register for Apache: Big Data - http://events.linuxfoundation.org/events/apache-big-data-north-america/attend/register- To register for ApacheCon - http://events.linuxfoundation.org/events/apachecon-north-america/attend/register- Early Bird registration rates end March 12th, but if you're a committer on an Apache project, you get the low committer rate, which is less than half of the early bird rate! For further updated about ApacheCon, follow us on Twitter, @ApacheCon, or drop by our IRC channel, #apachecon on the Freenode IRC network. Or contact me - rbo...@apache.org - with any questions or concerns. Thanks! Rich Bowen, VP Conferences, Apache Software Foundation -- (You've received this email because you're on a dev@ or users@ mailing list of an Apache Software Foundation project. For subscription and unsubscription information, consult the headers of this email message, as this varies from one list to another.)
Re: Towards Karaf (Container) 4.1.0
Sure, I will take a look (I'm preparing Karaf 4.1.0 dependencies updates
and ServiceMix bundles release right now).
I keep you posted in the Jira.
Regards
JB
On 01/18/2017 05:30 AM, Oliver Lietz wrote:
On Wednesday 18 January 2017 04:48:43 Jean-Baptiste Onofré wrote:
Oh, I see.
Regarding the schedule, I'm not sure we will have time to do this for
Karaf 4.1.0. I would more plan this for 4.1.1.
The changes are already pretty large in coming 4.1.0.
Agreed ?
Sure – working around with external config files.
But can you please, please have a look at KARAF-4105 again? 8D
Thanks,
O.
Regards
JB
On 01/18/2017 03:39 AM, Oliver Lietz wrote:
On Wednesday 18 January 2017 03:22:31 Jean-Baptiste Onofré wrote:
Hi Oli
Hi JB,
Not sure I follow you. Cfg file are configadmin files. Do we have a Jira
describing what you mean ?
.cfg is the plain (Java) property file format and .config is the more rich
format of Felix ConfigAdmin. Both formats and the differences are
described at [2]. KARAF-4346 is related but I guess there should be more
issues in JIRA targeting the concrete problems, e.g. features do not
support the inlining of ConfigAdmin format configs.
Regards,
O.
Regards
JB
On Jan 18, 2017, 03:20, at 03:20, Oliver Lietz
wrote:
On Thursday 05 January 2017 15:39:19 Jean-Baptiste Onofré wrote:
Hi guys,
I started the updates and fixes for Karaf 4.1.0.
As dependencies, we will need Pax Exam 4.10.0 and Pax Web 6.0.1.
Achim
and I will tackle this as it's pre-requisite for 4.1.0.
I plan to create karaf-4.1.x branch next week for a release the
following week.
Thoughts ?
I would like to see full support for configurations in Felix
Configuration
Admin format (.config). This feature is essential for Sling on Karaf as
several components require not only strings in configurations[1], but
not
supported in .cfg format [2]. Support for this format in Pax Exam is
under way
(PAXEXAM-805).
For downstream projects (like Sling), early pre-releases would be
helpful for
transition. There was some uproar as I had to disable build jobs for
Sling/Karaf when switching to 4.1-SNAPSHOT ("no external snapshots
policy") to
catch up with current Sling (requires R6).
Regards,
O.
[1]
https://github.com/apache/sling/tree/trunk/karaf/org.apache.sling.karaf-> >>>
con
figs/src/main/resources [2]
http://sling.apache.org/documentation/bundles/configuration-installer-fa
cto
ry.html>
Thanks,
Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Towards Karaf (Container) 4.1.0
On Wednesday 18 January 2017 04:48:43 Jean-Baptiste Onofré wrote:
> Oh, I see.
>
> Regarding the schedule, I'm not sure we will have time to do this for
> Karaf 4.1.0. I would more plan this for 4.1.1.
>
> The changes are already pretty large in coming 4.1.0.
>
> Agreed ?
Sure – working around with external config files.
But can you please, please have a look at KARAF-4105 again? 8D
Thanks,
O.
> Regards
> JB
>
> On 01/18/2017 03:39 AM, Oliver Lietz wrote:
> > On Wednesday 18 January 2017 03:22:31 Jean-Baptiste Onofré wrote:
> >> Hi Oli
> >
> > Hi JB,
> >
> >> Not sure I follow you. Cfg file are configadmin files. Do we have a Jira
> >> describing what you mean ?
> >
> > .cfg is the plain (Java) property file format and .config is the more rich
> > format of Felix ConfigAdmin. Both formats and the differences are
> > described at [2]. KARAF-4346 is related but I guess there should be more
> > issues in JIRA targeting the concrete problems, e.g. features do not
> > support the inlining of ConfigAdmin format configs.
> >
> > Regards,
> > O.
> >
> >> Regards
> >> JB
> >>
> >> On Jan 18, 2017, 03:20, at 03:20, Oliver Lietz
> >
> > wrote:
> >>> On Thursday 05 January 2017 15:39:19 Jean-Baptiste Onofré wrote:
> Hi guys,
>
> I started the updates and fixes for Karaf 4.1.0.
>
> As dependencies, we will need Pax Exam 4.10.0 and Pax Web 6.0.1.
> >>>
> >>> Achim
> >>>
> and I will tackle this as it's pre-requisite for 4.1.0.
>
> I plan to create karaf-4.1.x branch next week for a release the
> following week.
>
> Thoughts ?
> >>>
> >>> I would like to see full support for configurations in Felix
> >>> Configuration
> >>> Admin format (.config). This feature is essential for Sling on Karaf as
> >>>
> >>> several components require not only strings in configurations[1], but
> >>> not
> >>> supported in .cfg format [2]. Support for this format in Pax Exam is
> >>> under way
> >>> (PAXEXAM-805).
> >>>
> >>> For downstream projects (like Sling), early pre-releases would be
> >>> helpful for
> >>> transition. There was some uproar as I had to disable build jobs for
> >>> Sling/Karaf when switching to 4.1-SNAPSHOT ("no external snapshots
> >>> policy") to
> >>> catch up with current Sling (requires R6).
> >>>
> >>> Regards,
> >>> O.
> >>>
> >>> [1]
> >>> https://github.com/apache/sling/tree/trunk/karaf/org.apache.sling.karaf->
> >>> >>> con
> >>> figs/src/main/resources [2]
> >>> http://sling.apache.org/documentation/bundles/configuration-installer-fa
> >>> cto
> >>> ry.html>
> >>>
> Thanks,
> Regards
> JB
Re: Towards Karaf (Container) 4.1.0
Oh, I see.
Regarding the schedule, I'm not sure we will have time to do this for
Karaf 4.1.0. I would more plan this for 4.1.1.
The changes are already pretty large in coming 4.1.0.
Agreed ?
Regards
JB
On 01/18/2017 03:39 AM, Oliver Lietz wrote:
On Wednesday 18 January 2017 03:22:31 Jean-Baptiste Onofré wrote:
Hi Oli
Hi JB,
Not sure I follow you. Cfg file are configadmin files. Do we have a Jira
describing what you mean ?
.cfg is the plain (Java) property file format and .config is the more rich
format of Felix ConfigAdmin. Both formats and the differences are described at
[2]. KARAF-4346 is related but I guess there should be more issues in JIRA
targeting the concrete problems, e.g. features do not support the inlining of
ConfigAdmin format configs.
Regards,
O.
Regards
JB
On Jan 18, 2017, 03:20, at 03:20, Oliver Lietz
wrote:
On Thursday 05 January 2017 15:39:19 Jean-Baptiste Onofré wrote:
Hi guys,
I started the updates and fixes for Karaf 4.1.0.
As dependencies, we will need Pax Exam 4.10.0 and Pax Web 6.0.1.
Achim
and I will tackle this as it's pre-requisite for 4.1.0.
I plan to create karaf-4.1.x branch next week for a release the
following week.
Thoughts ?
I would like to see full support for configurations in Felix
Configuration
Admin format (.config). This feature is essential for Sling on Karaf as
several components require not only strings in configurations[1], but
not
supported in .cfg format [2]. Support for this format in Pax Exam is
under way
(PAXEXAM-805).
For downstream projects (like Sling), early pre-releases would be
helpful for
transition. There was some uproar as I had to disable build jobs for
Sling/Karaf when switching to 4.1-SNAPSHOT ("no external snapshots
policy") to
catch up with current Sling (requires R6).
Regards,
O.
[1]
https://github.com/apache/sling/tree/trunk/karaf/org.apache.sling.karaf-con
figs/src/main/resources [2]
http://sling.apache.org/documentation/bundles/configuration-installer-facto
ry.html>
Thanks,
Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Towards Karaf (Container) 4.1.0
On Wednesday 18 January 2017 03:22:31 Jean-Baptiste Onofré wrote:
> Hi Oli
Hi JB,
> Not sure I follow you. Cfg file are configadmin files. Do we have a Jira
> describing what you mean ?
.cfg is the plain (Java) property file format and .config is the more rich
format of Felix ConfigAdmin. Both formats and the differences are described at
[2]. KARAF-4346 is related but I guess there should be more issues in JIRA
targeting the concrete problems, e.g. features do not support the inlining of
ConfigAdmin format configs.
Regards,
O.
> Regards
> JB
>
> On Jan 18, 2017, 03:20, at 03:20, Oliver Lietz
wrote:
> >On Thursday 05 January 2017 15:39:19 Jean-Baptiste Onofré wrote:
> >> Hi guys,
> >>
> >> I started the updates and fixes for Karaf 4.1.0.
> >>
> >> As dependencies, we will need Pax Exam 4.10.0 and Pax Web 6.0.1.
> >
> >Achim
> >
> >> and I will tackle this as it's pre-requisite for 4.1.0.
> >>
> >> I plan to create karaf-4.1.x branch next week for a release the
> >> following week.
> >>
> >> Thoughts ?
> >
> >I would like to see full support for configurations in Felix
> >Configuration
> >Admin format (.config). This feature is essential for Sling on Karaf as
> >
> >several components require not only strings in configurations[1], but
> >not
> >supported in .cfg format [2]. Support for this format in Pax Exam is
> >under way
> >(PAXEXAM-805).
> >
> >For downstream projects (like Sling), early pre-releases would be
> >helpful for
> >transition. There was some uproar as I had to disable build jobs for
> >Sling/Karaf when switching to 4.1-SNAPSHOT ("no external snapshots
> >policy") to
> >catch up with current Sling (requires R6).
> >
> >Regards,
> >O.
> >
> >[1]
> >https://github.com/apache/sling/tree/trunk/karaf/org.apache.sling.karaf-con
> >figs/src/main/resources [2]
> >http://sling.apache.org/documentation/bundles/configuration-installer-facto
> >ry.html>
> >> Thanks,
> >> Regards
> >> JB
Re: Towards Karaf (Container) 4.1.0
Hi Oli
Not sure I follow you. Cfg file are configadmin files. Do we have a Jira
describing what you mean ?
Regards
JB
On Jan 18, 2017, 03:20, at 03:20, Oliver Lietz wrote:
>On Thursday 05 January 2017 15:39:19 Jean-Baptiste Onofré wrote:
>> Hi guys,
>>
>> I started the updates and fixes for Karaf 4.1.0.
>>
>> As dependencies, we will need Pax Exam 4.10.0 and Pax Web 6.0.1.
>Achim
>> and I will tackle this as it's pre-requisite for 4.1.0.
>>
>> I plan to create karaf-4.1.x branch next week for a release the
>> following week.
>>
>> Thoughts ?
>
>I would like to see full support for configurations in Felix
>Configuration
>Admin format (.config). This feature is essential for Sling on Karaf as
>
>several components require not only strings in configurations[1], but
>not
>supported in .cfg format [2]. Support for this format in Pax Exam is
>under way
>(PAXEXAM-805).
>
>For downstream projects (like Sling), early pre-releases would be
>helpful for
>transition. There was some uproar as I had to disable build jobs for
>Sling/Karaf when switching to 4.1-SNAPSHOT ("no external snapshots
>policy") to
>catch up with current Sling (requires R6).
>
>Regards,
>O.
>
>[1]
>https://github.com/apache/sling/tree/trunk/karaf/org.apache.sling.karaf-configs/src/main/resources
>[2]
>http://sling.apache.org/documentation/bundles/configuration-installer-factory.html
>
>
>> Thanks,
>> Regards
>> JB
Re: Towards Karaf (Container) 4.1.0
On Thursday 05 January 2017 15:39:19 Jean-Baptiste Onofré wrote:
> Hi guys,
>
> I started the updates and fixes for Karaf 4.1.0.
>
> As dependencies, we will need Pax Exam 4.10.0 and Pax Web 6.0.1. Achim
> and I will tackle this as it's pre-requisite for 4.1.0.
>
> I plan to create karaf-4.1.x branch next week for a release the
> following week.
>
> Thoughts ?
I would like to see full support for configurations in Felix Configuration
Admin format (.config). This feature is essential for Sling on Karaf as
several components require not only strings in configurations[1], but not
supported in .cfg format [2]. Support for this format in Pax Exam is under way
(PAXEXAM-805).
For downstream projects (like Sling), early pre-releases would be helpful for
transition. There was some uproar as I had to disable build jobs for
Sling/Karaf when switching to 4.1-SNAPSHOT ("no external snapshots policy") to
catch up with current Sling (requires R6).
Regards,
O.
[1]
https://github.com/apache/sling/tree/trunk/karaf/org.apache.sling.karaf-configs/src/main/resources
[2]
http://sling.apache.org/documentation/bundles/configuration-installer-factory.html
> Thanks,
> Regards
> JB
Re: [K4.1] Pax Logging: Sift appender
On Wednesday 18 January 2017 11:03:42 Guillaume Nodet wrote:
> In that case, it might be better to use the same config as previously, i.e.
> route on bundle.name instead of bundle.id.
+1
Thanks,
O.
> 2017-01-18 11:01 GMT+01:00 Jean-Baptiste Onofré :
> > +1
> >
> > It will do it.
> >
> > Regards
> > JB
> >
> > On Jan 18, 2017, 01:59, at 01:59, Oliver Lietz
> >
> > wrote:
> > >On Wednesday 18 January 2017 10:25:42 Guillaume Nodet wrote:
> > >> I just got it working with something like:
> > >>
> > >> log4j2.appender.routing.type = Routing
> > >> log4j2.appender.routing.name = Routing
> > >> log4j2.appender.routing.routes.type = Routes
> > >> log4j2.appender.routing.routes.pattern = \$\$\\\{ctx:bundle.id\}
> > >> log4j2.appender.routing.routes.bundle.type = Route
> > >> log4j2.appender.routing.routes.bundle.appender.type =
> > >> RollingRandomAccessFile
> > >> log4j2.appender.routing.routes.bundle.appender.name =
> > >
> > >Bundle-\$\\\{ctx:
> > >> bundle.id\}
> > >> log4j2.appender.routing.routes.bundle.appender.fileName =
> > >> ${karaf.data}/log/bundle-\$\\\{ctx:bundle.id\}.log
> > >> log4j2.appender.routing.routes.bundle.appender.filePattern =
> > >> ${karaf.data}/log/bundle-\$\\\{ctx:bundle.id\}.log.%i
> > >> log4j2.appender.routing.routes.bundle.appender.append = true
> > >> log4j2.appender.routing.routes.bundle.appender.layout.type =
> > >
> > >PatternLayout
> > >
> > >> log4j2.appender.routing.routes.bundle.appender.layout.pattern =
> > >> ${log4j2.pattern}
> > >> log4j2.appender.routing.routes.bundle.appender.policies.type =
> > >
> > >Policies
> > >
> > >> log4j2.appender.routing.routes.bundle.appender.policies.size.type =
> > >> SizeBasedTriggeringPolicy
> > >> log4j2.appender.routing.routes.bundle.appender.policies.size.size =
> > >
> > >8MB
> > >
> > >Thanks, Guillaume. Can you add this appender configuration to Karaf
> > >4.1?
> > >
> > >O.
> > >
> > >> 2017-01-17 23:31 GMT+01:00 mbelling :
> > >> > I am also interested in the sift/MDC configuration in Karaf 4.1.
> > >
> > >Was
> > >
> > >> > there
> > >> > any more progress on this?
Re: [K4.1] Pax Logging: Sift appender
Yes it makes sense.
Regards
JB
On Jan 18, 2017, 02:04, at 02:04, Guillaume Nodet wrote:
>In that case, it might be better to use the same config as previously,
>i.e.
>route on bundle.name instead of bundle.id.
>
>2017-01-18 11:01 GMT+01:00 Jean-Baptiste Onofré :
>
>> +1
>>
>> It will do it.
>>
>> Regards
>> JB
>>
>> On Jan 18, 2017, 01:59, at 01:59, Oliver Lietz
>
>> wrote:
>> >On Wednesday 18 January 2017 10:25:42 Guillaume Nodet wrote:
>> >> I just got it working with something like:
>> >>
>> >> log4j2.appender.routing.type = Routing
>> >> log4j2.appender.routing.name = Routing
>> >> log4j2.appender.routing.routes.type = Routes
>> >> log4j2.appender.routing.routes.pattern = \$\$\\\{ctx:bundle.id\}
>> >> log4j2.appender.routing.routes.bundle.type = Route
>> >> log4j2.appender.routing.routes.bundle.appender.type =
>> >> RollingRandomAccessFile
>> >> log4j2.appender.routing.routes.bundle.appender.name =
>> >Bundle-\$\\\{ctx:
>> >> bundle.id\}
>> >> log4j2.appender.routing.routes.bundle.appender.fileName =
>> >> ${karaf.data}/log/bundle-\$\\\{ctx:bundle.id\}.log
>> >> log4j2.appender.routing.routes.bundle.appender.filePattern =
>> >> ${karaf.data}/log/bundle-\$\\\{ctx:bundle.id\}.log.%i
>> >> log4j2.appender.routing.routes.bundle.appender.append = true
>> >> log4j2.appender.routing.routes.bundle.appender.layout.type =
>> >PatternLayout
>> >> log4j2.appender.routing.routes.bundle.appender.layout.pattern =
>> >> ${log4j2.pattern}
>> >> log4j2.appender.routing.routes.bundle.appender.policies.type =
>> >Policies
>> >> log4j2.appender.routing.routes.bundle.appender.policies.size.type
>=
>> >> SizeBasedTriggeringPolicy
>> >> log4j2.appender.routing.routes.bundle.appender.policies.size.size
>=
>> >8MB
>> >
>> >Thanks, Guillaume. Can you add this appender configuration to Karaf
>> >4.1?
>> >
>> >O.
>> >
>> >> 2017-01-17 23:31 GMT+01:00 mbelling :
>> >> > I am also interested in the sift/MDC configuration in Karaf 4.1.
>> >Was
>> >> > there
>> >> > any more progress on this?
>> >> >
>> >> >
>> >> >
>>
>
>
>
>--
>
>Guillaume Nodet
>
>Red Hat, Open Source Integration
>
>Email: gno...@redhat.com
>Web: http://fusesource.com
>Blog: http://gnodet.blogspot.com/
Re: [K4.1] Pax Logging: Sift appender
In that case, it might be better to use the same config as previously, i.e.
route on bundle.name instead of bundle.id.
2017-01-18 11:01 GMT+01:00 Jean-Baptiste Onofré :
> +1
>
> It will do it.
>
> Regards
> JB
>
> On Jan 18, 2017, 01:59, at 01:59, Oliver Lietz
> wrote:
> >On Wednesday 18 January 2017 10:25:42 Guillaume Nodet wrote:
> >> I just got it working with something like:
> >>
> >> log4j2.appender.routing.type = Routing
> >> log4j2.appender.routing.name = Routing
> >> log4j2.appender.routing.routes.type = Routes
> >> log4j2.appender.routing.routes.pattern = \$\$\\\{ctx:bundle.id\}
> >> log4j2.appender.routing.routes.bundle.type = Route
> >> log4j2.appender.routing.routes.bundle.appender.type =
> >> RollingRandomAccessFile
> >> log4j2.appender.routing.routes.bundle.appender.name =
> >Bundle-\$\\\{ctx:
> >> bundle.id\}
> >> log4j2.appender.routing.routes.bundle.appender.fileName =
> >> ${karaf.data}/log/bundle-\$\\\{ctx:bundle.id\}.log
> >> log4j2.appender.routing.routes.bundle.appender.filePattern =
> >> ${karaf.data}/log/bundle-\$\\\{ctx:bundle.id\}.log.%i
> >> log4j2.appender.routing.routes.bundle.appender.append = true
> >> log4j2.appender.routing.routes.bundle.appender.layout.type =
> >PatternLayout
> >> log4j2.appender.routing.routes.bundle.appender.layout.pattern =
> >> ${log4j2.pattern}
> >> log4j2.appender.routing.routes.bundle.appender.policies.type =
> >Policies
> >> log4j2.appender.routing.routes.bundle.appender.policies.size.type =
> >> SizeBasedTriggeringPolicy
> >> log4j2.appender.routing.routes.bundle.appender.policies.size.size =
> >8MB
> >
> >Thanks, Guillaume. Can you add this appender configuration to Karaf
> >4.1?
> >
> >O.
> >
> >> 2017-01-17 23:31 GMT+01:00 mbelling :
> >> > I am also interested in the sift/MDC configuration in Karaf 4.1.
> >Was
> >> > there
> >> > any more progress on this?
> >> >
> >> >
> >> >
>
--
Guillaume Nodet
Red Hat, Open Source Integration
Email: gno...@redhat.com
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/
Re: [K4.1] Pax Logging: Sift appender
+1
It will do it.
Regards
JB
On Jan 18, 2017, 01:59, at 01:59, Oliver Lietz wrote:
>On Wednesday 18 January 2017 10:25:42 Guillaume Nodet wrote:
>> I just got it working with something like:
>>
>> log4j2.appender.routing.type = Routing
>> log4j2.appender.routing.name = Routing
>> log4j2.appender.routing.routes.type = Routes
>> log4j2.appender.routing.routes.pattern = \$\$\\\{ctx:bundle.id\}
>> log4j2.appender.routing.routes.bundle.type = Route
>> log4j2.appender.routing.routes.bundle.appender.type =
>> RollingRandomAccessFile
>> log4j2.appender.routing.routes.bundle.appender.name =
>Bundle-\$\\\{ctx:
>> bundle.id\}
>> log4j2.appender.routing.routes.bundle.appender.fileName =
>> ${karaf.data}/log/bundle-\$\\\{ctx:bundle.id\}.log
>> log4j2.appender.routing.routes.bundle.appender.filePattern =
>> ${karaf.data}/log/bundle-\$\\\{ctx:bundle.id\}.log.%i
>> log4j2.appender.routing.routes.bundle.appender.append = true
>> log4j2.appender.routing.routes.bundle.appender.layout.type =
>PatternLayout
>> log4j2.appender.routing.routes.bundle.appender.layout.pattern =
>> ${log4j2.pattern}
>> log4j2.appender.routing.routes.bundle.appender.policies.type =
>Policies
>> log4j2.appender.routing.routes.bundle.appender.policies.size.type =
>> SizeBasedTriggeringPolicy
>> log4j2.appender.routing.routes.bundle.appender.policies.size.size =
>8MB
>
>Thanks, Guillaume. Can you add this appender configuration to Karaf
>4.1?
>
>O.
>
>> 2017-01-17 23:31 GMT+01:00 mbelling :
>> > I am also interested in the sift/MDC configuration in Karaf 4.1.
>Was
>> > there
>> > any more progress on this?
>> >
>> >
>> >
Re: [K4.1] Pax Logging: Sift appender
On Wednesday 18 January 2017 10:25:42 Guillaume Nodet wrote:
> I just got it working with something like:
>
> log4j2.appender.routing.type = Routing
> log4j2.appender.routing.name = Routing
> log4j2.appender.routing.routes.type = Routes
> log4j2.appender.routing.routes.pattern = \$\$\\\{ctx:bundle.id\}
> log4j2.appender.routing.routes.bundle.type = Route
> log4j2.appender.routing.routes.bundle.appender.type =
> RollingRandomAccessFile
> log4j2.appender.routing.routes.bundle.appender.name = Bundle-\$\\\{ctx:
> bundle.id\}
> log4j2.appender.routing.routes.bundle.appender.fileName =
> ${karaf.data}/log/bundle-\$\\\{ctx:bundle.id\}.log
> log4j2.appender.routing.routes.bundle.appender.filePattern =
> ${karaf.data}/log/bundle-\$\\\{ctx:bundle.id\}.log.%i
> log4j2.appender.routing.routes.bundle.appender.append = true
> log4j2.appender.routing.routes.bundle.appender.layout.type = PatternLayout
> log4j2.appender.routing.routes.bundle.appender.layout.pattern =
> ${log4j2.pattern}
> log4j2.appender.routing.routes.bundle.appender.policies.type = Policies
> log4j2.appender.routing.routes.bundle.appender.policies.size.type =
> SizeBasedTriggeringPolicy
> log4j2.appender.routing.routes.bundle.appender.policies.size.size = 8MB
Thanks, Guillaume. Can you add this appender configuration to Karaf 4.1?
O.
> 2017-01-17 23:31 GMT+01:00 mbelling :
> > I am also interested in the sift/MDC configuration in Karaf 4.1. Was
> > there
> > any more progress on this?
> >
> >
> >
Re: [K4.1] Pax Logging: Sift appender
I just got it working with something like:
log4j2.appender.routing.type = Routing
log4j2.appender.routing.name = Routing
log4j2.appender.routing.routes.type = Routes
log4j2.appender.routing.routes.pattern = \$\$\\\{ctx:bundle.id\}
log4j2.appender.routing.routes.bundle.type = Route
log4j2.appender.routing.routes.bundle.appender.type =
RollingRandomAccessFile
log4j2.appender.routing.routes.bundle.appender.name = Bundle-\$\\\{ctx:
bundle.id\}
log4j2.appender.routing.routes.bundle.appender.fileName =
${karaf.data}/log/bundle-\$\\\{ctx:bundle.id\}.log
log4j2.appender.routing.routes.bundle.appender.filePattern =
${karaf.data}/log/bundle-\$\\\{ctx:bundle.id\}.log.%i
log4j2.appender.routing.routes.bundle.appender.append = true
log4j2.appender.routing.routes.bundle.appender.layout.type = PatternLayout
log4j2.appender.routing.routes.bundle.appender.layout.pattern =
${log4j2.pattern}
log4j2.appender.routing.routes.bundle.appender.policies.type = Policies
log4j2.appender.routing.routes.bundle.appender.policies.size.type =
SizeBasedTriggeringPolicy
log4j2.appender.routing.routes.bundle.appender.policies.size.size = 8MB
2017-01-17 23:31 GMT+01:00 mbelling :
> I am also interested in the sift/MDC configuration in Karaf 4.1. Was there
> any more progress on this?
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.
> com/K4-1-Pax-Logging-Sift-appender-tp4049215p4049267.html
> Sent from the Karaf - Dev mailing list archive at Nabble.com.
>
--
Guillaume Nodet
Red Hat, Open Source Integration
Email: gno...@redhat.com
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/
