[
https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-223.
--
> IlliegalStateException thrown during Tomcat shutdown
> --
[
https://issues.apache.org/jira/browse/LOG4J2-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-185.
--
> Howto individually configure logging for separate instances of a webapp (war
> file)?
>
[
https://issues.apache.org/jira/browse/LOG4J2-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-172.
--
> Logging doesn't work in Hibernate
> -
>
> Key: LOG4J2
[
https://issues.apache.org/jira/browse/LOG4J2-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-184.
--
> the performance for the log4j initialization needs to be improved
> -
[
https://issues.apache.org/jira/browse/LOG4J2-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-181.
--
> SocketAppender reconnection doesn't work
>
>
>
[
https://issues.apache.org/jira/browse/LOG4J2-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-182.
--
> Typo in "fundamental tenants" on Performance page
> -
[
https://issues.apache.org/jira/browse/LOG4J2-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-183.
--
> SyslogAppender and remote rsyslog server
>
>
>
[
https://issues.apache.org/jira/browse/LOG4J2-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-224.
--
Resolution: Fixed
Fix Version/s: 2.0-beta6
Assignee: Ralph Goers
Fixed in revision 1476
[
https://issues.apache.org/jira/browse/LOG4J2-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-104.
--
> LogManager initialization failed when running from Jdeveloper.
>
Ralph Goers created LOG4J2-224:
--
Summary: FlumeAppender creation fails if the Flume RPCClient
cannot establish a connection.
Key: LOG4J2-224
URL: https://issues.apache.org/jira/browse/LOG4J2-224
Project:
I doubt it will fix LOG4J2-222 but I will have to take a look.
Yes - I am thinking several days to fix the other issue I found and some of the
Jira issues.
Ralph
On Apr 27, 2013, at 7:19 PM, Remko Popma wrote:
> Do you think this may fix LOG4J2-222 as well?
>
> +1 beta6 soon
> Would like to
Do you think this may fix LOG4J2-222 as well?
+1 beta6 soon
Would like to include manual changes & rename AsynchAppender. Can I have 36
hours to make these changes?
Sent from my iPhone
On 2013/04/28, at 10:52, Ralph Goers wrote:
> I used the sample flume-remote app - which exposed another bug
[
https://issues.apache.org/jira/browse/LOG4J2-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams closed LOG4J2-221.
Verified. This is a huge improvement. Now, people need to be careful and stop
creating compiler warnin
I used the sample flume-remote app - which exposed another bug beyond the one
below.
Configurator was setting a new configuration and then setting it to a default
during shutdown, which doesn't really shutdown the LoggerContext so the
shutdown hook was still present. Configurator has been modi
I will try to contact the people working on the projects below and see if they
are interested in collaborating on this.
From: Remko Popma
To: Log4J Dev-List
Sent: Sunday, April 28, 2013 10:47 AM
Subject: Zero-garbage, off-heap, binary loggers
This is some
This is something I would like to work on next.
Related links:
https://bitbucket.org/vladimir.dolzhenko/gflogger/wiki/Home
https://groups.google.com/forum/#!forum/mechanical-sympathy (topic: new log
library?)
Not sure if it will be ready by the time of the Log4j 2.0 GA release, probably
not (I
[
https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-223.
Resolution: Fixed
Fix Version/s: 2.0-beta6
Configurator was not stopping the LoggerContext b
[
https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643869#comment-13643869
]
Nick Williams commented on LOG4J2-223:
--
I guess you needed me to file a bug, huh? :-)
Ralph Goers created LOG4J2-223:
--
Summary: IlliegalStateException thrown during Tomcat shutdown
Key: LOG4J2-223
URL: https://issues.apache.org/jira/browse/LOG4J2-223
Project: Log4j 2
Issue Type:
Nick,
I think it is possible to restrict access from package A to package B in
Eclipse,
but this would be IDE-dependent. Not sure if that is good enough for you.
(I found this link, which may be outdated:
http://www.eclipsezone.com/eclipse/forums/t53736.html )
An alternative would be to use a n
[
https://issues.apache.org/jira/browse/LOG4J2-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-221.
Resolution: Fixed
Fix Version/s: 2.0-beta6
Assignee: Ralph Goers
Patch applied - pl
Remko Popma created LOG4J2-222:
--
Summary: Async Logger threadpool not shut down by Tomcat shutdown
Key: LOG4J2-222
URL: https://issues.apache.org/jira/browse/LOG4J2-222
Project: Log4j 2
Issue Ty
Thank you for the explanation.
I've seen/used this naming pattern instead of fooSub:
- doFoo
- implFoo
- fooImpl
Gary
On Apr 27, 2013, at 16:17, Ralph Goers wrote:
That would probably be extremely confusing.
The managers initialize in the constructor and stop in the release method.
But Abstr
Ralph nailed it.
Also to an earlier point/question Ralph raised that isn't included below:
> However, note that we have o.a.l.log4j.net which has all the networking
> related managers. Perhaps it should have been under appenders as well, but it
> also supports servers as well as managers, which
That would probably be extremely confusing.
The managers initialize in the constructor and stop in the release method. But
AbstractManager takes care of the release method by checking for the counter
going down to zero and then calling releaseSub (yes - that is a horrible name).
Managers actua
Should connect/disconnect just be start/stop?
Gary
On Apr 27, 2013, at 11:20, Nick Williams
wrote:
On Apr 27, 2013, at 9:50 AM, Gary Gregory wrote:
On Sat, Apr 27, 2013 at 10:43 AM, Nick Williams <
nicho...@nicholaswilliams.net> wrote:
> There already existed an o.a.l.log4j.core.appender.db
This all sounds reasonable to me. However, note that we have o.a.l.log4j.net
which has all the networking related managers. Perhaps it should have been
under appenders as well, but it also supports servers as well as managers,
which probably isn't as likely with db appenders...?
Ralph
On Apr 2
Agreed, but since Nick doesn't have commit rights that is a bit more difficult
for him. I suppose two patches could be supplied to the Jira for the database
appender.
Ralph
On Apr 27, 2013, at 7:35 AM, Gary Gregory wrote:
> I think it would be clearer to remove close in a district commit.
>
On Apr 27, 2013, at 9:50 AM, Gary Gregory wrote:
> On Sat, Apr 27, 2013 at 10:43 AM, Nick Williams
> wrote:
> There already existed an o.a.l.log4j.core.appender.db package that was empty.
> I discovered that I could create a base AbstractDatabaseAppender that took
> care of some operations co
On Sat, Apr 27, 2013 at 10:43 AM, Nick Williams <
nicho...@nicholaswilliams.net> wrote:
> There already existed an o.a.l.log4j.core.appender.db package that was
> empty. I discovered that I could create a base AbstractDatabaseAppender
> that took care of some operations common to JDBC, JPA /and/ N
There already existed an o.a.l.log4j.core.appender.db package that was empty. I
discovered that I could create a base AbstractDatabaseAppender that took care
of some operations common to JDBC, JPA /and/ NoSQL appenders. That led me to
use the existing db package as follows:
db/
common DB ap
Okay. Understood. Should I file a bug for someone to take care of that, or will
someone just take care of that?
Note that an inner class within a *Test class @Overrides the close method but
doesn't do anything within it and doesn't call it. A simple find usages will
reveal it.
Nick
On Apr 27,
I think we should keep the packaging simpler: o.a.l.log4j.core.appender.jpa
Gary
On Apr 27, 2013, at 10:15, Nick Williams wrote:
> o.a.l.log4j.core.appender.db.jpa
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache
I think it would be clearer to remove close in a district commit.
Gary
On Apr 27, 2013, at 10:12, Nick Williams wrote:
> Ok. I'll remove it in my work on the database appenders.
>
> On Apr 27, 2013, at 8:56 AM, Ralph Goers wrote:
>
>> Sounds like I originally intended to use close but used stop
Guys,
In order to make a JPA appender, as discussed we'll have to add an OPTIONAL
dependency on the persistence API. I'd like to restrict the source code so that
ONLY classes in o.a.l.log4j.core.appender.db.jpa can use the JPA classes. I
know from working in Tomcat source code that you can, som
Ok. I'll remove it in my work on the database appenders.
On Apr 27, 2013, at 8:56 AM, Ralph Goers wrote:
> Sounds like I originally intended to use close but used stop instead. If
> close isn't being used then it can be removed.
>
> Sent from my iPad
>
> On Apr 27, 2013, at 4:46 AM, Nick Will
Sounds like I originally intended to use close but used stop instead. If close
isn't being used then it can be removed.
Sent from my iPad
On Apr 27, 2013, at 4:46 AM, Nick Williams
wrote:
> While working on database appenders, I figured that the best place to
> "connect" is in Appender#star
Yes. But I was thinking there might be a section heading somewhere called
Location Information that specifically identifies each of the location patterns
and discusses the overhead of each. This is one area where I miss the C
preprocessor as the location stuff could have been hidden in a macro s
While working on database appenders, I figured that the best place to "connect"
is in Appender#start() and, likewise, the best place to "disconnect" is in
Appender#stop(). However, then I noticed that AbstractAppender defines a
close() method with the JavaDoc comment "Close the stream associated
Ok, then to summarize my understanding for LOG4J2-219 the solution would be to:
* internally create a root logger if one isn't explicitly configured (like in
beta5)
* this default root logger would have level ERROR (like in beta5)
* this default root logger would not have any appenders configured
[
https://issues.apache.org/jira/browse/LOG4J2-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Hegermann updated LOG4J2-192:
-
Affects Version/s: 2.0-beta5
> ${env:...} is not replaced in fileName
> -
41 matches
Mail list logo
