FR & ACF10 & Tomcat connections

[John M Bliss]

Hi. So, I had this issue:

http://www.houseoffusion.com/groups/cf-talk/thread.cfm/threadid:64610

...and am wondering whether FR allows me to see number of Tomcat connections consumed from the pool in real-time and/or recently and/or historically. (CP for this would also be great.)

Thanks.

--
John Bliss - http://about.me/jbliss

[John M Bliss]

[crickets]  :-)

[Charlie Arehart]

John, having now read that entire thread, I would ask (before answering your direct question here):

Have you rebuilt the web server connector, as Dave and Cam recommended? I agree with that assessment 100%. If you don’t do that, then you have an old connector that is already known to be a source of problems. The whole discussion of tomcat connections could be a total red herring. I help people solve CF server problems every day, and while the failure to rebuild the connector has been the root cause of problems many times, I have not yet seen an insufficient tomcat connection count to be the root cause yet once.

Please don’t hear me scolding you, or being condescending. I have no previous knowledge of your situation. I understand why people are often scrambling to find solutions, and I liken this time to that when we moved form CF 4/5 to 6, and people were often sharing tips about how to configure the JVM, when perhaps the root cause of their problem was really something else.

I’m just trying to say that for nearly every case of CF 10 instability (where the problem “suddenly” appeared only on the move to CF10), the solution has been just rebuilding the connector.

Here’s a more specific thing you can look for: what is the date of the isapi_redirect.dll in the [cf10\config\wsconfig\1 folder? If it’s from March 2012, it’s old. If it’s from Nov 2012, it’s been updated. Then also check if you have a \2 sibling folder and see its isapi_redirect.dll file.

Let us know if that helps. If you’ve already done it, and have had problems since then, then let us know.

I will say that FR has not ever exposed any info about the details of JRun-specific things, so I doubt it would have details of Tomcat-specific things.

 

/charlie

--
You received this message because you are subscribed to the Google Groups "FusionReactor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fusionreacto...@googlegroups.com.
To post to this group, send email to fusion...@googlegroups.com.
Visit this group at http://groups.google.com/group/fusionreactor?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[John M Bliss]

Yes, I rebuilt the connector. Since doing so, the problem has not recurred. I also increased the Tomcat connection pool based on Jordan's analysis:

http://www.houseoffusion.com/groups/cf-talk/thread.cfm/threadid:64610#355611

...of my log file:

http://www.brandiandjohn.com/codeshare/isapi_redirect.log

Do you disagree with Jordan?

[Charlie Arehart]

Good to hear that you did that, and hope it helps.

You ask if I disagree with his analysis. I tried to be clear in my reply: I think that people are often overlooking the more fundamental solution. So I would say that it may not have been necessary to have made that change. That’s not quite disagreeing with it, or saying you should undo it. Just saying you may not have needed to bother, if this was the root cause problem, and solving it might then not have stressed that connector pool. Make sense?

/charlie