Salesforce

WorldServer - export of big Translation Memory Data fails with error 'filename.tmx's size exceeds the limit of 4GByte.'

Printable View
« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentWorldServer
Symptoms/Context
When exporting a large Translation Memory, the export stops with this error (the name of the TMX file is just an example and will vary):

Message: TranslationMemory.tmx's size exceeds the limit of 4GByte.<br> TranslationMemory.tmx's size exceeds the limit of 4GByte.
  
Stack trace:
com.idiominc.ws.WSRuntimeException: TranslationMemory.tmx's size exceeds the limit of 4GByte.<br>
TranslationMemory's size exceeds the limit of 4GByte.
(covers org.apache.commons.compress.archivers.zip.Zip64RequiredException: TranslationMemory.tmx's size exceeds the limit of 4GByte.
  at com.idiominc.ws.impex.utility.ExchangeUtil.throwAsRuntimeException(ExchangeUtil.java:169)
  at com.idiominc.ws.servlet.tm.ExportTm.doResultSetExport(ExportTm.java:683)
  at com.idiominc.ws.servlet.tm.ExportTm.handle(ExportTm.java:294)
  at com.idiominc.ws.servlet.WSHttpServlet.handleServlet(WSHttpServlet.java:384)
  at com.idiominc.ws.servlet.WSHttpServlet.service(WSHttpServlet.java:169)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
  at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
  at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
  at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
  at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
  at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
  at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
  at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:957)
  at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
  at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423)
  at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079)
  at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:620)
  at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
  at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
  at java.lang.Thread.run(Thread.java:724)
Resolution
Workaround:  export partial TMs, for instance limit the search to all TM Entries in a specific source and target language only. If your TM is very big, you can limit the export further to TM entries that have been created in a specific period of time. For instance, all German to Spanish created in 2018. This is how this Search could look like:

User-added image

Remember to click on Export Result Set to export only the Result of your Search. 
Root Cause

There is a limitation of 4 GB Data size when exporting a Translation Memory. It is not possible to increase this data limit. 

An enhancement request  has been filed with id CRQ-7090.

Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 
Powered by