@LiamTheBox@lemmy.world to Greentext@sh.itjust.works • 15 days agoAnon tries programming in Javalemmy.worldimagemessage-square249fedilinkarrow-up1873arrow-down135
arrow-up1838arrow-down1imageAnon tries programming in Javalemmy.world@LiamTheBox@lemmy.world to Greentext@sh.itjust.works • 15 days agomessage-square249fedilink
minus-square@taladar@sh.itjust.workslinkfedilink48•15 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-square@HackerJoe@sh.itjust.workslinkfedilink29•15 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-square@superkret@feddit.orglinkfedilink4•14 days 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.