We've recently posted an FAQ for JRun that details the end of new feature development plan and answers some key questions for JRun customers.
More details here: http://www.adobe.com/products/jrun/productinfo/faq/eod/
"After careful consideration and analysis of both the server marketplace and customer feedback, Adobe plans to discontinue new feature development for Adobe® JRun™ software, the fast, affordable and reliable J2EE compatible application server. However, Adobe plans to release Updater 7, the next update to JRun, in the second half of 2007, in order to meet the needs of existing JRun customers."
Basically, the ColdFusion team has taken on the JRun team and taken the product under our wing. We're actively doing enhancements to JRun needed for ColdFusion, and that will continue for the long term foreseeable future. All the enhancements that went into the embedded JRun inside ColdFusion 8 are currently being baked into Updater 7 for JRun 4, and will go through an additional round of testing and then we'll release it to JRun customers. See the FAQ for what's in there.
The pattern for the future should look something like: ColdFusion needs some enhancements, they are made in JRun, integrated into ColdFusion, then rolled back out to JRun customers in the form of future Updaters, hot fixes, security fixes, etc.
Bottom line: Adobe JRun or ColdFusion customers are in good hands.
Here are some FAQ's for ColdFusion customers with regard to the JRun end of new feature development FAQ:
Q. What does the end of new feature development of JRun mean for me as a ColdFusion developer?
A. Very little. Adobe ColdFusion software uses JRun as the bundled J2EE application server in the classic “standalone” configuration and in the “multi-server configuration.” While Adobe has announced that there will be no new feature development for JRun as an independent commercial product, it is still very well suited for its current use in ColdFusion and we will continue to update JRun to address ColdFusion requirements. This development announcement will have no impact on the functionality of ColdFusion or any of its features.
Q. Can I still deploy ColdFusion on JRun?
A. Yes. ColdFusion MX 7 and the newly released ColdFusion 8, the 8th major release of ColdFusion, both include JRun as the bundled application server.
Q. Should I move to another J2EE application server?
A. There is absolutely no need to change application servers as JRun will be supported as part of ColdFusion for the foreseeable future. However, ColdFusion also continues to support the leading J2EE application servers from top vendors, so there are plenty of choices available should you wish to change for any reason: See http://www.adobe.com/products/coldfusion/systemreqs/ for the complete list of platforms supported by ColdFusion.
Q. What does this mean for my ColdFusion support contract? Can I still get support if I'm deployed on JRun?
A. Yes! ColdFusion, deployed either on the bundled JRun or on other supported J2EE application servers, has a full range of support plans available. See http://www.adobe.com/support/coldfusion/ for more details.
Q. Does Adobe also intend to discontinue development of ColdFusion?
A. No! Adobe’s commitment to continued development of ColdFusion is very strong. The recent ColdFusion 8 release is one of the most significant releases in the product’s more than 12 year history.
Q. Will Adobe continue to support JRun?
A. Yes. Adobe will continue to honor all existing support commitments. However, we will no longer sell new Gold-level contracts for JRun as of August 3rd, 2007. All active JRun Gold support contracts will be honored through to the end of their term. Upon renewal, customers may renew into the next highest level of support for JRun – Silver support. An Adobe Support Renewal representative will contact you 60 days prior to the expiration of your support contract to help you transition to your new plan.
If you are an existing Adobe OEM partner, contact your Account Manager for assistance with your contract terms.
If you have any questions regarding your JRun support agreement, contact a customer service representative at 1-800-833-6687 for North America. Outside North America, contact http://www.adobe.com/support/contact/.
The JRun team has been hard at work on the next major version of the JRun application server, code named "Cheetah", and you're welcome to participate.
Send an email to "email@example.com" (JRun's QA Manager) requesting participation in the Cheetah Beta program if you'd like to participate.
I'm told this Beta of JRun "Cheetah" is very stable and reliable, but there are rewards waiting for anyone who can prove otherwise! :)
In addition, I've also heard the JRun team intends to give away fully functional JRun licenses to the most active Beta participants, and they're hosting a JRun "Sample Apps Challenge"...Beta users who develop sample applications exploiting the new JRun Cheetah features will have a chance to not only be rewarded, but also have their apps featured as part of the JRun Cheetah release Samples Applications area of the release.
Sounds like a great deal to me!
Besides the usual list of customer-driven bug fixes, there's lots of other added goodness, including updated JDBC drivers, web server connectors, Apache Multi-Processing Modules (MPMs) support on Unix, performance enhancements and improvements, JRun Web Server (JWS) - JWS keep-alive functionality, a new log level for HTTP requests, enhanced OS support (HP-UX 11 and 11i), Mac OSX 10.4, Solaris 10, AIX 5.3, RedHat 8, AS 2.1, AS 3.0, AS 4.0 and SuSE 8.
JRun 4 Updater 6 also adds support for JDK 1.5 (note that CF is not supported on JDK 1.5 yet, however).
The ColdFusion team has "blessed" JRun 4 Updater 6, so it's "good to go" for CF customers running CF on the full version of JRun 4.
ColdFusion customers can also rest assured that any security and other critical fixes included in JRun 4 Updater 6 have been brought back into the forthcoming CF "Merrimack" release (all install configurations), although Merrimack will be shipping with JRun 4 Updater 5+ fixes, since the timing of the two releases didn't permit us to include JRun 4 Updater 6 this time around in the installer kits.
Some useful links: