[
https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713373#comment-13713373
]
Sudharma Puranik commented on LOG4J2-314:
-
Sure, I would add it in some time.
I have included the jars in the classpath, and I also added a
FastRollingFileAppender, which keeps on working after I redeploy, so it is
only the JPAAppender that stops working.
JD
On Fri, Jul 19, 2013 at 12:18 AM, Remko Popma wrote:
> What is your classpath?
>
> Your app dies while trying to
[
https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713341#comment-13713341
]
Remko Popma edited comment on LOG4J2-314 at 7/19/13 6:03 AM:
-
Can you borrow the kind of similar implementation done in logback? just my
2 cents?
On Wed, Jul 17, 2013 at 6:25 PM, Ralph Goers wrote:
> Stopping the Appender is not going to cause a rollover. You need a
> rollover policy that you can call that will then return true the next time
> it is acces
[
https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713341#comment-13713341
]
Remko Popma commented on LOG4J2-314:
Thanks! Can you also show how you programmaticall
[
https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudharma Puranik updated LOG4J2-314:
Description:
I have a log4j2.xml configuration file from which I am getting the Logger,
at
[
https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudharma Puranik updated LOG4J2-314:
Attachment: log4j2.xml
loggerThread.png
asyncAppendThread.pn
Sudharma Puranik created LOG4J2-314:
---
Summary: Multiple thread creation problem with AsyncAppender
Key: LOG4J2-314
URL: https://issues.apache.org/jira/browse/LOG4J2-314
Project: Log4j 2
Iss
Ok, I can do that.
On Fri, Jul 19, 2013 at 4:05 AM, Remko Popma wrote:
> I'd like to see your log4j.xml. Can you raise a Jira ticket and attach it?
>
> Sent from my iPhone
>
> On 2013/07/19, at 7:34, Remko Popma wrote:
>
> > Does your log4j2.xml also define an AsyncAppender?
> >
> > (Btw, what
Yes, log4j2.xml also defines a AsyncAppender but which is not mapped to any
logger. Is there a way that I can get the asyncAppender from the
xmlConfiguration and hook my RollingFileAppender? I did not find any such
convenience.
Why is handling of Appenders in log4j2 not straightforward? Or probabl
On Jul 18, 2013, at 20:28, Paul Benedict wrote:
"Proper documentation" is the key phrase. :-)
Yes! :)
Gary
On Thu, Jul 18, 2013 at 7:25 PM, Nick Williams <
[email protected]> wrote:
> Okay. Hold everything! Lol...
>
> I started working on this change and then realized something
"Proper documentation" is the key phrase. :-)
On Thu, Jul 18, 2013 at 7:25 PM, Nick Williams <
[email protected]> wrote:
> Okay. Hold everything! Lol...
>
> I started working on this change and then realized something. "Suppress"
> means "to forcibly put an end to," "restrain," or "p
Okay. Hold everything! Lol...
I started working on this change and then realized something. "Suppress" means
"to forcibly put an end to," "restrain," or "prevent the development, action,
or expression of." However, "ignore" means "refuse to take notice of or
acknowledge; disregard intentionally
Okay. I'll proceed with the change.
Nick
On Jul 18, 2013, at 2:08 PM, Ralph Goers wrote:
> First, I appreciate having the discussion before a code change like this is
> made. If that had been done I probably would have vetoed it. But this is the
> ASF where everybody gets a single voice and a
I'll try to whip something up this weekend.
Sent from my iPhone
On 2013/07/19, at 7:38, Ralph Goers wrote:
> That isn't completely true either. You could bridge JCL, JUL and Log4j 1.x
> to SLF4J using the SLF4J components and then route SLF4J to Log4j 2. That
> said, I probably wouldn't do
That isn't completely true either. You could bridge JCL, JUL and Log4j 1.x to
SLF4J using the SLF4J components and then route SLF4J to Log4j 2. That said, I
probably wouldn't do it that way.
The point is, I think the real problem is on the web site, not the name of the
jars. If one of us can
I'd like to see your log4j.xml. Can you raise a Jira ticket and attach it?
Sent from my iPhone
On 2013/07/19, at 7:34, Remko Popma wrote:
> Does your log4j2.xml also define an AsyncAppender?
>
> (Btw, what is a lakh?)
>
> Sent from my iPhone
>
> On 2013/07/19, at 0:31, Sudharma Puranik wro
Does your log4j2.xml also define an AsyncAppender?
(Btw, what is a lakh?)
Sent from my iPhone
On 2013/07/19, at 0:31, Sudharma Puranik wrote:
> I have a log4j2.xml configuration file from which I am getting the Logger,
> attached is the snapshot. when my logger is created a new thread is cre
On Jul 18, 2013, at 5:11 PM, Remko Popma wrote:
> I wasn't thinking of this from the point of view of the user; they will have
> an app that is coded using one of these logging apis, not all three.
Definitely not true! I have both SLF4J and JCL bridges in my applications. My
application itself
What is your classpath?
Your app dies while trying to load the resource
"META-INF/log4j-provider.properties".
This resource is in the log4j core jar. Do you have the log4j-core-2.0 jar in
the classpath?
Remko
From: JD Buys
To: Log4J Developers List
Sent: T
It is obviously not as clear-cut as I thought when I raised the question.
If "binding" is a word that communicates the intent/usage well for SLF4J users
we should keep it of course.
I was coming at this from the point of view of a Log4j developer and for us it
is nice to be able to use the same
I will give it a try tomorrow morning when I am back at work and let you
know the result.
On Thu, Jul 18, 2013 at 9:41 PM, Nick Williams <
[email protected]> wrote:
> Okay. Can you configure an additional, simple appender (like a file
> appender or similar) so that every event that g
[
https://issues.apache.org/jira/browse/LOG4J2-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-313.
Resolution: Fixed
Your patch was committed in revision 1504620. Please verify and close.
Okay. Can you configure an additional, simple appender (like a file appender or
similar) so that every event that gets logged goes to BOTH appenders?
Then, run your scenario again (works--redeploy--doesn't work). What I'm looking
for is if it's JUST the JPAAppender that quits working or if it's
Yes it is the only appender I have configured and it's added to the root
logger
On Thu, Jul 18, 2013 at 9:35 PM, Nick Williams <
[email protected]> wrote:
> Is the JPAAppender the only appender you have configured?
>
> Nick
>
> On Jul 18, 2013, at 2:32 PM, JD Buys wrote:
>
> Yep that
Is the JPAAppender the only appender you have configured?
Nick
On Jul 18, 2013, at 2:32 PM, JD Buys wrote:
> Yep that about sums it up.
> The rest of the application runs 100%.
>
>
> On Thu, Jul 18, 2013 at 4:58 PM, Nick Williams
> wrote:
>
> On Jul 18, 2013, at 9:52 AM, JD Buys wrote:
>
>
Yep that about sums it up.
The rest of the application runs 100%.
On Thu, Jul 18, 2013 at 4:58 PM, Nick Williams <
[email protected]> wrote:
>
> On Jul 18, 2013, at 9:52 AM, JD Buys wrote:
>
> I wonder if that might be where my problem is. I am using the
> BasicLogEventEntity, which
First, I appreciate having the discussion before a code change like this is
made. If that had been done I probably would have vetoed it. But this is the
ASF where everybody gets a single voice and a single vote. Although I dislike
this change and the effect it will have on my users I won't veto
First, these all started out being called adapters and even had their own
Maven groupId. We changed that a few releases ago. Second, although I have no
problem using the terminology on the web site I just hate having jar names that
long. I don't think it provides any value to them. And I am
Look at AbstractAppender. You will see that it exposes error methods that
Appender implementations can use.
Ralph
On Jul 18, 2013, at 10:56 AM, Nick Williams wrote:
> Well, as long as the Managers always propagate the error back to the
> Appender, then it shouldn't be a problem, right?
>
>
[
https://issues.apache.org/jira/browse/LOG4J2-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams closed LOG4J2-291.
> Failover appender doesn't fail over on JDBC appender error
>
[
https://issues.apache.org/jira/browse/LOG4J2-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712659#comment-13712659
]
Nick Williams commented on LOG4J2-291:
--
Good to hear! I'll close this now.
[
https://issues.apache.org/jira/browse/LOG4J2-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712653#comment-13712653
]
Michael Kloster commented on LOG4J2-291:
I pulled the latest snapshot today, built
My +1s below aside, let's not get off topic. Can someone get the JIRA created
and the announcement posted to the site and lists so that we can get this party
started? :-)
Nick
On Jul 18, 2013, at 2:01 AM, Ralph Goers wrote:
> I think "rush" is a bit of a stretch.
+1
> I've been working on th
Nice message Nick. I am in agreement with all your points.
Gary
On Thu, Jul 18, 2013 at 2:06 PM, Nick Williams <
[email protected]> wrote:
> Hmmm. So it sounds like we're at an impasse. Everyone except Ralph seems
> to agree to renaming it ignoreExceptions, bug Ralph said the below
So, again we are at an impasse it would seem. Paul, Gary, Nick, Remko all want
to rename these, Ralph opposes.
I /kind of/ see where Ralph's coming from here:
- log4j-slf4j-impl, called "SLF4J Binding," is an actual SLF4J implementation.
The SLF4J team calls them "bindings." This, the name "SLF
Hmmm. So it sounds like we're at an impasse. Everyone except Ralph seems to
agree to renaming it ignoreExceptions, bug Ralph said the below in opposition.
Ralph, can you clarify a little? Are you objecting to just renaming the
XML/JSON attribute (which, really, is the only thing that would break
Well, as long as the Managers always propagate the error back to the Appender,
then it shouldn't be a problem, right?
Where is the ErrorHandler supposed to be used? Is it in each Appender, or is it
used in whatever calls all of the Appenders (and, in that case, why wouldn't
the use be consisten
On Jul 18, 2013, at 9:52 AM, JD Buys wrote:
> I wonder if that might be where my problem is. I am using the
> BasicLogEventEntity, which works like I said until I redeploy then no logging
> to the JPAAppender occurs.
That's interesting. I'm very surprised that it works...
> I just said there
I wonder if that might be where my problem is. I am using the
BasicLogEventEntity, which works like I said until I redeploy then no
logging to the JPAAppender occurs.
I just said there was no stacktrace, but that was when starting up. When
the app is deployed, or the Glassfish server is shut down
Unfortunately there's no stack trace. When the app is redeployed the log
messages to the console still works and I can debug and see that the
JPAAppender is initialized.
Will debug through it thoroughly.
JD
On Thu, Jul 18, 2013 at 3:58 PM, Remko Popma wrote:
> Do you have a stack trace or erro
JD,
I look forward to the additional information you provide. In the meantime, just
a bit of info that I'm planning on putting in the documentation because it was
left out:
The JPAAppender was written for JPA 2.1 (minimum EclipseLink 2.5.0 or Hibernate
ORM 4.3.0), but strives to have backwards
Do you have a stack trace or error message? This does not give us much to go
on...
Sent from my iPhone
On 2013/07/18, at 22:04, JD Buys wrote:
> Hi,
>
> I have a strange error where if I deploy my application again, the JPA
> appender stops working.
> Any ideas why?
>
> I am running Glassfi
JD,
Thank you for the info, we look forward to your further details. At this
point, you can put it all in a new JIRA:
https://issues.apache.org/jira/browse/LOG4J2
Gary
On Thu, Jul 18, 2013 at 9:34 AM, JD Buys wrote:
> Yes, sorry, after I sent the email I realized it was very vague.
>
> I am u
[
https://issues.apache.org/jira/browse/LOG4J2-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-312:
Description:
- The XML root element was “eventSet”, it is now “events”. The word “set” is
misleadi
Yes, sorry, after I sent the email I realized it was very vague.
I am using log4j2 beta8 with eclipselink 2.3.0 on mysql.
The project is a ear module with which contains a war and ejb module, and I
am configuring log4j via code.
I will try and create a unit test or small program.
If the server s
Your report is too vague, can you be more precise please?
Which version of log4j2? What does your config look like? What does
not work exactly? Can you create a unit test or small program to
reproduce the issue? Which JPA provider? Which JDBC driver? Please
provide any information another person w
Hi,
I have a strange error where if I deploy my application again, the JPA
appender stops working.
Any ideas why?
I am running Glassfish 3.1.1
JD Buys
[
https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712093#comment-13712093
]
Ralph Goers commented on LOG4J2-10:
---
Yes. But I still have no idea how to test it.
[
https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712087#comment-13712087
]
Remko Popma commented on LOG4J2-10:
---
Ralph, did you eventually commit this?
If so, Timot
[
https://issues.apache.org/jira/browse/LOG4J2-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712086#comment-13712086
]
Remko Popma commented on LOG4J2-238:
Bob, some work was done on this issue as well as
I think "rush" is a bit of a stretch. I've been working on this for 4 years now
and we have been doing beta releases for a year. I don't mean any offense, but
I don't believe you being familiar with the whole code base is a requirement
for a GA release. To be honest, I haven't spent much time lo
52 matches
Mail list logo
