ColdFusion 10.0  -  Bug 3653076

Created on Tuesday, October 22, 2013

Login for more options

Title

Bad apache / tomcat connector for Mac OSX Mavericks 10.9

Description

Problem Description: the apache connector for ColdFusion 10 on Mac Osx 10.9 (Mavericks) does not work. Apache fails to start with a sigterm error when it hits the line to process:

in /etc/apache2/httpd.conf
Include "/private/etc/apache2/mod_jk.conf"


Steps to Reproduce: Do a plain install of ColdFusion 10, server edition, apache connector for /etc/apache2/ on a Mac OSX 10.9 (Mavericks) machine - any.

Actual Result: Apache fails to start, ColdFusion Administrator page can not be launched and further updated.

Expected Result:

Any Workarounds:
Uninstall ColdFusion - not a work around but at least it returns Apache to a working state or comment out the above line referenced in httpd.conf.

Another note: if you use in a terminal: sudo apachectl -e debug I get the following:
[[Tue Oct 22 21:44:19 2013] [debug] mod_so.c(246): loaded module jk_module
/usr/sbin/apachectl: line 90: 62575 Abort trap: 6 $HTTPD $ARGV

That last line about the Abort trap: 6 and $HTTPD $ARGV lead me to believe that there is something in this modified connector in /Applications/ColdFusion10/config/wsconfig/1/mod_jk.so that is the crux of the problem.

Test Configuration

My Hardware and Environment details:
Osx 10.9 Mavericks
Model Name: MacBook Pro
Model Identifier: MacBookPro10,1
Processor Name: Intel Core i7
Processor Speed: 2.8 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 16 GB
Boot ROM Version: MBP101.00EE.B03

App Language(s) English
OS Language(s) English
Platform(s) Mac 10.6 for Intel
Browser(s) Browsers All

Notes (79)

  • jcelias

    9:20:40 AM GMT+00:00 Feb 11, 2014

    I managed to fix my problems by following this guide: http://www.cfdad.com/2012/11/02/reconfigure-apache-connector-on-mac-mountain-lion-cf10/

    I hope that can help at least some of you...

    In any case, I really do not understand why Adobe makes Coldfusion developers' lives so hard...

    Tip: After you manage to get Coldfusion working again, go to the coldfusion administrator, then Settings, and click on the "Clear Template Cache Now" button.

    If you don't do that, and like me, was trying some local coldfusion page to bring it up, that page will continue failing.

  • Sean Coyne

    8:55:33 AM GMT+00:00 Feb 11, 2014

    Well, lets see... If you had to comment out that file to get Apache to start, where do you think you should look? Perhaps IN that file? Maybe?

    Again, this is not the appropriate forum for help. Did you re-run the apache connector after installing updater 13, as the instructions specify you need to? Again, don't answer this question here. This will be the last reply I make on the subject. You need to determine where in your config apache is having a problem and fix that problem. Try the apache config test, "sudo apachectl configtest" which will point out obvious syntax issues. My guess is that you didn't re-run the connector. Considering the bug is IN the connector, this is a pretty important step.

  • jcelias

    8:48:48 AM GMT+00:00 Feb 11, 2014

    Wilgeno,

    Yes, I did make a backup, and yes, I did copy only the settings.

    Sean Coyne,

    I had no clue that the coldfusion launcher Adobe left installed when I upgraded from CF9 to CF10 a year ago was deprecated (Adobe's installer should have removed it when we upgrade to CF10).

    In any case, I had CF10 working perfectly on OS X 10.8, and after I applied the Update 13 patch I upgraded to OS X 10.9 and now things don't work.

    So my question is very simple: What changes should I make to my system to have CF10 working again on OS X 10.9 Mavericks???

    So far I have apache running, but when I call a .cfm page all I get is the source code displayed (meaning, obviously, that apache is simply returning the file, and not sending it to the coldfusion preprocessor). So, how can I tell apache to use coldfusion again?

    Note that I had to comment out the line that said Include "/private/etc/apache2/mod_jk.conf" in httpd.conf to have apache running again.

  • Adam Cameron.

    8:47:07 AM GMT+00:00 Feb 11, 2014

    How the fuck do I UNwatch a bug in this thing?

    --
    Adam

  • Sean Coyne

    8:43:22 AM GMT+00:00 Feb 11, 2014

    @jcelias you are mixing up CF 10 and CF 9. Anything "JRun" related is CF9, so it has no bearing on CF10. Perhaps you have your apache config mixing the two. In any case the bug report is not an appropriate forum for issues like this. Try the CF forums on the Adobe site or StackOverflow or ServerFault (probably the better option in this case). As Wil said, any OS X upgrade will overwrite your Apache configuration files. It is up to you to back them up and then either restore them or make the appropriate changes to get them functional again.

  • Wilgeno

    8:41:52 AM GMT+00:00 Feb 11, 2014

    jcelias I would have hope that telling you this is a new version of apache that you would just copy the settings you needed from the old file to the new one. (facepalm) You did save a copy of the new httpd.conf file? right?

  • jcelias

    8:36:33 AM GMT+00:00 Feb 11, 2014

    Wilgeno,

    If I replace httpd.conf with the old one, apache does not start.

    I figured it had to do with this line:

    Include "/private/etc/apache2/mod_jk.conf"

    Which commented...

    #Include "/private/etc/apache2/mod_jk.conf"

    And that allowed Apache to reload and work again, BUT coldfusion still does not work.

    Also, if I try to manually launch Coldfusion from the Coldfusion launcher I get an error saying that it cannot launch coldfusion, and to please check the logs.

    I check the logs and I get this error:


    ------ LOGS START -------

    Error when opening jrun.xml: /Applications/JRun4/servers/cfusion/SERVER-INF/jrun.xml. Make sure file has the proper permissions ( read/write ).
    java.lang.NullPointerException
    at java.io.File.<init>(File.java:222)
    at jrunx.launcher.GUIView$9.actionPerformed(GUIView.java:635)
    at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2028)
    at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2351)
    at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
    at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
    at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
    at java.awt.Component.processMouseEvent(Component.java:6414)
    at javax.swing.JComponent.processMouseEvent(JComponent.java:3275)
    at java.awt.Component.processEvent(Component.java:6179)
    at java.awt.Container.processEvent(Container.java:2084)
    at java.awt.Component.dispatchEventImpl(Component.java:4776)
    at java.awt.Container.dispatchEventImpl(Container.java:2142)
    at java.awt.Component.dispatchEvent(Component.java:4604)
    at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4618)
    at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4279)
    at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4209)
    at java.awt.Container.dispatchEventImpl(Container.java:2128)
    at java.awt.Window.dispatchEventImpl(Window.java:2492)
    at java.awt.Component.dispatchEvent(Component.java:4604)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:717)
    at java.awt.EventQueue.access$400(EventQueue.java:82)
    at java.awt.EventQueue$2.run(EventQueue.java:676)
    at java.awt.EventQueue$2.run(EventQueue.java:674)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:86)
    at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:97)
    at java.awt.EventQueue$3.run(EventQueue.java:690)
    at java.awt.EventQueue$3.run(EventQueue.java:688)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:86)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:687)
    at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:296)
    at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:211)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:201)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:196)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:188)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)

    -------- LOGS END -------

    And based on that error, I try to find the path /Applications/JRun4/servers/cfusion/SERVER-INF/jrun.xml
    but it does not exist, since all I can find is that in the /Applications/JRun4/servers/cfusion/ directory is just one subdirectory called cfusion-ear/

    So what now???

  • Wilgeno

    8:19:18 AM GMT+00:00 Feb 11, 2014

    jcelias If you have not used apache since you upgraded to Mavericks, then the first thing you need to do is go find your old httpd.conf file. Upgrading OS X replaces your httpd.conf with a new one. You old one is saved in /etc/apache2/ as httpd.conf.pre-update. This is well known and expected behavior when upgrading OS X because Apache gets upgraded too.

  • jcelias

    8:09:26 AM GMT+00:00 Feb 11, 2014

    So I took the risk for everyone, and did the following:

    1. Installed Update 13 for Coldfusion from the Coldfusion administrator.

    2. Installed Mavericks (from the App Store update).

    3. Now when I call my coldfusion websites they are not recognized. It is as if Apache had forgotten how to pass .cfm requests to Coldfusion...

    So now I'm left with a workstation I cannot develop on... Great. Thanks Adobe...

    Question to others: Any ideas of what the setting should be in httpd.conf to get this working again on Mavericks? I'm about to use TimeMachine to see what happens if I restore to a previous httpd.conf file...

    p..s: This is *frustrating*, and I'm *extremely* disappointed at Adobe because of the way it is handling this issue...

    p.p.s.: Adobe, how about you write a simple step-by-step guide on how to upgrade an existing coldfusion installation to OS X 10.9???

  • lolajl

    4:18:17 PM GMT+00:00 Feb 10, 2014

    Sorry for the repeated posting . . . whenever this page got reloaded it kept sending out the cached text.

  • lolajl

    4:17:05 PM GMT+00:00 Feb 10, 2014

    Trying both Download and Download & Install results in:

    Error occurred while installing the update:
    Failed Signature verification

    I am on OS X Mavericks.

  • Anit Kumar Panda

    4:02:12 PM GMT+00:00 Feb 10, 2014

    @lolajl You need to install the mandatory update before you update the server.
    Here is the link http://helpx.adobe.com/coldfusion/kb/coldfusion-10-update-13.html with the instructions. If you still facing any challenge, please send at email to cfinstal<AT>adobe<DOT>com

  • lolajl

    11:48:51 AM GMT+00:00 Feb 10, 2014

    Trying both Download and Download & Install results in:

    Error occurred while installing the update:
    Failed Signature verification

    I am on OS X Mavericks.

  • anilnatha

    11:36:47 AM GMT+00:00 Feb 10, 2014

    I was getting the same error that lolajl was encountering, but worked around it by going to this URL, http://helpx.adobe.com/coldfusion/kb/coldfusion-10-update-13.html and downloading the jar file and installing the update via terminal.

  • lolajl

    11:26:43 AM GMT+00:00 Feb 10, 2014

    Trying both Download and Download & Install results in:

    Error occurred while installing the update:
    Failed Signature verification

    I am on OS X Mavericks.

  • Wilgeno

    11:26:40 AM GMT+00:00 Feb 10, 2014

    @lolajl There is a mandatory update that has to be installed before you can use the built in update system

    http://www.trunkful.com/index.cfm/2014/1/10/ColdFusion-10-on-OS-X-109-Mavericks

    http://helpx.adobe.com/coldfusion/kb/coldfusion-10-update-13.html

  • Anit Kumar Panda

    11:21:04 AM GMT+00:00 Feb 10, 2014

    @anilnatha: Open the server.xml at \ColdFusion10\cfusion\runtime\conf\ and search for (internal webserver start). Uncomment the connector section and restart CF service. You can then access the CF admin by
    http://ip:port/CFIDE/administrator/index.cfm where port no is the mentioned inside the connector section in server.xml. By default it is 8500.

  • anilnatha

    11:14:39 AM GMT+00:00 Feb 10, 2014

    @seancoyne, thank you for that tip. I didn't know you could change the the CF server to make use of the Apache configuration after CF server was installed. I'll give that a try. Thanks!

  • lolajl

    11:13:25 AM GMT+00:00 Feb 10, 2014

    Trying both Download and Download & Install results in:

    Error occurred while installing the update:
    Failed Signature verification

    I am on OS X Mavericks.

  • Sean Coyne

    10:37:28 AM GMT+00:00 Feb 10, 2014

    @anilnatha just use the built in web server and connect to apache AFTER you install the updater

  • anilnatha

    8:56:26 AM GMT+00:00 Feb 10, 2014

    Hello Anit, that course of action will not work. Reason is because once CF10 is installed, I'm unable to access the ColdFusion Administrator Panel to finish the installation and setup in order to patch the update. The errors in my console after installing via the DMG state that this plugin is the reason for failures. The settings I chose during my installation was to make use of my Apache configuration instead of using the builtin server and I also disabled the option to auto start CF at boot. I don't know if that helps you or not, but your recommended course of action is not sufficient for my problem. If you need more information, please let me know.

  • Anit Kumar Panda

    6:09:47 PM GMT+00:00 Feb 9, 2014

    The fix is included in Update 13 only. This is not incorporated within the DMG installer at Adobe's site. After installing CF10 from the DMG installer, please apply CF10 Update 13, to make it work with OS X Mavericks.

  • anilnatha

    6:01:05 PM GMT+00:00 Feb 9, 2014

    Has this update made its way into the DMG installer for CF10 that is available from the Adobe website? I have come across this issue while attempting to install CF10 on my MacbookPro running 10.9.1 using the .dmg I downloaded from the Adobe website this evening. The crash logs I viewed from the Console app referred to the 'mod_jk.so' plugin as the problem. So although "Update 13" has been released, I'm unable to successfully install CF10 using the available installer from Adobe.

  • Piyush Kumar Nayak

    6:21:10 AM GMT+00:00 Jan 10, 2014

    The fix for this bug has been incorporated and released as Update 13 for CF10. You should get an auto notification in the CF admin console to download and install it.
    For further details you may refer the following article:
    http://helpx.adobe.com/coldfusion/kb/coldfusion-10-update-13.html

  • jcelias

    12:31:34 AM GMT+00:00 Dec 30, 2013

    So what's the drill?

    How do we upgrade to Mavericks and where can we find the patch?

    Do we apply the patch and then upgrade to Mavericks and all will work well? or is there some command-line work we need to do to get this going?

    This is getting *ridiculous*. No one can upgrade their machines to OS X Mavericks simply because of this issue. I'm already looking at alternatives to Adobe's Coldfusion, this is unacceptable behavior from Adobe's part.

    Check this out: http://openbd.org

  • DL Murphy

    6:11:11 AM GMT+00:00 Dec 23, 2013

    @Rupesh or @Piyush - can you give us a date when ColdFusion 10 Update 13 will be available? My computer is getting refreshed this week at work so I'm getting a new MacBook Pro running Mavericks. I'm trying to figure out what I need to do for ColdFusion. If this update is available soon, that would be great timing. So, can you give us a date? Thanks.

  • rezengine

    8:26:12 AM GMT+00:00 Dec 11, 2013

    This issue is marked as fixed, but can anyone show me how to find or apply this fix? My dev machine is now out of action. I hadn't noticed as I'd been working on non-CF bits with no problem.

    I actually use the Apple Server App, but underneath that is simply a wrapper to Apache. Should still work and should have been tested and patched well in advance.

    Really want to dump CF and go with another language, but as a working professional that's not something you can do overnight. Clients can't wait for me to learn something new before I can build their sites!

  • MarcinSz

    8:38:14 PM GMT+00:00 Dec 9, 2013

    @CFDad - I guess you can always still install it and run it with the internal web server to get it patched up, and then do the web server connector. Not ideal, but it doesn't totally "brick" the install to not have this in the downloadable installer.

  • CFDad

    8:25:27 PM GMT+00:00 Dec 9, 2013

    @Rupesh, that's nice that the fix will be in a ColdFusion update, but the problem is in the ColdFusion installer DMG for Mac. How can a Mac user, who has to reinstall ColdFusion due to an upgrade to Mavericks even get a working version of ColdFusion going in the first place? Will there be an updated ColdFusion Developer/Server installer for Mac released soon, and if so when?

  • Rupesh Kumar

    8:16:12 PM GMT+00:00 Dec 9, 2013

    Sorry for the confusion folks. This has been fixed in both CF 10 & CF 11 and the fix is scheduled to come in CF 10 update 13. Piyush missed including the second part :-)

  • jcelias

    4:53:51 PM GMT+00:00 Dec 9, 2013

    A workaround for some (and yes, I admit it is a royal pain in the rear): If you use Parallels Desktop, you could install the Developer version of CF10 on Windows inside your Mac, and develop on Windows until Adobe gives us a proper fix for CF10 users on OS X, or until CF11 makes its grand appearance on OS X...

  • xiinteractiv

    1:05:47 PM GMT+00:00 Dec 9, 2013

    @jcelias - its not just stopping developers from upgrading... if you haven't upgraded you can still work.

    Many of us have already upgraded to OSX Mavericks and for CF development we are dead in the water... with no help on the way. Simply put, we cannot develop in CF at all on our OSX Mavericks macs.

  • Wilgeno

    10:20:44 AM GMT+00:00 Dec 9, 2013

    So yet again Adobe has decided to just not support a widely used platform. Again the issue here isn't OS X! The issue is Adobe failing to support newer versions of APACHE Web server. Apache is one of the most widely used web servers out there. Adobe has failed! Again! Saying you will add support in the next version of ColdFusion isn't a valid solution. This will affect more than just OS X users. It will affect anyone trying to use the newer versions of Apache. See this bug for more proof that Adobe is essentially ignoring Apache. https://bugbase.adobe.com/index.cfm?event=bug&id=3651785

  • xiinteractiv

    10:13:47 AM GMT+00:00 Dec 9, 2013

    @jcelias - its not just stopping developers from upgrading... if you haven't upgraded you can still work.

    Many of us have already upgraded to OSX Mavericks and for CF development we are dead in the water... with no help on the way. Simply put, we cannot develop in CF at all on our OSX Mavericks macs.

  • yuri.vorontsov

    10:13:31 AM GMT+00:00 Dec 9, 2013

    Dear Adobe, is this some sort of sick joke? This answer is laughable to say the least. It should be in a hotfix and not in the 'next version' Thanks for making me very easy to advise my customers about dealing with ACF ever again after been onboard since 1998. Good bye and thanks for all the fish.

  • xiinteractiv

    10:04:20 AM GMT+00:00 Dec 9, 2013

    saying you fixed it in CF11 is the WRONG ANSWER - it doesn't help anyone today. So I guess you expect all the CF developers on Mac to just stop working on everything CF until you release CF11??? If the CF11 release date is sometime in the next few days then you might make us happy.

    What you are saying is you really don't grasp the problem and furthermore... you just plain don't care.

    Maybe we should stop talking about the CF10 fix in this thread and use it to discuss CF alternatives that will work on the Mac platform.

    Earth to Piyush Kumar Nayak - did you fall off the planet or something? You need to ESCALATE this issue and get us a reasonable ETA for the fix. The longer you delay the worse the problem gets.

  • Adam Cameron.

    9:10:30 AM GMT+00:00 Dec 9, 2013

    Just on the basis that this has 46 votes and 42 comments, if I was Adobe, I'd just suck it up and get the fix out for CF10 as an exercise in PR.

    This is all dragging out a bit too much, innit?

    --
    Adam

  • jcelias

    8:53:07 AM GMT+00:00 Dec 9, 2013

    If this bug was fixed for CF11 that is *unacceptable* to us developers who have spent time and money on CF10!!!

    CF11 is not even out yet (anyone knows *when* it will be out btw?), and we cannot stop our production process moving to OS X Mavericks simply because Adobe did not bother to test CF10 with it.

    I'm *very* disappointed at the way Adobe is handling this issue, and I'm also having second thoughts about the long-term prospects of CF with this attitude Adobe has in relation to us developers.

    Does anyone know of a way to get to top managers at Adobe so they can check this issue out. I think the top-level managers must be unaware of the severity of this problem and the urgency to fix it correctly. They're literally single-handily stopping thousands of OS X developers from upgrading to OS X Mavericks with this tactic!!!

  • xiinteractiv

    8:46:03 AM GMT+00:00 Dec 9, 2013

    saying you fixed it in CF11 is the WRONG ANSWER - it doesn't help anyone today. So I guess you expect all the CF developers on Mac to just stop working on everything CF until you release CF11??? If the CF11 release date is sometime in the next few days then you might make us happy.

    What you are saying is you really don't grasp the problem and furthermore... you just plain don't care.

    Maybe we should stop talking about the CF10 fix in this thread and use it to discuss CF alternatives that will work on the Mac platform.

    Earth to Piyush Kumar Nayak - did you fall off the planet or something? You need to ESCALATE this issue and get us a reasonable ETA for the fix. The longer you delay the worse the problem gets.

  • Adam Cameron.

    7:57:18 AM GMT+00:00 Dec 9, 2013

    Isn't the issue here that it's not supported in *ColdFusion 10*? Fixing it in CF11 ain't much help to anyone.

    --
    Adam

  • lolajl

    7:37:07 AM GMT+00:00 Dec 9, 2013

    Let me see if I understand this - the upcoming version as in, CF11?

  • Piyush Kumar Nayak

    5:41:05 AM GMT+00:00 Dec 9, 2013

    This bug has been fixed for the upcoming version of CF.

  • MikeMcConnell

    5:20:21 AM GMT+00:00 Dec 6, 2013

    @xiinteractiv: You can add me to that list as well. I've already started porting applications over to Railo. It's faster and I have yet to run in to compatibility issues (not to mention it's free). For me, Adobe started losing it's luster about the time they abandoned the Flex/Flash platform. Looks like they're heading that way with ColdFusion as well. It was a good ride, but time to move on.

    M. McConnell

  • xiinteractiv

    5:45:09 PM GMT+00:00 Dec 5, 2013

    TO ADOBE:

    It has been nice using CF all these years, but your lack of appropriate response on this issue is unfortunately the last straw for me. I have been a loyal CFer for about 12 years.

    Not any longer.

    From this point forward I will not build any new sites in CF. I will maintain the ones that have to be maintained and eventually migrate them all to another platform other than CF.

    Unfortunately, I don't think you [Adobe] care. But you will, because there are a lot of CFers making the same decision and your loyal customers are dwindling.

  • lolajl

    3:10:34 PM GMT+00:00 Dec 5, 2013

    I looked for #3679774 but couldn't find it . . . has anyone been able to find this bug report?

  • CFDad

    2:57:37 PM GMT+00:00 Dec 5, 2013

    If this is fixed, where is the fix? The installer still does not work on OSX 10.9 Mavericks. Please keep this ticket open until so.

  • TroyAllenSr

    10:33:11 AM GMT+00:00 Dec 5, 2013

    How is this one "Fixed"? Was there a patch released that included this fix?

  • Piyush Kumar Nayak

    11:49:02 PM GMT+00:00 Dec 4, 2013

    logged another bug #3679774 for Apache restart issue. closing this.

  • ac iLiv

    3:36:51 PM GMT+00:00 Nov 25, 2013

    Mike's mod_jk.so works for us. Thank you Mike!!

  • ac iLiv

    2:54:39 PM GMT+00:00 Nov 25, 2013

    Mike's mod_jk.so works for us. Thank you Mike!!

  • ac iLiv

    1:42:44 PM GMT+00:00 Nov 25, 2013

    Mike's mod_jk.so works for us. Thank you Mike!!

  • mikenicholls

    8:24:28 PM GMT+00:00 Oct 30, 2013

    The Apache Tomcat bug report is here: https://issues.apache.org/bugzilla/show_bug.cgi?id=55696

  • CFDad

    7:55:01 PM GMT+00:00 Oct 29, 2013

    I too had trouble with the file Mike posted, but I figured out how to fix and compile, thanks to Mike Nicholls. I wrote out some instructions if it helps anyone else:
    http://www.cfdad.com/2013/10/27/how-to-compile-adobe-coldfusion-10-apache-connector-for-osx-mavericks-10-9/

  • MikeMcConnell

    12:19:32 PM GMT+00:00 Oct 27, 2013

    Ahhh...Thank you. I didn't notice that before.

    MLM

  • CFDad

    12:10:17 PM GMT+00:00 Oct 27, 2013

    @Mike McConnell, the status of the bug got changed to "ToFix", and the reason "BugVerified" - I think that is promising. but I wish Adobe would chime in here and say whats going on.

  • MikeMcConnell

    12:07:11 PM GMT+00:00 Oct 27, 2013

    Has Adobe even acknowledged this problem yet? It's been 4 days, now. Does anyone else find that concerning?

  • MikeMcConnell

    12:05:08 PM GMT+00:00 Oct 27, 2013

    Has Adobe even acknowledged this problem yet? It's been 4 days, now. Does anyone else find that concerning?

  • CFDad

    12:34:57 AM GMT+00:00 Oct 26, 2013

    I can confirm that I followed Mike's directions, recompiled from the connector source after changing the exact same lines with his fix and it's working on my machine now.

  • CFDad

    10:10:37 PM GMT+00:00 Oct 25, 2013

    I can confirm that I followed Mike's directions, recompiled from the connector source after changing the exact same lines with his fix and it's working on my machine now.

  • David Dykstra

    8:01:50 AM GMT+00:00 Oct 25, 2013

    Mike's file is working for me as well.

  • CFDad

    11:57:29 PM GMT+00:00 Oct 24, 2013

    weird, Mike's file isn't working for me. It's just not processing

  • yuri.vorontsov

    12:03:26 PM GMT+00:00 Oct 24, 2013

    Thank you Mike, I managed to get it up and running.

  • TroyAllenSr

    7:04:55 AM GMT+00:00 Oct 24, 2013

    FYI...the Apple updater also replaces your httpd.conf file, but luckily it makes a backup for you. Read more here...

    http://mallinson.ca/post/web-development-with-mavericks/

  • joebrislin

    5:11:58 AM GMT+00:00 Oct 24, 2013

    Mike, Thanks for the fix! Your file worked great!

  • broberts360

    4:00:23 AM GMT+00:00 Oct 24, 2013

    Also confirmed Mike's file works...

  • broberts360

    3:58:30 AM GMT+00:00 Oct 24, 2013

    Also confirmed Mike's file works...

  • cielen.com

    8:39:20 PM GMT+00:00 Oct 23, 2013

    +1 - just tested Mike's file and it works fine

  • jonsteenbergen

    6:08:39 PM GMT+00:00 Oct 23, 2013

    Confirming Mike's file works for me.
    Thanks Mike!

  • broberts360

    3:54:56 PM GMT+00:00 Oct 23, 2013

    Also confirmed Mike's file works...

  • Giancarlo Gomez

    3:37:54 PM GMT+00:00 Oct 23, 2013

    Mikes Version works for me as well .. ridiculous that the CF Team has not been testing this or ready for it .. same goes for Creative Cloud .. their app is currently incompatible with Mavericks ... pretty lame if you ask me

  • Manko Timur

    2:56:45 PM GMT+00:00 Oct 23, 2013

    Mike's version of jk_map.so works good for me.
    Mike, thank you

  • broberts360

    2:56:32 PM GMT+00:00 Oct 23, 2013

    Also confirmed Mike's file works...

  • Sean Coyne

    2:20:29 PM GMT+00:00 Oct 23, 2013

    I can confirm that Mike's recompiled version does work

  • MarcinSz

    2:11:40 PM GMT+00:00 Oct 23, 2013

    Adobe - what's the rationale for using a custom mod_jk instead of the standard Tomcat connector? All it seems to cause is headaches every time something is updated.

  • mikenicholls

    2:10:31 PM GMT+00:00 Oct 23, 2013

    Recompiling after making a small changed worked fine for me, Adobe do provide their version of the source:
    http://helpx.adobe.com/coldfusion/kb/rhel-connector-configuration/_jcr_content/main-pars/download_1/file.res/connector-source.zip

    I replaced this line in /native/common/jk_map.c:
    strcpy(buf, rc);
    with:
    memmove(buf, rc, len + 1);

    I'm not a C programmer so I can't guarantee I've introduced some horrible bug, but things have been working for me so far. Here's the copy I'm using if anybody else wanted to try:
    https://skydrive.live.com/redir?resid=ACCA7C11400D15FA!618&authkey=!AOZJmH3HBrjvJ7s

  • TylerSilcox

    1:07:04 PM GMT+00:00 Oct 23, 2013

    To add to the description, this is error that's written to the log when the mod_jk is included in httpd:

    "httpd[...]: detected source and destination buffer overlap"

    Which then prevents the apache from (re-)starting up.

  • Nik S.

    12:28:33 PM GMT+00:00 Oct 23, 2013

    @Sean Coyne
    Point taken, just seems every major OS X release causes newfound headaches with CF. Adobe has clearly stated that their mod_jk will only work with Apache up to 2.2.22, but hasn't done anything about it when 2.4 has been out for what, 2 years now?

  • Sean Coyne

    12:14:48 PM GMT+00:00 Oct 23, 2013

    @Nik S all Apple has done is upgrade Apache modestly (from 2.2.22 to 2.2.24, not even the latest which is 2.4.x). Not to mention that Apple has had builds of OS X 10.9 available for months for members of the developer program which of course Adobe is one.

    On a side note, if you use MAMP Pro and the version of Apache that comes with it (2.2.22 at this time) the connector works fine.

  • Nik S.

    12:11:27 PM GMT+00:00 Oct 23, 2013

    Not sure why Apple insists on screwing things up with every new version, but this is affected my local dev as well. It would be great if Adobe could release an update ASAP for this!

Duplicate ID
Reported By CFDad

Status

State Closed
Status Fixed
Reason

Importance

Priority 4-Very High
Frequency All users will encounter
Failure Type Non Functioning
Product Area Installation/Config

Build

Found In Build Final
Fixed In Build 286522

Attachments (0)

No Files Attached

Votes (48)

  • QUICKSTEP25

    3:06:16 AM GMT+00:00 Jan 15, 2014

    I think it is obvious why this bug impacts productivity. Unless I work on one web site project at a time... sure that sounds like a wonderful working business model that I can pitch to my clients.

  • tmathias

    4:02:19 PM GMT+00:00 Jan 7, 2014

    I'm a longtime CF developer, and to not be able to use CF on my Mavericks laptop is incredibly frustrating.

  • rezengine

    6:02:44 AM GMT+00:00 Dec 11, 2013

    more shoddy nonsense from the CF team

  • ac iLiv

    1:36:00 PM GMT+00:00 Nov 25, 2013

    Umm how does it impact productivity? It doesn't work -- does that make sense?

  • LarryCLyons

    9:06:21 AM GMT+00:00 Nov 16, 2013

    As a CF Developer on a Mac I'm stalled until this is fixed.

  • Tomas Sancio

    2:24:47 PM GMT+00:00 Nov 9, 2013

    This is a problem because I've updated to Mavericks and cannot reconnect ColdFusion 10. Will try the workarounds but this should be direct, at least through straight-forward commands in the Terminal.

  • steckinsights

    8:41:46 AM GMT+00:00 Nov 9, 2013

    It's impossible to develop for Coldfusion on the latest version of Mac OS.

  • KE7DLT

    9:20:08 AM GMT+00:00 Oct 31, 2013

    Either needs fixed or I need to come up with an alternate library to mod_jk

  • xiinteractiv

    10:07:54 PM GMT+00:00 Oct 27, 2013

    I am running OSX Mavericks.
    Im trying to install CF10 on XAMPP
    XAMPP fails after installing CF
    I have fixed the JAVA_home path and java.home path, etc etc etc.
    tried the so file listed in this article http://www.n42designs.com/blog/index.cfm/2013/10/23/Running-ColdFusion-10-on-OS-X-Mavericks

    no joy.
    I must say adobe... its things like this that make me want to just stop using CF.

    I need a fix for this please respond.

  • cfmcoder

    9:20:47 AM GMT+00:00 Oct 27, 2013

    Adobe please make an update ASAP.

  • iMarqDigital

    7:58:26 AM GMT+00:00 Oct 27, 2013

    My main development platform is MacOS. This severely interrupts my development cycle and posses a huge problem for me in producing for my clients. I chose ColdFusion because I believed it offered better solutions when compared to other development languages such as ASP or PHP. But I think I may have to seriously consider PHP as my development language of choice as I cannot afford this type of down-time. This absolutely cripples the small-business/freelance developer/designer such as myself.

  • KevinKreuter

    6:44:31 PM GMT+00:00 Oct 26, 2013

    As others have stated, Mac OS X is my primary dev platform (and many other developers that I know), need this fixed.

  • Wilgeno

    8:57:23 AM GMT+00:00 Oct 26, 2013

    Its time for Adobe to actually get ahead of the game and update software for new OS's and web servers.

  • dsbrady_98

    8:09:02 AM GMT+00:00 Oct 26, 2013

    This makes it hard to upgrade to Mavericks and use CF at the same time.

  • Oscar E. Despradel

    8:35:42 PM GMT+00:00 Oct 25, 2013

    I update to mavericks and now I cant develop in coldfusion please guys fix this asap

  • jcelias

    8:18:17 PM GMT+00:00 Oct 25, 2013

    If this bug was fixed for CF11 that is *unacceptable* to us developers who have spent time and money on CF10!!!

    CF11 is not even out yet (anyone knows *when* it will be out btw?), and we cannot stop our production process moving to OS X Mavericks simply because Adobe did not bother to test CF10 with it. I'm *very* disappointed at the way Adobe is handing this issue, and I'm also having second thoughts about the long-term prospects of CF with this attitude Adobe has in relation to us developers.

  • blogonria

    7:18:51 AM GMT+00:00 Oct 25, 2013

    Please provide fix through updater.

  • DL Murphy

    11:15:13 PM GMT+00:00 Oct 24, 2013

    Wow. The current version of CF on the current version of Mac and Windows seems obvious. Please fix it soon!

  • David Dykstra

    3:32:02 PM GMT+00:00 Oct 24, 2013

    Same Here, Upgraded my OS to 10.9, now I am unable to continue developing CF10 on my machine. Please Fix SOON!

  • Bill0431

    2:57:15 PM GMT+00:00 Oct 24, 2013

    Don't understand how this wasn't anticipated by Adobe?

  • Erik Westra

    12:23:08 PM GMT+00:00 Oct 24, 2013

    Please fix this asap .

  • bradwood.com

    10:53:56 AM GMT+00:00 Oct 24, 2013

    This really does need to be supported. CF10 is the current version of ColdFusion and needs to support modern OS's.

  • Thomas-SPONX-DE

    6:50:55 AM GMT+00:00 Oct 24, 2013

    Waiting for an Update ................. It is not possible to get the CF10 developer edition to run on OSX Mavericks.

  • joebrislin

    5:10:49 AM GMT+00:00 Oct 24, 2013

    This bug causes all of our Mac systems to be unable to be updated to OS X Mavericks. Numerous systems have already come across this issue and development is now impeded.

  • Doug Cain

    4:20:37 AM GMT+00:00 Oct 24, 2013

    we shouldn't have this kind of issue every time there is an update to apache.

    how hard can it be to get the connector to work with the current apache version?

  • Paul Brekelmans

    4:20:18 AM GMT+00:00 Oct 24, 2013

    Ik just bought new Mac's for development yesterday. We work with CF10 and with this my dev team will stop developing. That's an issue.

  • Dik

    2:21:29 AM GMT+00:00 Oct 24, 2013

    Same issue here, but with CF 9 and OS X 10.9.

    It's impossible to run the webserver connector or modify the config manually.

  • GuustNieuwenhuis

    1:28:15 AM GMT+00:00 Oct 24, 2013

    this needs to be fixed! actually, this shouldn't have been an issue...

  • cielen.com

    8:41:07 PM GMT+00:00 Oct 23, 2013

    definitely needs to be fixed!

  • Stacy_in_WV

    5:42:31 PM GMT+00:00 Oct 23, 2013

    also confirmed - same issue

  • JoshuaCurtiss

    3:33:40 PM GMT+00:00 Oct 23, 2013

    Cannot use ColdFusion 10 on my Mac workstation without doing MAMP or internal ColdFusion server.

  • Giancarlo Gomez

    3:29:33 PM GMT+00:00 Oct 23, 2013

    I am experiencing the same thing and will be trying Mike's file to see if it works for now.

  • Adam Cameron.

    2:18:47 PM GMT+00:00 Oct 23, 2013

    I don't use a Mac but the ColdFusion team need to improve their game with supporting current OS versions. we've already been through all this with the previous version of OSX and Windows 8. There's been a dev release of this available to Adobe since June... they should have been ready for this. Adobe need to understand developers keep their machines current, and this means CF needs to work on the current releases of the operating systems developers will be using.

    --
    Adam

  • MarcinSz

    2:09:51 PM GMT+00:00 Oct 23, 2013

    Can't do local CF dev on 10.9 without messy workarounds if this bug isn't fixed.

  • LuisMajano

    1:53:44 PM GMT+00:00 Oct 23, 2013

    This is verified as it no longer works.

  • tylerc

    1:30:08 PM GMT+00:00 Oct 23, 2013

    My dev environment is OS-X

  • screennameunavailable99

    1:16:05 PM GMT+00:00 Oct 23, 2013

    CF wants to run on dev-class macs. Dev-class macs run Mavericks.

  • TylerSilcox

    1:09:39 PM GMT+00:00 Oct 23, 2013

    Please fix or at least provide a solution so that we can update the files/configurations ourselves...we need your help Adobe.

  • TroyAllenSr

    12:33:52 PM GMT+00:00 Oct 23, 2013

    I am always pushing my development Mac to the limits, even with 16 Gigs of RAM. The new performance enhancements in 10.9 Mavericks should greatly improve my development performance, especially in RAM usage.

  • mattradel

    12:28:34 PM GMT+00:00 Oct 23, 2013

    Updated to Mavericks and it crashed my Apache/CF environment. Can't...get...work...done...

  • Nik S.

    12:19:53 PM GMT+00:00 Oct 23, 2013

    Preventing our devs from upgrading, please update as soon as possible!

  • lolajl

    12:16:23 PM GMT+00:00 Oct 23, 2013

    Bumping up this bug because I plan to be installing Maverick, but not until this is fixed.

  • jonsteenbergen

    11:15:21 AM GMT+00:00 Oct 23, 2013

    Also experiencing the same issue after upgrading to mavricks.

  • broberts360

    11:01:05 AM GMT+00:00 Oct 23, 2013

    Confirmed...my local development environment is toast after updating to Mavericks - Apache 2.2.24. Commenting out the mod_jk loader in apache2/httpd let's apache startup which is good for standard but still need ColdFusion 10 up and running.

  • Sikachyna

    10:46:04 AM GMT+00:00 Oct 23, 2013

    Confirmed same Apache behaviour after system was update to Mavericks

  • MikeMcConnell

    9:41:57 AM GMT+00:00 Oct 23, 2013

    Confirmed...I also experienced what is described in the original report. ColdFusion 10 is non-functional under Mavericks.

  • Sean Coyne

    8:55:20 AM GMT+00:00 Oct 23, 2013

    I can confirm as well. Apache fails to start and with LogLevel set to debug you can see that the connector continues to load and crash repeatedly until apache is killed. Apache is never able to fully start.

  • yuri.vorontsov

    7:06:46 AM GMT+00:00 Oct 23, 2013

    I confirm this issue. As an addition: mod_jk.so dumps shared memory files every second into /wsconfig/1 directory. The latest version of mod_jk.so 1.2.37 won't compile on Mavericks as well.

Your session has expired! Click to login
Current form data will be preserved

Cancel