LiamTheBox@lemmy.world to Greentext · 2 months agoAnon tries programming in Javalemmy.worldimagemessage-square248fedilinkarrow-up1882arrow-down136
arrow-up1846arrow-down1imageAnon tries programming in Javalemmy.worldLiamTheBox@lemmy.world to Greentext · 2 months agomessage-square248fedilink
minus-squaretaladarlinkfedilinkarrow-up53arrow-down6·2 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-squareHackerJoelinkfedilinkarrow-up30arrow-down1·2 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-squaresuperkret@feddit.orglinkfedilinkarrow-up4·2 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.