Re: Error pulling Karaf Docker Image

2021-01-22 Thread Jean-Baptiste Onofre 
By the way, you can see the images here:

https://hub.docker.com/r/apache/karaf/tags?page=1=last_updated 


I will push latest tag today.

Regards
JB

> Le 22 janv. 2021 à 22:23, Erwin Hogeweg  a écrit :
> 
> Excellent, thanks JB.
> 
> Erwin
> 
> 
>> On Jan 22, 2021, at 16:11, JB Onofré > > wrote:
>> 
>> I didn’t create the latest tag alias. I will. 
>> 
>> Defining the exact version should work (like 4.3.0). 
>> 
>> Regards
>> JB
>> 
>>> Le 22 janv. 2021 à 22:10, Erwin Hogeweg >> > a écrit :
>>> 
>>> Hi All -
>>> 
>>> I am trying to pull a karaf docker image but that fails with the following 
>>> error:
>>> 
>>> docker pull apache/karaf
>>> Using default tag: latest
>>> Error response from daemon: manifest for apache/karaf:latest not found: 
>>> manifest unknown: manifest unknown
>>> 
>>> Am I doing something wrong?
>>> 
>>> MacOS 11.1
>>> Docker version 20.10.2, build 2291f61
>>> 
>>> 
>>> Cheers,
>>> 
>>> Erwin
>>> 
>

Re: Error pulling Karaf Docker Image

2021-01-22 Thread Erwin Hogeweg 
Excellent, thanks JB.

Erwin


> On Jan 22, 2021, at 16:11, JB Onofré  wrote:
> 
> I didn’t create the latest tag alias. I will. 
> 
> Defining the exact version should work (like 4.3.0). 
> 
> Regards
> JB
> 
>> Le 22 janv. 2021 à 22:10, Erwin Hogeweg  a écrit :
>> 
>> Hi All -
>> 
>> I am trying to pull a karaf docker image but that fails with the following 
>> error:
>> 
>>  docker pull apache/karaf
>>  Using default tag: latest
>>  Error response from daemon: manifest for apache/karaf:latest not found: 
>> manifest unknown: manifest unknown
>> 
>> Am I doing something wrong?
>> 
>>  MacOS 11.1
>>  Docker version 20.10.2, build 2291f61
>> 
>> 
>> Cheers,
>> 
>> Erwin
>>

Re: Error pulling Karaf Docker Image

2021-01-22 Thread JB Onofré 
I didn’t create the latest tag alias. I will. 

Defining the exact version should work (like 4.3.0). 

Regards
JB

> Le 22 janv. 2021 à 22:10, Erwin Hogeweg  a écrit :
> 
> Hi All -
> 
> I am trying to pull a karaf docker image but that fails with the following 
> error:
> 
>   docker pull apache/karaf
>   Using default tag: latest
>   Error response from daemon: manifest for apache/karaf:latest not found: 
> manifest unknown: manifest unknown
> 
> Am I doing something wrong?
> 
>   MacOS 11.1
>   Docker version 20.10.2, build 2291f61
> 
> 
> Cheers,
> 
> Erwin
>

Error pulling Karaf Docker Image

2021-01-22 Thread Erwin Hogeweg 
Hi All -

I am trying to pull a karaf docker image but that fails with the following 
error:

docker pull apache/karaf
Using default tag: latest
Error response from daemon: manifest for apache/karaf:latest not found: 
manifest unknown: manifest unknown

Am I doing something wrong?

MacOS 11.1
Docker version 20.10.2, build 2291f61


Cheers,

Erwin

Re: Configuring MDC logging karaf 4 camel 3.7.0

2021-01-22 Thread Oleg Cohen 
Thank you, JB!

Is it possible now? If yes, is there an example.

Best,
Oleg

