@LiamTheBox to [email protected] • 1 day agoAnon tries programming in Javaimagemessage-square224arrow-up1789arrow-down132
arrow-up1757arrow-down1imageAnon tries programming in Java@LiamTheBox to [email protected] • 1 day agomessage-square224
minus-square@[email protected]linkfedilink47•1 day 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]linkfedilink26•1 day 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]linkfedilink1•8 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.