Where are default JVM settings in Lucee? Want to compare with our current jvm.config in ACF.

Lucee distros runs on Tomcat, so look in

tomcat/conf/catalina.properties

I'll have to figure out what I need to pull across from our ACF settings...

It's worth noting Lucee "proper" has no JVM settings

@Jim Priest It's been a while since I did a switch from acf to lucee, but I don't think the acf settings really were good baselines, the newer jvm defaults were better than what the prior acf stuff was using

Yeah, I haven't had a memory issue that GC "tuning" fixed in decades. The defaults are pretty darn good these days

i did some matrix testing of Lucee with different java distros default settings, barely a difference

I'm basically replacing ACF in our current Docker setup so doing a vanilla install... Our jvm.config file has been added on over the years... I have no idea what's relevant anymore plus all the things Adobe adds. I'll add nothing and see how the defaults are 🙂

Well yeah- if you're just comparing all openjdk distros, they're all built from 99% the same source anyway as oracle JDK

Not sure about these (from CF2021)

java.args=

--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED 
--add-opens=java.base/java.nio=ALL-UNNAMED 
--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 
--add-opens=java.base/java.net=ALL-UNNAMED 
--add-opens=java.base/java.io=ALL-UNNAMED 

-Dcoldfusion.jsafe.defaultalgo=FIPS186Random 

-Dcom.sun.media.jai.disableMediaLib=true 

-Djava.awt.headless=true 
-Djava.locale.providers=COMPAT,SPI 
-Djava.security.auth.policy={application.home}/lib/neo_jaas.policy 
-Djava.security.egd=/dev/urandom 

-Djdk.attach.allowAttachSelf=true 

-Dorg.apache.coyote.USE_CUSTOM_STATUS_MSG_IN_HEADER=true 

-Dsun.font.layoutengine=icu 

-Dtika.config=tika-config.xml

think -Djava.locale.providers=COMPAT just got dumped recently?

• the opens that are needed are prolly already added by Lucee • the coldfusion one wouldn't apply to Lucee • I don't know if medialib is used by Lucee, but prolly not • the headless one doens't hurt for a server • not sure what the local providers one does, maybe google it • the auth policy likely refers to a CF-specific file • The urandom one may be fine. Dunno if it's doing anything in particular • self attach I don't THINK is needed by Lucee these days for anything. • the custom status message prolly depends on your version of tomcat. The newer jakarta specs have removed custom messages so that may or may not even apply • not sure about the font one, it's a sun prop so pretty old • I don't know if Lucee uses tika, but if they do I doubt that file exists in the same place

lucee does use tika.

Ok, I would assume Micha has programmatically configured the file for it to use if necessary

I wouldn't touch anything, if something doesn't work, it will tell you, with a long stacktrace!!!!

Sounds good. I don't have any of these set now, and things spin up... I'll continue chugging along til something breaks 🙂

That's the spirit

next you'll be flogging teslas outside the whitehouse! oh wait

lol. The other day in another thread Jim said he would request a new waffle tag in all 3 engines and the first to build it would win. I rolled out https://forgebox.io/view/bx-waffle later that night.

Woooo!