Yeah !!!!!

Ray - any idea if the issue with Apache integration is an Apache issue, or an Apache on Leopard issue? I only ask because I was going to upgrade my Winders Apache to the latest version.

I don't think so as I now have everything working (thanks to Mark!)

Ray did you use the wsconfig tool to hook CF 8 to apache 2.2? I have CF working but have yet to the get the connector working despite trying wsconfig. I get an error when I use wsconfig to compile the connector. I can compile manually but then I get an error from apache saying the connector is wrong architecture.

Yes, I did. I had to use sudo and run it from the command line. Mark helped me with that.

Interesting neither a clean install or running the wsconfig tool is giving me a mod_jrun22.so that apache likes. Apache says:

Cannot load /Applications/JRun4/lib/wsconfig/1/mod_jrun22.so into server: dlopen(/Applications/JRun4/lib/wsconfig/1/mod_jrun22.so, 10): no suitable image found. Did find:\n\t/Applications/JRun4/lib/wsconfig/1/mod_jrun22.so: mach-o, but wrong architecture

Not sure what I am going wrong.

I'm not getting it to run with apache2 either. Been through all of the recompiles and still getting the same message Kurt has. Not sure what voodoo Mark Drew pulled to get his running but I'm giving up for now.

What do you mean by recompiles? I never had to recompile anything on my end.

Great . . . looks like I'm going to be upgrading to Leopard very soon - need to pick up another HD for Time Machine (don't want to wipe out the drive I'm currently using as backup - I kinda need it to back up before upgrading. ;-) Need to wrap up this project that I'm working on - going to do my darnedst best to get it finished before end of week!

Awesome. This is going to speed up my migration to Leopard.

When you go into wsconfig and setup the apache connection there is an option to compile the connector on the advanced screen. I have tried this option checked and unchecked but still have the same problem with the apache connector. I wonder if someone could post a working mod_jrun22.so so we could use that.

I finally got cf 8 connected to apache 2.2 on 10.5. Thanks to a post to the CF on Mac email list I was able to run the following two commands to get the connector to compile for my 64 bit Intel machine.

apxs -c -Wc,-arch -Wc,x86_64 -Wl,-arch -Wl,x86_64 -n jrun22 \
mod_jrun22.c jrun_maptable_impl.c jrun_property.c jrun_session.c \
platform.c jrun_mutex.c jrun_proxy.c jrun_utils.c

apxs -i -n jrun22 -S LIBEXECDIR=/Applications/JRun4/lib/wsconfig/1/ \
mod_jrun22.la

Special thanks to Ulf Unger for figuring those commands out!

@Kurt: Did you delete ALL of the JRUN directory? It seems you had an old version. Also, what kind of install did you do? Mutliserver or Standalone?

I removed JRUN completely after stopping Apache.

@Mark - I did a completely fresh install of cf 8 multiserver. I installed into a completely new directory and yet for some reason wsconfig didn't compile the right connector for me. Luckily when I was able to use Ulf's instructions for manually compiling the right connector.

I tried recompiling mod_jrun22.so from source but still get the message about being the wrong architecture. I substituted x86_64 with i386 as I'm on a MacBook - but still no luck :-(

Any ideas?

Anyone else having CF8 hang and then die? The logs keep telling me: The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

and the console tells me it can't instantiate a java virtual machine because of whatever is happening. I had initially gotten it running as a normal CF with a link to the hacked mod_jrun22.so connection to Apache2 but now, its a no go. Help!

Hi phi, I ran into this error too... but if I launch CF via

sudo /Applications/ColdFusion8/bin/coldfusion start

it works.

Has anyone been able to get ColdFusion 8 working on Leopard Server? It seems to be working on standard Leopard but not in a server environment. Any help would be appreciated.

I had the same problem as some of you installing CF8 using Apache on Leopard; and was going nuts installing/uninstalling CF hoping some magic combination of steps would do the trick. I finally got both working on my MBP with i386 chip.

I don't really understand some of the architecture behind all this, but based on a clue I found at http://www.fatcatsoftware.c..., I decided to take a peek at my apache compilation report: sudo apachectl -V:

Server version: Apache/2.2.6 (Unix)
Server built: Sep 23 2007 18:07:19
Server's Module Magic Number: 20051115:5
Server loaded: APR 1.2.7, APR-Util 1.2.7
Compiled using: APR 1.2.7, APR-Util 1.2.7
Architecture: 64-bit

But I have a 32 bit system! So I followed the hack he did to strip out the architectures I didn't want from apache:

bw-mbp:~] bwebster% cd /usr/sbin

[bw-mbp:~] bwebster% sudo cp httpd httpd-fat

[bw-mbp:~] bwebster% sudo lipo httpd -thin i386 -output httpd

And it's a miracle - after that I was able to follow the instructions to "recompile" using the apxs commands -

Hope this helps someone else who has been pulling out their hair.

Hi all, thanks for this - although I had to google for Mark Drew's site first - am I missing the obvious link on this page?

Anyway, it seems Adobe is always jsut a little (?!) bit behind OS X developments. I can not believe they still haven't got a OS X 10.5 Leopard SERVER CF8 installer out.... it's been how long now? Can they not afford the Apple Developer License? It's about 300 USD a year, I'd happily pay it for them it that's what's holding them up. Luckily they got CF8 working on Tiger Server, and it is the best combo I've ever used (with the XServe as well, that is). However, at some point, we'd really like to move on to Leopard Server, and it is approaching Q2/2008 and still no viable solution for this? That's just poor Adobe.

Thanks to all for doing Adobe's work and helping us develop for CF8 on modern machines!!
Jonas

Silly me - just discovered the blue link - apologies for my first line :-)

To be fair to Adobe Jonas, Adobe is already working on support, but they aren't just taking care of Leopard, but also supporting 64bit OSes and making other updates as well. So this isn't just something they want to 'patch'. It IS in development right now.

Thanks for this Raymond, it's good to hear such positive news from you guys who get information from Adobe. I had my hopes that it was in development, not too surprising really. The question of interest is - what is the timeframe of that development - and if they forget to fix something like the FCK-Editor in Safari during that release because they were too busy integrating Sharepoint or tweaking Exchange-integration, I might just come ranting again and expect them to provide a feedback. I'm not expecting you to answer this.

However...
perhaps you could talk to your Adobe buddies to introduce a list of upcoming changes/releases expected to be delivered in Q1/Q2/Q3 etc. in the devnet sections? That would be enormously helpful. Or does this exist, and I can't find it (very possible!). Before they block this with a comment about "never telling the outside world about new revision timeframes", I'm not expecting them to announce when Photoshop CS5X will be launched, I'm strictly referring to fixing issues with the currently released product - CF in this case..

That way developers could plan their efforts and not waste time doing things they'd expect to work by now (six month after a major OS was released I wanted to use the local CF development setup advocated on the Adobe site with CFEclipse on OS X Leopard - turns out it doesn't work - bummer!). Without comments by you or Ben (he answered my questions about the FCK-Editor compatibility with Safari: "within a few weeks"), we'd probably be left entirely in the dark as to when things will change from Adobe's side, no?

As fun as it is to re-install and tweak settings, some prefer to offer new exciting features to their clients and generally makes it easier to advocate CF in the wide world.

Currently we'll either patch wild west style, everyone doing it a little bit different, and have a working solution across modern browsers gainign the most popularity, or we resort to selling the idea of CF8's cool new features (I love them, don't get me wrong!) to the clients and then handle the distress calls that feature xyz doesn't work in the best browsers. Or Option 3 - simply not implement half of the cool new features and wait for Adobe to fix it all. Sometime.

Contrary to Adobe's policy of fixing a hundred (little and big things) months after first release, I doubt I am the only one who would sometimes welcome a TINY patch to fix ONE problem only, and get that bit out of the way. If it means I have to manually overwrite ten files in two folders to get a usable CF'ed-FCKeditor in Safari 3.x, then so be it. But I would prefer Adobe to post instructions on this and not searching the web for an hour and attemt to do it myself, only to find out that if I try this on Vista, it won't work. Or that it stops working when we're finally blessed with the Adobe CF Updater in April/May 2008.

If you're still with me, my main point is that I believe Adobe could improve a lot on managing customer expectations, and I believe it would also be better for Adobe to communicate small steps of improvements with at least a rough timeline - after all, these GOT to exist internally already.

We're not going to leave ColdFusion and Adobe if they ever miss a self-set "expected deadline", but it would help to focus development enormously if there was an indication of when what will be fixed!

End of rant.
Not directed at you.
But you're one of the few who get through to Adobe.
Hope's on the Jedi!
May the force of the CF community be with you! :-)
Feel free to forward to Adobe "CF-CEO".
Feel free to delete to clear up your page.

All the best,
Jonas

Heh, well, I have to tell you - compared to the old days, folks know a LOT more about CF updates then they used to. ;) Some things have to be kept secret of course.