> On Jan 22, 2021, at 9:01 AM, Jean-Baptiste Onofre  wrote:
> 
> Hi Oleg,
> 
> The file name ${ctx:camel.contextId}.log is "normal" as it’s created before 
> the first camel context is created.
> 
> We can set additivity false or exclude "no context" in the sift appender.
> 
> Regards
> JB
> 
>> Le 22 janv. 2021 à 14:54, Oleg Cohen > > a écrit :
>> 
>> Hi JB,
>> 
>> I am also interested in this functionality and I have tried the same on a 
>> Mac. All worked good for me, but I see a file created 
>> camel-context-${ctx:camel.contextId}.log in the data/log folder that 
>> contains the entire duplicate log. Same as karaf.log. Have you observed the 
>> same?
>> 
>> Than you,
>> Oleg
>> 
>> On Fri, Jan 22, 2021 at 12:09 AM Jean-Baptiste Onofre > > wrote:
>> Hi Michael,
>> 
>> I’ve resumed my test about Camel MDC.
>> 
>> So, I created a simple route like this:
>> 
>> 
>> http://www.osgi.org/xmlns/blueprint/v1.0.0 
>> ">
>> 
>>   http://camel.apache.org/schema/blueprint 
>> " useMDCLogging="true">
>> 
>>   
>>   Hello World
>>   
>> 
>>   
>> 
>> 
>> 
>> Then, in etc/org.ops4j.pax.logging.cfg, I added:
>> 
>> log4j2.rootLogger.appenderRef.Sift.ref = Routing
>> 
>> …
>> 
>> log4j2.appender.routing.type = Routing
>> log4j2.appender.routing.name  = Routing
>> log4j2.appender.routing.routes.type = Routes
>> log4j2.appender.routing.routes.pattern = \$\$\\\{ctx:bundle.name 
>> \}
>> 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.name \}
>> log4j2.appender.routing.routes.bundle.appender.fileName = 
>> ${karaf.log}/camel-context-\$\\\{ctx:camel.contextId\}.log
>> log4j2.appender.routing.routes.bundle.appender.filePattern = 
>> ${karaf.log}/bundle-\$\\\{ctx:bundle.name \}.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
>> 
>> You can see the fileName containing camel.contextId.
>> 
>> In data/log, I can see the log file created for my Camel Context: 
>> camel-context-camel-1.log containing:
>> 
>> 2021-01-22T06:07:28,801 | INFO  | Blueprint Event Dispatcher: 1 | 
>> JmxManagementStrategy| 88 - org.apache.camel.camel-management - 
>> 3.7.0 | JMX is enabled
>> 2021-01-22T06:07:28,890 | INFO  | Blueprint Event Dispatcher: 1 | 
>> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
>> 3.7.0 | Apache Camel 3.7.0 (camel-1) is starting
>> 2021-01-22T06:07:28,892 | INFO  | Blueprint Event Dispatcher: 1 | 
>> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
>> 3.7.0 | MDC logging is enabled on CamelContext: camel-1
>> 2021-01-22T06:07:28,968 | INFO  | Blueprint Event Dispatcher: 1 | 
>> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
>> 3.7.0 | StreamCaching is not in use. If using streams then it's recommended 
>> to enable stream caching. See more details at 
>> http://camel.apache.org/stream-caching.html 
>> 
>> 2021-01-22T06:07:28,998 | INFO  | Blueprint Event Dispatcher: 1 | 
>> InternalRouteStartupManager  | 65 - org.apache.camel.camel-base-engine - 
>> 3.7.0 | Route: test started and consuming from: timer://fire <>
>> 2021-01-22T06:07:29,003 | INFO  | Blueprint Event Dispatcher: 1 | 
>> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
>> 3.7.0 | Total 1 routes, of which 1 are started
>> 2021-01-22T06:07:29,004 | INFO  | Blueprint Event Dispatcher: 1 | 
>> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
>> 3.7.0 | Apache Camel 3.7.0 (camel-1) started in 112ms
>> 2021-01-22T06:07:30,017 | INFO  | Camel (camel-1) thread #1 - timer://fire 
>> <> | test | 63 - org.apache.camel.camel-api - 
>> 3.7.0 | Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello 
>> World]
>> 
>> So, all good.
>> 
>> Can you confirm that if you use this on your machine it doesn’t work ? 
>> 
>> I’m looking for a Windows VM to test.
>> 
>> Regards
>> JB
>> 
>>> Le 21 janv. 2021 à 10:31, michael e >>

RE: Configuring MDC logging karaf 4 camel 3.7.0

2021-01-22 Thread michael e 
Hi JB,

I confirm, (for testing you can use my desktop).

Regards,
Michael.


De : Jean-Baptiste Onofre 
Envoyé : vendredi 22 janvier 2021 06:09
À : user 
Objet : Re: Configuring MDC logging karaf 4 camel 3.7.0

Hi Michael,

I’ve resumed my test about Camel MDC.

So, I created a simple route like this:


http://www.osgi.org/xmlns/blueprint/v1.0.0;>

  http://camel.apache.org/schema/blueprint; 
useMDCLogging="true">

  
  Hello World
  

  



Then, in etc/org.ops4j.pax.logging.cfg, I added:

log4j2.rootLogger.appenderRef.Sift.ref = Routing

…

