Files API triggering ApiDeadlineExceededException

50 views
Skip to first unread message

jon

unread,
Mar 16, 2012, 9:04:56 AM3/16/12
to Google App Engine
Every file upload attempt using our web app is currently failing with
the following exception:

Caused by: com.google.apphosting.api.ApiProxy
$ApiDeadlineExceededException: The API call file.Create() took too
long to respond and was cancelled.
at com.google.net.rpc3.client.RpcStub$RpcCallbackDispatcher
$1.runInContext(RpcStub.java:748)
at com.google.tracing.TraceContext$TraceContextRunnable
$1.run(TraceContext.java:455)
at com.google.tracing.TraceContext.runInContext(TraceContext.java:
695)
at com.google.tracing.TraceContext
$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:
333)
at com.google.tracing.TraceContext
$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:
325)
at com.google.tracing.TraceContext
$TraceContextRunnable.run(TraceContext.java:453)
at com.google.net.rpc3.client.RpcStub
$RpcCallbackDispatcher.rpcFinished(RpcStub.java:788)
at com.google.net.rpc3.client.RpcStub
$RpcCallbackDispatcher.failure(RpcStub.java:779)
at
com.google.net.rpc3.impl.client.RpcClientInternalContext.runCallbacks(RpcClientInternalContext.java:
890)
at
com.google.net.rpc3.impl.client.RpcClientInternalContext.finishRpcAndNotifyApp(RpcClientInternalContext.java:
793)
at
com.google.net.rpc3.impl.client.RpcNetChannel.afterFinishingActiveRpc(RpcNetChannel.java:
1049)
at
com.google.net.rpc3.impl.client.RpcNetChannel.finishRpc(RpcNetChannel.java:
895)
at
com.google.net.rpc3.impl.client.RpcNetChannel.handleResponse(RpcNetChannel.java:
2248)
at
com.google.net.rpc3.impl.client.RpcNetChannel.messageReceived(RpcNetChannel.java:
2060)
at com.google.net.rpc3.impl.client.RpcNetChannel.access
$2000(RpcNetChannel.java:147)
at com.google.net.rpc3.impl.client.RpcNetChannel
$TransportCallback.receivedMessage(RpcNetChannel.java:3097)
at com.google.net.rpc3.impl.client.RpcChannelTransportData
$TransportCallback.receivedMessage(RpcChannelTransportData.java:602)
at
com.google.net.rpc3.impl.wire.RpcBaseTransport.receivedMessage(RpcBaseTransport.java:
420)
at
com.google.net.rpc3.impl.wire.RpcClientTcpTransport.parseOneMessage(RpcClientTcpTransport.java:
773)
at
com.google.net.rpc3.impl.wire.RpcClientTcpTransport.parseMessages(RpcClientTcpTransport.java:
651)
at com.google.net.rpc3.impl.wire.RpcClientTcpTransport.access
$100(RpcClientTcpTransport.java:38)
at com.google.net.rpc3.impl.wire.RpcClientTcpTransport
$1.dataReceived(RpcClientTcpTransport.java:293)
at
com.google.net.async3.SocketConnection.handleNetworkReadEvent(SocketConnection.java:
843)
at com.google.net.async3.SocketConnection.access
$400(SocketConnection.java:40)
at com.google.net.async3.SocketConnection
$NetworkReadHandlerImpl.run(SocketConnection.java:872)
at com.google.net.eventmanager.AbstractFutureTask
$Sync.innerRun(AbstractFutureTask.java:260)
at
com.google.net.eventmanager.AbstractFutureTask.run(AbstractFutureTask.java:
121)
at
com.google.net.eventmanager.EventManagerImpl.runTask(EventManagerImpl.java:
576)
at
com.google.net.eventmanager.EventManagerImpl.internalRunWorkerLoop(EventManagerImpl.java:
997)
at
com.google.net.eventmanager.EventManagerImpl.runWorkerLoop(EventManagerImpl.java:
878)
at
com.google.net.eventmanager.WorkerThreadInfo.runWorkerLoop(WorkerThreadInfo.java:
134)
at com.google.net.eventmanager.EventManagerImpl
$WorkerThread.run(EventManagerImpl.java:1833)



Environment:
GAE/J 1.6.3.1
HRD

This is different from (but perhaps related to)
ApiDeadlineExceededException caused by images.GetUrlBase which was
happening last month ( see http://code.google.com/p/googleappengine/issues/detail?id=6771
)


Karl Rosaen

unread,
Mar 16, 2012, 11:15:49 AM3/16/12
to google-a...@googlegroups.com
After migrating to HRD we had to start using the 'exclusive_lock=True' parameter (from python) to fix this error, perhaps there's an equivalent parameter in java?

Karl

jon

unread,
Mar 16, 2012, 7:59:52 PM3/16/12
to Google App Engine
I've been using the Java equivalent of exclusive lock all along.
Reply all
Reply to author
Forward
0 new messages