bugzilla | 1 Mar 01:05 2008
Picon

[Bug 43295] Zeroconf always uses default port (4560)

https://issues.apache.org/bugzilla/show_bug.cgi?id=43295

--- Comment #9 from Lilianne E. Blaze <lilianne_blaze <at> tlen.pl>  2008-02-29 16:05:00 ---
Are there any news and/or ETA on this?

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 1 Mar 03:01 2008
Picon

[Bug 43874] SocketHubAppender should expose actual port in use to extending classes

https://issues.apache.org/bugzilla/show_bug.cgi?id=43874

Lilianne E. Blaze <lilianne_blaze <at> tlen.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lilianne_blaze <at> tlen.pl

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 1 Mar 03:02 2008
Picon

[Bug 43295] Zeroconf always uses default port (4560)

https://issues.apache.org/bugzilla/show_bug.cgi?id=43295

Lilianne E. Blaze <lilianne_blaze <at> tlen.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lilianne_blaze <at> tlen.pl

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
carnold | 2 Mar 11:38 2008
Picon

[GUMP <at> vmgump]: Project logging-log4j-12-tests (in module logging-log4j-12) failed

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at general <at> gump.apache.org.

Project logging-log4j-12-tests has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 3 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - logging-log4j-12-tests :  Fast and flexible logging package for Java

Full details are available at:
    http://vmgump.apache.org/gump/public/logging-log4j-12/logging-log4j-12-tests/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -INFO- Made directory [/srv/gump/public/workspace/logging-log4j-12/tests/classes]
 -INFO- Failed with reason build failed

The following work was performed:
http://vmgump.apache.org/gump/public/logging-log4j-12/logging-log4j-12-tests/gump_work/build_logging-log4j-12_logging-log4j-12-tests.html
Work Name: build_logging-log4j-12_logging-log4j-12-tests (Type: Build)
Work ended in a state of : Failed
Elapsed: 38 secs
Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java -Djava.awt.headless=true
-Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar
org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml
(Continue reading)

bugzilla | 3 Mar 08:08 2008
Picon

Bug report for Log4j [2008/03/02]

+---------------------------------------------------------------------------+
| Bugzilla Bug ID                                                           |
|     +---------------------------------------------------------------------+
|     | Status: UNC=Unconfirmed NEW=New         ASS=Assigned                |
|     |         OPN=Reopened    VER=Verified    (Skipped Closed/Resolved)   |
|     |   +-----------------------------------------------------------------+
|     |   | Severity: BLK=Blocker CRI=Critical  REG=Regression  MAJ=Major   |
|     |   |           MIN=Minor   NOR=Normal    ENH=Enhancement TRV=Trivial |
|     |   |   +-------------------------------------------------------------+
|     |   |   | Date Posted                                                 |
|     |   |   |          +--------------------------------------------------+
|     |   |   |          | Description                                      |
|     |   |   |          |                                                  |
|13099|Opn|Nor|2002-09-27|DOMConfigurator ignores category factory setting  |
|17887|Opn|Maj|2003-03-11|RollingFileAppender does not work for 10 threads  |
|20395|New|Enh|2003-06-01|PreparedStatementAppender Enhancement             |
|22894|Opn|Nor|2003-09-02|Single backslash not accepted in File param value |
|22934|Opn|Nor|2003-09-04|org.apache.log4j.jmx is not compatible with JMX 1.|
|23329|Ass|Maj|2003-09-22|<logger> element in XML config should support reso|
|25355|New|Enh|2003-12-09|allow to require "TLS/SSL only" for outgoing mails|
|25747|New|Enh|2003-12-24|more explanations when hitting "WARN No appenders |
|26084|New|Nor|2004-01-13|Log Event detail panel does not show special chara|
|27363|New|Enh|2004-03-02|JNI based SyslogAppender                          |
|27367|New|Enh|2004-03-02|NetSendAppender                                   |
|28647|Ass|Enh|2004-04-28|Add "Flush on Level" capability to FileAppender   |
|29244|Inf|Nor|2004-05-27|Preserve XML content in log messages when using XM|
|29304|New|Nor|2004-05-30|Starting XMLSocketAppender from config file       |
|29305|New|Nor|2004-05-30|Chainsaw doesn't see locationinfo from XMLSocketRe|
|29735|New|Nor|2004-06-22|Receiver list display error  when receiver has no |
|30055|New|Nor|2004-07-12|Problem with registering Appenders with the same n|
(Continue reading)

bugzilla | 4 Mar 14:19 2008
Picon

DO NOT REPLY [Bug 44526] New: segmentation fault occuring when PropertyConfigurator.configure( propertyFile) function is called

https://issues.apache.org/bugzilla/show_bug.cgi?id=44526

           Summary: segmentation fault occuring when
                    PropertyConfigurator.configure(propertyFile) function is
                    called
           Product: Log4j
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Configurator
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: anil_t_n <at> yahoo.co.in

i am using the log4j(version unknown but size = 378778) with Red Hat Enterprise
Linux ES release 4 (Nahant Update 5) . here when my application calls
PropertyConfigurator.configure(propertyFile); function , a segmentation fault
is occuring . 
The same application when run on hp_UX does not give any error .
Does this behaviour have anything to do with configuration or is log4j having
o/s dependency? 
Kindly help.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
(Continue reading)

bugzilla | 6 Mar 21:15 2008
Picon

DO NOT REPLY [Bug 44551] New: SocketHubAppender in the 1.2. 16 does not support a scroll back buffer or application property

https://issues.apache.org/bugzilla/show_bug.cgi?id=44551

           Summary: SocketHubAppender in the 1.2.16 does not support a
                    scroll back buffer or application property
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Appender
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: jason.tholstrup <at> gmail.com

Created an attachment (id=21644)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=21644)
Patch to fix the issues listed in the description

Part 1)
The 1.3 version of SocketHubAppender uses a cyclic buffer to store the last X
log messages that are delivered to the client on connection so that they can
have some of the recently logged events. This was never back ported to the
1.2.X branch.

Part 2)
The 1.2.X version of SocketAppender supports an application property which
chainsaw can read to specify which application the log is for. 
SocketHubAppender should also support this functionality.

(Continue reading)

bugzilla | 6 Mar 21:16 2008
Picon

DO NOT REPLY [Bug 44551] SocketHubAppender in the 1.2. 16 does not support a scroll back buffer or application property

https://issues.apache.org/bugzilla/show_bug.cgi?id=44551

Jason Tholstrup <jason.tholstrup <at> gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jason.tholstrup <at> gmail.com

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 7 Mar 03:49 2008
Picon

DO NOT REPLY [Bug 44551] SocketHubAppender in the 1.2. 16 does not support a scroll back buffer or application property

https://issues.apache.org/bugzilla/show_bug.cgi?id=44551

--- Comment #1 from Paul Smith <psmith <at> apache.org>  2008-03-06 18:49:05 PST ---
This patch looks good to me, I can't see any reason not to apply it.

Scott?  any final comments?

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 7 Mar 05:53 2008
Picon

DO NOT REPLY [Bug 44551] SocketHubAppender in the 1.2. 16 does not support a scroll back buffer or application property

https://issues.apache.org/bugzilla/show_bug.cgi?id=44551

--- Comment #2 from Scott Deboy <sdeboy <at> iname.com>  2008-03-06 20:53:21 PST ---
Looks good to me as well.

Thanks for the contribution Jason

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Gmane