Slow to the game on this but been busy working! If you want to get in on the 64bit / Leopard beta check out Kristen’s blog.

Apple has released the first general OS update for Leopard. Full information on their site and available via Software Update.

So last geek post on a Saturday night before I go out.

Trying to get a site running which uses a lot of rewrite rules. Enable the module in the /etc/apache2/httpd.conf file, configtest and restart. That should be it, erm, no. All I saw when browsing the site was a nice 404 page. Checking in the /var/log/apache2/error_log I see the following line:

[Sat Nov 10 19:13:24 2007] [error] [client 127.0.0.1] Negotiation: discovered file(s) matching request: /Users/ianwinter/Sites/domainname/public_html/content (None could be negotiated)., referer: http://www.domainname.co.uk.local/

Now I already knew that apache2 handles the Order directive for allow & deny differently so I’d already changed the main directory block to the following to allow everything:

<Directory />
Options FollowSymLinks
AllowOverride All
Order deny,allow
Allow from all
</Directory>

Turns out after unsuccessful Google searches and me going back to trying all sorts (good old chmod -R 777 included) that unless you specifically setup a directory block for the /Users/ianwinter/Sites path it doesn’t listen.

<Directory /Users/ianwinter/Sites/*>
Options All
AllowOverride All
Order deny,allow
Allow from all
</Directory>

It doesn’t do this on Windows but I seem to recall having to do something on a RedHat system before. Maybe it’s a *NIX thing.

Having got ColdFusion 8 running in multi-server mode on Leopard I decided to try and deploy CF7 to it as well. Started out going well, following the same process I’ve always used. I created a new server, removed the default-ear, started the proxy service and stopped the web service then dropped in the cf7 ear file. Setup all the apache2 config and restarted that OK. For reference I’ve got a jrun.conf with the module in then a cf702.conf included by default with the jrun.conf in httpd.conf then a cf8.conf I include in vhosts as needed. The server started OK but when I tried browsing the cf7.local vhost I created I was shown the message:

500
java.lang.NullPointerException
at coldfusion.license.LicenseManager._isSingleIP(LicenseManager.java:171)
at coldfusion.license.LicenseManager.isSingleIP(LicenseManager.java:68)
at coldfusion.CfmServlet.getFilterChain(CfmServlet.java:66)
at coldfusion.CfmServlet.service(CfmServlet.java:103)
at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:78)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:284)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)
at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

Interesting as it’s the same box, both configured on 127.0.0.1. A reload didn’t cure it, so off to google. I found a couple of posts relating to flash remoting. The first one was over on <a href=”http://www.talkingtree.com/blog/index.cfm/2004/9/15/flashgateway”>Steven Erat’s</a> blog from way back in 2004 related to something with flash remoting. I found a few other posts saying I’d need to remove the flash remoting ear file, which, I didn’t have showing in the JMC.

I decided to take a look in the JRun4 directory to see what flash related files there were:

macmini:JRun4 ianwinter$ find . -name "*flash*"
./docs/jmchelp/gs-flash-jrun.htm
./servers/cf702/SERVER-INF/temp/cfusion.war-1439562941/CFIDE/administrator/images/flashmenu.swf
./servers/cf702/SERVER-INF/temp/cfusion.war-1439562941/WEB-INF/cfform/flash-unicode-table.xml
./servers/cf702/SERVER-INF/temp/cfusion.war-1439562941/WEB-INF/cfusion/lib/flashgateway.jar
./servers/cf702/SERVER-INF/temp/cfusion.war-1439562941/WEB-INF/cfusion/lib/flashremoting_update.jar
./servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfform/flash-unicode-table.xml
./servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/flashgateway.jar
./servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/preso/loadflash.js
./servers/samples/flashsamples-ear
./servers/samples/flashsamples-ear/ejbs/flashgateway
./servers/samples/SERVER-INF/classes/flashgateway

Some of these obviously can stay but as I don’t use flash remoting I decided to remove the flashgateway.jar and flashremoting-update.jar files. I backed up the servers directory as well first and have at this point stopped the servers.

macmini:JRun4 ianwinter$ sudo rm
./servers/cf702/SERVER-INF/temp/cfusion.war-1439562941/WEB-INF/cfusion/lib/flashgateway.jar
./servers/cf702/SERVER-INF/temp/cfusion.war-1439562941/WEB-INF/cfusion/lib/flashremoting_update.jar
./servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/flashgateway.jar

Restart all the JRun servers and browse back to cf7.local and voila it works. Bit of a faf and no good if you want flash remoting but it works. I don’t know if you remove just one of the flash remoting jar’s, like just from the cf7 server if it’d work, or, perhaps you can change mappings somewhere, solves my problem so I’m happy.

I still can’t get CF8 to start correctly on Leopard so having used Lingon previously on Tiger I downloaded the latest version from SourceForge. It’s been redesigned for Leopard as version 2.0.1 and looks really nice.

Configuration is easy, just add in a name, I choose com.adobe.jrunStartCfusion. In the “what” box just stick in “/Applications/JRun4/bin/jrun -start cfusion” and I only choose “Run it when it is loaded by the system (at startup or login)”. Once you’ve got that in hit save, reboot (I think logout would work but hey) and you’re done. Do a quick “ps -ef | grep cfusion” and you should see your CF process.

Taken via macrumours Apple have begun seeding OSX 10.5.1 to developers for testing. Seems like there’s a quite a few issues been looked into for the release.

Looks like Adobe could be announcing support for ColdFusion on Leopard and 64bit (other than Solaris) soon (hopefully). [via forta.com]