I read the doc. you pointed out as such: when "out.close()" was
called, the "writeChannel" was not closed; when "readChannel.close()"
was called, the "reader" itself was not closed. So, looks like you
only need to do one or the other. It may have to do with how closing
is implemented on the chan
Without "out.close()" throws this exception on or
"writeChannel.closeFinally()":
Exception in thread "main" java.lang.IllegalStateException: The
current request does not hold the exclusive lock.
at
com.google.appengine.api.files.FileServiceImpl.close(FileServiceImpl.java:
315)
at
c
Sorry to revive an old thread
Even when billing is enabled, this seems to be a problem, because
remote_api will issue diferent requests and the closeFinally() request
won't have the lock anyway, after you create the file.
Any way to acomplish this?
--
You received this message because you ar
I have exactly the same problem, and when I set "lock = true;
writeChannel = fileService.openWriteChannel(file,
lock);"
I get a "com.google.appengine.api.files.LockException" - did you ever
resolve this issue.
On Dec 9 2011, 5:45 pm, Ronoaldo José de Lana Pereira
wrote:
If you want to read a file from the cloud storage, it works fine. but
writing creates problem. have you solved this issue? If yes, please guide
me.
On Thursday, August 18, 2011 10:05:20 PM UTC+8, André Salvati wrote:
>
> Hi,
>
> Maybe I've misunderstood docs, but I thought it was possible an
>
I am really hoping to find an answer for this. I have been searching for
the last week without any luck. I really need a method to add large
numbers of images on a regular basis from a remote location and this looks
like it could be a solution if I could get past the exception.
On Thursday, N
Why not just use the Google Cloud Storages APIs then to upload directly to
a bucket that you then access from you GAE application?
On Sunday, 27 January 2013 01:37:34 UTC+11, Andrew Kunkel wrote:
>
> I am really hoping to find an answer for this. I have been searching for
> the last week withou
