gamboa

@paulmillar here ``` transfermanagers.enable.db=true ```

Thank you for your feedback. I think changing this parameter would require to restart the RTM?

@DmitryLitvintsev the error has not recurred since then. There are not failed transfer observations correlated to that error.

FYI, this discussion is now moved to dCache rt support system

thank you

@paulmillar you mean compresing at storage or during transfer?

Hello @paulmillar for some reason I missed your questions on this old ticket. I am closing it now as I can not see this issue anymore we have upgraded 7.2...

Hello, Indeed. ``` 024-02-05 10:28:48 Launching /usr/bin/java -server -Xmx6144m -XX:MaxDirectMemorySize=6144m -Dsun.net.inetaddr.ttl=1800 -Dorg.globus.tcp.port.range=20000,25000 -Dorg.dcache.dcap.port=0 -Dorg.dcache.ftp.log-aborted-transfers=true -Dorg.dcache.net.tcp.portrange=33115:33315 -Djava.security.krb5.realm= -Djava.security.krb5.kdc= -Djavax.security.auth.useSubjectCredsOnly=false -Djava.security.auth.login.config=/etc/dcache/jgss.conf -Dcontent.types.user.table=/etc/dcache/content-types.properties -Dzookeeper.sasl.client=false -Dcurator-dont-log-connection-problems=true -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/dcache/dc235eightDomain-oom.hprof -XX:+ExitOnOutOfMemoryError -XX:+StartAttachListener -XX:+UseCompressedOops -javaagent:/usr/share/dcache/classes/aspectjweaver-1.9.9.1.jar -Djava.net.preferIPv6Addr ```...

FYI for security issues the RT ticket [www.dcache.org #10590] Re: JAVA heap memory limits not respected after 9.2.6 upgrade GitHub issue #7507 is used now as there are java related...

Yes, is more than the specified. See an example here for pools running See the process ``` root 271305 0.0 0.0 112808 976 pts/0 S+ 09:16 0:00 \_ grep --color=auto...