function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
NikkiNikki 

No space left on device error

The Salesforce 2.0 xmlrpc api threw an exception this morning that I have never seen before. I have used this code for months and this is the first time I've seen it. Here is the stack trace:

org.apache.xmlrpc.XmlRpcException: java.lang.RuntimeException: java.io.IOException: No space left on device
at common.api.Querier.doQuery(Querier.java:374)
at common.api.Dispatcher.inner_dispatch(Dispatcher.java:400)
at common.api.Dispatcher.dispatch(Dispatcher.java:283)
at common.api.Dispatcher.inner_execute(Dispatcher.java:229)
at common.api.Dispatcher.execute(Dispatcher.java:111)
at helma.xmlrpc.XmlRpcServer$Worker.execute(XmlRpcServer.java:135)
at helma.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:78)
at servlet.Api.doPost(Api.java:251)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:165)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:103)
at com.caucho.server.dispatch.ServletFilterChain.doFilter(ServletFilterChain.java:113)
at system.filter.PreGzipFilter.doFilter(PreGzipFilter.java:72)
at com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:84)
at com.caucho.server.cache.CacheFilterChain.doFilter(CacheFilterChain.java:190)
at com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:177)
at com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:221)
at com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:263)
at com.caucho.server.port.TcpConnection.run(TcpConnection.java:323)
at com.caucho.util.ThreadPool.runTasks(ThreadPool.java:430)
at com.caucho.util.ThreadPool.run(ThreadPool.java:377)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.IOException: No space left on device
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:260)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:110)
at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1639)
at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1548)
at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1146)
at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1100)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1241)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1355)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:281)
at common.api.QueryXmlWriter.beginSpooling(QueryXmlWriter.java:86)
at common.api.QueryXmlWriter.writeObject(QueryXmlWriter.java:57)
at common.api.Querier.executeQuery(Querier.java:517)
at common.api.Querier.doQuery(Querier.java:330)

Thanks, Nikki
benjasikbenjasik
This is a bug on our end, related to a process not cleaning up temp files. We are working on getting a patch out ASAP.