Skip to main content
Inspiring
November 13, 2013
Answered

CF10 Enabled Metrics Logging but getting nulls instead

  • November 13, 2013
  • 2 replies
  • 1945 views

In an effort to troublshoot some issues I'm having I enabled metrics logging in CFADMIN but this is all I'm seeing in the metrics.log file.  What gives?

"Information","scheduler-1","11/13/13","15:59:54",,"Max threads: null Current thread count: null Current thread busy: null Max processing time: null Request count: null Error count: 21 Bytes received: null Bytes sent: null Free memory: 1737648152 Total memory: 2117206016 Active Sessions: 0"

"Information","scheduler-1","11/13/13","16:00:54",,"Max threads: null Current thread count: null Current thread busy: null Max processing time: null Request count: null Error count: 21 Bytes received: null Bytes sent: null Free memory: 1565060456 Total memory: 2117206016 Active Sessions: 0"

"Information","scheduler-3","11/13/13","16:01:54",,"Max threads: null Current thread count: null Current thread busy: null Max processing time: null Request count: null Error count: 21 Bytes received: null Bytes sent: null Free memory: 1634382744 Total memory: 2089222144 Active Sessions: 0"

"Information","scheduler-2","11/13/13","16:02:54",,"Max threads: null Current thread count: null Current thread busy: null Max processing time: null Request count: null Error count: 21 Bytes received: null Bytes sent: null Free memory: 1532903104 Total memory: 2089222144 Active Sessions: 0"

"Information","scheduler-0","11/13/13","16:03:54",,"Max threads: null Current thread count: null Current thread busy: null Max processing time: null Request count: null Error count: 21 Bytes received: null Bytes sent: null Free memory: 1371544704 Total memory: 2089222144 Active Sessions: 0"

"Information","scheduler-2","11/13/13","16:04:54",,"Max threads: null Current thread count: null Current thread busy: null Max processing time: null Request count: null Error count: 21 Bytes received: null Bytes sent: null Free memory: 1193930792 Total memory: 2089222144 Active Sessions: 0"

"Information","scheduler-3","11/13/13","16:05:54",,"Max threads: null Current thread count: null Current thread busy: null Max processing time: null Request count: null Error count: 21 Bytes received: null Bytes sent: null Free memory: 1749200240 Total memory: 2117664768 Active Sessions: 0"

"Information","scheduler-3","11/13/13","16:06:54",,"Max threads: null Current thread count: null Current thread busy: null Max processing time: null Request count: null Error count: 21 Bytes received: null Bytes sent: null Free memory: 1614707664 Total memory: 2117664768 Active Sessions: 0"

"Information","scheduler-2","11/13/13","16:07:54",,"Max threads: null Current thread count: null Current thread busy: null Max processing time: null Request count: null Error count: 21 Bytes received: null Bytes sent: null Free memory: 1485357392 Total memory: 2117664768 Active Sessions: 0"

This topic has been closed for replies.
Correct answer andrewlorien

I found the answer here : ColdFusion 11 Metrics Log NULL values | Chris Tierney

Change the connector port in CFIDE (just below where you check "enable metrics logging" to the one set as the AJP connector port in server.xml - often 8012.  You'll have to restart coldfusion.

Lots of ways to double check that, i used

grep -ir 'connector port' /opt/coldfusion10/

2 replies

andrewlorienCorrect answer
Participating Frequently
July 31, 2015

I found the answer here : ColdFusion 11 Metrics Log NULL values | Chris Tierney

Change the connector port in CFIDE (just below where you check "enable metrics logging" to the one set as the AJP connector port in server.xml - often 8012.  You'll have to restart coldfusion.

Lots of ways to double check that, i used

grep -ir 'connector port' /opt/coldfusion10/

Legend
November 13, 2013

You might like to try Java Management Extensions and use JDK tools like Jconsole to measure CF Java and Tomcat metrics.

HTH, Carl.

DCwebGuyAuthor
Inspiring
November 14, 2013

Thanks, I will look into that.  Frankly, this issue seems like just another "bug" in CF10.

January 20, 2014

anyone found a solution to this problem ?