LiamTheBox@lemmy.world to Greentext@sh.itjust.works · 2 days agoAnon tries programming in Javalemmy.worldimagemessage-square243fedilinkarrow-up1835arrow-down134
arrow-up1801arrow-down1imageAnon tries programming in Javalemmy.worldLiamTheBox@lemmy.world to Greentext@sh.itjust.works · 2 days agomessage-square243fedilink
minus-squaretaladar@sh.itjust.workslinkfedilinkarrow-up49arrow-down3·2 days 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-squareHackerJoe@sh.itjust.workslinkfedilinkarrow-up26arrow-down1·2 days 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-squaresuperkret@feddit.orglinkfedilinkarrow-up1·23 hours 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.