log4j2.appender.routing.type = Routing
log4j2.appender.routing.name = Routing
log4j2.appender.routing.routes.type = Routes
log4j2.appender.routing.routes.pattern = \$\$\\\{ctx:bundle.name\}
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.name\}
log4j2.appender.routing.routes.bundle.appender.fileName = 
${karaf.log}/camel-context-\$\\\{ctx:camel.contextId\}.log
log4j2.appender.routing.routes.bundle.appender.filePattern = 
${karaf.log}/bundle-\$\\\{ctx:bundle.name\}.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

You can see the fileName containing camel.contextId.

In data/log, I can see the log file created for my Camel Context: 
camel-context-camel-1.log containing:

2021-01-22T06:07:28,801 | INFO  | Blueprint Event Dispatcher: 1 | 
JmxManagementStrategy| 88 - org.apache.camel.camel-management - 
3.7.0 | JMX is enabled
2021-01-22T06:07:28,890 | INFO  | Blueprint Event Dispatcher: 1 | 
AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
3.7.0 | Apache Camel 3.7.0 (camel-1) is starting
2021-01-22T06:07:28,892 | INFO  | Blueprint Event Dispatcher: 1 | 
AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
3.7.0 | MDC logging is enabled on CamelContext: camel-1
2021-01-22T06:07:28,968 | INFO  | Blueprint Event Dispatcher: 1 | 
AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
3.7.0 | StreamCaching is not in use. If using streams then it's recommended to 
enable stream caching. See more details at 
http://camel.apache.org/stream-caching.html
2021-01-22T06:07:28,998 | INFO  | Blueprint Event Dispatcher: 1 | 
InternalRouteStartupManager  | 65 - org.apache.camel.camel-base-engine - 
3.7.0 | Route: test started and consuming from: timer://fire
2021-01-22T06:07:29,003 | INFO  | Blueprint Event Dispatcher: 1 | 
AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
3.7.0 | Total 1 routes, of which 1 are started
2021-01-22T06:07:29,004 | INFO  | Blueprint Event Dispatcher: 1 | 
AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
3.7.0 | Apache Camel 3.7.0 (camel-1) started in 112ms
2021-01-22T06:07:30,017 | INFO  | Camel (camel-1) thread #1 - timer://fire | 
test | 63 - org.apache.camel.camel-api - 3.7.0 | 
Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello World]

So, all good.

Can you confirm that if you use this on your machine it doesn’t work ?

I’m looking for a Windows VM to test.

Regards
JB

Le 21 janv. 2021 à 10:31, michael e 
mailto:michaelel...@outlook.fr>> a écrit :

Hello JB,

Any news or fix ?

Thanks regards,
Michael.


De : Jean-Baptiste Onofre mailto:j...@nanthrax.net>>
Envoyé : jeudi 14 janvier 2021 10:16
À : user mailto:user@karaf.apache.org>>
Objet : Re: Configuring MDC logging karaf 4 camel 3.7.0

Oh my bad, I completely forget the Windows test ;)

I will do it just after AMQ release. For the tracking I will create a Jira.

I’m very sorry.

Regards
JB

Le 14 janv. 2021 à 10:03, michael e 
mailto:michaelel...@outlook.fr>> a écrit :

Hi JB,

Any news about this ?

Regards,
Michael.



De : Jean-Baptiste Onofre mailto:j...@nanthrax.net>>
Envoyé : mercredi 6 janvier 2021 17:21
À : user@karaf.apache.org 
mailto:user@karaf.apache.org>>
Objet : Re: Configuring MDC logging karaf 4 camel 3.7.0

Hi Michael,

Happy new year too !

I forgot during end of year vacation. I’m busy with ActiveMQ release 
preparation now, but I will switch back to test on Windows tomorrow.

Regards
JB

Le 6 janv. 2021 à 17:07, michael e 
mailto:michaelel...@outlook.fr>> a écrit :

Hello JB,

Happy new year, any news about this ?

Thanks,
Michael.



De : JB Onofré

Re: Configuring MDC logging karaf 4 camel 3.7.0

2021-01-22 Thread Jean-Baptiste Onofre 
Hi Oleg,

The file name ${ctx:camel.contextId}.log is "normal" as it’s created before the 
first camel context is created.

We can set additivity false or exclude "no context" in the sift appender.

Regards
JB

