https://bz.apache.org/bugzilla/show_bug.cgi?id=2
Tysonrudgey changed:
What|Removed |Added
CC||brend...@bbtechltd.com
--- Comment #2 from
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
https://bz.apache.org/bugzilla/show_bug.cgi?id=58710
--- Comment #1 from Ralph Goers ---
Log4j 1.x has reached end-of-life. Please see
https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces.
--
You are receiving this mail because:
You are the assignee for the bug
https://bz.apache.org/bugzilla/show_bug.cgi?id=58710
Bug ID: 58710
Summary: Errors in JavaDoc for
org.apache.log4j.Category.shutdown()
Product: Log4j
Version: unspecified
Hardware: All
OS: All
https://bz.apache.org/bugzilla/show_bug.cgi?id=58709
Bug ID: 58709
Summary: Possibly incorrect code sample
Product: Log4j
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
https://bz.apache.org/bugzilla/show_bug.cgi?id=58708
Bug ID: 58708
Summary: Double negation in the Short Introduction
Product: Log4j
Version: unspecified
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
https://bz.apache.org/bugzilla/show_bug.cgi?id=50486
--- Comment #61 from mar...@frightanic.com ---
(In reply to Gary Gregory from comment #60)
> Why not use the latest?
Because you probably don't want the test yourself whether the leak still exists
if you could simply check the issue li
https://bz.apache.org/bugzilla/show_bug.cgi?id=50486
--- Comment #60 from Gary Gregory ---
Why not use the latest?
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: log4j-dev
https://bz.apache.org/bugzilla/show_bug.cgi?id=50486
--- Comment #59 from Jay Khimani ---
Anybody knows which slf4j version I should be picking up in order to have this
fix? Currently I'm using 1.7.5
Thanks,
- Jay
--
You are receiving this mail because:
You are the assignee for th
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
https://bz.apache.org/bugzilla/show_bug.cgi?id=58470
--- Comment #1 from Gary Gregory ---
This is the bug tracking system for Log4j version 1 which is EOL.
For version 2, please use https://issues.apache.org/jira/browse/log4j2/
--
You are receiving this mail because:
You are the assignee for
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
https://bz.apache.org/bugzilla/show_bug.cgi?id=58470
ahmed elattar changed:
What|Removed |Added
CC||a.at...@egyptianbanks.net
https://bz.apache.org/bugzilla/show_bug.cgi?id=58470
Bug ID: 58470
Summary: xml message
Product: Log4j
Version: unspecified
Hardware: PC
Status: NEW
Severity: major
Priority: P2
Component: Other
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
https://bz.apache.org/bugzilla/show_bug.cgi?id=57002
Herve changed:
What|Removed |Added
Blocks||57062
--
You are receiving this mail because
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
https://bz.apache.org/bugzilla/show_bug.cgi?id=57714
--- Comment #19 from Gary Gregory ---
Please see https://logging.apache.org/log4j/2.x/manual/migration.html
--
You are receiving this mail because:
You are the assignee for the bug
https://bz.apache.org/bugzilla/show_bug.cgi?id=57714
--- Comment #18 from Aakash ---
Hi Ralph
I have replaced the existing log4j 1.2.16 jar with log4j1.2-api jar version
2.3.Am I replacing with the right jar for using bridge for migrating from
log4j1.x to log4j 2. Could you please help
https://bz.apache.org/bugzilla/show_bug.cgi?id=57714
--- Comment #17 from Ralph Goers ---
*** Bug 58218 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug
https://bz.apache.org/bugzilla/show_bug.cgi?id=58218
Ralph Goers changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://bz.apache.org/bugzilla/show_bug.cgi?id=58218
--- Comment #1 from Aakash ---
Can someone help me for the below defect please.
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe
https://bz.apache.org/bugzilla/show_bug.cgi?id=57714
--- Comment #16 from Aakash ---
Stable version for migrating using logging Bridge 1.x
--
You are receiving this mail because:
You are the assignee for the bug.
-
To
https://bz.apache.org/bugzilla/show_bug.cgi?id=57714
--- Comment #15 from Aakash ---
Many Thanks Ralph.
Currently I am using log4j version 1.2.16 and slf4j version 1.6.1. Which is the
stable version that can be used to resolve this issue.
--
You are receiving this mail because:
You are the
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
https://bz.apache.org/bugzilla/show_bug.cgi?id=57714
--- Comment #14 from Ralph Goers ---
Your stack trace shows you are calling Log4j1 via the SLF4J API. You can use
Log4J 2's sLF4J binding instead of the Binding to Log4j 1 provided by the SLF4J
project.
Log4j 2 does not have this issue
https://bz.apache.org/bugzilla/show_bug.cgi?id=57714
--- Comment #13 from Aakash ---
As stated in the reference link provided by you, we have two solutions for
upgrading lo4j 1.x to log4j2.At this point of time we wont be able to upgrade
to log4j2 completely as this application deals with live
https://bz.apache.org/bugzilla/show_bug.cgi?id=57714
--- Comment #12 from Aakash ---
Thanks a lot Ralph. Appreciate your quick response.
--
You are receiving this mail because:
You are the assignee for the bug.
-
To
https://bz.apache.org/bugzilla/show_bug.cgi?id=57714
--- Comment #11 from Ralph Goers ---
There is no temporary fix for this issue and is one of the reasons Log4j 2 came
about. The only fix is to upgrade to Log4j 2.
--
You are receiving this mail because:
You are the assignee for the bug
https://bz.apache.org/bugzilla/show_bug.cgi?id=57714
--- Comment #10 from Aakash ---
Hi Gary,
Could you please help with a temporary solution for resolving this issue. Also
will upgrading log4j 1.x to log4j2 resolve this issue?
--
You are receiving this mail because:
You are the assignee for
https://bz.apache.org/bugzilla/show_bug.cgi?id=57714
--- Comment #9 from Aakash ---
Could you please help with a temporary solution for this. As this is creating
issue on production server with business impact.
Thanks in advance
--
You are receiving this mail because:
You are the assignee for
https://bz.apache.org/bugzilla/show_bug.cgi?id=57714
--- Comment #8 from Gary Gregory ---
FYI:
https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
--
You are receiving this mail because:
You are the assignee for the bug
https://bz.apache.org/bugzilla/show_bug.cgi?id=58218
Aakash changed:
What|Removed |Added
Severity|normal |blocker
Priority|P2
https://bz.apache.org/bugzilla/show_bug.cgi?id=58218
Bug ID: 58218
Summary: Blocked trying to get lock:
org/apache/log4j/spi/RootLogger
Product: Log4j
Version: unspecified
Hardware: Other
OS: Linux
https://bz.apache.org/bugzilla/show_bug.cgi?id=57714
Aakash changed:
What|Removed |Added
Version|1.2.17 |unspecified
CC
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
https://bz.apache.org/bugzilla/show_bug.cgi?id=58139
Gary Gregory changed:
What|Removed |Added
OS||All
Resolution
https://bz.apache.org/bugzilla/show_bug.cgi?id=58139
Jonathan changed:
What|Removed |Added
Severity|normal |major
OS
https://bz.apache.org/bugzilla/show_bug.cgi?id=58139
Bug ID: 58139
Summary: Log4J 2.3.0 -
org.apache.logging.log4j.core.osgi.BundleContextSelect
or - ClassNotFoundException
Product: Log4j
Version: unspecified
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
https://bz.apache.org/bugzilla/show_bug.cgi?id=51047
--- Comment #16 from Gary Gregory ---
(In reply to Jess Holle from comment #13)
> (In reply to Gary Gregory from comment #12)
> > You patch uses Java 5 and Log4j 1 is on Java 1.4, so that's a no go anyway
> > :-(
>
>
https://bz.apache.org/bugzilla/show_bug.cgi?id=51047
--- Comment #15 from Jess Holle ---
(In reply to mirabilos from comment #14)
> We’re on Java 7, and Operations will move everything to Java 8 Really Soon
> Now™ because of the security support situation (using Debian’s OpenJDK
> ex
https://bz.apache.org/bugzilla/show_bug.cgi?id=51047
--- Comment #14 from mirabilos ---
We’re on Java 7, and Operations will move everything to Java 8 Really Soon Now™
because of the security support situation (using Debian’s OpenJDK exclusively
helps, but better is better).
--
You are
https://bz.apache.org/bugzilla/show_bug.cgi?id=51047
--- Comment #13 from Jess Holle ---
(In reply to Gary Gregory from comment #12)
> You patch uses Java 5 and Log4j 1 is on Java 1.4, so that's a no go anyway
> :-(
I've long since given up and been building and relying upo
https://bz.apache.org/bugzilla/show_bug.cgi?id=51047
--- Comment #12 from Gary Gregory ---
You patch uses Java 5 and Log4j 1 is on Java 1.4, so that's a no go anyway :-(
--
You are receiving this mail because:
You are the assignee for th
https://bz.apache.org/bugzilla/show_bug.cgi?id=51047
--- Comment #11 from mirabilos ---
Hm, that doesn’t work for us – we don’t even use it explicitly, but things like
WildFly and Liferay do.
But we can just exchange the one .class file in their JARs locally, and we can
have the patch here for
https://bz.apache.org/bugzilla/show_bug.cgi?id=51047
--- Comment #10 from Gary Gregory ---
Hi,
At this point I would not put too much hope in seeing a new 1.2.x release. We
are not actively maintaining it. I would migrate to v2 and use the 1.2
compatibility layer to get started.
--
You are
https://bz.apache.org/bugzilla/show_bug.cgi?id=51047
mirabilos changed:
What|Removed |Added
Attachment #26871|0 |1
is obsolete
https://bz.apache.org/bugzilla/show_bug.cgi?id=58062
--- Comment #2 from Gary Gregory ---
Note that v1 is not actively maintained. I strongly encourage you to migrate to
v2, which includes a v1.2 compatibility layer.
--
You are receiving this mail because:
You are the assignee for the bug
https://bz.apache.org/bugzilla/show_bug.cgi?id=58062
Tang Xinye changed:
What|Removed |Added
URL||https://github.com/apache/l
https://bz.apache.org/bugzilla/show_bug.cgi?id=58062
Tang Xinye changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bz.apache.org/bugzilla/show_bug.cgi?id=57036
Gary Gregory changed:
What|Removed |Added
Resolution|--- |FIXED
OS
https://bz.apache.org/bugzilla/show_bug.cgi?id=47588
Crystal changed:
What|Removed |Added
CC||jrs.wife...@gmail.com
--- Comment #2 from
https://bz.apache.org/bugzilla/show_bug.cgi?id=48142
Crystal changed:
What|Removed |Added
CC||jrs.wife...@gmail.com
--
You are receiving
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
https://bz.apache.org/bugzilla/show_bug.cgi?id=58062
Tang Xinye changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bz.apache.org/bugzilla/show_bug.cgi?id=58062
Bug ID: 58062
Summary: Close IO Streams in finally statement
Product: Log4j
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: critical
https://bz.apache.org/bugzilla/show_bug.cgi?id=58035
--- Comment #1 from Gary Gregory ---
What happens with 1.2.17? Otherwise try 2.x with the 1.2 compatibility jar. 1.2
is not maintained atm.
--
You are receiving this mail because:
You are the assignee for the bug
https://bz.apache.org/bugzilla/show_bug.cgi?id=49354
Pablo <12...@hotmail.es> changed:
What|Removed |Added
Blocks||58035
--
You are rec
https://bz.apache.org/bugzilla/show_bug.cgi?id=58035
Bug ID: 58035
Summary: XMLLayout writes illegal characters to XML file
Product: Log4j
Version: 1.2
Hardware: PC
OS: Windows XP
Status: NEW
Severity
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
https://bz.apache.org/bugzilla/show_bug.cgi?id=58003
bf...@thoughtworks.com changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status
https://bz.apache.org/bugzilla/show_bug.cgi?id=58003
--- Comment #2 from Gary Gregory ---
Also note that you should use Log4j 2 if possible since it is the version being
actively developed and maintained, not 1.2.
--
You are receiving this mail because:
You are the assignee for the bug.
You
https://bz.apache.org/bugzilla/show_bug.cgi?id=58003
--- Comment #1 from Gary Gregory ---
This example does not define a package for its class MyApp, IOW there is no
package statement.
Loggger.getLogger(Class) simply calls: LogManager.getLogger(clazz.getName())
So the only way you are getting
https://bz.apache.org/bugzilla/show_bug.cgi?id=58003
Bug ID: 58003
Summary: Official website give a wrong example
Product: Log4j
Version: 1.2.17
Hardware: Macintosh
Status: NEW
Severity: major
Priority: P2
https://bz.apache.org/bugzilla/show_bug.cgi?id=58003
bf...@thoughtworks.com changed:
What|Removed |Added
OS||All
Severity|major
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
https://bz.apache.org/bugzilla/show_bug.cgi?id=57891
Bug ID: 57891
Summary: UDPAppender stops to send if destination port is
unreachable
Product: Log4j
Version: 1.2.17
Hardware: Other
OS: Linux
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
https://bz.apache.org/bugzilla/show_bug.cgi?id=57881
Bug ID: 57881
Summary: Additional step required to build project
Product: Log4j
Version: unspecified
Hardware: PC
Status: NEW
Severity: minor
Priority: P2
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
https://bz.apache.org/bugzilla/show_bug.cgi?id=41214
--- Comment #58 from Gary Gregory ---
I'm afraid you will not get much more than our stock answer here: Our energy is
focused on Log4j 2, and in particular into getting our next release, 2.3, out
the door, hopefully in a week or two. F
https://bz.apache.org/bugzilla/show_bug.cgi?id=41214
--- Comment #57 from Gustavo ---
Hi people. I have the same issue with log4j 1.2.17. Any update on this? Is
there any ETA
Thanks!
--
You are receiving this mail because:
You are the assignee for the bug
1 - 100 of 4844 matches
Mail list logo
