OK, understood. So let me try with 4.0.5 then.
Regards
JB
On 01/30/2018 08:25 AM, jyothi wrote:
> JB, Unfortunately this issue is happening on one instance of Client
> environment , where I can't check with other versions. I couldn't reproduce
> it in our local windows environment to check with
JB, Unfortunately this issue is happening on one instance of Client
environment , where I can't check with other versions. I couldn't reproduce
it in our local windows environment to check with latest version and be
certain that its working with latest version.
Also, there is no flexibility for
Can you please test with 4.0.10 (I will do it anyway) as we updated Pax Logging
version ?
Thanks,
Regards
JB
On 01/30/2018 08:03 AM, jyothi wrote:
> Working with Karaf 4.0.5. Didn't work on other versions.
>
> Tested with appender to the root logger and also removing spaces. It worked
> when
Working with Karaf 4.0.5. Didn't work on other versions.
Tested with appender to the root logger and also removing spaces. It worked
when removing spaces. But spaces are coming from Karaf script like below.
config:edit org.ops4j.pax.logging
config:property-set log4j.appender.custom.file
Hi,
Does it work if you add the appender to the rootLogger ?
Did you try with latest 4.0.10 ?
Regards
JB
On 01/30/2018 07:47 AM, jyothi wrote:
> Hi JB,
>
> Sorry couldn't mail, please find the complete pax logging file here and as
> said this issue is in Windows environment
>
>
> # Root
Hi JB,
Sorry couldn't mail, please find the complete pax logging file here and as
said this issue is in Windows environment
# Root logger
log4j.rootLogger = INFO, out, osgi:*
log4j.throwableRenderer=org.apache.log4j.OsgiThrowableRenderer
# Security audit logger
Hi JB!!
Mailed you the pax logging file and this issue is reproducible in Windows
environment.
Regards,
Jyothi
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
Can you send the complete org.ops4j.pax.logging.cfg ?
What's your OS ?
Thanks,
Regards
JB
On 01/30/2018 06:01 AM, jyothi wrote:
> Hi JB,
>
> Please find the attached image, where user log is not restricted to 1MB with
> below config in Pax Logging. Can you please suggest us on this if spaces
Hi JB,
Please find the attached image, where user log is not restricted to 1MB with
below config in Pax Logging. Can you please suggest us on this if spaces are
not an issue?
log4j.appender.custom = org.apache.log4j.RollingFileAppender
log4j.appender.custom.append = true
Sorry for the delay.. Back from vacation !!
Configuring appender in this way in pom and importing org.apache.log4j in
. Please let me know if I answered you properly
org.ops4j.pax.logging
pax-logging-service
1.8.4
provided
org.ops4j.pax.logging
You need to add the appender to a logger (rootLogger or specific one).
Can you share how you "call" the appender ?
Regards
JB
On 01/10/2018 01:29 AM, jyothi wrote:
Hi,
I didn't add custom to rootLogger.Do I need to add it?
Yes I restarted Karaf after the changes and this issue happened
Hi,
I didn't add custom to rootLogger.Do I need to add it?
Yes I restarted Karaf after the changes and this issue happened only on two
machines and not reproduced in other machines.
Thanks,
Jyothi.
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
Hmmm, it works fine on my box using 4.0.5 using the following config:
log4j.rootLogger=DEBUG, out, custom, osgi:*
...
log4j.appender.custom = org.apache.log4j.RollingFileAppender
log4j.appender.custom.append = true
log4j.appender.custom.file = ${karaf.data}/log/custom.log
Hi Jyothi,
I just tested with Karaf 4.0.11-SNAPSHOT and it works fine (using or not space).
Let me try with Karaf 4.0.5.
Regards
JB
On 12/14/2017 06:04 AM, jyothi wrote:
Hi JB!!
We are using karaf-4.0.5.
Thanks & Regards,
Jyothi.
--
Sent from:
Thank you so much JB!!
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
Hi Jyothi,
I have a local branch with the fix in Pax Logging. I will prepare a release to
be able to update in Karaf.
I keep you posted.
Regards
JB
On 01/04/2018 05:30 AM, jyothi wrote:
Hi JB!!
Sorry for disturbing you frequently on this !!
Please let me know if I can track of this JIRA
Hi JB!!
Sorry for disturbing you frequently on this !!
Please let me know if I can track of this JIRA issue?
Regards,
Jyothi.
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
Hi,
not yet, I will create the Jira and work on it today.
Sorry about the delay.
Regards
JB
On 12/22/2017 06:09 AM, jyothi wrote:
Hi JB!!
Can we know if you got a chance to check the spaces issue in Pax Logging?
Thanks & Regards,
Jyothi.
--
Sent from:
Hi JB!!
Can we know if you got a chance to check the spaces issue in Pax Logging?
Thanks & Regards,
Jyothi.
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
Hi Jyothi
Actually, there's two things:
1. Pax Logging should trim extra space
2. The config:* commands should not add extra spaces ;)
So, let me check for both ;)
Regards
JB
On 12/15/2017 08:26 AM, jyothi wrote:
Hi JB!!
When we removed spaces it worked!! Thanks for that.
But the config
Hi JB!!
When we removed spaces it worked!! Thanks for that.
But the config file content is generated using below script or ConfigMBean
update method.Can you please tell how can we remove the spaces without
manual action?
Ex:
config:edit org.ops4j.pax.logging
config:property-set
Hi JB!!
We are using karaf-4.0.5.
Thanks & Regards,
Jyothi.
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
Hi,
your configuration looks good to me.
Yes, please try to remove extra space first.
By the way, what's the Karaf version (I guess 4.0.x regarding your cfg file) ?
As reminder, Karaf 4.0.x uses log4j 1.x configuration style, and from Karaf
4.1.x, we are using log4j 2.x style.
Regards
JB
Hi JB,
Thanks for the quick response!!
Regarding spaces, that is generated one using config:property-append from
Karaf console. I will try to remove spaces and check if it works!!
Please find my complete pax logging config and I didn't added anything to
rootLogger. Do I need to add custom to
Hi,
It should work (it's what we are using without problem for "out" appender).
I guess you added this appender in the logger (rootLogger or specific logger)
right ?
Can you try to remove extra spaces around '=' ?
Regards
JB
On 12/13/2017 07:05 AM, jyothi wrote:
Hi,
I have configured for
Hi,
I have configured for a custom log in pax logging in Karaf as follows and
found the size of the custom log is not restricted to 1 MB and increasing.
Can you please let us know what could be the issue? Thanks in advance
log4j.appender.custom = org.apache.log4j.RollingFileAppender
26 matches
Mail list logo
