set clumping to 100
Update version of JGlobus to 2.0.6-rc8.d
commit d068a7f5918b587ed05b7229137b1a34bf676dfc
Author: Gerd Behrmann <behrmann@gmail.com>
Date:   Mon Mar 24 13:09:00 2014 +0100

    pool: Avoid memory exhaustion problems on write with xrootd and http

    The http and xrootd movers use an OrderedMemoryAwayThreadPoolExecutor. This
    thread pool limits memory usage per client, however it relies on being able to
    estimate the size of the messages in the queue. It knows how to calculate the
    size for ChannelBuffer objects, however it doesn't know how to do this for most
    other objects. Since we store protocol messages in the queue, the limit doesn't
    have the intended effect. The consequence is that a slow disk or full pool can
    cause the queue to fill up and trigger OOM.

    The patch solves this by moving the ExecutorHandler to the front of the
    pipeline such that only ChannelBuffers are stored in the queue.

    Target: trunk
    Request: 2.8
    Request: 2.7
    Request: 2.6
    Require-notes: yes
    Require-book: no
    Acked-by: Dmitry Litvintsev <litvinse@fnal.gov>
    Patch: http://rb.dcache.org/r/6796/
    (cherry picked from commit 7e6df2048c31c62cbd75b0aac0c1817b048f3faa)
    (cherry picked from commit 62c01b21a3b609491f34754dc8eb7102a57caf87)

    Conflicts:
    	modules/dcache/src/main/java/org/dcache/xrootd/pool/XrootdPoolNettyServer.java