<[EMAIL PROTECTED]> wrote:
> I'm not a Solaris guy, but I ran into an issue using Apache 2.0.48 and CFMX
> on SuSE a while back. I found a TechNote that explained how to manually do a
> custom build of the Apache JRun connector. Apparently the combination of
> CFMX 6.1, Apache 2+, and SuSE 9 weren't compatible out of the box.
>
> I'm wondering if your problem is similar? If you think it might help I'll
> run thru my links archives and see if I can find the tech note. Even if the
> specifics are different, the procedure to do a make against the Apache and
> CFMX connector libraries should be nearly identical...
>
> Eh, forget it, I just found the link. Macromedia recommends rebuilding the
> connector under various circumstances and here are the procedures:
> http://www.macromedia.com/support/jrun/ts/documents/apache_connector_rebuild
> .htm
>
> It can't hurt... it only takes 5 minutes to do.
>
> BUT, here's another document that might help. There's several Apache AND
> Solaris-specific errors listed in known issues for the JRun updater listed
> here:
> http://www.macromedia.com/support/jrun/ts/documents/updater_4_known_issues.h
> tm
>
Thanks Jared. In my experience, the only reason to need to manually
compile the web server connector is if you're on a platform that isn't
directly supported by Macromedia (and so it can't find certain system
libraries). In my case, Solaris 8 / Apache 2.0.48 is indeed a valid
configuration, so I shouldn't need to do that (nor have I needed to do
it in the past, and I've done many installations).
As for the known issues, yeah, I've looked at that page about 600
times to make sure I've done everything the way I should (as I
mentioned previously, the install was completely successful), but to
no avail. I'm beginning to lean towards the JRun version differences
at the main reason behind my problems. It would make sense that there
would be classes/jars in the Updater 4 build that don't exist in the
Updater 2 build, hence causing startup issues. Further, I had the
recent hotfix for not responding to requests (hf55681_61.jar)
installed, and it hosed my Updater 2 install because of this very
reason (I had missed the statement in the release notes that said the
patch is built on the Updater 3 code base).
While I don't need it that often, these are the times when I wish JRun
enjoyed even half of the community support ColdFusion does!! You can
see the virtual tumbleweed blow by on the JRun-specific lists/forums.
Regards,
Dave.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