> Le 22 janv. 2021 à 14:54, Oleg Cohen  a écrit :
> 
> Hi JB,
> 
> I am also interested in this functionality and I have tried the same on a 
> Mac. All worked good for me, but I see a file created 
> camel-context-${ctx:camel.contextId}.log in the data/log folder that contains 
> the entire duplicate log. Same as karaf.log. Have you observed the same?
> 
> Than you,
> Oleg
> 
> On Fri, Jan 22, 2021 at 12:09 AM Jean-Baptiste Onofre  > wrote:
> Hi Michael,
> 
> I’ve resumed my test about Camel MDC.
> 
> So, I created a simple route like this:
> 
> 
> http://www.osgi.org/xmlns/blueprint/v1.0.0 
> ">
> 
>   http://camel.apache.org/schema/blueprint 
> " useMDCLogging="true">
> 
>   
>   Hello World
>   
> 
>   
> 
> 
> 
> Then, in etc/org.ops4j.pax.logging.cfg, I added:
> 
> log4j2.rootLogger.appenderRef.Sift.ref = Routing
> 
> …
> 
> log4j2.appender.routing.type = Routing
> log4j2.appender.routing.name  = Routing
> log4j2.appender.routing.routes.type = Routes
> log4j2.appender.routing.routes.pattern = \$\$\\\{ctx:bundle.name 
> \}
> 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.name \}
> log4j2.appender.routing.routes.bundle.appender.fileName = 
> ${karaf.log}/camel-context-\$\\\{ctx:camel.contextId\}.log
> log4j2.appender.routing.routes.bundle.appender.filePattern = 
> ${karaf.log}/bundle-\$\\\{ctx:bundle.name \}.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
> 
> You can see the fileName containing camel.contextId.
> 
> In data/log, I can see the log file created for my Camel Context: 
> camel-context-camel-1.log containing:
> 
> 2021-01-22T06:07:28,801 | INFO  | Blueprint Event Dispatcher: 1 | 
> JmxManagementStrategy| 88 - org.apache.camel.camel-management - 
> 3.7.0 | JMX is enabled
> 2021-01-22T06:07:28,890 | INFO  | Blueprint Event Dispatcher: 1 | 
> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
> 3.7.0 | Apache Camel 3.7.0 (camel-1) is starting
> 2021-01-22T06:07:28,892 | INFO  | Blueprint Event Dispatcher: 1 | 
> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
> 3.7.0 | MDC logging is enabled on CamelContext: camel-1
> 2021-01-22T06:07:28,968 | INFO  | Blueprint Event Dispatcher: 1 | 
> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
> 3.7.0 | StreamCaching is not in use. If using streams then it's recommended 
> to enable stream caching. See more details at 
> http://camel.apache.org/stream-caching.html 
> 
> 2021-01-22T06:07:28,998 | INFO  | Blueprint Event Dispatcher: 1 | 
> InternalRouteStartupManager  | 65 - org.apache.camel.camel-base-engine - 
> 3.7.0 | Route: test started and consuming from: timer://fire <>
> 2021-01-22T06:07:29,003 | INFO  | Blueprint Event Dispatcher: 1 | 
> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
> 3.7.0 | Total 1 routes, of which 1 are started
> 2021-01-22T06:07:29,004 | INFO  | Blueprint Event Dispatcher: 1 | 
> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
> 3.7.0 | Apache Camel 3.7.0 (camel-1) started in 112ms
> 2021-01-22T06:07:30,017 | INFO  | Camel (camel-1) thread #1 - timer://fire <> 
> | test | 63 - org.apache.camel.camel-api - 3.7.0 
> | Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello World]
> 
> So, all good.
> 
> Can you confirm that if you use this on your machine it doesn’t work ? 
> 
> I’m looking for a Windows VM to test.
> 
> Regards
> JB
> 
>> Le 21 janv. 2021 à 10:31, michael e > > a écrit :
>> 
>> Hello JB,
>> 
>> Any news or fix ?
>> 
>> Thanks regards,
>> Michael.
>> 
>> De : Jean-Baptiste Onofre mailto:j...@nanthrax.net>>
>> Envoyé : jeudi 14 janvier 2021 10:16
>> À : user mailto:user@karaf.apache.org>>
>> Objet : Re: Configuring MDC logging karaf 4 camel 3.7.0
>>

Re: Configuring MDC logging karaf 4 camel 3.7.0

2021-01-22 Thread Oleg Cohen 
Hi JB,

I am also interested in this functionality and I have tried the same on a
Mac. All worked good for me, but I see a file
created camel-context-${ctx:camel.contextId}.log in the data/log folder
that contains the entire duplicate log. Same as karaf.log. Have you
observed the same?

Than you,
Oleg

On Fri, Jan 22, 2021 at 12:09 AM Jean-Baptiste Onofre 
wrote:

