ColdFusion 9, 10, 11, and 2016 release, easily migrate to ColdFusion (2018 release). For details on migrating to ColdFusion (2018 release), visit the ColdFusion migration resources section of the ColdFusion Developer Center.
Staff
43 posts
Hi Charlie Arehart , I’m migrating from CF11 to cf18 and I have got a back up of all neo*.xml files of cf11 project. I was referring to docs ( https://forums.adobe.com/message/10661306#10661306 ) and I have done all the required settings in both IIS server and CFAdmin but still getting java.null.pointer exception.
In the java and jvm setting of cfadmin the jvm args are
( -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005 -server –add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED –add-opens=java.base/java.nio=ALL-UNNAMED –add-modules=java.xml.ws –add-opens=java.base/java.lang=ALL-UNNAMED –add-opens=java.base/sun.util.cldr=ALL-UNNAMED –add-opens=java.base/sun.util.locale.provider=ALL-UNNAMED -XX:MaxMetaspaceSize=192m -XX:+UseParallelGC -Xbatch -Djdk.attach.allowAttachSelf=true -Dcoldfusion.home={application.home} -Duser.language=en -Dcoldfusion.rootDir={application.home} -Dcom.sun.xml.bind.v2.bytecode.ClassTailor.noOptimize=true -Dcoldfusion.libPath={application.home}/lib -Dorg.apache.coyote.USE_CUSTOM_STATUS_MSG_IN_HEADER=true -Dcoldfusion.jsafe.defaultalgo=FIPS186Random -Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.JavaUtilLog -Djava.util.logging.config.file={application.home}/lib/logging.properties -Djava.locale.providers=COMPAT,SPI -Dsun.font.layoutengine=icu ).
There is some UNNAMED args in that is this causing the null pointer exception?
Please help me I’m new to this.
No, there’s nothing wrong about those args referring to “unnamed”. That’s as it should be. (Those args with two dashes are new for Java 9, and thus for CF2018, which runs for now on Java 10.)
And while the display here makes it look like yours (like add-opens) have only one dash in front of them, I suspect that what’s happened is simply that the portal editor or display mechanism has rendered those two dashes as a single long dash (and “em dash”).
Bottom line: your jvm args here look fine. (I did a compare of yours to mine, and they were identical.)
One gotcha that just got me is with cflogin when moving from CF10 to 2018.
In CF 8, 9, and 10 this worked great:
Main (root) Application.cfc just used to authenticate via cflogin and set an ApplicationToken e.g. RootToken.
Different applications in sub-folders that required a login had their own Application.cfc with different application names but with <cflogin applicationtoken=”RootToken” >. This gave my server a single sign on (SSO) without any extra application overhead between sub-applications within my site.
Once I upgraded to 2018, none of these sub-applications worked because the user was not logged in. I tried “extending” the Application.cfc files and using an ApplicationProxy file, but that didn’t work. Eventually, I just renamed all my sub-applications to the same name, which made the whole site one big application and that worked. I liked the old way better though. I also don’t understand what the point of the ApplicationToken attribute for cflogin is now.
Hopefully this will keep someone else from beating their head against a wall for too long…
I would add a clarification to Anit is saying it’s “not possible” to update from 8 to 2018. It’s certainly “possible”. I have 2 current clients who’ve just made the move.
Of course, it’s a little more work than moving from 9–which is itself a bigger jump than moving from 10, and so on. And certainly some migrations are far easier than others, just depending on the coding used.
But I suppose Anit may have been referring to the “migration wizard” feature, for importing admin settings from prior CF versions loaded on the same machine. Some may know that it launches when the CF Admin is first used after a CF installation, or can be manually configured to run again later. THAT tool DOES generally support importing admin settings for only 2 or 3 prior releases.
He may also have been thinking of what the migration guide covers, and fair enough. I just wanted to clarify things, as there is otherwise no particular reason why one MUST update to 10 first.
Finally, I’ll say that I and others can help folks making that move. See my list of troubleshooting consultants at https://www.cf411.com/cftrouble.
(I see that there were TWO different people who asked about 8, and Anit has answered them each individually with the same answer. As I wanted to offer a counterpoint (to both), I’m posting this as a new comment rather than duplicating a reply to each.)
Yeah, what about 8?
Its not possible to migrate from CF8 to CF2018. You can migrate from CF8 to CF10 and then CF10 to CF2018, as a workaround.
Hi,
What about Coldfusion 8?
Its not possible to migrate from CF8 to CF2018. You can migrate from CF8 to CF10 and then CF10 to CF2018, as a workaround.
You must be logged in to post a comment.
23 Nov
10AM Pacific
Online
