[logback-dev] [JIRA] Commented: (LBCLASSIC-117) Log context based log splitting in SocketServer

[Rick Janda (JIRA)]

    [ http://jira.qos.ch/browse/LBCLASSIC-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11098#action_11098 ] 

Rick Janda commented on LBCLASSIC-117:
--------------------------------------

Works fine, Ceki, thank you very much. :-)

I only had to change ILoggingEvent to LoggingEvent.

I recognized a problem with the error handling of the SimpleSocketServer. When something is wrong with the discriminator class, e.g. a typo in the class attribute of the discriminator tag in the config file, than the server does not print out any error at all. It just ignores the SiftingAppender in this case. The problem seems to be in the SimpleSocketServer. If I try to use the SiftingAppender with a non exisiting descriminator class directly in the web application, the ClassNotFound exception is printed out to the console as expected. Shall I add this as a bug to Jira?

Kind regards, Rick

> Log context based log splitting in SocketServer
> -----------------------------------------------
>
>                 Key: LBCLASSIC-117
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-117
>             Project: logback-classic
>          Issue Type: New Feature
>          Components: Other
>    Affects Versions: unspecified
>            Reporter: Rick Janda
>            Assignee: Ceki Gulcu
>
> Hello logback team,
> I have the following setup:
> I have several web applications running in the same Tomcat instance.
> The JNDIContextSelector is used to give every deployed webapp its own logging context.
> The logging events are transmitted to a SocketServer.
> On the side of the SocketServer I want to split the logging events based on their log context to different files.
> My idea was to use filters, that filter according the logging context name. But this context name seems to be not reachable from within a filter.
> Would it be possible to add the logging context name as property to the LoggingEvent class that the name is available on the socket server side?
> Or add another means to accomplish the logging event splitting on the SocketServer side?
> This would really simplify our setup as of we would only need one SocketServer for all the Webapps.
> Thanks in advance for your help.
> Kind regards, 
> Rick

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira