[jira] Resolved: (LOG4NET-163) Tutorial examples on doc web site are broken links
[ https://issues.apache.org/jira/browse/LOG4NET-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Grabowski resolved LOG4NET-163. --- Resolution: Invalid " The following examples are only available in the log4net release download, not on-line. To obtain the examples download one of the log4net releases. " > Tutorial examples on doc web site are broken links > -- > > Key: LOG4NET-163 > URL: https://issues.apache.org/jira/browse/LOG4NET-163 > Project: Log4net > Issue Type: Bug > Components: Documentation >Reporter: Steve Hickman >Priority: Minor > Original Estimate: 4h > Remaining Estimate: 4h > > It appears that all the links to example projects on the log4net > examples/tutorial page > (http://logging.apache.org/log4net/release/example-apps.html) > are broken -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (LOG4NET-163) Tutorial examples on doc web site are broken links
Tutorial examples on doc web site are broken links -- Key: LOG4NET-163 URL: https://issues.apache.org/jira/browse/LOG4NET-163 Project: Log4net Issue Type: Bug Components: Documentation Reporter: Steve Hickman Priority: Minor It appears that all the links to example projects on the log4net examples/tutorial page (http://logging.apache.org/log4net/release/example-apps.html) are broken -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (LOG4NET-161) downloads abort aftger 4.8mn
[ https://issues.apache.org/jira/browse/LOG4NET-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stehan Meyn resolved LOG4NET-161. - Resolution: Fixed Tried it again just now and problem has disappeared. Not clear what caused it. > downloads abort aftger 4.8mn > > > Key: LOG4NET-161 > URL: https://issues.apache.org/jira/browse/LOG4NET-161 > Project: Log4net > Issue Type: Bug > Components: Other >Affects Versions: 1.2.9, 1.2.10 >Reporter: Stehan Meyn > > I tried to download both 1.2.9 and 1.2.10 and the resulting files are > 4,923,392 bytes long. (they are supposed to bemore than 7.65mB). > I checked using a different channels (i.e. local lan and broadband wireless) > and different applications (ie. Firefox, IE and wget) - always same result. > Since I can't think of other reasons why this should fail in this peculiar > way i wonder if the problem lies at the repository end. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (LOG4NET-162) It stops writing to the log file after certain threads are terminated and recreated.
[ https://issues.apache.org/jira/browse/LOG4NET-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609209#action_12609209 ] Ron Grabowski commented on LOG4NET-162: --- Have you enabled internal log4net debugging? What do those logs look like when the logging stops? > It stops writing to the log file after certain threads are terminated and > recreated. > > > Key: LOG4NET-162 > URL: https://issues.apache.org/jira/browse/LOG4NET-162 > Project: Log4net > Issue Type: Bug >Affects Versions: 1.2.10 > Environment: C#, .net framework 3.0, VS2005, Windows XP, intel > pentium 4, 3 GHz, 1 GB RAM >Reporter: Amjad Khoja >Priority: Blocker > Original Estimate: 0.17h > Remaining Estimate: 0.17h > > We are using log4net in an windows service application, which spans number of > threads. Logging works perfect until we try to refresh the cache where we > terminate the threads and recreate it and in between the logging stops. When > debug we see that it goes to the logger print message statement and there is > no error but nothing gets written to the log file. > This behaviour is undpredictable as sometimes it works fine when it goes > through the complete refresh method. > Settings of Log4net in app.config is as follow. > > type="log4net.Appender.RollingFileAppender"> > > > > > > > > /> > > > > > > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (LOG4NET-162) It stops writing to the log file after certain threads are terminated and recreated.
[ https://issues.apache.org/jira/browse/LOG4NET-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Grabowski updated LOG4NET-162: -- Priority: Critical (was: Blocker) > It stops writing to the log file after certain threads are terminated and > recreated. > > > Key: LOG4NET-162 > URL: https://issues.apache.org/jira/browse/LOG4NET-162 > Project: Log4net > Issue Type: Bug >Affects Versions: 1.2.10 > Environment: C#, .net framework 3.0, VS2005, Windows XP, intel > pentium 4, 3 GHz, 1 GB RAM >Reporter: Amjad Khoja >Priority: Critical > Original Estimate: 0.17h > Remaining Estimate: 0.17h > > We are using log4net in an windows service application, which spans number of > threads. Logging works perfect until we try to refresh the cache where we > terminate the threads and recreate it and in between the logging stops. When > debug we see that it goes to the logger print message statement and there is > no error but nothing gets written to the log file. > This behaviour is undpredictable as sometimes it works fine when it goes > through the complete refresh method. > Settings of Log4net in app.config is as follow. > > type="log4net.Appender.RollingFileAppender"> > > > > > > > > /> > > > > > > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (LOG4NET-161) downloads abort aftger 4.8mn
[ https://issues.apache.org/jira/browse/LOG4NET-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609204#action_12609204 ] Ron Grabowski commented on LOG4NET-161: --- All three of these tickets are for the same thing: LOG4NET-159 LOG4NET-160 LOG4NET-161 You're going to have to post more information like time of download, the mirror the file was downloaded from, etc. I was able to download the file ok on 6/30/2008 from 192.87.106.226: C:\>wget http://archive.apache.org/dist/incubator/log4net/1.2.10/incubating-log4net-1.2.10.zip --07:37:03-- http://archive.apache.org/dist/incubator/log4net/1.2.10/incubating-log4net-1.2.10.zip => `incubating-log4net-1.2.10.zip' Resolving archive.apache.org... 192.87.106.226 Connecting to archive.apache.org|192.87.106.226|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 8,203,576 (7.8M) [application/zip] 100%[>] 8,203,576442.76K/sETA 00:00 07:37:22 (436.94 KB/s) - `incubating-log4net-1.2.10.zip' saved [8203576/8203576] > downloads abort aftger 4.8mn > > > Key: LOG4NET-161 > URL: https://issues.apache.org/jira/browse/LOG4NET-161 > Project: Log4net > Issue Type: Bug > Components: Other >Affects Versions: 1.2.9, 1.2.10 >Reporter: Stehan Meyn > > I tried to download both 1.2.9 and 1.2.10 and the resulting files are > 4,923,392 bytes long. (they are supposed to bemore than 7.65mB). > I checked using a different channels (i.e. local lan and broadband wireless) > and different applications (ie. Firefox, IE and wget) - always same result. > Since I can't think of other reasons why this should fail in this peculiar > way i wonder if the problem lies at the repository end. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (LOG4NET-162) It stops writing to the log file after certain threads are terminated and recreated.
It stops writing to the log file after certain threads are terminated and recreated. Key: LOG4NET-162 URL: https://issues.apache.org/jira/browse/LOG4NET-162 Project: Log4net Issue Type: Bug Affects Versions: 1.2.10 Environment: C#, .net framework 3.0, VS2005, Windows XP, intel pentium 4, 3 GHz, 1 GB RAM Reporter: Amjad Khoja Priority: Blocker We are using log4net in an windows service application, which spans number of threads. Logging works perfect until we try to refresh the cache where we terminate the threads and recreate it and in between the logging stops. When debug we see that it goes to the logger print message statement and there is no error but nothing gets written to the log file. This behaviour is undpredictable as sometimes it works fine when it goes through the complete refresh method. Settings of Log4net in app.config is as follow. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
