bpurcell.org - Step-by-Step Instruction for Clustering ColdFusion MX 6.1 - includes session replication
Calendar
SunMonTueWedThuFriSat
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30        

Subject Archives
Amazon EC2 (15)
ColdFusionMX (155)
Corvette (3)
Flash Lite (4)
Flash Media Server (5)
Flash Player (3)
Flex (39)
General Web Dev (14)
HDTV (3)
Jboss (1)
Jquery (2)
JRun (59)
Max 2003 (3)
Other (33)
PC Hardware (16)
Software (17)
SpatialKey (7)
Wireless (8)
Working Out (1)

RSS Feed
Feed Listing

Site Contents
Home
My Blog
ColdFusion
JRun
Flex
Wireless & Networking
Hardware & Gadgets
HDTV
Software Picks
Pictures
Contact Me
Search


My Articles & Papers
Flex Performance
Server/Client
mm.com Under the Hood
Multiple Instances of CFMX
Multiple Instance Config
NLB with ColdFusion
Clustering CFMX for J2EE
Multi-Tier Hardware LB w CFMX
Cisco CSS & Coldfusion MX
JRun 4 Jini based Clustering
WiFi Growth

2ID Tacweb

Other Hobbys
Body-For-Life Challenge

Personal Projects
Family Pool
Deck Gate

username:
password:
 

 
Viewing Individual Entry / Main
December 17, 2003
Based on feedback I recieved from customers running into issues clustering ColdFusion MX 6.1 with the J2EE install I wanted to put together a step-by-step procedure along with screenshots. This article is an update from my Clustering CFMX for J2EE article on the macromedia.com website.  I added all the updates for ColdFusion MX 6.1 and a work around for a 6.1 bug. I will work on putting this on the mm.com site so others can benefit. You can view the step by step instructions here. Any feedback is welcome if you think I am missing something.

Comments

One important note on sticky sessions that we ran into was that the ear files must be named exactly the same. We had created cfusion1-ear and cfusion2-ear and session replication would not work. There was a specific error in the log, something about "unable to find the folder cfusion1-ear....". I assume it was looking on our cfusion2 server at that time. Anyway, we changed both instances to cfusion1-ear and it worked. Our server admin later said that he had to change them both to cfusion-ear to get something else to work right. Not sure what that was about. So the lesson is, follow the instructions exactly and name them both cfusion-ear.


 
Page Render Time:203