LO56443: "LOG4J:WARN NO APPENDERS COULD BE FOUND FOR LOGGER" ERROR

APAR status

• Closed as fixed if next.

Error description

• A customer database contains an agent which makes use of Log4j
  classes. A resources jar file is attached (imported) to the
  agent and includes properties files for Log4j:
  
  - log4j.properties
  - log4j to console.properties
  - log4j with notes appender.properties
  
  Initially running the agent results in errors as shown below:
  
  ...Caused by: java.security.AccessControlException: Access
  denied
  
  (java.lang.RuntimePermission getClassLoader)
   at
  java.security.AccessController.checkPermission(AccessController.
  java:108
  )
   at
  java.lang.SecurityManager.checkPermission(SecurityManager.java:5
  33)
   at
  COM.ibm.JEmpower.applet.AppletSecurity.superDotCheckPermission(A
  ppletSec
  urity.java:1449)
   at
  COM.ibm.JEmpower.applet.AppletSecurity.checkRuntimePermission(Ap
  pletSecu
  rity.java:1311)
   at
  COM.ibm.JEmpower.applet.AppletSecurity.checkPermission(AppletSec
  urity.ja
  va:1611)
   at
  COM.ibm.JEmpower.applet.AppletSecurity.checkPermission(AppletSec
  urity.ja
  va:1464)
   at java.lang.Thread.getContextClassLoader(Thread.java:456)
  
  
  This first error is a permissions issue and can be corrected by
  amending the java.policy file. For testing the file can be
  amended as follows (Note this setting is for testing only and is
  not recommended for any production environment):
  
  // Standard extensions get all permissions by default
  
  grant {permission java.security.AllPermission;};
  
  
  After updating the java.policy the permissions issue is
  resolved however the following error will continue to be
  raised when executing the agent.
  
  log4j:WARN No appenders could be found for logger (JavaAgent).
  log4j:WARN Please initialize the log4j system properly.
  
  When the same jar file that is already attached to the agent is
  placed in the Notes\jvm\lib\ext folder then the log4j error is
  fully resolved.
  
  It is not clear why the issue is only partially resolved by
  updating the java.policy file when placing the same .jar file in
  the Notes\jvm\lib\ext folder fully corrects the error.
  

Local fix

• When the same jar file containing the log4j properties that is
  already attached to the agent is placed in the Notes\jvm\lib\ext
  folder then the error is fully resolved.
  

Problem summary

• The problem will be fixed in the next release of the product.
  

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# DPOL8BBH6N.
  The problem will be fixed in the next release of the product.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R850 PSN

     UP