Re: Logging complete exception trace.

2015-10-10 Thread Kiran Badi
it's working, you are awesome Ralph. I own you beer mann. On Saturday, October 10, 2015, Kiran Badi wrote: > Hah let me check this silly overlook from my end. > > On Saturday, October 10, 2015, Ralph Goers > wrote: > >> In DbUtil.java you have >> >> catch (SQLException ex) { >>logger.error(

Re: Logging complete exception trace.

2015-10-10 Thread Kiran Badi
Hah let me check this silly overlook from my end. On Saturday, October 10, 2015, Ralph Goers wrote: > In DbUtil.java you have > > catch (SQLException ex) { >logger.error("Got SQLException" + ex); > } > > You are performing a string concatenation of “Got SQLException” and > ex.toString(). ex

Re: Logging complete exception trace.

2015-10-09 Thread Ralph Goers
In DbUtil.java you have catch (SQLException ex) { logger.error("Got SQLException" + ex); } You are performing a string concatenation of “Got SQLException” and ex.toString(). ex.toString() essentially will only print the message associated with the exception, which is what you said you are

Re: Logging complete exception trace.

2015-10-09 Thread Ralph Goers
Oh darn. Thanks for the reminder. I forgot to look at it when I got home and once again I am at work. I will set a reminder for myself to look at this. Ralph > On Oct 9, 2015, at 9:35 AM, Kiran Badi wrote: > > Thanks Ralph. > > Do you see anything which I can change to get it working ? > > O

Re: Logging complete exception trace.

2015-10-09 Thread Kiran Badi
Thanks Ralph. Do you see anything which I can change to get it working ? On Tuesday, October 6, 2015, Ralph Goers wrote: > I will try to look at it later this evening when I get home from work. > > Ralph > > > On Oct 6, 2015, at 10:02 AM, Kiran Badi > wrote: > > > > Hi, > > > > I realised the

Re: Logging complete exception trace.

2015-10-06 Thread Ralph Goers
I will try to look at it later this evening when I get home from work. Ralph > On Oct 6, 2015, at 10:02 AM, Kiran Badi wrote: > > Hi, > > I realised the I had zipped all project files and it was not containing the > war file > > I have now copied the war file to this shared drive, > > https:

Re: Logging complete exception trace.

2015-10-06 Thread Kiran Badi
Hi, I realised the I had zipped all project files and it was not containing the war file I have now copied the war file to this shared drive, https://drive.google.com/folderview?id=0B-D3EnvFXkj7OTV2a2t2a1I1dk0&usp=sharing Please see if someone can take a look and tell me as what I am doing wron

Re: Logging complete exception trace.

2015-10-05 Thread Kiran Badi
Hi All, Here is the link for the war file which I have created. I am on log4j2 2.3 version, tomcat 8.0.15 and JDK 1.7. Example is given as close to the issue as what I have in my application. I have not set the mysql driver so that I get exception whenever I try to connect to db. https://drive.

Re: Logging complete exception trace.

2015-09-21 Thread Kiran Badi
Ok let me build the sample war file for it and see if I can reproduce it outside of my app. Thanks for hint. On Monday, September 21, 2015, Ralph Goers wrote: > Can you provide a sample app that demonstrates this? We have a lot of > tests that don't exhibit this behavior so we really need somet

Re: Logging complete exception trace.

2015-09-21 Thread Ralph Goers
Can you provide a sample app that demonstrates this? We have a lot of tests that don't exhibit this behavior so we really need something not we can debug. Sent from my iPad > On Sep 21, 2015, at 5:11 AM, Kiran Badi wrote: > > Hi All > > How do I debug this issue now. > > Appreciate the help

Re: Logging complete exception trace.

2015-09-21 Thread Kiran Badi
Hi All How do I debug this issue now. Appreciate the help since I have log4j2 at many places. So making a change now to logging framework will consume lot of time and I seriously do not have luxury of it. On Saturday, September 19, 2015, Kiran Badi wrote: > Ok I did the change to the pattern

Re: Logging complete exception trace.

2015-09-19 Thread Kiran Badi
Ok I did the change to the pattern and now my pattern looks like, %d{dd/MMM/ HH:mm:ss,SSS}- %c{2}: %m%xEx%n 19/Sep/2015 09:29:13,975- mypackage.myclass: Got the DAO ExceptionError inserting data to db. Column count doesn't match value count at row 1 No luck :) On Fri, Sep 18, 2015 at 8:

Re: Logging complete exception trace.

2015-09-18 Thread Kiran Badi
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 2015/09/18, at 23:27, Kir

Re: Logging complete exception trace.

2015-09-18 Thread Remko Popma
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 > > %d{dd/MMM/ H

Re: Logging complete exception trace.

2015-09-18 Thread Kiran Badi
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 23).http-bio-8084-e

Re: Logging complete exception trace.

2015-09-18 Thread Kiran Badi
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 sufficient I think. > But this

Re: Logging complete exception trace.

2015-09-18 Thread Remko Popma
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 patt

Re: Logging complete exception trace.

2015-09-18 Thread Kiran Badi
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 org.apache.logging.log4j.Logg

Re: Logging complete exception trace.

2015-09-18 Thread Remko Popma
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 Ba

Logging complete exception trace.

2015-09-18 Thread Kiran Badi
Hi All, I have below log42 xml in classes folder and I am on log4j2 . This setting does not log exception and it just logs1 line exception. How do I make log4j2 to log complete exception trace in mysite log ? C:/logs/ %d{dd/MMM/