Difference: KnownIssues (67 vs. 68)

Revision 682014-06-12 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="GeneralDocumentation"

Known issues

Line: 17 to 17
  The workaround consists on running YAIM every time one of the above packages is update.
Changed:
<
<

Configuration error: cannot get instance of CommandManager: org/glite/lb/LBException

>
>

Configuration error: cannot get instance of CommandManager: org/glite/lb/LBException

  This issue occurs in one of the following cases:
Changed:
<
<
  • when upgrading the CREAM CE from 1.15 to 1.16. The workaround is to create a symbolic link in the web application:
ln -s /usr/share/java/glite-lb-client-java.jar /var/lib/tomcat*/webapps/ce-cream/WEB-INF/lib
  • when using the package glite-lb-client-java from EPEL (v. 2.0.5-2 and later). Downgrading the package to EMI-3 is necessary.
>
>
  • when upgrading the CREAM CE from 1.15 to 1.16.
  • when upgrading the package glite-lb-client-java to version 2.0.6-1 or later
 
Changed:
<
<

SEVERE: A web application created a ThreadLocal ... but failed to remove it when the web application was stopped

>
>
The workaround consists on creating a symbolic link in the web application deployment directory:
ln -sf /usr/lib/java/glite-lb-client-java.jar /var/lib/tomcat*/webapps/ce-cream/WEB-INF/lib

SEVERE: A web application created a ThreadLocal ... but failed to remove it when the web application was stopped

  This error is reported only by tomcat6 when the server container is being shutting down. Even if the message shows a memory leak this issue doesn't occur when the server is running.
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback