Difference: KnownIssues (68 vs. 69)

Revision 692014-11-04 - PaoloAndreetto

Line: 1 to 1

META TOPICPARENT	name="GeneralDocumentation"

Known issues

Line: 8 to 8

Known problems in CREAM software or in other software modules affecting a CREAM based CE (the list refer to known problem affecting the latest release of the software released in EMI)

Added:

>
>

Null pointer exception from Tomcat6 HTTP processor

Due to a [https://bugzilla.redhat.com/show_bug.cgi?id=1128396|bug] in tomcat6 (up to version 6.0.24.78), the container fails to parse a chunked transfer encoding and raises the following exception:

Aug 01, 2014 12:34:56 AM org.apache.coyote.http11.Http11Processor process
SEVERE: Error finishing request
java.lang.NullPointerException
        at org.apache.coyote.http11.filters.ChunkedInputFilter.parseHeader(ChunkedInputFilter.java:420)
        at org.apache.coyote.http11.filters.ChunkedInputFilter.parseEndChunk(ChunkedInputFilter.java:409)
        at org.apache.coyote.http11.filters.ChunkedInputFilter.doRead(ChunkedInputFilter.java:155)
        at org.apache.coyote.http11.filters.ChunkedInputFilter.end(ChunkedInputFilter.java:208)
        at org.apache.coyote.http11.InternalInputBuffer.endRequest(InternalInputBuffer.java:336)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:886)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
        at java.lang.Thread.run(Thread.java:745)

There's no workaround at the moment.

Missing infoprovider wrapper or corrupted configuration file in EMI-3

Due to a bug in rpm scriptlets of the packages:

dynsched-generic

Line: 17 to 34

The workaround consists on running YAIM every time one of the above packages is update.

Deleted:

<
<

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

This issue occurs in one of the following cases:

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

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.

Line: 362 to 370

Problems in CREAM software or in other software modules affecting a CREAM based CE that have already been fixed (i.e. they are not affecting the latest release of the software released in EMI)

Added:

>
>

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

This issue occurs in one of the following cases:

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

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

Fix provided in EMI-3 update 21

Error from TORQUE infoprovider: Exception: Cannot find user for xxxxx.xxxxxxxx

This error can be reported by the low level infoprovider of TORQUE when the CREAM service and TORQUE server are deployed on different hosts and a set of "local accounts", not belonging to any pool account, are defined on the TORQUE server. The error message is misleading, the infoprovider is not able to retrieve the group of the local account, not the user.

View topic | History: r69 < r68 < r67 < r66 | More topic actions...