Hochladen von Assets schlägt fehl | AEM

Problem

08.05.2018 18:23:42.554 *ERROR* [qtp1803264533-931031] org.apache.sling.engine.impl.parameters.ParameterSupport parseMultiPartPost: Error parsing request
org.apache.commons.fileupload.FileUploadBase$IOFileUploadException: Processing of multipart/form-data request failed. No space left on device
 at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:351)
 at org.apache.sling.engine.impl.parameters.ParameterSupport.parseMultiPartPost(ParameterSupport.java:399)
 at org.apache.sling.engine.impl.parameters.ParameterSupport.getRequestParameterMapInternal(ParameterSupport.java:309)
 at org.apache.sling.engine.impl.parameters.ParameterSupport.getParameter(ParameterSupport.java:179)
 at org.apache.sling.engine.impl.parameters.ParameterSupportHttpServletRequestWrapper.getParameter(ParameterSupportHttpServletRequestWrapper.java:40)
 at org.apache.sling.auth.core.impl.SlingAuthenticator.handleImpersonation(SlingAuthenticator.java:1319)
 at org.apache.sling.auth.core.impl.SlingAuthenticator.getResolver(SlingAuthenticator.java:794)
 at org.apache.sling.auth.core.impl.SlingAuthenticator.doHandleSecurity(SlingAuthenticator.java:511)
 at org.apache.sling.auth.core.impl.SlingAuthenticator.handleSecurity(SlingAuthenticator.java:460)
 at org.apache.sling.engine.impl.SlingHttpContext.handleSecurity(SlingHttpContext.java:131)
 at org.apache.felix.http.base.internal.whiteboard.PerBundleServletContextImpl.handleSecurity(PerBundleServletContextImpl.java:81)
 at org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:57)
 at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:128)
 at org.apache.felix.http.base.internal.dispatch.DispatcherServlet.service(DispatcherServlet.java:49)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
 at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
 at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)
 at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)
 at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
 at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
 at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
 at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
 at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
 at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
 at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
 at org.eclipse.jetty.server.Server.handle(Server.java:499)
 at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)
 at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
 at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)
 at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
 at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
 at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: No space left on device
 at java.io.FileOutputStream.writeBytes(Native Method)
 at java.io.FileOutputStream.write(FileOutputStream.java:326)
 at org.apache.commons.io.output.ByteArrayOutputStream.writeTo(ByteArrayOutputStream.java:261)
 at org.apache.commons.io.output.DeferredFileOutputStream.thresholdReached(DeferredFileOutputStream.java:181)
 at org.apache.commons.io.output.ThresholdingOutputStream.checkThreshold(ThresholdingOutputStream.java:224)
 at org.apache.commons.io.output.ThresholdingOutputStream.write(ThresholdingOutputStream.java:128)
 at org.apache.commons.fileupload.util.Streams.copy(Streams.java:107)
 at org.apache.commons.fileupload.util.Streams.copy(Streams.java:70)
 at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:347)
 ... 31 common frames omitted

Ursache

Der temporäre Ordner verfügt über nicht genügend freien Speicherplatz.

Lösung

Um das unmittelbare Problem zu beheben:

  1. AEM stoppen.
  2. Leeren Sie den temporären Ordner.
  3. Starten Sie AEM.

Mit dem JVM-Parameter -Djava.io.tmpdir=/temp/folder/path (wobei /temp/folder/path der gewünschte Ort ist) kann ein anderer temporärer Speicherort für AEM konfiguriert werden. Die JVM-Parameter können in der Variable CQ_JVM_OPTS im crx-quickstart/bin/start-script aktualisiert werden. Zusätzlich kann die Upload-Leistung durch den Einsatz eines Hochleistungslaufwerks für diesen Standort, wie z. B. eines „RAM-Laufwerks“, verbessert werden.

 Adobe

Schneller und einfacher Hilfe erhalten

Neuer Benutzer?