@[email protected] to [email protected] • 7 months agoAnon tries programming in Javalemmy.worldimagemessage-square242fedilinkarrow-up1890
arrow-up1890imageAnon tries programming in Javalemmy.world@[email protected] to [email protected] • 7 months agomessage-square242fedilink
minus-square@[email protected]linkfedilink54•7 months agoThey forgot to mention that production Java applications apparently need to log a certain minimum number of completely meaningless stacktraces per hour to work properly. Or at least I assume that is the case from the fact that all of them do that.
minus-square@[email protected]linkfedilink30•7 months agoBest with an old and vulnerable log4j on a Windows log server. We don’t know what’ll happen if we update. And we don’t know if the dude who coded it will answer our calls. YOLO!
minus-square@[email protected]linkfedilink4•7 months agoAt that point, just kill the VM the app is running on and deal with the fallout.
They forgot to mention that production Java applications apparently need to log a certain minimum number of completely meaningless stacktraces per hour to work properly. Or at least I assume that is the case from the fact that all of them do that.
Best with an old and vulnerable log4j on a Windows log server.
At that point, just kill the VM the app is running on and deal with the fallout.