Switch from e.printstacktrace to log.trace(ExceptionUtils.getStackTrace(e)) because of log flood

[GoogleCodeExporter]

What steps will reproduce the problem?
1. signin using facebook
2. signout
3. go back to the page 

What is the expected output? What do you see instead?

Go to catalina.out and you'll see these trace attached in the file

I believe this is the culprit:

//DefaultSASHelper.java
@Override
public Profile getProfile() {
    Profile profile = null;
    SocialAuthManager manager = getAuthManager();
    if (manager != null) {
        try {
            AuthProvider provider = manager.getCurrentAuthProvider();
            profile = provider.getUserProfile();

        } catch (Exception e) {
                        //this floods the logs
            e.printStackTrace();
        }
    }
    return profile;
}

What version of the product are you using?

social-auth 2.3

P.S.
If possible can we switch logging to slf4j so we can silence or enable the bog 
via configuration??

Original issue reported on code.google.com by soc...@jeepnee.com on 16 Jul 2012 at 2:03

[GoogleCodeExporter]

attaching again the logs. I attached the wrong one

Original comment by soc...@jeepnee.com on 16 Jul 2012 at 2:15

Attachments:

• social-auth-trace.log

[GoogleCodeExporter]

Is it working fine if you don't logout.

After logging out from facebook, in grails example I am unable to get contacts 
but profile is visible.

Regards
Tarun

Original comment by tar...@brickred.com on 16 Jul 2012 at 4:34

[GoogleCodeExporter]

hello,

it is working fine with me. the problem is it floods the logs which slows down 
the server. can we for the mean time remove the printstacktrace if switching to 
slf4j will consume time??

Original comment by soc...@jeepnee.com on 17 Jul 2012 at 1:55

[GoogleCodeExporter]

Original comment by tar...@brickred.com on 16 Aug 2012 at 4:40

• Changed state: Done