Below tech note for ColdFusion 9.0.1 Cumulative Hotfix 4 has been updated with instructions for jpedal.jar.
http://helpx.adobe.com/coldfusion/kb/cumulative-hotfix-4-coldfusion-901.html
How does this affect you:
If your ColdFusion server was not patched with Cumulative Hotfix 2 prior to applying Cumulative Hotfix 4, you would need to download the JPedal.zip file. See the above tech note link for more details.
If your ColdFusion server was already patched with Cumulative Hotfix 2 before you applied Cumulative Hotfix 4, you already have the correct file and need not do anything.
I just want to point out again that the ColdFusion updates page has not been updated with this latest Hotfix (or Hotfix 3 for that matter).
http://www.adobe.com/support/coldfusion/downloads_updates.html#cf9
Wil pointed this out earlier but I think it got lost in the other conversation.
Rakshith: thank-you for listening to your community. Obviously what’s done is done, so we just need to look forward. Hopefully lessons have been learned – it sounds like they have – and things will go in a more measured, controlled and… well… *successful* way in future.
If you need any volunteers in testing these things before you put them out the door, I’m sure you’ll find them here. Be it actual testing or just sanity checking stuff.
Cheers.
—
Adam
@All: I agree the updates this time had multiple issues with us updating the CHFs and technotes more than once. We also understand that updating a CHF is not a great idea and we are better off to come up with a new CHF than updating it. I also understand the frustration that this might caused to all of you. There can obviously be no excuse from our side for the issues caused.
We have already identified the issues in the internal processes that we follow and have noted actions to correct them.
You will us coming out with an improved process and quality updates henceforth.
I agree with Adam’s post, Adobe please release a single update, and if the binaries change INCREASE THE VERSION NUMBER or at least put a letter suffix! How about SHA/MD5 checksums, file sizes etc so we can tell if we have Update 4, Update 4 re-release, etc
jpedal.jar is required for PDF operations. This is what Adobe broke badly on the Mac side. The fact that they “forgot” to include it in the last couple hot fixes tells me that this team is in over their head and has no real means or tracking releases. I have a a lot of servers to inspect now to see if I need this file.
Additionally, is this posted on the Adobe site for ColdFusion updates? I SURE DON’T SEE IT!!! http://www.adobe.com/support/coldfusion/downloads_updates.html#cf9
This is well beyond a bad joke!
If jpedal.zip is only required in some cases, why does the technote say to always install it ?
Why isn’t it just rolled into the existing zip files and, as Michael says, release the it as CHF5 saying “it’s only required if X” ? That would seem easier for everyone.
Hi Nimit, thanks for clarifying that.
But in regards to this comment “we have not made any changes in the files which we shipped with CHF4″…this just demonstrates that you guys just don’t quite get how this stuff is supposed to work.
Once you release a patch (be that a single file, an aggregation of a bunch of files, or just some config instructions), that’s it. You’re not supposed to then go change it.
We should not be having discussions along the lines of “well if you’ve installed CHF2 then you don’t need this version of CHF4, but if you’ve only done CHF3 or CHF4 (the one from last week) then you need to do this new CHF4”. That’s just nonsense.
I have to know that if I installed something called “CHF x” at a given point in time, I know exactly what that patch represents. It mustn’t change.
What you SHOULD have done is released this new instruction as CHF5. Even if all the files bar one are the same, it’s still a new patch level.
Equally “we have not made any changes in the files which we shipped with CHF4″… well yes you have. We now need to install this jpedal thing too. That’s a change in the files you shipped with CHF4, isn’t it?
Can you guys PLEASE adopt a coherent and non-ambiguous approach to releasing these patches. And you you also please focus more on whatever internal processes you have to make sure these things are released correctly in the first place. The last week or so have been an absolute joke as far as patching CF goes: it seems like it’s just one cock-up after another. And it really really shouldn’t be this hard, should it?
I’m sorry if I seem blunt, but this is a mess. And you have to shoulder responsibility for messing your clients around, and being a general disappointment recently (not you personally, Nimit, but the ColdFusion product in general). ColdFusion is better than that, and deserves to be treated better by the Adobe team.
—
Adam
@Adam
Just to be clear, if we’d not installed CHF2, but HAD installed CHF4 on Friday, we now need to do it again?
No, you need not to apply CHF4 again. You just need to download jpedal.zip file and follow the instructions mentioned in the technote.
And what if we’d installed CHF3 at some stage, but had never installed CHF2?
In this case, you need to apply CHF4, for more details refer: http://helpx.adobe.com/coldfusion/kb/cumulative-hotfix-4-coldfusion-901.html
What’s the story behind this? Did CHF2 (correctly) include jpedal, but CHF3 and the first CHF4 accidentally didn’t? Just trying to read between the lines here.
Yes, CHF2 had jpedal.jar file, but it is not there in CHF3 or CHF4. So, we added it separately.
Rather than changing an existing hotfix (again!), would it not be more clear to the community to have released this as CHF5?
It is a good suggestion, but we have not made any changes in the files which we shipped with CHF4. There is only one file(jpedal.jar) which we added.
Just to be clear, if we’d not installed CHF2, but HAD installed CHF4 on Friday, we now need to do it again?
And what if we’d installed CHF3 at some stage, but had never installed CHF2?
What’s the story behind this? Did CHF2 (correctly) include jpedal, but CHF3 and the first CHF4 accidentally didn’t? Just trying to read between the lines here.
Rather than changing an existing hotfix (again!), would it not be more clear to the community to have released this as CHF5?
—
Adam
You must be logged in to post a comment.