ColdFusion 11 Will Not Start After Enabling J2EE Session Variables

Posted: January 20, 2015 in ColdFusion Servers
Tags: , , ,

Update 1/20/2015: Fix is available in the refreshed Full installers. More information on this is available here at:
http://blogs.coldfusion.com/post.cfm/coldfusion-11-installers-refreshed-has-fix-for-server-fails-to-start-on-enabling-j2ee-session-variables-and-installation-on-japanese-os

After some wicked process of elimination at CF Webtools I found out that I was unable to start/restart ColdFusion 11 after enabling J2EE Session Variables in the ColdFusion Administrator.

I went through almost all types of installs thinking it was an issue with the Amazon EC2 server it was on. Thinking this because we have CF11 servers running with J2EE enabled already.

The difference, and the the issue it turns out, is the updated installer that includes update 3 for Windows x64. The original installer doesn’t seem to have this issue.

The underlying issue is whether or not Tomcat persistent sessions were turned on or off. This apparently keeps a session alive during a restart. ColdFusion apparently doesn’t like this if it’s on.

To turn off Tomcat persistent sessions (this seems a little backwards though):

  1. Open {cf instance}/runtime/conf/context.xml
  2. Uncomment <Manager pathname=”” />
  3. Save file and close
  4. Start ColdFusion

This seems to have been an issue on ColdFusion 10 that somehow made its way back to 11.

Thanks to Derrick Anderson with BigTeams for finding this old issue at we3geeks.

I have opened bug ticket 3923565 with Adobe.

Advertisements
Comments
  1. Jeem Stot says:

    Thank you so much! This did much to help me retain my sanity. 🙂 I downloaded the new installer (with update 3) and have been at a roadblock for around two weeks trying to figure out what the heck is going on.

  2. Mike Collins says:

    Thanks Chris, this just closed a case I was working on. It would work right after we would rebuild the 3 server instances and build the cluster then it would stop restarting after some short time period, probably since it had time to build up some sessions to persist. Glad I read the RSS feed this morning.

  3. joe kus says:

    Thanks, Mr. Sanity Saver. We are running three instances. Needed to uncomment in all three in order for services to restart.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s