In December enterprises faced the nightmare of dealing with a critical security vulnerability. This time it was the Log4j/Log4Shell exposure that surfaced just in time for the holidays. Given how pervasive Log4j is used by both enterprise apps and cloud services, the inevitable “all hands on...
I am writing this while the industry is in panic finding and patching log4j after CVE-2021-44228 ("Log4Shell") was reported. Of course IBM and probably all other vendors inspect their products and come out with patches as fast we can. You have probably seen many security bulletins announcing...
Custom Log4j logging is not working after 10.5 migration from 9.x? You can try below steps. Since 10.5, webMethods has migrated to Log4j2. To migrate: Copy /common/lib/ext/log4j/log4j-12api.jar into /instances/default/lib/jars/. In custom wrapper.conf, set the following: ...
1. Create a Java properties file named wmjms.properties if it does not already exist and add it to your application class path. 2. Add the following lines in the file to set Log4j as your logging service and to specify the Log4j configuration file location: com.webmethods.jms.log...