CheckThreadLocalMapForLeaks

[Aquitaine]

Our CF10 Windows server crapped out last night with a Tomcat error to the effect of 'the service is not running' (rather than a 500 from IIS or something). Found this in coldfusion-error.log:

Nov 13, 2014 12:03:41 PM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks

SEVERE: The web application [/] created a ThreadLocal with key of type [coldfusion.util.DateUtils$1] (value [coldfusion.util.DateUtils$1@101c628c]) and a value of type [java.util.GregorianCalendar] (value [java.util.GregorianCalendar[time=1418457600000,areFieldsSet=true,areAllFieldsSet=true,lenient=false,zone=sun.util.calendar.ZoneInfo[id="America/Los_Angeles",offset=-28800000,dstSavings=3600000,useDaylight=true,transitions=185,lastRule=java.util.SimpleTimeZone[id=America/Los_Angeles,offset=-28800000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2014,MONTH=11,WEEK_OF_YEAR=50,WEEK_OF_MONTH=2,DAY_OF_MONTH=13,DAY_OF_YEAR=347,DAY_OF_WEEK=7,DAY_OF_WEEK_IN_MONTH=2,AM_PM=0,HOUR=0,HOUR_OF_DAY=0,MINUTE=0,SECOND=0,MILLISECOND=0,ZONE_OFFSET=-28800000,DST_OFFSET=0]]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.

There are a couple dozen more of these.

The web application wasn't stopped at 12:03:41pm - it kept going for some time after that.

Any idea what's going on here?

[tribule]

We get this error on every start of CF10. It is something that can be ignored we have told, but if it's stopping your server then there is another issue. Does the error stop the server or do they just appear when CF is started/restarted?

[Aquitaine]

It doesn't stop the server and I haven't noticed it before - just that the server stopped serving, and the only errors we found in the logs were those.  We've had a lot of instability over the last week but typically those end in 503s rather than just 'the service it not running' (and the CF service was still running)

Odd that it would register a SEVERE error that's ignorable, but I guess that's not too unusual these days.

[tribule]

The same happens for us and Adobe have never said what causes it. There are other threads on here about it from 2012, and they are unresolved too. CF has lots of "unresolved" things, I find

Are you on update 14? We had lots of 503's with that update.