tracker issue : CF-4205254

select a category, or use search below
(searches all categories and all time range)

Bootstrap classloader doesn't handle trailing slash in updates/ path in coldfusion.classPath

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/UserError

Reporter/Name(from Bugbase): Bradley W. / ()

Created: 09/25/2019

Components: Installation/Config, JEE Deployment

Versions: 2018

Failure Type: Non Functioning

Found In Build/Fixed In Build: Final / NA

Priority/Frequency: Normal / Some users will encounter

Locale/System: / Platforms All

Vote Count: 2

Problem Description:

If you start up a CF war and have a coldfusion.classPath system property defined that uses a trailing slash on the updates folder, ColdFusion will not load the hotfix jar prior to any update jars in the updates folder and any hotfixes may not work.  This affects CommandBox, which sets an explicit coldfusion.classPath property ending with a slash.  

Steps to Reproduce:

Start up an Adobe engine in CommandBox and add an update jar and hotfix jar into the updates folder.  The order they are loaded in is not guaranteed based on the logic that is supposed to run in the bootstrap jar.  There is special logic for loading jars from any path ending with "/updates" but this logic assumes there will be no trailing slash.  Nimit helped me troubleshoot this and detect the bug.

Actual Result:

Hotfix jar may be loaded in wrong order.

Expected Result:

Hotfix jar should be loaded in correct order.

Any Workarounds:

Not really.



Hi Brad, We will not be fixing this issue as it is the problem with the way you guys were using it. Please let me know if you have any concern with this. -Nimit
Comment by Nimit S.
32088 | November 19, 2019 05:02:24 AM GMT
Why is this ticket closed with no comment? Why can't ColdFusion have it's logic made more sturdy instead of the brittle logic in place now. Something as simple as a trailing slash should not break this. Is there a compelling reason for Adobe to not improve ColdFusion here?
Comment by Bradley W.
32057 | January 31, 2020 06:07:34 AM GMT
@nimit, yes I have concerns as I detailed in my previous comment. It is sloppy for Adobe to leave this behavior in place. As I said last time, it is brittle and uneccessarily restrictive. I'm not aware of Adobe documenting the fact that a trailing slash will break things. This is the equivalent to when Apple's first iPhone had poor reception and they blamed their users for "holding the phone wrong". Come on and just fix the logic to not be so brittle. You could have fixed it in the time we've spent discussing it in this ticket. I was on a video call with you when I found this bug and you agreed it was incorrect at the time.
Comment by Bradley W.
32089 | February 05, 2020 05:33:04 AM GMT
Also, a note to anyone who may be confused by my comment about there not being an Adobe comment. Nimit's original comment was internal only and did not show up here. It was only after I left my first comment and then pinged Priyank that Nimit's comment appeared here.
Comment by Bradley W.
32090 | February 05, 2020 05:35:42 AM GMT