<@U071QGDLH> thanks for putting the Adobe updates ...
# docker-commandbox
d
@jclausen thanks for putting the Adobe updates on forgebox so quickly - from the security bulletin (https://helpx.adobe.com/coldfusion/kb/coldfusion-2018-update-17.html) it says it needs some JVM options for the security patch:
For Application Servers
On JEE installations, set the following JVM flag, "-Djdk.serialFilter= !org.mozilla.**;!com.sun.syndication.**;!org.apache.commons.beanutils.**; !org.jgroups.**", in the respective startup file depending on the type of Application Server being used.
Is this something that should go into the base commandbox? I have added to my server.json for the moment but wondered if there is a better way of making sure the default commandbox already has them?
👍 3
j
@dougcain I will add this to the Java tool options we already use and rebuild the images
d
cool thanks 🙂
will it overwrite the existing ones? If so how will I know they are rebuilt?
j
I will ping you here
👍 1
b
I've considered adding these by default in CommandBox when starting an Adobe server, but I've never gotten around to it.
Right now, you'd need to provide that JVM arg, unless of course, Jon adds something to the base image to add it
j
@dougcain I’ve added them a
JAVA_TOOL_OPTIONS
so as not to conflict with user-provided JVM args. A new patch version is building now.
d
gotta luv a bit of automation ⚙️⚙️
seems like the builds have completed - how long does it generally take for forge box to notice (current publish date / time hasn’t changed from this morning)
b
Jon didn't update the ForgeBox CF engines, just the docker images
d
ahh, that would be it - not thinking clearly!
3.7.8 here we come
can’t see the new JVM args showing up in either the commandbox console log or “ps -ef | grep java” - am I looking in the wrong place? Not sure where JAVA_TOOL_OPTIONS would be seen
will go with server.json for the moment until I get to grips with it more
b
JAVA_TOOL_OPTIONS
That's just an environment variable
Check
server.system.environment
from your CF code and see if it's there
The JVM should also have some output saying it picked that up too on startup
d
I did look in the docker image ran “set” and didn;t see anything there
j
They show up the first time anything “java” executes - so they would be right at the beginning of the container output.