We're seeing a large number of SEVERE errors in the logs since updating to CF11,0,02,291725. Always in the following pairs. CF is now crashing about every 10-15 minutes.
We're running on Ubuntu, with external JRE. I reviewed all of SEVERE: The web application [/] created a ThreadLocal - but the errors are slightly different, and notably, a new version of Coldfusion.
Nov 03, 2014 1:52:41 PM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
SEVERE: The web application [/] created a ThreadLocal with key of type [com.sun.xml.bind.v2.ClassFactory$1] (value [com.sun.xml.bind.v2.ClassFactory$1@30124fd9]) and a value of type [java.util.WeakHashMap] (value [{class javax.xml.bind.annotation.W3CDomHandler=public javax.xml.bind.annotation.W3CDomHandler()}]) 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.
Nov 03, 2014 1:52: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@2384837]) and a value of type [java.util.GregorianCalendar] (value [java.util.GregorianCalendar[time=1415051534877,areFieldsSet=true,areAllFieldsSet=true,lenient=false,zone=sun.util.calendar.ZoneInfo[id="America/Vancouver",offset=-28800000,dstSavings=3600000,useDaylight=true,transitions=189,lastRule=java.util.SimpleTimeZone[id=America/Vancouver,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=10,WEEK_OF_YEAR=45,WEEK_OF_MONTH=2,DAY_OF_MONTH=3,DAY_OF_YEAR=307,DAY_OF_WEEK=2,DAY_OF_WEEK_IN_MONTH=1,AM_PM=1,HOUR=1,HOUR_OF_DAY=13,MINUTE=52,SECOND=14,MILLISECOND=877,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.
using built-in vs external JRE didn't make any difference. Nor did selectively turning on or off sites running on the server (there's 6 sites, none of which generate high load).
Note: currently investigating issues relating to Solr collections.
Any one seen/experienced this? have suggestions?
AdChoices