Specifying the trustStore and keyStore properties

Related Categories: Breeze, CPS, Security ColdFusion, JRun,

I've written a topic on enabling SSL and another topic which talks about debugging SSL, but what if you don't want to use the default cacerts or keystore (trustStore) files? Or, what if you have to install a new jvm for DST compliance, but don't want to share certificate stores among Java apps? What if you have a centralized file you want all of your Java apps to use to enable SSL. In these cases you can use the Java system properties to configure these files at runtime.

[More]

Comments (2) | Print | Send | del.icio.us | Digg It! | Linking Blogs

JRun: End of feature development

Related Categories: ColdFusion, JRun

Friday, August 3, 2007 Adobe announced the end of feature development for JRun server. What this means is there will not be a JRun 5. Adobe will continue to sell JRun 4 and continue to bundle JRun 4 with ColdFusion. The EOD announcement includes info about support plans. Technote kb402448 provides more detailed information on the EOD impact on ColdFusion.

Comments (1) | Print | Send | del.icio.us | Digg It! | Linking Blogs

JRun system log file rotation

Related Categories: ColdFusion, JRun

Some readers are aware of setting JRun log file rotation size and number in the jrun.xml. However the JRun stderr and stdout system logs do not conform to these settings. Last year Adobe released technote 8698aeb8 which contained a hot fix for bug 59486. When JRun is run as a Windows service, the stderr (jrun.server.name-err.log) and stdout (jrun.servere.name-out.log) do not rotate, thus greatly increasing their size until they become eventual server bottlenecks. The hot fix allows administrators to configure a file rotation size with the jrunsvc.exe. The hot fix also requires CFMX 7.0.1+ (Server configuration) or JRun 4 Updater 5+. I had a customer run into this issue and it became apparent that not everyone is aware of this hot fix, nor of the fact that the FileLogEventHandler settings in jrun.xml do not apply to the JRun system logs. Those settings only apply to what are known as the JRun Event logs -- event, debug, info, warning, user, and metrics. So what you'll see is the coldfusion-event.log rotating at about 200k (or the current rotationSize value); however, the coldfusion-out.log will continue to grow past 200k (typically a few hundred MBs). Applying the hot fix and specifying a log rotation size will cause the coldfusion-err.log and coldfusion-out.log to rotate at the specified value.

Comments (2) | Print | Send | del.icio.us | Digg It! | Linking Blogs