Dominik Psenner (JIRA | 12 Feb 22:35 2016
Picon

[jira] [Closed] (LOG4NET-504) Exception mode during configuration


     [
https://issues.apache.org/jira/browse/LOG4NET-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Psenner closed LOG4NET-504.
-----------------------------------
    Resolution: Won't Fix
      Assignee: Dominik Psenner

This issue is documented here:

https://logging.apache.org/log4net/release/faq.html#trouble-file-perm

The logging framework should under no circumstance throw exceptions that could crash the applications.
Such exceptions are treated as serious bugs:

https://logging.apache.org/log4net/release/faq.html#reliability

Because of the afore mentioned reasons I'm closing the issue as won't fix.

> Exception mode during configuration
> -----------------------------------
>
>                 Key: LOG4NET-504
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-504
>             Project: Log4net
>          Issue Type: Wish
>          Components: Other
>            Reporter: Gregory Zak
>            Assignee: Dominik Psenner
(Continue reading)

Dominik Psenner (JIRA | 12 Feb 22:25 2016
Picon

[jira] [Commented] (LOG4NET-505) AdoNetAppender with Npgsql data provider


    [
https://issues.apache.org/jira/browse/LOG4NET-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15145328#comment-15145328
] 

Dominik Psenner commented on LOG4NET-505:
-----------------------------------------

It would be great if you could write a patch that fixes the issue or a test that reproduces the issue.

> AdoNetAppender with Npgsql data provider
> ----------------------------------------
>
>                 Key: LOG4NET-505
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-505
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.15
>            Reporter: Vadim Ivanou
>
> I'm trying to use AdoNetAppender with postgresql database and Npgsql data provider 3.0.x.
Unfortunately it throws an exception in SendBuffer method while executing dbCmd.Prepare(). I believe
the reason for that is that Npgsql requires all Parameters to be present in a command before calling
Prepare method. I created my own adapter that overrides SendBuffer method and populates sql command
parameters before Prepare and it worked fine.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
(Continue reading)

Gregory Zak (JIRA | 10 Feb 23:48 2016
Picon

[jira] [Comment Edited] (LOG4NET-504) Exception mode during configuration


    [
https://issues.apache.org/jira/browse/LOG4NET-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141873#comment-15141873
] 

Gregory Zak edited comment on LOG4NET-504 at 2/10/16 10:47 PM:
---------------------------------------------------------------

No, the problem is that the app didn't have permissions to write the log files, including the internal
logging files. In case of permission issues, it seems reasonable to throw exceptions to the user so they
don't spend hours pulling their hair out wondering why on earth nothing is being written. After all,
permission issues are something you solve once at the beginning and then everything is smooth afterwards.

was (Author: thegzak <at> gmail.com):
No, the problem is that the app didn't have permissions to write the log files, including the internal
logging files. In case of permission issues, it seems reasonable to through exceptions to the user so they
don't spend hours pulling their hair out wondering why on earth nothing is being written. After all,
permission issues are something you solve once at the beginning and then everything is smooth afterwards.

> Exception mode during configuration
> -----------------------------------
>
>                 Key: LOG4NET-504
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-504
>             Project: Log4net
>          Issue Type: Wish
>          Components: Other
>            Reporter: Gregory Zak
>            Priority: Minor
>
(Continue reading)

Gregory Zak (JIRA | 10 Feb 23:47 2016
Picon

[jira] [Commented] (LOG4NET-504) Exception mode during configuration


    [
https://issues.apache.org/jira/browse/LOG4NET-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141873#comment-15141873
] 

Gregory Zak commented on LOG4NET-504:
-------------------------------------

No, the problem is that the app didn't have permissions to write the log files, including the internal
logging files. In case of permission issues, it seems reasonable to through exceptions to the user so they
don't spend hours pulling their hair out wondering why on earth nothing is being written. After all,
permission issues are something you solve once at the beginning and then everything is smooth afterwards.

> Exception mode during configuration
> -----------------------------------
>
>                 Key: LOG4NET-504
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-504
>             Project: Log4net
>          Issue Type: Wish
>          Components: Other
>            Reporter: Gregory Zak
>            Priority: Minor
>
> When getting started with log4net configuration for the first time, it would be extremely helpful to have
a mode where a call to one of the various {{.Configure()}} methods would throw exceptions as they were
encountered, rather than silently sailing past them / aborting.
> I'm currently absolutely stuck with [this
issue|http://stackoverflow.com/questions/35103249/log4net-not-writing-to-log-file] on
stackoverflow, and I've already tried all the expected suggestions (enable trace debugging, check for
(Continue reading)

Vadim Ivanou (JIRA | 3 Feb 16:00 2016
Picon

[jira] [Created] (LOG4NET-505) AdoNetAppender with Npgsql data provider

Vadim Ivanou created LOG4NET-505:
------------------------------------

             Summary: AdoNetAppender with Npgsql data provider
                 Key: LOG4NET-505
                 URL: https://issues.apache.org/jira/browse/LOG4NET-505
             Project: Log4net
          Issue Type: Bug
          Components: Appenders
    Affects Versions: 1.2.15
            Reporter: Vadim Ivanou

I'm trying to use AdoNetAppender with postgresql database and Npgsql data provider 3.0.x. Unfortunately
it throws an exception in SendBuffer method while executing dbCmd.Prepare(). I believe the reason for
that is that Npgsql requires all Parameters to be present in a command before calling Prepare method. I
created my own adapter that overrides SendBuffer method and populates sql command parameters before
Prepare and it worked fine.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Dominik Psenner (JIRA | 3 Feb 10:34 2016
Picon

[jira] [Commented] (LOG4NET-504) Exception mode during configuration


    [
https://issues.apache.org/jira/browse/LOG4NET-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130107#comment-15130107
] 

Dominik Psenner commented on LOG4NET-504:
-----------------------------------------

You can enable log4net's internal logging (see faq). Doesn't that help you figure out why things do not work
as expected? Further I've reduced the priority of this issue.

> Exception mode during configuration
> -----------------------------------
>
>                 Key: LOG4NET-504
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-504
>             Project: Log4net
>          Issue Type: Wish
>          Components: Other
>            Reporter: Gregory Zak
>            Priority: Minor
>
> When getting started with log4net configuration for the first time, it would be extremely helpful to have
a mode where a call to one of the various {{.Configure()}} methods would throw exceptions as they were
encountered, rather than silently sailing past them / aborting.
> I'm currently absolutely stuck with [this
issue|http://stackoverflow.com/questions/35103249/log4net-not-writing-to-log-file] on
stackoverflow, and I've already tried all the expected suggestions (enable trace debugging, check for
config errors explicitly, etc etc), but I'm still staring at a silent failure (the most frustrating kind
of failure) unable to make any progress.
(Continue reading)

Dominik Psenner (JIRA | 3 Feb 10:32 2016
Picon

[jira] [Updated] (LOG4NET-504) Exception mode during configuration


     [
https://issues.apache.org/jira/browse/LOG4NET-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Psenner updated LOG4NET-504:
------------------------------------
    Priority: Minor  (was: Blocker)

> Exception mode during configuration
> -----------------------------------
>
>                 Key: LOG4NET-504
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-504
>             Project: Log4net
>          Issue Type: Wish
>          Components: Other
>            Reporter: Gregory Zak
>            Priority: Minor
>
> When getting started with log4net configuration for the first time, it would be extremely helpful to have
a mode where a call to one of the various {{.Configure()}} methods would throw exceptions as they were
encountered, rather than silently sailing past them / aborting.
> I'm currently absolutely stuck with [this
issue|http://stackoverflow.com/questions/35103249/log4net-not-writing-to-log-file] on
stackoverflow, and I've already tried all the expected suggestions (enable trace debugging, check for
config errors explicitly, etc etc), but I'm still staring at a silent failure (the most frustrating kind
of failure) unable to make any progress.
> Don't make me switch to NLog guys!

--
(Continue reading)

Gregory Zak (JIRA | 2 Feb 00:26 2016
Picon

[jira] [Updated] (LOG4NET-504) Exception mode during configuration


     [
https://issues.apache.org/jira/browse/LOG4NET-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Zak updated LOG4NET-504:
--------------------------------
    Description: 
When getting started with log4net configuration for the first time, it would be extremely helpful to have a
mode where a call to one of the various {{.Configure()}} methods would throw exceptions as they were
encountered, rather than silently sailing past them / aborting.

I'm currently absolutely stuck with [this
issue|http://stackoverflow.com/questions/35103249/log4net-not-writing-to-log-file] on
stackoverflow, and I've already tried all the expected suggestions (enable trace debugging, check for
config errors explicitly, etc etc), but I'm still staring at a silent failure (the most frustrating kind
of failure) unable to make any progress.

Don't make me switch to NLog guys!

  was:
When getting started with log4net configuration for the first time, it would be extremely helpful to have a
mode where a call to one of the various .Configure() methods would throw exceptions as they were
encountered, rather than silently sailing past them / aborting.

I'm currently absolutely stuck with [this
issue|http://stackoverflow.com/questions/35103249/log4net-not-writing-to-log-file] on
stackoverflow, and I've already tried all the expected suggestions (enable trace debugging, check for
config errors explicitly, etc etc), but I'm still staring at a silent failure (the most frustrating kind
of failure) unable to make any progress.

(Continue reading)

Gregory Zak (JIRA | 2 Feb 00:26 2016
Picon

[jira] [Updated] (LOG4NET-504) Exception mode during configuration


     [
https://issues.apache.org/jira/browse/LOG4NET-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Zak updated LOG4NET-504:
--------------------------------
    Priority: Blocker  (was: Major)

> Exception mode during configuration
> -----------------------------------
>
>                 Key: LOG4NET-504
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-504
>             Project: Log4net
>          Issue Type: Wish
>          Components: Other
>            Reporter: Gregory Zak
>            Priority: Blocker
>
> When getting started with log4net configuration for the first time, it would be extremely helpful to have
a mode where a call to one of the various .Configure() methods would throw exceptions as they were
encountered, rather than silently sailing past them / aborting.
> I'm currently absolutely stuck with [this
issue|http://stackoverflow.com/questions/35103249/log4net-not-writing-to-log-file] on
stackoverflow, and I've already tried all the expected suggestions (enable trace debugging, check for
config errors explicitly, etc etc), but I'm still staring at a silent failure (the most frustrating kind
of failure) unable to make any progress.
> Don't make me switch to NLog guys!

--
(Continue reading)

Gregory Zak (JIRA | 2 Feb 00:25 2016
Picon

[jira] [Created] (LOG4NET-504) Exception mode during configuration

Gregory Zak created LOG4NET-504:
-----------------------------------

             Summary: Exception mode during configuration
                 Key: LOG4NET-504
                 URL: https://issues.apache.org/jira/browse/LOG4NET-504
             Project: Log4net
          Issue Type: Wish
          Components: Other
            Reporter: Gregory Zak

When getting started with log4net configuration for the first time, it would be extremely helpful to have a
mode where a call to one of the various .Configure() methods would throw exceptions as they were
encountered, rather than silently sailing past them / aborting.

I'm currently absolutely stuck with the following issue on stackoverflow, and I've already tried all the
expected suggestions (enable trace debugging, check for config errors explicitly, etc etc), but I'm
still staring at a silent failure (the most frustrating kind of failure) unable to make any progress.

Don't make me switch to NLog guys!

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Gregory Zak (JIRA | 2 Feb 00:25 2016
Picon

[jira] [Updated] (LOG4NET-504) Exception mode during configuration


     [
https://issues.apache.org/jira/browse/LOG4NET-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Zak updated LOG4NET-504:
--------------------------------
    Description: 
When getting started with log4net configuration for the first time, it would be extremely helpful to have a
mode where a call to one of the various .Configure() methods would throw exceptions as they were
encountered, rather than silently sailing past them / aborting.

I'm currently absolutely stuck with [this
issue|http://stackoverflow.com/questions/35103249/log4net-not-writing-to-log-file] on
stackoverflow, and I've already tried all the expected suggestions (enable trace debugging, check for
config errors explicitly, etc etc), but I'm still staring at a silent failure (the most frustrating kind
of failure) unable to make any progress.

Don't make me switch to NLog guys!

  was:
When getting started with log4net configuration for the first time, it would be extremely helpful to have a
mode where a call to one of the various .Configure() methods would throw exceptions as they were
encountered, rather than silently sailing past them / aborting.

I'm currently absolutely stuck with the following issue on stackoverflow, and I've already tried all the
expected suggestions (enable trace debugging, check for config errors explicitly, etc etc), but I'm
still staring at a silent failure (the most frustrating kind of failure) unable to make any progress.

Don't make me switch to NLog guys!

(Continue reading)


Gmane