<[EMAIL PROTECTED]> wrote:
> No sweat... we CFers are just JRun guys in bunny suits anyway. :D
>
> So your hypothesis is that since you've got a smattering of updater 2,
> updater 4, and hotfix codebase you're having versioning conflicts (or...
> really... a seriously corrupted installation of JRun) that are preventing
> you from starting up successfully, right?
>
> Why not download the JRun eval version, install fresh copies with the
> current codebase, then use your license key to validate the installations? I
> know reinstalling all of it would be a big pain in the patootie, but
> still...
>
> It's better than something that doesn't work at all!
>
Yeah, that would work too. However, I finally got a response from a
Macromedia rep on the JRun forums who noted that the version
differences are definitely an issue, particularly because of the the
changes/fixes with session replication and clustering. I'm in the
process of updating my other instance now and I'll let you know how it
works out.
PS -- He also noted that this little tidbit should have been in the
release notes (clustering across different JRun builds), but got left
out somehow. So hopefully this will serve as a good warning to
others!!
Regards,
Dave.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