> Hi Michael,
>
> I’ve resumed my test about Camel MDC.
>
> So, I created a simple route like this:
>
> 
> http://www.osgi.org/xmlns/blueprint/v1.0.0;>
>
>   http://camel.apache.org/schema/blueprint;
> useMDCLogging="true">
> 
>   
>   Hello World
>   
> 
>   
>
> 
>
> Then, in etc/org.ops4j.pax.logging.cfg, I added:
>
> log4j2.rootLogger.appenderRef.Sift.ref = Routing
>
> …
>
> log4j2.appender.routing.type = Routing
> log4j2.appender.routing.name = Routing
> log4j2.appender.routing.routes.type = Routes
> log4j2.appender.routing.routes.pattern = \$\$\\\{ctx:bundle.name\}
> 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.name\}
> log4j2.appender.routing.routes.bundle.appender.fileName
> = ${karaf.log}/camel-context-\$\\\{ctx:camel.contextId\}.log
> log4j2.appender.routing.routes.bundle.appender.filePattern
> = ${karaf.log}/bundle-\$\\\{ctx:bundle.name\}.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
>
> You can see the fileName containing camel.contextId.
>
> In data/log, I can see the log file created for my Camel
> Context: camel-context-camel-1.log containing:
>
> 2021-01-22T06:07:28,801 | INFO  | Blueprint Event Dispatcher: 1 |
> JmxManagementStrategy| 88 - org.apache.camel.camel-management -
> 3.7.0 | JMX is enabled
> 2021-01-22T06:07:28,890 | INFO  | Blueprint Event Dispatcher: 1 |
> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine
> - 3.7.0 | Apache Camel 3.7.0 (camel-1) is starting
> 2021-01-22T06:07:28,892 | INFO  | Blueprint Event Dispatcher: 1 |
> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine
> - 3.7.0 | MDC logging is enabled on CamelContext: camel-1
> 2021-01-22T06:07:28,968 | INFO  | Blueprint Event Dispatcher: 1 |
> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine
> - 3.7.0 | StreamCaching is not in use. If using streams then it's
> recommended to enable stream caching. See more details at
> http://camel.apache.org/stream-caching.html
> 2021-01-22T06:07:28,998 | INFO  | Blueprint Event Dispatcher: 1 |
> InternalRouteStartupManager  | 65 - org.apache.camel.camel-base-engine
> - 3.7.0 | Route: test started and consuming from: timer://fire
> 2021-01-22T06:07:29,003 | INFO  | Blueprint Event Dispatcher: 1 |
> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine
> - 3.7.0 | Total 1 routes, of which 1 are started
> 2021-01-22T06:07:29,004 | INFO  | Blueprint Event Dispatcher: 1 |
> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine
> - 3.7.0 | Apache Camel 3.7.0 (camel-1) started in 112ms
> 2021-01-22T06:07:30,017 | INFO  | Camel (camel-1) thread #1 - timer://fire
> | test | 63 - org.apache.camel.camel-api -
> 3.7.0 | Exchange[ExchangePattern: InOnly, BodyType: String, Body: Hello
> World]
>
> So, all good.
>
> Can you confirm that if you use this on your machine it doesn’t work ?
>
> I’m looking for a Windows VM to test.
>
> Regards
> JB
>
> Le 21 janv. 2021 à 10:31, michael e  a écrit :
>
> Hello JB,
>
> Any news or fix ?
>
> Thanks regards,
> Michael.
>
> --
> *De :* Jean-Baptiste Onofre 
> *Envoyé :* jeudi 14 janvier 2021 10:16
> *À :* user 
> *Objet :* Re: Configuring MDC logging karaf 4 camel 3.7.0
>
> Oh my bad, I completely forget the Windows test ;)
>
> I will do it just after AMQ release. For the tracking I will create a Jira.
>
> I’m very sorry.
>
> Regards
> JB
>
> Le 14 janv. 2021 à 10:03, michael e  a écrit :
>
> Hi JB,
>
> Any news about this ?
>
> Regards,
> Michael.
>
> --
>
> *De :* Jean-Baptiste Onofre 
> *Envoyé :* mercredi 6 janvier 2021 17:21
> *À :* user@karaf.apache.org 
> *Objet :* Re: Configuring MDC logging karaf 4 camel 3.7.0
>
> Hi Michael,
>
> Happy new year too !
>
> I forgot during end of year vacation. I’m busy with ActiveMQ release
> preparation now, but I will switch back to test on Windows tomorrow.
>
> Regards
> JB
>
> Le 6 janv. 2021 à 17:07, michael e  a écrit :
>
>