why is cftimer throwing a NPE here? <https://trycf...
# adobe
z
a
Seems OK on CF2016 & CF2018. Odd. However I'd never trust the accuracy of trycf's error behaviour given it messes with the code before running it. I'm en route to the pub to watch the rugby otherwise I'd run it in a reliable environment and see what happens.
z
yeah my thoughts as well
I'm so used to seeing a NPE and just looking up the code myself!
<cftry>
<cftimer></cftimer>
<cfcatch>
<cfdump var=#cfcatch#>
<cfabort>
</cfcatch>
</cftry>
<h1>done</h1>
java.lang.NullPointerException at coldfusion.tagext.lang.TimerTag.doEndTag(TimerTag.java:155) at cfmain16688728096562dc93fe4922d4c922d31d32da2a82d500e01a82c242ecfm1844914942.runPage(A5B8EFA2-98EC-DD71-6F7AE3BDD3846E68:2) at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:257) at coldfusion.tagext.lang.IncludeTag.handlePageInvoke(IncludeTag.java:749) at
a
@zackster it's just trycf.com. Works fine for me on a real install. Ping @abram
z
yeah, still should never NPE