Hi Azadi,
Thanks for your comment.
we are not using cflog and also we dnt have custom logging.
We are using CFTRY CATCH BLOCK as and when required.
Regards,
Bhavesh
Main Topics
Browse All TopicsHello Experts,
I'm getting attached error in Coldfusion Application Log frequently.
Any one has idea about the same?
Did these errors are harmful?
I also don't when these error are occurs.
Please find the attached screen shot for more information.
Please guide me.
Thanks in advance.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
is your app using any framework or is it plain-vanilla cfml?
how about error handling: sure no logging is done in onError() or in error template(s)?
and what code do you run in <cfcatch> blocks, if any?
is this a prod or dev server? can you try running the app on a different server?
which cf version is this running on, btw, and what's the server os?
this is rather baffling...
Azadi
yes - good call, _agx_!
definitely check the exception.log file - but make sure you open it in a text editor like Notepad and NOT in the log viewer in cf administartor (unless you really enjoy clicking 'next' link a couple thousand times).
once it's opened in notepad, scroll to the end of it (or press ctrl+end) and work your way up from the last logged exception.
each exception in that log starts with something like
"Error","jrpp-3","11/03/09
followed by cf exception details (like "coldfusion.compiler.Inval
the jrpp-XXX is related to Thread ID you see in the application.log.
check and see if exception.log contains more info.
Azadi
the exception message may be empty, but we now know now your code is throwing a java.lang.NullPointerExcep
without seeing the code of home.cfm and Application.cfm/cfc (and any other pages included by ho,e.cfm) it's not possible to debug this further - java.lang.NullPointerExcep
Azadi
> that can happen for so many different reasons
+1
> the exception message may be empty, but we now know now your code is throwing a
> java.lang.NullPointerExcep
Yep, but what I was getting at was that it explains why there was no error description in the app logs. Because the error _message_ (not type - NullPointerException) was an empty string "". Just something to remember for the future ;-)
Business Accounts
Answer for Membership
by: azadisaryevPosted on 2009-11-02 at 06:26:09ID: 25719523
while having errors logged with blank application name is possible - i have seen runtime errors (i.e. errors in cf tags/cfcs syntax) logged with a blank application name value, even though the application did have a name set - the lack of any details is a bit misterious...
one thing i can think of is that maybe your application catches and suppresses all errors and does custom logging? maybe that custom logging code is not including the error detail in the logs?
another thought: do you have a site-wide error handler set up? does it do any logging? check the code of that template to see if maybe <cflog> tag needs changes to log the app name and error message...
the abundance of errors in the log is a bit alarming - i would not just brush this off even if on the surface your application(s) seem to be running fine...
Azadi