Title says it all. ColdFusion 9.0.1 has been released.
ColdFusion 9.0.1 Update Released
22 responses to “ColdFusion 9.0.1 Update Released”
-
Nah, it’s not just a hot fix it a blaze’n hot update. Literally because it even has Blaze 4 update inside. The caching, Amazon S3 ehnancements and more. You guys have to schedule this update for your developers ASAP! Great update without reservation.
-
After running this update on our test server, I get an error on every datasource. I tried reinstalling the patch but I get the same error every time. Anyone else run into this?
java.sql.SQLException: macromedia.jdbc.sqlserver.SQLServerLicense cannot be cast to macromedia.jdbc.sqlserverbase.BaseLicense
The root cause was that: java.sql.SQLException: macromedia.jdbc.sqlserver.SQLServerLicense cannot be cast to macromedia.jdbc.sqlserverbase.BaseLicense -
Quick question regarding the SOLR updates, I use the SOLR install that was installed natively with CF9. Does the 9.0.1 update, update this or do I need to run the update listed here:
http://www.adobe.com/support/coldfusion/downloads.html
Thanks in advance 🙂 -
Yep, different.
-
It breaks returnformat=json for my CFCs – any numeric values are returned as strings 🙂
-
Is it same to assume that it does something different than 9.00?
-
It adds ORM support for multiple data sources!!!
That’s not worth mentioning at all???????? -
I just installed this and getting only a white page when trying to get to my CF admin. Does anybody have the same issue?
-
Same problem as Dan:
java.sql.SQLException: macromedia.jdbc.sqlserver.SQLServerLicense cannot be cast to macromedia.jdbc.sqlserverbase.BaseLicense
The root cause was that: java.sql.SQLException: macromedia.jdbc.sqlserver.SQLServerLicense cannot be cast to macromedia.jdbc.sqlserverbase.BaseLicense -
@David/Dan:
It seems that there is an issue with the new database drivers in ColdFusion 9.0.1 and SeeFusion. The CF team is looking into and hopefully we can figure out what’s going on.
In the meantime, you can easily revert back to the prev -
Where can I find documentation for S3? I can’t even explain how awesome this feature alone is…
-
@Alex T: Ray Camden just wrote a very nice blog article demo’ing the new S3 features:
http://www.coldfusionjedi.com/index.cfm/2010/7/15/CF901-Guide-to-Amazon-S3-support-in-ColdFusion-901
very cool 😀 -
@Adam
We followed the procedures to revert to the older Database drivers and we are still getting the same Datasource service is not available error. Is there anything else we could try to fix the issue? If not how can we uninstall the 9.0.1 update -
@Adam
The JDBC revert didn’t work for me either, and I’m also not using SeeFusion on the machine with the failed upgrade.
The server that died is a win2008 VPS on Hosting.com which was upgraded from 8 to 9, and now 9.01.
My dev server -
@Tom Jenkins: 9.0.1 updater will update solr as well
-
Got the datasource error also, and I’m not using SeeFusion.
Copying the jar file did not help. -
We got an database error too on our Red Hat Linux Server.
We downgraded to ColdFusion 9.0 and it works.
We did not use SeeFusion, but we use FusionReactor.
Is there a solution any working solution or will adobe fix this? -
Reverting the macromedia_drivers.jar worked for me. If anyone knows when Adobe will fix this, please let us know.
-
See this article: http://kb2.adobe.com/cps/857/cpsid_85773.html
— Ben -
I have yet a different solution regarding the error above, "macromedia.jdbc.sqlserver.SQLServerLicense cannot be cast to macromedia.jdbc.sqlserverbase.BaseLicense". I got it too, but I was running both FusionReactor and SeeFusion.
But about the recommendations above to copy the jar file from the updater_backup directory to the WEB-INFcfusionlib, I found that in my case, both the files were the same (did a compare).
But they were both different from that in the [cf]lib directory. That one is mentioned by no one above, but it’s long been the location where that jar had lived. So I decided to "comment out" the one in [cf]wwwrootWEB-INFlib by renaming it to macromedia_drivers.jar.bak. (That required that CF be stopped to do the renaming.) I then restarted CF, and the DSN that was failing now worked (including both those that are and are not wrapped with FusionReactor/SeeFusion).
I don’t know if this would be a recommended solution for others, but in case anyone hits what I did, if it may help, I wanted to share it. -
Charlie, this exact issue just bit me, and I found your observation about the location of the backup driver jar file to be correct. Thank you.
-
Both solutions didnt’work for us but then i got the idea to restore the ‘old’ drivers (i made backup before upgrading) to the WEB-INF/lib directory AND to the Coldfusion/lib directory and that worked.
Leave a Reply