This document was generated from CDN thread
Created by: Jonathon Thomas on 10-07-2008 11:11:25 PM
I'm randomly seeing an error occur when calling api.addToLog(). The line I'm trying to log never shows up in the activity log, but the stack trace below shows up in the error log.
10.1.210.40.1215712892172.59.TestApp,07/10/2008 14:01:32.204,An error was encountered while attempting to log an event with the ID "custom". The error was: java.lang.NullPointerException: null The error was: java.lang.NullPointerException
java.lang.NullPointerException
at com.audium.server.session.b.a(SourceFile:3488)
at com.audium.server.session.LoggerAPI.getLoggerScratchData(SourceFile:72)
at com.audium.logger.application.activity.ByDayRotation.getAppropriateWriter(SourceFile:42)
at com.audium.logger.application.activity.ActivityLogger.log(SourceFile:177)
at com.audium.server.logger.ApplicationLoggerBase.runLogger(SourceFile:152)
at com.audium.server.logger.b$b.run(SourceFile:53)
at java.lang.Thread.run(Unknown Source)
I can't reproduce the error consistently. The call to addToLog() seems normal enough...the arguments are valid (not null).
Any ideas what causes the error?
Thanks,
Jonathon
Subject: Re: Logging exception
Replied by: Elam Birnbaum on 16-07-2008 02:27:02 PM
Hi Johnathan,
Please let me know which exact version of UE you are using. This issue looks to be a synchronization issue when attempting to log data. There were some synchronization issues in a few versions of the software that were fixed so I can let you know which update fixes the issues you are seeing once I know the version you are using.
Thanks.
Subject: Re: Logging exception
Replied by: Jonathon Thomas on 16-07-2008 03:29:31 PM
We're using CallServices 3.6.10
Subject: Re: Logging exception
Replied by: Elam Birnbaum on 17-07-2008 11:43:16 PM
Hi Johnathan,
The next release after 3.6.10, Universal Edition 6.0 fixed a couple of issues related to logging and NullPointerExceptions. While I cannot say for sure, I am fairly confident that this release resolves the issue you are seeing.
Unfortunately, the only workarounds in 3.6.10 would be to use your own logger instead of the activity logger or do not perform logging. Note that the issue is related to synchronization and will only appear in high load situations so under lower volume this should be seen less or not at all.
I'm sorry I couldn't be more help for the version you currently have. I would recommend you investigate upgrading to Universal Edition 6.0.x.
