[jira] [Commented] (LOG4J2-1191) Log4j completely hangs in TcpSocketManager after a while...

[ https://issues.apache.org/jira/browse/LOG4J2-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033448#comment-15033448 ] Wolfgang Grossinger commented on LOG4J2-1191: - I asked operating to do that i

[jira] [Commented] (LOG4J2-1191) Log4j completely hangs in TcpSocketManager after a while...

[ https://issues.apache.org/jira/browse/LOG4J2-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033502#comment-15033502 ] Mikael Ståldal commented on LOG4J2-1191: Have you tried to wrap the Socket append

[jira] [Commented] (LOG4J2-435) Feature request: auto-delete older log files

[ https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033630#comment-15033630 ] Remko Popma commented on LOG4J2-435: I've given it some thought and one option is to i

[jira] [Comment Edited] (LOG4J2-435) Feature request: auto-delete older log files

[ https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033046#comment-15033046 ] Remko Popma edited comment on LOG4J2-435 at 12/1/15 12:49 PM: --

Re: Remko's schedule

Thank you for your kind words! I'll be helping build out a trading platform more or less from scratch. Lots of interesting challenges. Not sure how things will work out time-wise, so just giving a heads-up. On Mon, Nov 30, 2015 at 10:30 PM, Ralph Goers wrote: > I hope that isn’t the case. Your

Re: [jira] [Commented] (LOG4J2-508) Add new Levels: NOTICE, DIAG, VERBOSE.

This is a divisive issue and I really don't want to spark up the discussion again, but have you tried using custom levels for this in your projects? On Mon, Nov 30, 2015 at 10:30 PM, Gary Gregory (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/LOG4J2-508?page=com.atlassian.jira.p

[jira] [Created] (LOG4J2-1209) LoggerContext.stop() hangs indefinitely if any Appender's stop() method hangs

Mikael Ståldal created LOG4J2-1209: -- Summary: LoggerContext.stop() hangs indefinitely if any Appender's stop() method hangs Key: LOG4J2-1209 URL: https://issues.apache.org/jira/browse/LOG4J2-1209 Pro

[jira] [Commented] (LOG4J2-1209) LoggerContext.stop() hangs indefinitely if any Appender's stop() method hangs

[ https://issues.apache.org/jira/browse/LOG4J2-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033861#comment-15033861 ] Mikael Ståldal commented on LOG4J2-1209: Or else we need to review all appenders

[jira] [Commented] (LOG4J2-1209) LoggerContext.stop() hangs indefinitely if any Appender's stop() method hangs

[ https://issues.apache.org/jira/browse/LOG4J2-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033859#comment-15033859 ] Mikael Ståldal commented on LOG4J2-1209: One way to mitigate this would be if {{L

[jira] [Comment Edited] (LOG4J2-1209) LoggerContext.stop() hangs indefinitely if any Appender's stop() method hangs

[ https://issues.apache.org/jira/browse/LOG4J2-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033861#comment-15033861 ] Mikael Ståldal edited comment on LOG4J2-1209 at 12/1/15 3:27 PM: --

[jira] [Comment Edited] (LOG4J2-1209) LoggerContext.stop() hangs indefinitely if any Appender's stop() method hangs

[ https://issues.apache.org/jira/browse/LOG4J2-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033861#comment-15033861 ] Mikael Ståldal edited comment on LOG4J2-1209 at 12/1/15 3:26 PM: --

[jira] [Updated] (LOG4J2-1209) LoggerContext.stop() hangs indefinitely if any Appender's stop() method hangs

[ https://issues.apache.org/jira/browse/LOG4J2-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1209: --- Description: {{LoggerContext.stop()}} hangs indefinitely if any Appender's {{stop()}} method

[jira] [Updated] (LOG4J2-1209) LoggerContext.stop() hangs indefinitely if any Appender's stop() method hangs

[ https://issues.apache.org/jira/browse/LOG4J2-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1209: --- Description: {{LoggerContext.stop()}} hangs indefinitely if any Appender's {{stop()}} method

[jira] [Commented] (LOG4J2-1209) LoggerContext.stop() hangs indefinitely if any Appender's stop() method hangs

[ https://issues.apache.org/jira/browse/LOG4J2-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033885#comment-15033885 ] Ralph Goers commented on LOG4J2-1209: - I would suggest that we call each shutdown met

[jira] [Commented] (LOG4J2-1191) Log4j completely hangs in TcpSocketManager after a while...

[ https://issues.apache.org/jira/browse/LOG4J2-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033895#comment-15033895 ] Mikael Ståldal commented on LOG4J2-1191: If I understand it correctly, the defaul

[jira] [Commented] (LOG4J2-1209) LoggerContext.stop() hangs indefinitely if any Appender's stop() method hangs

[ https://issues.apache.org/jira/browse/LOG4J2-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033908#comment-15033908 ] Mikael Ståldal commented on LOG4J2-1209: Don't forget to make that thread daemon

[jira] [Commented] (LOG4J2-1209) LoggerContext.stop() hangs indefinitely if any Appender's stop() method hangs

[ https://issues.apache.org/jira/browse/LOG4J2-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033920#comment-15033920 ] Gary Gregory commented on LOG4J2-1209: -- We can also use an executor service to manag

[jira] [Commented] (LOG4J2-649) Close a dynamically created appender

[ https://issues.apache.org/jira/browse/LOG4J2-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15034047#comment-15034047 ] Mikael Ståldal commented on LOG4J2-649: --- I suggest we augment the unit test to ensur

[jira] [Commented] (LOG4J2-1209) LoggerContext.stop() hangs indefinitely if any Appender's stop() method hangs

[ https://issues.apache.org/jira/browse/LOG4J2-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15034112#comment-15034112 ] Ralph Goers commented on LOG4J2-1209: - Yes, that is the way I would implement it. But

Re: SocketAppender.createAppender() and Protocol Enum

I think I'll not duplicate the create() API, that seems silly. I do not believe we should provide BC at the level in the Core. Gary On Mon, Nov 2, 2015 at 9:47 PM, Gary Gregory wrote: > Sure, that's easy. > > Gary > On Nov 2, 2015 6:39 PM, "Remko Popma" wrote: > >> Okay. Can you leave the exis

Re: SocketAppender.createAppender() and Protocol Enum

On Tue, Dec 1, 2015 at 9:17 PM, Gary Gregory wrote: > I think I'll not duplicate the create() API, that seems silly. I do not > believe we should provide BC at the level in the Core. > Done. Gary > > Gary > > On Mon, Nov 2, 2015 at 9:47 PM, Gary Gregory > wrote: > >> Sure, that's easy. >> >>

Re: SocketAppender.createAppender() and Protocol Enum

I appreciated you want to keep core clean, but if it's easy to avoid breaking BC we should. We're talking about adding a factory method and calling one factory method from the other. Isn't that very little effort? Seems worth the effort to be kind to our users. Sent from my iPhone > On 2015/1

Re: SocketAppender.createAppender() and Protocol Enum

Mark the old one deprecated and remove the factory annotation? On 1 December 2015 at 22:14, Remko Popma wrote: > I appreciated you want to keep core clean, but if it's easy to avoid > breaking BC we should. We're talking about adding a factory method and > calling one factory method from the oth

Re: SocketAppender.createAppender() and Protocol Enum

Will do... Gary On Tue, Dec 1, 2015 at 11:14 PM, Remko Popma wrote: > I appreciated you want to keep core clean, but if it's easy to avoid > breaking BC we should. We're talking about adding a factory method and > calling one factory method from the other. Isn't that very little effort? > Seems

Re: SocketAppender.createAppender() and Protocol Enum

Done. Gary On Wed, Dec 2, 2015 at 12:31 AM, Gary Gregory wrote: > Will do... > > Gary > > On Tue, Dec 1, 2015 at 11:14 PM, Remko Popma > wrote: > >> I appreciated you want to keep core clean, but if it's easy to avoid >> breaking BC we should. We're talking about adding a factory method and >>

Re: [jira] [Commented] (LOG4J2-508) Add new Levels: NOTICE, DIAG, VERBOSE.

I don't want to deal with custom projects in this case I am dealing with now, and I also think that custom levels play well for domain-specific levels, not to augment the current system. For example, DEFCON1 through 5, Hurricane force winds, medical device alerts, things like that. IMO, adding leve

Build failed in Jenkins: Log4j 2.x #1570

See Changes: [ggregory] Javadoc. [ggregory] Add back and deprecate method. -- [...truncated 195 lines...] Running org.apache.logging.log4j.message.FormattedMessageTest Tests run: 7, Failures: 0, Err

Re: SocketAppender.createAppender() and Protocol Enum

Very quick! Thanks! Remko Sent from my iPhone > On 2015/12/02, at 14:36, Gary Gregory wrote: > > Done. > > Gary > >> On Wed, Dec 2, 2015 at 12:31 AM, Gary Gregory wrote: >> Will do... >> >> Gary >> >>> On Tue, Dec 1, 2015 at 11:14 PM, Remko Popma wrote: >>> I appreciated you want to keep