Re: Logging complete exception trace.

Yes I am on 2.3. On Friday, September 18, 2015, Remko Popma wrote: > Sorry, I made a mistake: %t prints out the Thread. Please replace %tEx > with %xEx. Can you show the output of that? > > Also, what version of log4j are you using? 2.3? > > Sent from my iPhone > > > On

Re: Logging complete exception trace.

Hmm, your source code looks correct. In your config, you could probably remove the named logger entry. >>> >>> >>> The alone is sufficient I think. But this won't solve the issue... Do you see this behavior everywhere or only in some places? If you replace %ex in your

Re: Logging complete exception trace.

Sorry, I made a mistake: %t prints out the Thread. Please replace %tEx with %xEx. Can you show the output of that? Also, what version of log4j are you using? 2.3? Sent from my iPhone > On 2015/09/18, at 23:27, Kiran Badi wrote: > > Ok here is the pattern changed I tried >

Re: Why is log4net not more similar to log4j(2)?

Nick, You ask and discuss on the dev list. The number of developers isn’t that large so it should be readily apparent if there is interest. That said, Log4j 1.x was pretty dormant when I started working on Log4j 2. I worked for almost 18 months before I committed anything just because I

Re: Why is log4net not more similar to log4j(2)?

On 2015-09-17, Gary Gregory wrote: > "Patches welcome" is my motto :-) > Gary > On Wed, Sep 16, 2015 at 2:42 PM, Nicholas Duane wrote: >> Sending to both the log4j and log4net mailing lists. >> I'm curious why log4net is not more similar to log4j(2)? Is it because >> there

Re: Logging complete exception trace.

Thanks Remko for reply, I think that's how I do it. Please see below the way I use it. I am on log4j2 and I have log4j-api, log4j-core and log4j-web jars in the lib directory of my web app. I import these 2 packages import org.apache.logging.log4j.LogManager; import

Re: Why is log4net not more similar to log4j(2)?

To answer your last question, at the ASF the project committers decide what they are going to do. They make decisions by discussing their ideas on the mailing list. In some ways, the ASF is a “do-ocracy”. You can make all the recommendations you want, but ultimately it is up to whoever

Re: Logging complete exception trace.

In your application, do not use logger.error(exception); but use logger.error("some message", exception); instead. The first form will take the exception object as an object and calls toString() on it, which is not what you want. Remko Sent from my iPhone > On 2015/09/18, at 18:00, Kiran

Re: Logging complete exception trace.

Ok Remko, Let me make the changes and come back. On Fri, Sep 18, 2015 at 2:57 PM, Remko Popma wrote: > Hmm, your source code looks correct. In your config, you could probably > remove the named logger entry. > >>> > >>> > >>> > > > The alone is

Re: Why is log4net not more similar to log4j(2)?

See inline.. 2015-09-18 21:21 GMT+02:00 Nicholas Duane : > "So, yes, log4net2 should be based on log4j2 and reuse all the knowledge > that has been generated within log4j2." > > While that sounds like it could mean a port I guess it doesn't necessarily > mean it is a port. I

Re: Logging complete exception trace.

Ok here is the pattern changed I tried %d{dd/MMM/ HH:mm:ss,SSS}- %c{1}: %m%tEx%n After doing this, I got this in logs, 18/Sep/2015 17:23:05,421- myclass: Got the DAO ExceptionError inserting into database. Parameter index out of range (24 > number of parameters, which is

RE: Why is log4net not more similar to log4j(2)?

I looked over the thread you included below. I can't tell from that whether the suggestion was to port log4j2. Not sure if the comment about starting log4net 2.0 "from scratch" is an indication of having it be a port of log4j2. In my mind the biggest benefit would be to have the same

Re: Why is log4net not more similar to log4j(2)?

is something like jni4net an interim solution? Use log4j2 as is, just expose the logging methods to .Net? All the guts would still be log4j2. Yes, a little icky and clunky (and possibly not even viable), but just throwing it out there *■ DOUGLAS E. WEGSCHEID* // Lead Analyst, Directories

RE: Why is log4net not more similar to log4j(2)?

I'll take a look at the link. So if I'm interested in helping, if in fact the goal is to port log4j2 to .net, then how do I know whether anyone who would make that decision is even thinking about that, if they are thinking about it how do I know if they've decided to move forward, and when

RE: Why is log4net not more similar to log4j(2)?

Given that both c# and java are very similar in both syntax and interpreter that runs the bytecode, users of log4j can expect a very steep learning curve when starting with log4net. Despite that log4net is based on log4j and thus may lack some things found in log4j2. These missing things and the