svn commit: r1649999 - in /incubator/log4cxx/trunk/src/main/cpp: charsetencoder.cpp fileappender.cpp odbcappender.cpp properties.cpp simpledateformat.cpp
Author: chand
Date: Wed Jan 7 06:52:03 2015
New Revision: 164
URL: http://svn.apache.org/r164
Log:
LOGCXX-434 : The attached patch fixes some cppcheck warnings. Credits to
'Christian Ehrlicher
Modified:
incubator/log4cxx/trunk/src/main/cpp/charsetencoder.cpp
incubator/log4cxx/trunk/src/main/cpp/fileappender.cpp
incubator/log4cxx/trunk/src/main/cpp/odbcappender.cpp
incubator/log4cxx/trunk/src/main/cpp/properties.cpp
incubator/log4cxx/trunk/src/main/cpp/simpledateformat.cpp
Modified: incubator/log4cxx/trunk/src/main/cpp/charsetencoder.cpp
URL:
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/main/cpp/charsetencoder.cpp?rev=164&r1=1649998&r2=164&view=diff
==
--- incubator/log4cxx/trunk/src/main/cpp/charsetencoder.cpp (original)
+++ incubator/log4cxx/trunk/src/main/cpp/charsetencoder.cpp Wed Jan 7 06:52:03
2015
@@ -400,7 +400,7 @@ public:
Transcoder::decode(encoding, ename);
try {
encoder = CharsetEncoder::getEncoder(ename);
-} catch(IllegalArgumentException ex) {
+} catch(IllegalArgumentException &ex) {
encoder = new USASCIICharsetEncoder();
}
}
Modified: incubator/log4cxx/trunk/src/main/cpp/fileappender.cpp
URL:
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/main/cpp/fileappender.cpp?rev=164&r1=1649998&r2=164&view=diff
==
--- incubator/log4cxx/trunk/src/main/cpp/fileappender.cpp (original)
+++ incubator/log4cxx/trunk/src/main/cpp/fileappender.cpp Wed Jan 7 06:52:03
2015
@@ -275,10 +275,10 @@ void FileAppender::setFile(
if(!parentDir.exists(p) && parentDir.mkdirs(p)) {
outStream = new FileOutputStream(filename, append1);
} else {
- throw ex;
+ throw;
}
} else {
-throw ex;
+throw;
}
}
Modified: incubator/log4cxx/trunk/src/main/cpp/odbcappender.cpp
URL:
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/main/cpp/odbcappender.cpp?rev=164&r1=1649998&r2=164&view=diff
==
--- incubator/log4cxx/trunk/src/main/cpp/odbcappender.cpp (original)
+++ incubator/log4cxx/trunk/src/main/cpp/odbcappender.cpp Wed Jan 7 06:52:03
2015
@@ -183,7 +183,7 @@ void ODBCAppender::execute(const LogStri
SQLFreeHandle(SQL_HANDLE_STMT, stmt);
}
- throw e;
+ throw;
}
SQLFreeHandle(SQL_HANDLE_STMT, stmt);
closeConnection(con);
Modified: incubator/log4cxx/trunk/src/main/cpp/properties.cpp
URL:
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/main/cpp/properties.cpp?rev=164&r1=1649998&r2=164&view=diff
==
--- incubator/log4cxx/trunk/src/main/cpp/properties.cpp (original)
+++ incubator/log4cxx/trunk/src/main/cpp/properties.cpp Wed Jan 7 06:52:03 2015
@@ -296,7 +296,7 @@ public:
}
protected:
-bool get(LogString& in, logchar& c)
+static bool get(LogString& in, logchar& c)
{
if (in.empty()) {
c = 0;
Modified: incubator/log4cxx/trunk/src/main/cpp/simpledateformat.cpp
URL:
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/main/cpp/simpledateformat.cpp?rev=164&r1=1649998&r2=164&view=diff
==
--- incubator/log4cxx/trunk/src/main/cpp/simpledateformat.cpp (original)
+++ incubator/log4cxx/trunk/src/main/cpp/simpledateformat.cpp Wed Jan 7
06:52:03 2015
@@ -232,7 +232,6 @@ public:
private:
size_t width;
- char zeroDigit;
};
@@ -438,7 +437,7 @@ private:
class HourToken : public NumericToken
{
public:
- HourToken( int width1, int /* offset1 */ ) : NumericToken( width1 )
+ HourToken( int width1, int /* offset1 */ ) : NumericToken( width1 ), offset(
0 )
{
}
svn commit: r1655676 - in /incubator/log4cxx/trunk/src/main: cpp/syslogappender.cpp cpp/syslogwriter.cpp include/log4cxx/helpers/syslogwriter.h include/log4cxx/net/syslogappender.h
Author: chand
Date: Thu Jan 29 14:25:00 2015
New Revision: 1655676
URL: http://svn.apache.org/r1655676
Log:
LOGCXX-442:Using non standard ports with syslog.Credits to 'Ulrik'.
Modified:
incubator/log4cxx/trunk/src/main/cpp/syslogappender.cpp
incubator/log4cxx/trunk/src/main/cpp/syslogwriter.cpp
incubator/log4cxx/trunk/src/main/include/log4cxx/helpers/syslogwriter.h
incubator/log4cxx/trunk/src/main/include/log4cxx/net/syslogappender.h
Modified: incubator/log4cxx/trunk/src/main/cpp/syslogappender.cpp
URL:
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/main/cpp/syslogappender.cpp?rev=1655676&r1=1655675&r2=1655676&view=diff
==
--- incubator/log4cxx/trunk/src/main/cpp/syslogappender.cpp (original)
+++ incubator/log4cxx/trunk/src/main/cpp/syslogappender.cpp Thu Jan 29 14:25:00
2015
@@ -323,6 +323,17 @@ void SyslogAppender::setSyslogHost(const
delete this->sw;
this->sw = 0;
}
+LogString slHost = syslogHost1;
+int slHostPort = -1;
+
+LogString::size_type colonPos = 0;
+colonPos = slHost.rfind(':');
+if (colonPos != LogString::npos)
+{
+slHostPort = StringHelper::toInt(slHost.substr(colonPos+1));
+// Erase the :port part of the host name
+slHost.erase( colonPos );
+}
// On the local host, we can directly use the system function 'syslog'
// if it is available (cf. append)
@@ -330,9 +341,11 @@ void SyslogAppender::setSyslogHost(const
if (syslogHost1 != LOG4CXX_STR("localhost") && syslogHost1 !=
LOG4CXX_STR("127.0.0.1")
&& !syslogHost1.empty())
#endif
-this->sw = new SyslogWriter(syslogHost1);
+if (slHostPort >= 0) this->sw = new SyslogWriter(slHost,
slHostPort);
+else this->sw = new SyslogWriter(slHost);
-this->syslogHost = syslogHost1;
+this->syslogHost = slHost;
+this->syslogHostPort = slHostPort;
}
Modified: incubator/log4cxx/trunk/src/main/cpp/syslogwriter.cpp
URL:
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/main/cpp/syslogwriter.cpp?rev=1655676&r1=1655675&r2=1655676&view=diff
==
--- incubator/log4cxx/trunk/src/main/cpp/syslogwriter.cpp (original)
+++ incubator/log4cxx/trunk/src/main/cpp/syslogwriter.cpp Thu Jan 29 14:25:00
2015
@@ -26,13 +26,11 @@
#include
#include
-#define SYSLOG_PORT 514
-
using namespace log4cxx;
using namespace log4cxx::helpers;
-SyslogWriter::SyslogWriter(const LogString& syslogHost1)
-: syslogHost(syslogHost1)
+SyslogWriter::SyslogWriter(const LogString& syslogHost1, int syslogHostPort1)
+: syslogHost(syslogHost1), syslogHostPort(syslogHostPort1)
{
try
{
@@ -61,7 +59,7 @@ void SyslogWriter::write(const LogString
DatagramPacketPtr packet(
new DatagramPacket((void*) data.data(), data.length(),
- address, SYSLOG_PORT));
+ address, syslogHostPort));
ds->send(packet);
}
Modified:
incubator/log4cxx/trunk/src/main/include/log4cxx/helpers/syslogwriter.h
URL:
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/main/include/log4cxx/helpers/syslogwriter.h?rev=1655676&r1=1655675&r2=1655676&view=diff
==
--- incubator/log4cxx/trunk/src/main/include/log4cxx/helpers/syslogwriter.h
(original)
+++ incubator/log4cxx/trunk/src/main/include/log4cxx/helpers/syslogwriter.h Thu
Jan 29 14:25:00 2015
@@ -34,11 +34,13 @@
class LOG4CXX_EXPORT SyslogWriter
{
public:
-SyslogWriter(const LogString& syslogHost);
+#define SYSLOG_PORT 514
+SyslogWriter(const LogString& syslogHost, int
syslogHostPort = SYSLOG_PORT);
void write(const LogString& string);
private:
LogString syslogHost;
+int syslogHostPort;
InetAddressPtr address;
DatagramSocketPtr ds;
};
Modified: incubator/log4cxx/trunk/src/main/include/log4cxx/net/syslogappender.h
URL:
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/main/include/log4cxx/net/syslogappender.h?rev=1655676&r1=1655675&r2=1655676&view=diff
==
--- incubator/log4cxx/trunk/src/main/include/log4cxx/net/syslogappender.h
(original)
+++ incubator/log4cxx/trunk/src/main/include/log4cxx/net/syslogappender.h Thu
Jan 29 14:25:00 2015
@@ -129,6 +129,7 @@
Re: Commit access to log4cxx
hi roland, you can publish patch in the dev mailing list. so a commiter can review it and commit to repo. On Fri, Mar 9, 2012 at 12:01 AM, Roland wrote: > Hi.. > > How to get commit access to log4cxx project? > > There is a really annoying Makefile problem. > > There is a patch but no-one has pushed it to SVN/git. > > If no one else will, I'd like to do it. > > Thank you, > Roland Uuesoo > -- *Chand Priyankara* |(094) 773-361566 |ch...@engineering.com |www.blog.friendly.com [image: Facebook] <http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger]<http://chandpriyankara.blogspot.com/> [image: Google Plus] <http://plus.google.com/104246340732624023499> <http://www.iucnredlist.org/amazing-species> Please consider your environmental responsibility. Before printing this e-mail message, ask yourself whether you really need a hard copy. * *
Re: Is log4cxx still alive?
hi all, i think its better to continue with https://github.com/apache/log4cxx repo. Since it has change log, we can go ahead with committing bug fixes. But i wonder which has the latest code. On Fri, Mar 9, 2012 at 2:59 PM, Roland wrote: > Hi. > > I appreciate your try to make a fork but there are a few things on my mind > before I'd commit there. > > 1. There already exists a project named log4cpp > http://log4cpp.sourceforge.**net/ <http://log4cpp.sourceforge.net/> > so the name is a bit misleading > > 2. You did not include old changelog, which is available at > https://github.com/apache/**log4cxx <https://github.com/apache/log4cxx> > > > A thing about log4net > > It seems less cross-plaform than log4cxx, and seems to be harder to use on > an embedded device. > > > Since ASF members do not want to maintain this software, like is visible > from here.. > https://issues.apache.org/**jira/browse/LOGCXX-385<https://issues.apache.org/jira/browse/LOGCXX-385>(a > patch to fix a issue) > > I think the best idea would be to create a fork of that > https://github.com/apache/**log4cxx <https://github.com/apache/log4cxx>GIT > repository. > > I think old commit history with the bugs that were fixed is necessary for > a forked project. > > Thanks, > Roland > -- *Chand Priyankara* |(094) 773-361566 |ch...@engineering.com |www.blog.friendly.com [image: Facebook] <http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger]<http://chandpriyankara.blogspot.com/> [image: Google Plus] <http://plus.google.com/104246340732624023499> <http://www.iucnredlist.org/amazing-species> Please consider your environmental responsibility. Before printing this e-mail message, ask yourself whether you really need a hard copy. * *
Re: Does log4cxx is thread safe
Shall we continue with double locking? On Sat, Mar 24, 2012 at 9:03 PM, Roger Orr wrote: > Rob Riggs wrote: > > > What version of the compiler are you using? The new C++11 standard > > requires that scoped static variables are initialized in a thread-safe > > manner. I would expect that VC10/VC11 works correctly. > > Sadly it seems even VC 11 beta doesn't implement the new standard in this > area. > I am a little disappointed :-( > > Regards, > Roger. > > -- *Chand Priyankara* |(094) 773-361566 |ch...@engineering.com |www.blog.friendly.com [image: Facebook] <http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger]<http://chandpriyankara.blogspot.com/> [image: Google Plus] <http://plus.google.com/104246340732624023499> <http://www.iucnredlist.org/amazing-species> Please consider your environmental responsibility. Before printing this e-mail message, ask yourself whether you really need a hard copy. * *
Re: Moving log4cxx to the Attic
We are using this library, a lot. This is kind of a well stable product, and seems small amount of changes,enhancements. So it seems inactive, but NOT. Some custom appenders been developed, but not in code base. i feel, we *cant *consider this as dead. :( regards, *Chand Priyankara* [image: Facebook]<http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger] <http://chandpriyankara.blogspot.com/> [image: Google Plus]<http://plus.google.com/104246340732624023499> |BSc(Eng) - Electrical & Information |(094) 773-361-566 |ch...@engineering.com |http://chandpriyankara.blogspot.com <http://www.iucnredlist.org/amazing-species>sent via internet On Thu, Feb 7, 2013 at 2:44 PM, Alexandru Zbârcea wrote: > We use log4xx extensively ... > > There are few changes I wanted to push, but I had no time ... > > On Thu, Feb 7, 2013 at 7:43 AM, Andrew Lazarus wrote: > >> It's doing everything I want! So I haven't had any need to develop >> further. >> >> On Feb 06, 2013, at 09:31 PM, Christian Grobmeier >> wrote: >> >> Hello >> >> I would like to propose we move the log4cxx component to the attic. >> I am not sure if the Apache Attic itself is the right place: >> http://attic.apache.org/ >> >> as it seems to feed on TLDs only. I will ask there, if we agree that >> log4cxx is not really maintained and that there will no work happen in >> future. >> >> I have hoped that there were a couple of people coming back to the >> project when they see somebody is committing their patches. But it >> hasn't happened and my own C skills are not enough to push this (time >> is an issue too). >> >> In case we agree, I would like to to keep the old log4cxx website, >> saying this project is not longer maintained and the source code has >> been moved to attic (if the attic.apache.org would take it). Other >> options are also welcome, just let me hear what you think. >> >> Best regards, >> Christian >> >> -- >> http://www.grobmeier.de >> https://www.timeandbill.de >> >> >
Re: log4cxx - reaching out for interested developers
Hi Christian, Thanks for you work on log4cxx. What I mean is its better go towards Incubator, than Attic. Because, I still believe log4cxx is the primary logging framework for C++ related projects. The concern is, even though the number of C++ based [new]projects are less, still it is a good choice to move with. If we move this to Attic[Apache project has reached its end of life], even a new user will be hesitate to use this incredible tool. But still in Incubation, there is a possibility to increase the number of dev/user support, since newbies are looking Incubation projects than Attic projects. Personally, I use log4cxx for several C++ projects really confidence with it, and willing to use it in upcoming projects as well. So, I'll be there, in my best to support/develop/enhance log4cxx. I can support log4cxx with been as an Incubation mentor. regards, *Chand Priyankara* [image: Facebook]<http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger] <http://chandpriyankara.blogspot.com/> [image: Google Plus]<http://plus.google.com/104246340732624023499> |BSc(Eng) - Electrical & Information |(094) 773-361-566 |ch...@engineering.com |http://chandpriyankara.blogspot.com <http://www.iucnredlist.org/amazing-species>sent via internet On Thu, Apr 18, 2013 at 1:51 PM, Christian Grobmeier wrote: > Hello log4cxx users/devs, > > I wrote an E-Mail in february to consider log4cxx for the attic. > > The attic means the code is accessible, but no Apache committer is > actively maintaining it or releasing code. > > In february a couple of people shown their interest in the project. I > thought a while about it, considering to apply patches myself. But as > I have not much knowledge/interest in c++ it is really not the best > option. > > Another option came to my mind. I have not clarified it with others so > far, so i am not sure if this would work out. > > Anyway, at Apache we have the so-called Incubator. It is a place where > we build up communities, clarify legal things and so on. It is not so > easy to get new committers in an existing tlp, but it is more easy to > allow direct commit access to interested parties in the incubator. > > The log4cxx project would not be an "official" apache project, until > it is coming out of the incubator. This will be the case if the > community around log4cxx has proven a level of interest and long-term > commitment, if the community has learned what is "around Apache" and > how to create proper releases. > > If there are 3 people with an interest, I am willing to help with > incubation as mentor. > > But please, if you are considering to help and step up: do it only if > you *really* have an interest and a *really* willing to donate some of > your time. If you are in doubt if OS work at Apache is for you, > consider to clone log4cxx at github and work there for a while. > > I will give this e-mail a couple of days to develop; after this I will > either open a vote for the Attic or discuss the option of a new > incubation with a new development team. > > Cheers > Christian > > -- > http://www.grobmeier.de > https://www.timeandbill.de >
Re: log4cxx - reaching out for interested developers
Hello, That's great Christian , and I'm OK with it. *“Something must be done. This is something. Therefore we must do it!”* * * Hopefully, waiting for more support from the community.* * * * * * regards, *Chand Priyankara* [image: Facebook]<http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger] <http://chandpriyankara.blogspot.com/> [image: Google Plus]<http://plus.google.com/104246340732624023499> |BSc(Eng) - Electrical & Information |(094) 773-361-566 |ch...@engineering.com |http://chandpriyankara.blogspot.com <http://www.iucnredlist.org/amazing-species>sent via internet On Thu, Apr 18, 2013 at 3:05 PM, Christian Grobmeier wrote: > [- log4j-user, +log4cxx-user] > > Hello Chand, > > thanks for your feedback! > > You made a few good points. Still, a project which is not maintained bug > patching its code base or creating releases is actually "end of life". > That said, the role "mentor" is restricted to active long-term > Apache-people (spoken easily). > > But it would be possible for you to join the developers team as committer. > In this case you would get direct write access to SVN. I, as mentor, would > assist you to understand all the rules of the Apache Software Foundation. > > That said, I count you as "initial committer" if we would go into the > incubator, right? > > Lets hope a few more people are interested, then we might have a chance to > go to incubation. > > Cheers > Christian > > > > > On Thu, Apr 18, 2013 at 10:59 AM, chand priyankara > wrote: > >> Hi Christian, >> >> Thanks for you work on log4cxx. >> What I mean is its better go towards Incubator, than Attic. >> Because, I still believe log4cxx is the primary logging framework for C++ >> related projects. >> The concern is, even though the number of C++ based [new]projects >> are less, still it is a good choice to move with. >> >> If we move this to Attic[Apache project has reached its end of life], >> even a new user will be hesitate to use this incredible tool. >> But still in Incubation, there is a possibility to increase the number of >> dev/user support, since newbies are looking Incubation projects than Attic >> projects. >> >> Personally, I use log4cxx for several C++ projects really confidence with >> it, and willing to use it in upcoming projects as well. >> So, I'll be there, in my best to support/develop/enhance log4cxx. >> >> I can support log4cxx with been as an Incubation mentor. >> >> >> >> >> regards, >> >> >> *Chand Priyankara* [image: >> Facebook]<http://www.facebook.com/chand.priyankara> >> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: >> Blogger] <http://chandpriyankara.blogspot.com/> [image: Google >> Plus]<http://plus.google.com/104246340732624023499> >> >> |BSc(Eng) - Electrical & Information >> |(094) 773-361-566 >> |ch...@engineering.com >> |http://chandpriyankara.blogspot.com >> <http://www.iucnredlist.org/amazing-species>sent via internet >> >> >> On Thu, Apr 18, 2013 at 1:51 PM, Christian Grobmeier > > wrote: >> >>> Hello log4cxx users/devs, >>> >>> I wrote an E-Mail in february to consider log4cxx for the attic. >>> >>> The attic means the code is accessible, but no Apache committer is >>> actively maintaining it or releasing code. >>> >>> In february a couple of people shown their interest in the project. I >>> thought a while about it, considering to apply patches myself. But as >>> I have not much knowledge/interest in c++ it is really not the best >>> option. >>> >>> Another option came to my mind. I have not clarified it with others so >>> far, so i am not sure if this would work out. >>> >>> Anyway, at Apache we have the so-called Incubator. It is a place where >>> we build up communities, clarify legal things and so on. It is not so >>> easy to get new committers in an existing tlp, but it is more easy to >>> allow direct commit access to interested parties in the incubator. >>> >>> The log4cxx project would not be an "official" apache project, until >>> it is coming out of the incubator. This will be the case if the >>> community around log4cxx has proven a level of interest and long-term >>> commitment, if the community has learned what is "around Apache" and >>> how to create proper releases
Re: log4cxx - reaching out for interested developers
Hi all, What I suggest here is, that we should come to a conclusion soon and resume/re-start developments/fixes ASAP. Because that's the only way to regain Log4CXX glory!!! Last few weeks, I tried to fix some [atlease blocking]bugs, but I couldn't finish since i don't have commit rights.Once you go through the bug lists,you may find those enhancements requested are not such big issues. But we have to make it happen. Christian??? Any steps further, please regards, *Chand Priyankara* [image: Facebook]<http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger] <http://chandpriyankara.blogspot.com/> [image: Google Plus]<http://plus.google.com/104246340732624023499> |BSc(Eng) - Electrical & Information |(094) 773-361-566 |ch...@engineering.com |http://chandpriyankara.blogspot.com <http://www.iucnredlist.org/amazing-species>sent via internet On Tue, Apr 23, 2013 at 9:52 PM, Christian Grobmeier wrote: > On Tue, Apr 23, 2013 at 6:19 PM, Nick Williams > wrote: > > Lacking any responses, I'll chime in: > > > > I didn't know log4cxx existed. The only Cxx code I write is Java+Native. > With that said, now that I know it exists, I will investigate using it in > my native code; I'm not sure. > > > > I'd love to try to help some, but I simply don't have time right now. > I'm in the middle of writing a book. Perhaps after the book comes out, but > that's going to be another 8 months from now. > > > > It sure would be a shame to see it head to the attic. :-( > > Just want to make sure everybody knows that attic doesn't mean > "deleted". The code will be accessible and we'll make a pointer to it. > It is just an indicator that there is nobody working on it (I just > have not the time to learn the skills :-(). > > When ever a group of people (I guess 3 to 5 would make it happen) come > together and *want* to maintain it, we can get it back from the attic > without big pain. > > So, if you have finished your book (curious about what you write!) you > have a chance to revive it. > > Cheers > > > > > > Nick > > > > On Apr 18, 2013, at 3:21 AM, Christian Grobmeier wrote: > > > >> Hello log4cxx users/devs, > >> > >> I wrote an E-Mail in february to consider log4cxx for the attic. > >> > >> The attic means the code is accessible, but no Apache committer is > >> actively maintaining it or releasing code. > >> > >> In february a couple of people shown their interest in the project. I > >> thought a while about it, considering to apply patches myself. But as > >> I have not much knowledge/interest in c++ it is really not the best > >> option. > >> > >> Another option came to my mind. I have not clarified it with others so > >> far, so i am not sure if this would work out. > >> > >> Anyway, at Apache we have the so-called Incubator. It is a place where > >> we build up communities, clarify legal things and so on. It is not so > >> easy to get new committers in an existing tlp, but it is more easy to > >> allow direct commit access to interested parties in the incubator. > >> > >> The log4cxx project would not be an "official" apache project, until > >> it is coming out of the incubator. This will be the case if the > >> community around log4cxx has proven a level of interest and long-term > >> commitment, if the community has learned what is "around Apache" and > >> how to create proper releases. > >> > >> If there are 3 people with an interest, I am willing to help with > >> incubation as mentor. > >> > >> But please, if you are considering to help and step up: do it only if > >> you *really* have an interest and a *really* willing to donate some of > >> your time. If you are in doubt if OS work at Apache is for you, > >> consider to clone log4cxx at github and work there for a while. > >> > >> I will give this e-mail a couple of days to develop; after this I will > >> either open a vote for the Attic or discuss the option of a new > >> incubation with a new development team. > >> > >> Cheers > >> Christian > >> > >> -- > >> http://www.grobmeier.de > >> https://www.timeandbill.de > >> > >> - > >> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > >> For additional commands, e-mail: log4j-user-h...@logging.apache.org > >> > > > > > > -- > http://www.grobmeier.de > https://www.timeandbill.de >
Re: log4cxx - reaching out for interested developers
Hi all, Any further suggestions in going forward other than Incubator or Attic? or else, can we get in to a conclusion, please. regards, *Chand Priyankara* [image: Facebook]<http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger] <http://chandpriyankara.blogspot.com/> [image: Google Plus]<http://plus.google.com/104246340732624023499> |BSc(Eng) - Electrical & Information |(094) 773-361-566 |ch...@engineering.com |http://chandpriyankara.blogspot.com <http://www.iucnredlist.org/amazing-species>sent via internet On Fri, Apr 26, 2013 at 12:13 AM, Florian Seydoux wrote: > Le Thu, 18 Apr 2013 13:04:25 +0200, > Christian Grobmeier wrote : > > > [...] > > Basically there are many people who "keep > > an eye on the project", discuss, commit a few things but keep their > > level of activity pretty low. This works too, as long as the person > > "sticks" with the project. > > > Hi All, > > As a user of this great library since almost 7 years (with some > discontinuities) , I'll be very happy to see it "back online". > > The proposition of Christian to move them on Incubation stage makes > sense, and seems even very appealing. > > Despite I didn't actively contributed till now, I would be very happy > to offer some of my time for such task, following the quoted opinion > here above. > > Of course, starting by simply providing patches would already be a > first step for me - I just wanted to let you know that there are > potential workpower, just waiting some activity on the lib to be > 'activated'. > > Cheers > > Florian > >
Re: docs
Please refer to below URL for the moment. https://svn.apache.org/repos/asf/logging/site/trunk/docs/log4cxx/apidocs/index.html regards, *Chand Priyankara* [image: Facebook]<http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger] <http://chandpriyankara.blogspot.com/> [image: Google Plus]<http://plus.google.com/104246340732624023499> |BSc(Eng) - Electrical & Information |(094) 773-361-566 |ch...@engineering.com |http://chandpriyankara.blogspot.com <http://www.iucnredlist.org/amazing-species>sent via internet On Mon, Sep 9, 2013 at 9:03 PM, Littlefield, Tyler wrote: > Hello: > I clicked on the log4cxx apidocs link as well as the manual link on the > log4cxx wiki and kepe getting 404 errors. Is log4cxx still being > used/developed? Any idea where the docs might be? I am evaluating logging > libraries and this is my third this morning. Glog has almost no docs to > speak of, boost::logging is well, boost and log4cxx seems to have misplaced > it's documentation. > > -- > Take care, > Ty > http://tds-solutions.net > He that will not reason is a bigot; he that cannot reason is a fool; he > that dares not reason is a slave. > >
Re: Fwd: [RESULT] [VOTE] Accept Log4cxx for Incubation
Hi Christian, Really appreciate on your apache contribution on wakeup sleeping projects like Log4CXX, Wave, etc. Hopefully, once again we'll make a firm base for those projects in going forward. +1 for Christian. regards, *Chand Priyankara* [image: Facebook]<http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger] <http://chandpriyankara.blogspot.com/> [image: Google Plus]<http://plus.google.com/104246340732624023499> |BSc(Eng) - Electrical & Information |(094) 773-361-566 |ch...@engineering.com |http://chandpriyankara.blogspot.com <http://www.iucnredlist.org/amazing-species>sent via internet On Mon, Dec 9, 2013 at 3:36 PM, Thorsten Schöning wrote: > Guten Tag Christian Grobmeier, > am Montag, 9. Dezember 2013 um 10:30 schrieben Sie: > > > The next days I will try to work on the next steps and create accounts > > for all who submitted their ICLA. > > I recognized that my ICLA is still missing, my boss promised me to > send ours today. > > Mit freundlichen Grüßen, > > Thorsten Schöning > > -- > Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de > AM-SoFT IT-Systeme http://www.AM-SoFT.de/ > > Telefon...05151- 9468- 55 > Fax...05151- 9468- 88 > Mobil..0178-8 9468- 04 > > AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln > AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow > >
Re: Accounts requested
Many Thanks Christian, So, while code is ready for changes, how can we have a plan to go ahead? we can first start with collecting and verifying bug fixes and patches which are already on mailing lists, right? Any plan, or a preferred way to get started? regards, *Chand Priyankara* [image: Facebook]<http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger] <http://chandpriyankara.blogspot.com/> [image: Google Plus]<http://plus.google.com/104246340732624023499> |BSc(Eng) - Electrical & Information |(094) 773-361-566 |ch...@engineering.com |http://chandpriyankara.blogspot.com <http://www.iucnredlist.org/amazing-species>sent via internet On Mon, Dec 16, 2013 at 2:19 PM, Christian Grobmeier wrote: > Hi folks, > > i just requested all accounts listed here: > http://incubator.apache.org/projects/log4cxx2.html > > Now we just need to wait that Infra resolves this ticket: > https://issues.apache.org/jira/browse/INFRA-7092 > > And then I can finally give you access to the code. > > Ready for playing with the new toy around xmas ;-) > > Regards, > Christian > > > --- > http://www.grobmeier.de > @grobmeier > GPG: 0xA5CC90DB >
Re: SVN Access granted
Hi team, Christian, Permission works fine. Tested. regards, *Chand Priyankara* [image: Facebook]<http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger] <http://chandpriyankara.blogspot.com/> [image: Google Plus]<http://plus.google.com/104246340732624023499> |BSc(Eng) - Electrical & Information |(094) 773-361-566 |ch...@engineering.com |http://chandpriyankara.blogspot.com <http://www.iucnredlist.org/amazing-species>sent via internet On Thu, Jan 2, 2014 at 9:53 PM, Christophe de Vienne wrote: > Hello, > > Le 02/01/2014 16:55, Christian Grobmeier a écrit : > > On 2 Jan 2014, at 16:47, Rhys Ulerich wrote: > >> I also see commits from authors > >> afester > >> carnold > >> cdevienne > >> mcatan > >> via svn log (http://stackoverflow.com/questions/2494984). Any > >> complaints if I add these folks names as well as "Emeritus" as that > >> Maven pom.xml does? > > > > No, its fine. Except of Curt (carnold) I even never heard of the other > > guys, > > so it's really history. If they come back, they can change the state > > themselves > > as they still have write access. > History is still keeping an eye on the list :-) > > I will most probably not contribute anymore to log4cxx though. > > Thanks to new team for re-activating the project. > > Good luck and happy new year ! > > Christophe >
Re: setup Continuous Integration
Hi Rhys, Thanks. I'll work on this issue. Seems there is some code fix to be done, regrading a variable passing to a function [missing const]. regards, *Chand Priyankara* [image: Facebook]<http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger] <http://chandpriyankara.blogspot.com/> [image: Google Plus]<http://plus.google.com/104246340732624023499> |BSc(Eng) - Electrical & Information |(094) 773-361-566 |ch...@engineering.com |http://chandpriyankara.blogspot.com <http://www.iucnredlist.org/amazing-species>sent via internet On Wed, Jan 8, 2014 at 8:55 AM, Rhys Ulerich wrote: > > Can you please provide me a workaround to following error while building > logcxx from current trunk: > > > > loggingevent.h:171:45: error: declaration of 'typedef > log4cxx::spi::KeySet log4cxx::spi::LoggingEvent::KeySet' [-fpermissive] > > Is this using Autotools? Or Ant? If it's Autotools you can probably use > CXXFLAGS=-fpermissive ./configure > instead of the usual >./configure > > I've had luck with this in the past: > https://red.ices.utexas.edu/issues/2971 > > I've filed https://issues.apache.org/jira/browse/LOGCXX-419 and will > take a look at it. > > - Rhys >
Re: Contributor OS cross reference?
I use following in frequent: Linux Ubuntu[gcc] Windows 7[visual studio 2008] Linux Redhat5[gcc] regards, *Chand Priyankara* [image: Facebook]<http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger] <http://chandpriyankara.blogspot.com/> [image: Google Plus]<http://plus.google.com/104246340732624023499> |BSc(Eng) - Electrical & Information |(094) 773-361-566 |ch...@engineering.com |http://chandpriyankara.blogspot.com <http://www.iucnredlist.org/amazing-species>sent via internet On Wed, Jan 8, 2014 at 10:18 PM, Rhys Ulerich wrote: > > Personally, I have currently access to: > > Several compilers >GCC 4.5, 4.6, 4.7, 4.8 >Intel 11.1, 12.1, 13.1 > on Ubuntu and Scientific Linux boxen. Not much else. > > - Rhys >
Re: setup Continuous Integration
Hi Rhys, I'll comment in jira. Hope it'll be better. regards, *Chand Priyankara* [image: Facebook]<http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger] <http://chandpriyankara.blogspot.com/> [image: Google Plus]<http://plus.google.com/104246340732624023499> |BSc(Eng) - Electrical & Information |(094) 773-361-566 |ch...@engineering.com |http://chandpriyankara.blogspot.com <http://www.iucnredlist.org/amazing-species>sent via internet On Thu, Jan 9, 2014 at 9:08 AM, Rhys Ulerich wrote: > Hi Chand, > > I've filed https://issues.apache.org/jira/browse/LOGCXX-419 and will >>> take a look at it. >>> >> > I believe I have that fixed now. Please let me know if it continues to > give you trouble. > > - Rhys >
Re: [jira] [Commented] (LOGCXX-419) 'typedef spi::KeySet KeySet' changes meaning of typedef
Index: src/main/include/log4cxx/spi/loggingevent.h === --- src/main/include/log4cxx/spi/loggingevent.h (revision 1556590) +++ src/main/include/log4cxx/spi/loggingevent.h (working copy) @@ -160,7 +160,7 @@ * @return Set an unmodifiable set of the MDC keys. * */ -KeySet getMDCKeySet() const; +spi::KeySet getMDCKeySet() const; /** Obtain a copy of this thread's MDC prior to serialization regards, *Chand Priyankara* [image: Facebook]<http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger] <http://chandpriyankara.blogspot.com/> [image: Google Plus]<http://plus.google.com/104246340732624023499> |BSc(Eng) - Electrical & Information |(094) 773-361-566 |ch...@engineering.com |http://chandpriyankara.blogspot.com <http://www.iucnredlist.org/amazing-species>sent via internet On Thu, Jan 9, 2014 at 11:26 AM, Rhys Ulerich wrote: > > I didn't like that 'fpermissive' thing. > > Agreed. It was only a workaround. > > > I fixed it by putting spi:: in KeySet. > > Goofy question, how exactly? I'd love to see a diff. > > - Rhys >
Re: [jira] [Closed] (LOGCXX-419) 'typedef spi::KeySet KeySet' changes meaning of typedef
hey All, Is it OK that we close once verified? Or does it need any further steps before closing? regards, *Chand Priyankara* [image: Facebook]<http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger] <http://chandpriyankara.blogspot.com/> [image: Google Plus]<http://plus.google.com/104246340732624023499> |BSc(Eng) - Electrical & Information |(094) 773-361-566 |ch...@engineering.com |http://chandpriyankara.blogspot.com <http://www.iucnredlist.org/amazing-species>sent via internet On Fri, Jan 10, 2014 at 7:05 AM, Chand Priyankara (JIRA) < log4cxx-dev@logging.apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/LOGCXX-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] > > Chand Priyankara closed LOGCXX-419. > --- > > > resolve is fine. agreed. > > > 'typedef spi::KeySet KeySet' changes meaning of typedef > > --- > > > > Key: LOGCXX-419 > > URL: https://issues.apache.org/jira/browse/LOGCXX-419 > > Project: Log4cxx > > Issue Type: Bug > > Components: Filter > >Affects Versions: 0.10.0, 0.10.1 > > Environment: Ubuntu Saucy, GCC 4.8.1, Autotools > >Reporter: Rhys Ulerich > >Assignee: Rhys Ulerich > > > > Observed in the build... > > In file included from > ../../../../log4cxx/src/main/include/log4cxx/spi/filter.h:24:0, > > from > ../../../../log4cxx/src/main/include/log4cxx/filter/andfilter.h:27, > > from ../../../../log4cxx/src/main/cpp/andfilter.cpp:18: > > ../../../../log4cxx/src/main/include/log4cxx/spi/loggingevent.h:171:45: > error: declaration of ‘typedef log4cxx::spi::KeySet > log4cxx::spi::LoggingEvent::KeySet’ [-fpermissive] > > typedef spi::KeySet KeySet; > > ^ > > In file included from > ../../../../log4cxx/src/main/include/log4cxx/helpers/objectptr.h:21:0, > > from > ../../../../log4cxx/src/main/include/log4cxx/spi/filter.h:21, > > from > ../../../../log4cxx/src/main/include/log4cxx/filter/andfilter.h:27, > > from ../../../../log4cxx/src/main/cpp/andfilter.cpp:18: > > ../../../../log4cxx/src/main/include/log4cxx/spi/loggingevent.h:46:34: > error: changes meaning of ‘KeySet’ from ‘typedef class > std::vector > log4cxx::spi::KeySet’ [-fpermissive] > > LOG4CXX_LIST_DEF(KeySet, LogString); > > ^ > > ../../../../log4cxx/src/main/include/log4cxx/log4cxx.h:48:55: note: in > definition of macro ‘LOG4CXX_LIST_DEF’ > > #define LOG4CXX_LIST_DEF(N, T) typedef std::vector N > > > > -- > This message was sent by Atlassian JIRA > (v6.1.5#6160) >
Re: To be aligned: which C++ dialect for log4cxx
Hi, What you really mean by '~restrict'? Is it for some recent releases, or just like forever? And whats the actual root cause to get in to this kind of a problem? regards, *Chand Priyankara* [image: Facebook]<http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger] <http://chandpriyankara.blogspot.com/> [image: Google Plus]<http://plus.google.com/104246340732624023499> |BSc(Eng) - Electrical & Information |(094) 773-361-566 |ch...@engineering.com |http://chandpriyankara.blogspot.com <http://www.iucnredlist.org/amazing-species>sent via internet On Tue, Jan 14, 2014 at 8:17 PM, Pedro Lamarão wrote: > Em 11/01/2014 10:03, Florian Seydoux escreveu: > > Hi all, >> a short question: do wee all agree to ~restrict the codebase to ansi C++ >> (ie. -std=c++98) without 03/11 extension? >> (despite it's not enforced on gcc compilation) >> >> > There are no 2003 extensions. > ISO C++ 2003 is the same as ISO C++ 1998 with the incorporation of various > errata. > > Perhaps you are worried about Visual C++ 6. > It doesn't and could never fully support ISO C++ 1998 or ISO C++ 2003, > because it was released before those standards were completed. > Is this the case? > > P. >
RE: using log4cxx from sca component
I think you should give full file path or reference path.it just create the File handler. Try using the other overloaded function or another configure function. Best luck. Chand priyankara From: Thorsten Schöning Sent: 2/6/2014 19:59 To: log4cxx-dev@logging.apache.org Subject: Re: using log4cxx from sca component Guten Tag Shantharaj, Nandan, am Donnerstag, 6. Februar 2014 um 15:13 schrieben Sie: > Requirement in our application was to create a wrapper > around log4cxx functionality, so that in future any other logging > functionality can be used instead of log4cxx. You will loose some of the benefits of Log4cxx that way, e.g. you can't use the efficient LOG4CXX_*-macros and will loose things like line numbers and function names where the logging occurred because those are inserted by the pre processor. The latter will always be the methods of your wrapper unless the wrapper is entirely implemented as macros itself. > For that, we created a component, wrapping log4cxx > functionality using software component architecture (sca) framework. [...] > Issue: > File name passed from component to DOM configurator > never gets passed and following is the error inside log4cxx. > "log4cxx: Could not open file [ ] " Sounds like you need to debug your wrapper, the filename surely gets lost somewhere. I don't see how we can help with that. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...05151- 9468- 55 Fax...05151- 9468- 88 Mobil..0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: Chat room?
+1 regards, *Chand Priyankara* [image: Facebook]<http://www.facebook.com/chand.priyankara> [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image: Blogger] <http://chandpriyankara.blogspot.com/> [image: Google Plus]<http://plus.google.com/104246340732624023499> |BSc(Eng) - Electrical & Information |(094) 773-361-566 |ch...@engineering.com |http://chandpriyankara.blogspot.com <http://www.iucnredlist.org/amazing-species>sent via internet On Fri, Mar 28, 2014 at 8:18 PM, Rhys Ulerich wrote: > Do we have a chat room? Would it be worth lurking in #log4cxx on Freenode? > > - Rhys >
Re: Registering as a dev/contributor
hi koby, In order to introduce kind of a new build system, there should be a conversation/discussion with other developers and get in to some conclusion on it. But already there is build process to build for windows. Since log4cxx is cross-platform, we like to have a common build system. So, its unsure to add MSVS solution file at once. But don't make disappointed at the first contact with log4cxx team. We like to have you in contact. If you can mail your files[as a patch] to the dev/user group, it'll surely have a value to someone, to someday. regards, Chand Priyankara On Sun, Jun 8, 2014 at 4:18 PM, Thorsten Schöning wrote: > Guten Tag Koby Fruchtnis, > am Sonntag, 8. Juni 2014 um 07:20 schrieben Sie: > > > As a first task, I'd like to add a CMakeFiles.txt script to the > > root, for easily building a MSVC sln/project. > > I'm afraid it's not that easy, there has been a discussion about the > build process in the future and CMake was one option, but there's no > result yet. The project already uses autotools and ANT, distributes > some older project files for some IDEs and from my opinion we > shouldn't add another system that easily. We simply can't support so > many build systems. > > Mit freundlichen Grüßen, > > Thorsten Schöning > > -- > Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de > AM-SoFT IT-Systeme http://www.AM-SoFT.de/ > > Telefon...05151- 9468- 55 > Fax...05151- 9468- 88 > Mobil..0178-8 9468- 04 > > AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln > AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow > >
Re: Registering as a dev/contributor
hi Koby, Well, yes. If you are possible, development team is happily accepting patches for bugs. Also, log4cxx is not just coding. There are plenty of other things as well, like documentations, help, samples, etc. If you are interested in working with code, you can make your comments on the JIRA itself, so that all devs will get notified. Interested people will surely join with you. Once the fix ready they'll apply it to the branch for surely. You'll also get credit on it, for surely. :) regards, Chand Priyankara. On Mon, Jun 9, 2014 at 1:51 PM, wrote: > Thank you for your reply. > > > > Is there a better outlet for my desire to assist the log4cxx project? > > Would you suggest to pick a critical bug from JIRA, and to discuss it with > the reporter/committers? > > > > Best regards, > > > > Koby Fruchtnis > > > > *From:* chandpriyank...@gmail.com [mailto:chandpriyank...@gmail.com] *On > Behalf Of *chand priyankara > *Sent:* Sunday, June 08, 2014 6:19 PM > *To:* koby...@gmail.com > *Cc:* Log4CXX Dev > *Subject:* Re: Registering as a dev/contributor > > > > hi koby, > > In order to introduce kind of a new build system, there should be a > conversation/discussion with other developers and get in to some conclusion > on it. > > But already there is build process to build for windows. Since log4cxx is > cross-platform, we like to have a common build system. So, its unsure to > add MSVS solution file at once. > > But don't make disappointed at the first contact with log4cxx team. We > like to have you in contact. If you can mail your files[as a patch] to the > dev/user group, it'll surely have a value to someone, to someday. > > > regards, > > > > Chand Priyankara > > > > On Sun, Jun 8, 2014 at 4:18 PM, Thorsten Schöning > wrote: > > Guten Tag Koby Fruchtnis, > am Sonntag, 8. Juni 2014 um 07:20 schrieben Sie: > > > > As a first task, I'd like to add a CMakeFiles.txt script to the > > root, for easily building a MSVC sln/project. > > I'm afraid it's not that easy, there has been a discussion about the > build process in the future and CMake was one option, but there's no > result yet. The project already uses autotools and ANT, distributes > some older project files for some IDEs and from my opinion we > shouldn't add another system that easily. We simply can't support so > many build systems. > > Mit freundlichen Grüßen, > > Thorsten Schöning > > -- > Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de > AM-SoFT IT-Systeme http://www.AM-SoFT.de/ > > Telefon...05151- 9468- 55 > Fax...05151- 9468- 88 > Mobil..0178-8 9468- 04 > > AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln > AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow > > >
[jira] [Commented] (LOGCXX-419) 'typedef spi::KeySet KeySet' changes meaning of typedef
[ https://issues.apache.org/jira/browse/LOGCXX-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866347#comment-13866347 ] Chand Priyankara commented on LOGCXX-419: - Hi Rhys, I didn't like that 'fpermissive' thing. That's why I wanted to make it fix by changing typedef. I fixed it by putting spi:: in KeySet. But now I see you've moved typedef up. So it is fine, no obligations. Further I'll do a build and let you know. > 'typedef spi::KeySet KeySet' changes meaning of typedef > --- > > Key: LOGCXX-419 > URL: https://issues.apache.org/jira/browse/LOGCXX-419 > Project: Log4cxx > Issue Type: Bug > Components: Filter >Affects Versions: 0.10.0, 0.10.1 > Environment: Ubuntu Saucy, GCC 4.8.1, Autotools >Reporter: Rhys Ulerich >Assignee: Rhys Ulerich > > Observed in the build... > In file included from > ../../../../log4cxx/src/main/include/log4cxx/spi/filter.h:24:0, > from > ../../../../log4cxx/src/main/include/log4cxx/filter/andfilter.h:27, > from ../../../../log4cxx/src/main/cpp/andfilter.cpp:18: > ../../../../log4cxx/src/main/include/log4cxx/spi/loggingevent.h:171:45: > error: declaration of ‘typedef log4cxx::spi::KeySet > log4cxx::spi::LoggingEvent::KeySet’ [-fpermissive] > typedef spi::KeySet KeySet; > ^ > In file included from > ../../../../log4cxx/src/main/include/log4cxx/helpers/objectptr.h:21:0, > from > ../../../../log4cxx/src/main/include/log4cxx/spi/filter.h:21, > from > ../../../../log4cxx/src/main/include/log4cxx/filter/andfilter.h:27, > from ../../../../log4cxx/src/main/cpp/andfilter.cpp:18: > ../../../../log4cxx/src/main/include/log4cxx/spi/loggingevent.h:46:34: error: > changes meaning of ‘KeySet’ from ‘typedef class > std::vector > log4cxx::spi::KeySet’ [-fpermissive] > LOG4CXX_LIST_DEF(KeySet, LogString); > ^ > ../../../../log4cxx/src/main/include/log4cxx/log4cxx.h:48:55: note: in > definition of macro ‘LOG4CXX_LIST_DEF’ > #define LOG4CXX_LIST_DEF(N, T) typedef std::vector N -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (LOGCXX-419) 'typedef spi::KeySet KeySet' changes meaning of typedef
[ https://issues.apache.org/jira/browse/LOGCXX-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chand Priyankara closed LOGCXX-419. --- resolve is fine. agreed. > 'typedef spi::KeySet KeySet' changes meaning of typedef > --- > > Key: LOGCXX-419 > URL: https://issues.apache.org/jira/browse/LOGCXX-419 > Project: Log4cxx > Issue Type: Bug > Components: Filter >Affects Versions: 0.10.0, 0.10.1 > Environment: Ubuntu Saucy, GCC 4.8.1, Autotools >Reporter: Rhys Ulerich >Assignee: Rhys Ulerich > > Observed in the build... > In file included from > ../../../../log4cxx/src/main/include/log4cxx/spi/filter.h:24:0, > from > ../../../../log4cxx/src/main/include/log4cxx/filter/andfilter.h:27, > from ../../../../log4cxx/src/main/cpp/andfilter.cpp:18: > ../../../../log4cxx/src/main/include/log4cxx/spi/loggingevent.h:171:45: > error: declaration of ‘typedef log4cxx::spi::KeySet > log4cxx::spi::LoggingEvent::KeySet’ [-fpermissive] > typedef spi::KeySet KeySet; > ^ > In file included from > ../../../../log4cxx/src/main/include/log4cxx/helpers/objectptr.h:21:0, > from > ../../../../log4cxx/src/main/include/log4cxx/spi/filter.h:21, > from > ../../../../log4cxx/src/main/include/log4cxx/filter/andfilter.h:27, > from ../../../../log4cxx/src/main/cpp/andfilter.cpp:18: > ../../../../log4cxx/src/main/include/log4cxx/spi/loggingevent.h:46:34: error: > changes meaning of ‘KeySet’ from ‘typedef class > std::vector > log4cxx::spi::KeySet’ [-fpermissive] > LOG4CXX_LIST_DEF(KeySet, LogString); > ^ > ../../../../log4cxx/src/main/include/log4cxx/log4cxx.h:48:55: note: in > definition of macro ‘LOG4CXX_LIST_DEF’ > #define LOG4CXX_LIST_DEF(N, T) typedef std::vector N -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (LOGCXX-308) I can not print millisecond with %Q
[
https://issues.apache.org/jira/browse/LOGCXX-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867442#comment-13867442
]
Chand Priyankara commented on LOGCXX-308:
-
Does anyone has the reported platform and make verify this?
I event bother if this bug category is acceptable for this issue.
> I can not print millisecond with %Q
>
>
> Key: LOGCXX-308
> URL: https://issues.apache.org/jira/browse/LOGCXX-308
> Project: Log4cxx
> Issue Type: Bug
> Components: Layout
>Affects Versions: 0.10.0
> Environment: uname -a
> SunOS netra01 5.8 Generic_108528-17 sun4u sparc SUNW,UltraAX-i2
> CC -V
> CC: Sun WorkShop 6 update 2 C++ 5.3 Patch 111685-03 2001/10/19
>Reporter: Yihong Zhan
>Assignee: Curt Arnold
>Priority: Blocker
> Fix For: 0.10.0
>
>
> In log4cxx 0.9.7, I can print millisecond with "%Q"
> For example, %d{%Y-%m-%d %H:%M:%S.%Q} will print "2008-07-27 02:03:45.080"
> But in 0.10.0, "%Q" does not work and the result is "2008-07-27 02:03:45.%Q".
> My platform is sparc-solaris8 CC5.3
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (LOGCXX-407) documentation pages are redirected to non existing page
[ https://issues.apache.org/jira/browse/LOGCXX-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chand Priyankara updated LOGCXX-407: Priority: Major (was: Blocker) > documentation pages are redirected to non existing page > --- > > Key: LOGCXX-407 > URL: https://issues.apache.org/jira/browse/LOGCXX-407 > Project: Log4cxx > Issue Type: Bug > Components: Documentation >Affects Versions: 0.10.0, 0.10.1 > Environment: web browsers >Reporter: Andreas Kirsch > Labels: documentation > > Every link on the Apache platform to documentation and manual of log4cxx is > redirected to a non existing path. The following result is shown: > Not Found > The requested URL /log4cxx/log4cxx-0.11.0-SNAPSHOT/manual.html was not found > on this server. > Apache/2.4.3 (Unix) OpenSSL/1.0.0g Server at logging.apache.org Port 80 > In this case no 0.11.0 snapshot does exist. Even 0.10.x lacks major > functionality of 0.9.x branch. Branch 0.10.x can only be accepted as an > instable working branch. Please fix this mess and set 0.9.7 as current > release - even if it has memory leaks due missing virtual dtors in base > classes! > The affected links can be found on web page: > https://wiki.apache.org/logging-log4cxx/ > log4cxx documentation: http://logging.apache.org/log4cxx/manual.html > log4cxx API documentation: > http://logging.apache.org/log4cxx/apidocs/index.html > https://logging.apache.org/log4cxx/ >About Apache log4cxx -> What is log4cxx? >API Documentation https://logging.apache.org/log4cxx/apidocs/index.html -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (LOGCXX-407) documentation pages are redirected to non existing page
[ https://issues.apache.org/jira/browse/LOGCXX-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867613#comment-13867613 ] Chand Priyankara commented on LOGCXX-407: - Merging common web link issues > documentation pages are redirected to non existing page > --- > > Key: LOGCXX-407 > URL: https://issues.apache.org/jira/browse/LOGCXX-407 > Project: Log4cxx > Issue Type: Bug > Components: Documentation >Affects Versions: 0.10.0, 0.10.1 > Environment: web browsers >Reporter: Andreas Kirsch >Priority: Blocker > Labels: documentation > > Every link on the Apache platform to documentation and manual of log4cxx is > redirected to a non existing path. The following result is shown: > Not Found > The requested URL /log4cxx/log4cxx-0.11.0-SNAPSHOT/manual.html was not found > on this server. > Apache/2.4.3 (Unix) OpenSSL/1.0.0g Server at logging.apache.org Port 80 > In this case no 0.11.0 snapshot does exist. Even 0.10.x lacks major > functionality of 0.9.x branch. Branch 0.10.x can only be accepted as an > instable working branch. Please fix this mess and set 0.9.7 as current > release - even if it has memory leaks due missing virtual dtors in base > classes! > The affected links can be found on web page: > https://wiki.apache.org/logging-log4cxx/ > log4cxx documentation: http://logging.apache.org/log4cxx/manual.html > log4cxx API documentation: > http://logging.apache.org/log4cxx/apidocs/index.html > https://logging.apache.org/log4cxx/ >About Apache log4cxx -> What is log4cxx? >API Documentation https://logging.apache.org/log4cxx/apidocs/index.html -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (LOGCXX-361) 15-16 milliseconds granularity on Windows
[ https://issues.apache.org/jira/browse/LOGCXX-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867643#comment-13867643 ] Chand Priyankara commented on LOGCXX-361: - Hi Sameer, Log4CXX been silent for a while and is back again. We are pleased to get your help on fixing this issue. Please let us know your fix, so one of us can merge it to the trunk. Its great if you can attach a patch file. Thanks. > 15-16 milliseconds granularity on Windows > -- > > Key: LOGCXX-361 > URL: https://issues.apache.org/jira/browse/LOGCXX-361 > Project: Log4cxx > Issue Type: Improvement > Components: Layout > Environment: Windows NT/2003 >Reporter: Sameer Gupta >Assignee: Curt Arnold > Original Estimate: 72h > Remaining Estimate: 72h > > I have noticed the message timestamps being logged are atleast 15-16 > milliseconds apart on windows NT/2003 systems even though the messages > actually requested to be logged were just couple of milliseconds apart. This > is due to the functions being used in the log4cxx code which are based on the > SYSTEMTIME structure. The accuracy of these functions is 15-16 milliseconds > at the most. I have tried to play around with the code and implemented > performance counters to produce sub 15-16 milliseconds accuracy between two > message timestamps. This will specially help the users who develop low > latency applications. > > I am wondering if I can contribute my work to the project. Please let me know > how I can join the project as a developer and what is the procedure to > contribute. Opologies, if this has already been implemented. > > Regards, > Sameer -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (LOGCXX-358) SMTPAppender generating Emails with an empty body
[ https://issues.apache.org/jira/browse/LOGCXX-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chand Priyankara reassigned LOGCXX-358: --- Assignee: Chand Priyankara (was: Curt Arnold) > SMTPAppender generating Emails with an empty body > - > > Key: LOGCXX-358 > URL: https://issues.apache.org/jira/browse/LOGCXX-358 > Project: Log4cxx > Issue Type: Bug > Components: Appender >Affects Versions: 0.10.0 > Environment: Linux lx-chdsd02 2.6.9-67.0.1.ELsmp #1 SMP Fri Nov 30 > 11:57:43 EST 2007 x86_64 x86_64 x86_64 GNU/Linux >Reporter: Ryan L Hart >Assignee: Chand Priyankara > Labels: SMTPAppender, libesmtp > Attachments: smtpappender.patch > > > After compiling log4cxx with -DLOG4CXX_HAS_LIBESMTP defined to get the > SMTPAppender working, the SMTPAppender now generates Emails as expected. > However, the body of the Email message is always blank. Is anyone else > experiencing this problem? Here's my DOMConfigurator configuration file. > > > xmlns:log4j="http://jakarta.apache.org/log4j/";> > > > > > > > > > > > > > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (LOGCXX-308) I can not print millisecond with %Q
[
https://issues.apache.org/jira/browse/LOGCXX-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867442#comment-13867442
]
Chand Priyankara edited comment on LOGCXX-308 at 1/15/14 4:10 PM:
--
Does anyone has the reported platform and make verify this?
I bother if this bug category is acceptable for this issue.
was (Author: chand):
Does anyone has the reported platform and make verify this?
I event bother if this bug category is acceptable for this issue.
> I can not print millisecond with %Q
>
>
> Key: LOGCXX-308
> URL: https://issues.apache.org/jira/browse/LOGCXX-308
> Project: Log4cxx
> Issue Type: Bug
> Components: Layout
>Affects Versions: 0.10.0
> Environment: uname -a
> SunOS netra01 5.8 Generic_108528-17 sun4u sparc SUNW,UltraAX-i2
> CC -V
> CC: Sun WorkShop 6 update 2 C++ 5.3 Patch 111685-03 2001/10/19
>Reporter: Yihong Zhan
>Assignee: Curt Arnold
>Priority: Blocker
> Fix For: 0.10.0
>
>
> In log4cxx 0.9.7, I can print millisecond with "%Q"
> For example, %d{%Y-%m-%d %H:%M:%S.%Q} will print "2008-07-27 02:03:45.080"
> But in 0.10.0, "%Q" does not work and the result is "2008-07-27 02:03:45.%Q".
> My platform is sparc-solaris8 CC5.3
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Assigned] (LOGCXX-308) I can not print millisecond with %Q
[
https://issues.apache.org/jira/browse/LOGCXX-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chand Priyankara reassigned LOGCXX-308:
---
Assignee: Chand Priyankara (was: Curt Arnold)
> I can not print millisecond with %Q
>
>
> Key: LOGCXX-308
> URL: https://issues.apache.org/jira/browse/LOGCXX-308
> Project: Log4cxx
> Issue Type: Bug
> Components: Layout
>Affects Versions: 0.10.0
> Environment: uname -a
> SunOS netra01 5.8 Generic_108528-17 sun4u sparc SUNW,UltraAX-i2
> CC -V
> CC: Sun WorkShop 6 update 2 C++ 5.3 Patch 111685-03 2001/10/19
>Reporter: Yihong Zhan
>Assignee: Chand Priyankara
>Priority: Blocker
> Fix For: 0.10.0
>
>
> In log4cxx 0.9.7, I can print millisecond with "%Q"
> For example, %d{%Y-%m-%d %H:%M:%S.%Q} will print "2008-07-27 02:03:45.080"
> But in 0.10.0, "%Q" does not work and the result is "2008-07-27 02:03:45.%Q".
> My platform is sparc-solaris8 CC5.3
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (LOGCXX-308) I can not print millisecond with %Q
[
https://issues.apache.org/jira/browse/LOGCXX-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chand Priyankara updated LOGCXX-308:
Priority: Major (was: Blocker)
> I can not print millisecond with %Q
>
>
> Key: LOGCXX-308
> URL: https://issues.apache.org/jira/browse/LOGCXX-308
> Project: Log4cxx
> Issue Type: Bug
> Components: Layout
>Affects Versions: 0.10.0
> Environment: uname -a
> SunOS netra01 5.8 Generic_108528-17 sun4u sparc SUNW,UltraAX-i2
> CC -V
> CC: Sun WorkShop 6 update 2 C++ 5.3 Patch 111685-03 2001/10/19
>Reporter: Yihong Zhan
>Assignee: Chand Priyankara
> Fix For: 0.10.0
>
>
> In log4cxx 0.9.7, I can print millisecond with "%Q"
> For example, %d{%Y-%m-%d %H:%M:%S.%Q} will print "2008-07-27 02:03:45.080"
> But in 0.10.0, "%Q" does not work and the result is "2008-07-27 02:03:45.%Q".
> My platform is sparc-solaris8 CC5.3
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Assigned] (LOGCXX-412) Log4cxx doesn't roll normally when working under multiple processes environment
[ https://issues.apache.org/jira/browse/LOGCXX-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chand Priyankara reassigned LOGCXX-412: --- Assignee: Chand Priyankara > Log4cxx doesn't roll normally when working under multiple processes > environment > --- > > Key: LOGCXX-412 > URL: https://issues.apache.org/jira/browse/LOGCXX-412 > Project: Log4cxx > Issue Type: Improvement > Components: Appender >Affects Versions: 0.10.0 > Environment: RHEL 5.x, 6.x >Reporter: Wei Sun >Assignee: Chand Priyankara > Fix For: 0.10.0 > > Attachments: log4cxx-multi_processes.patch > > Original Estimate: 96h > Remaining Estimate: 96h > > Log4cxx cannot roll file as expected when working under multiple processes > environment, it will write to arbitrary log files, both size-base and > time-based rolling policy have this issue. The attached patch fixed this by > adding synchronization mechanism among different processes, it has been > verified with apache(multiple process mode) under RHEL 4.x-6.x for size-based > rolling and time-based rolling. To apply this needs to define > LOG4CXX_MULTI_PROCESS macros. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (LOGCXX-361) 15-16 milliseconds granularity on Windows
[ https://issues.apache.org/jira/browse/LOGCXX-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940759#comment-13940759 ] Chand Priyankara commented on LOGCXX-361: - The issue is filed for 'Windows NT/2003'. Is there any possibility to make a test-case to verify current latency? Also would it be consistent to everyone? > 15-16 milliseconds granularity on Windows > -- > > Key: LOGCXX-361 > URL: https://issues.apache.org/jira/browse/LOGCXX-361 > Project: Log4cxx > Issue Type: Improvement > Components: Layout > Environment: Windows NT/2003 >Reporter: Sameer Gupta >Assignee: Curt Arnold > Original Estimate: 72h > Remaining Estimate: 72h > > I have noticed the message timestamps being logged are atleast 15-16 > milliseconds apart on windows NT/2003 systems even though the messages > actually requested to be logged were just couple of milliseconds apart. This > is due to the functions being used in the log4cxx code which are based on the > SYSTEMTIME structure. The accuracy of these functions is 15-16 milliseconds > at the most. I have tried to play around with the code and implemented > performance counters to produce sub 15-16 milliseconds accuracy between two > message timestamps. This will specially help the users who develop low > latency applications. > > I am wondering if I can contribute my work to the project. Please let me know > how I can join the project as a developer and what is the procedure to > contribute. Opologies, if this has already been implemented. > > Regards, > Sameer -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (LOGCXX-439) Dynamic Configuration of Log4cxx XML with Properties is not proper
[
https://issues.apache.org/jira/browse/LOGCXX-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064838#comment-14064838
]
chand priyankara commented on LOGCXX-439:
-
hi balajilbk,
can you please provide a testcase to recreate the scenario.
will be more helpful if you can provide some code, with a sample configuration
file.
> Dynamic Configuration of Log4cxx XML with Properties is not proper
> --
>
> Key: LOGCXX-439
> URL: https://issues.apache.org/jira/browse/LOGCXX-439
> Project: Log4cxx
> Issue Type: Bug
> Components: Configurator
>Affects Versions: 0.10.0
> Environment: Windows XP SP 2/7, Visual Studio 2010.
>Reporter: balajilbk
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Dear Team,
> Thanks for the wonderful logging framework.
> In my application, the Log4cxx Configuration XML file contain few fields in
> appender with %properties{Property Name}. The properties are set using
> log4cxx::MDC::put method in my program. When doing the first time
> configuration, the DOMConfigurator configures the data properly because of
> the available thread context.
> But if we update the configuration file dynamically without re-starting the
> application, the thread is not having any MDC data. Hence the property is
> empty when re-configuring using dynamic usage of the DOMConfigurator.
> Kindly help me to resolve this issue.
> Thanks in advance.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (LOGCXX-441) Log4cxx SocketAppender leads to application crash
[ https://issues.apache.org/jira/browse/LOGCXX-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129505#comment-14129505 ] chand priyankara commented on LOGCXX-441: - hi, I had a look on the same in windows with http://logging.apache.org/chainsaw/ in-fact, I used XML configuration: but it didn't make any crash on windows. Can you give the appender configurations? I don't think still its possible to have a backup log to file in case of failure, but you can used two appenders at the same time. so you wont lost the logs. > Log4cxx SocketAppender leads to application crash > - > > Key: LOGCXX-441 > URL: https://issues.apache.org/jira/browse/LOGCXX-441 > Project: Log4cxx > Issue Type: Bug > Components: Appender >Affects Versions: 0.10.0 > Environment: CentOS, RHEL, C++11 >Reporter: Rakesh Sehgal > Labels: features > Fix For: 0.11.0 > > > I am using log4cxx and recently started working with SocketAppender. I use > the following: > java org.apache.log4j.net.SimpleSocketServer 4712 log4j-server.properties > and am able to write logs on the server. I do also have a local SizeRollover > policy setup. This all works fine, until I stop running the > SimpleSockerServer. At which point my C++ application crashes, I think after > the ReconnectionDelayTime specified in the properties file. > Below is the gdb output from crash: > 0 0x003c5fa0e6fd in write () from /lib64/libpthread.so.0 > 1 0x779eade7 in apr_socket_send () from /usr/lib64/libapr-1.so.0 > 2 0x77d52bb1 in > log4cxx::helpers::Socket::write(log4cxx::helpers::ByteBuffer&) () from > /usr/lib64/liblog4cxx.so.10 > 3 0x77d595ed in > log4cxx::helpers::SocketOutputStream::flush(log4cxx::helpers::Pool&) () from > /usr/lib64/liblog4cxx.so.10 > 4 0x77d5468c in > log4cxx::net::SocketAppender::append(log4cxx::helpers::ObjectPtrT const&, > log4cxx::helpers::Pool&) () from /usr/lib64/liblog4cxx.so.10 > 5 0x77cd7d9d in > log4cxx::AppenderSkeleton::doAppend(log4cxx::helpers::ObjectPtrT const&, > log4cxx::helpers::Pool&) () from /usr/lib64/liblog4cxx.so.10 > 6 0x77cd50f4 in > log4cxx::helpers::AppenderAttachableImpl::appendLoopOnAppenders(log4cxx::helpers::ObjectPtrT > const&, log4cxx::helpers::Pool&) () from /usr/lib64/liblog4cxx.so.10 > 7 0x77d1adfd in > log4cxx::Logger::callAppenders(log4cxx::helpers::ObjectPtrT const&, > log4cxx::helpers::Pool&) const () from /usr/lib64/liblog4cxx.so.10 > 8 0x77d1c4ac in > log4cxx::Logger::forcedLog(log4cxx::helpers::ObjectPtrT const&, > std::basic_string, std::allocator > const&, log4cxx::spi::LocationInfo > const&) const () from /usr/lib64/liblog4cxx.so.10` > As an improvement, Is it possible to make log4cxx write logs to a local file > in case the server stops? If I start the server again, before the application > crashes, SocketAppender does not receive the logs again. Any other > suggestions to send logs over the network? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LOGCXX-449) crash on program exit when no logging output is produced
[ https://issues.apache.org/jira/browse/LOGCXX-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256807#comment-14256807 ] chand priyankara commented on LOGCXX-449: - hi Morgan. I tried to recreate the issue, but I couldn't with latest: Can you please provide which versions you used? trunk (23/12/2014) $ ldd main linux-vdso.so.1 => (0x7fff1a3fe000) liblog4cxx.so.10 => /home/chand/share/log4cxx_build/trunk/src/main/cpp/.libs/liblog4cxx.so.10 (0x7ff965c43000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7ff96592a000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7ff965713000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7ff96534d000) libapr-1.so.0 => /home/chand/share/log4cxx_build/apr-1.5.1/.libs/libapr-1.so.0 (0x7ff965119000) libaprutil-1.so.0 => /home/chand/share/log4cxx_build/apr-util-1.5.4/.libs/libaprutil-1.so.0 (0x7ff964ef3000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7ff964bed000) /lib64/ld-linux-x86-64.so.2 (0x7ff966033000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7ff9649ce000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7ff9647ca000) libexpat.so.0 => /home/chand/share/log4cxx_build/apr-util-1.5.4/xml/expat/.libs/libexpat.so.0 (0x7ff9645a) libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x7ff964367000) > crash on program exit when no logging output is produced > > > Key: LOGCXX-449 > URL: https://issues.apache.org/jira/browse/LOGCXX-449 > Project: Log4cxx > Issue Type: Bug >Affects Versions: 0.10.0 >Reporter: Chris Morgan > Attachments: CMakeLists.txt, log4cxx-test.cpp > > > Using log4cxx and exiting the program without performing any logging results > in a crash. > Calling log4cxx::LogManager::shutdown(); appears to solve this but that isn't > documented as a requirement anywhere on the log4cxx site. > $ ./log4cxx-test > *** Error in `./log4cxx-test': free(): corrupted unsorted chunks: > 0x01efd4e0 *** > === Backtrace: = > /lib64/libc.so.6(+0x75a4f)[0x7f88dad17a4f] > /lib64/libc.so.6(+0x7cd78)[0x7f88dad1ed78] > /lib64/libc.so.6(+0x39110)[0x7f88dacdb110] > /lib64/libc.so.6(+0x39135)[0x7f88dacdb135] > /lib64/libc.so.6(__libc_start_main+0xfc)[0x7f88dacc3d6c] > ./log4cxx-test[0x4021c9] > === Memory map: > 0040-00404000 r-xp fd:00 2657668 > /home/cmorgan/projects/test/log4cxx_crash/build/log4cxx-test > 00603000-00604000 r--p 3000 fd:00 2657668 > /home/cmorgan/projects/test/log4cxx_crash/build/log4cxx-test > 00604000-00605000 rw-p 4000 fd:00 2657668 > /home/cmorgan/projects/test/log4cxx_crash/build/log4cxx-test > 01efa000-01f1b000 rw-p 00:00 0 > [heap] > 3071a0-3071a15000 r-xp fd:00 1054976 > /usr/lib64/libz.so.1.2.8 > 3071a15000-3071c14000 ---p 00015000 fd:00 1054976 > /usr/lib64/libz.so.1.2.8 > 3071c14000-3071c15000 r--p 00014000 fd:00 1054976 > /usr/lib64/libz.so.1.2.8 > 3071c15000-3071c16000 rw-p 00015000 fd:00 1054976 > /usr/lib64/libz.so.1.2.8 > 307720-3077227000 r-xp fd:00 1056493 > /usr/lib64/libexpat.so.1.6.0 > 3077227000-3077427000 ---p 00027000 fd:00 1056493 > /usr/lib64/libexpat.so.1.6.0 > 3077427000-3077429000 r--p 00027000 fd:00 1056493 > /usr/lib64/libexpat.so.1.6.0 > 3077429000-307742a000 rw-p 00029000 fd:00 1056493 > /usr/lib64/libexpat.so.1.6.0 > 3079e0-3079fb5000 r-xp fd:00 1063356 > /usr/lib64/libdb-5.3.so > 3079fb5000-307a1b5000 ---p 001b5000 fd:00 1063356 > /usr/lib64/libdb-5.3.so > 307a1b5000-307a1bc000 r--p 001b5000 fd:00 1063356 > /usr/lib64/libdb-5.3.so > 307a1bc000-307a1bf000 rw-p 001bc000 fd:00 1063356 > /usr/lib64/libdb-5.3.so > 3082e0-3082e04000 r-xp fd:00 1063622 > /usr/lib64/libplc4.so > 3082e04000-3083003000 ---p 4000 fd:00 1063622 > /usr/lib64/libplc4.so > 3083003000-3083004000 r--p 3000 fd:00 1063622 > /usr/lib64/libplc4.so > 3083004000-3083005000 rw-p 400
[jira] [Commented] (LOGCXX-448) config-thread hangs foreever in sleep if a very short lookup intervall was configured
[
https://issues.apache.org/jira/browse/LOGCXX-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256846#comment-14256846
]
chand priyankara commented on LOGCXX-448:
-
I think this requires apr build with APR_HAS_THREADS flag on...
is there any specific configurations or is it only in the provided environment?
> config-thread hangs foreever in sleep if a very short lookup intervall was
> configured
> -
>
> Key: LOGCXX-448
> URL: https://issues.apache.org/jira/browse/LOGCXX-448
> Project: Log4cxx
> Issue Type: Bug
> Components: Configurator
>Affects Versions: 0.10.0, 0.11.0
> Environment: FreeBSD-8, gcc 4.2.1
>Reporter: Ben-Alexander Altendorf
>Priority: Minor
>
> If one configure a very short intervall for watching the l4x configuration
> file application hangs forever on exit. The short lookup intervall is only to
> reproduce this error on faster machines.
> We encountered the error on our slow single cpu target machines.
> simple demo prog:
> #include
> int main(int argc, char* argv[])
> {
> std::string configFile = "test.l4x";
> log4cxx::xml::DOMConfigurator::configureAndWatch(configFile, 1);
> sleep(2);
> return 0;
> }
> hangs forever in Thread::sleep
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (LOGCXX-434) Fix some cppcheck warnings
[ https://issues.apache.org/jira/browse/LOGCXX-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267335#comment-14267335 ] chand priyankara commented on LOGCXX-434: - Patch applied. Changes seems fine. Build successfully. > Fix some cppcheck warnings > -- > > Key: LOGCXX-434 > URL: https://issues.apache.org/jira/browse/LOGCXX-434 > Project: Log4cxx > Issue Type: Bug >Affects Versions: 0.11.0 > Environment: openSUSE 13.1 / 64 Bit >Reporter: Christian Ehrlicher >Priority: Minor > Attachments: logcxx-434.patch > > > The attached patch fixes some cppcheck warnings. They're not really important > (except the uninitialized variable in HourToken class ) but I found them > during my tests with cppcheck on recent svn HEAD. It's good to see that these > warnings are the only noticeable warnings from cppcheck :) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LOGCXX-452) Applying patch
chand priyankara created LOGCXX-452: --- Summary: Applying patch Key: LOGCXX-452 URL: https://issues.apache.org/jira/browse/LOGCXX-452 Project: Log4cxx Issue Type: Sub-task Components: Core Affects Versions: 0.11.0 Environment: Ubuntu, Susue Reporter: chand priyankara Priority: Trivial Fix For: 0.11.0 Applying build warnings -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (LOGCXX-452) Applying patch
[ https://issues.apache.org/jira/browse/LOGCXX-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chand priyankara resolved LOGCXX-452. - Resolution: Fixed Patch applied to remove build warnings > Applying patch > -- > > Key: LOGCXX-452 > URL: https://issues.apache.org/jira/browse/LOGCXX-452 > Project: Log4cxx > Issue Type: Sub-task > Components: Core >Affects Versions: 0.11.0 > Environment: Ubuntu, Susue >Reporter: chand priyankara >Priority: Trivial > Labels: easyfix > Fix For: 0.11.0 > > Original Estimate: 1h > Remaining Estimate: 1h > > Applying build warnings -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (LOGCXX-434) Fix some cppcheck warnings
[ https://issues.apache.org/jira/browse/LOGCXX-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chand Priyankara reassigned LOGCXX-434: --- Assignee: Chand Priyankara Assigned to mark as resolved > Fix some cppcheck warnings > -- > > Key: LOGCXX-434 > URL: https://issues.apache.org/jira/browse/LOGCXX-434 > Project: Log4cxx > Issue Type: Bug >Affects Versions: 0.11.0 > Environment: openSUSE 13.1 / 64 Bit >Reporter: Christian Ehrlicher >Assignee: Chand Priyankara >Priority: Minor > Attachments: logcxx-434.patch > > > The attached patch fixes some cppcheck warnings. They're not really important > (except the uninitialized variable in HourToken class ) but I found them > during my tests with cppcheck on recent svn HEAD. It's good to see that these > warnings are the only noticeable warnings from cppcheck :) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (LOGCXX-434) Fix some cppcheck warnings
[ https://issues.apache.org/jira/browse/LOGCXX-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chand Priyankara resolved LOGCXX-434. - Resolution: Fixed Fix Version/s: 0.11.0 Marking as fixed since patch applied > Fix some cppcheck warnings > -- > > Key: LOGCXX-434 > URL: https://issues.apache.org/jira/browse/LOGCXX-434 > Project: Log4cxx > Issue Type: Bug >Affects Versions: 0.11.0 > Environment: openSUSE 13.1 / 64 Bit >Reporter: Christian Ehrlicher >Assignee: Chand Priyankara >Priority: Minor > Fix For: 0.11.0 > > Attachments: logcxx-434.patch > > > The attached patch fixes some cppcheck warnings. They're not really important > (except the uninitialized variable in HourToken class ) but I found them > during my tests with cppcheck on recent svn HEAD. It's good to see that these > warnings are the only noticeable warnings from cppcheck :) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (LOGCXX-442) Using non standard ports with syslog
[ https://issues.apache.org/jira/browse/LOGCXX-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chand Priyankara resolved LOGCXX-442. - Resolution: Fixed Fix Version/s: 0.11.0 Assignee: Chand Priyankara Patched with the fix to make compatible with log4j, by providing the ability to specify the port with the address. Credits to 'Ulrik' for the patch. Trunk build successfully after patch. Locally tested. > Using non standard ports with syslog > > > Key: LOGCXX-442 > URL: https://issues.apache.org/jira/browse/LOGCXX-442 > Project: Log4cxx > Issue Type: New Feature > Components: Core >Affects Versions: 0.10.0 > Environment: Windows 2012 > Reporter: nov1ce >Assignee: Chand Priyankara >Priority: Minor > Fix For: 0.11.0 > > Attachments: syslogappenderport.patch > > > Hello, > Would it be feasible to add a possibility to use non standard ports with > syslog, either by specifying the :port at the SyslogHost part, or via > additional parameter (for example: ? > It looks like it's hardcoded to 514/udp right now: > syslogwriter.cpp: > #define SYSLOG_PORT 514 > Thank you. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
