[google-appengine] Re: Stability of Java 8 on Standard Environment

I was able to find a work-around to be able to publish to a PubSub topic in the Java 8 standard environment until a permanent fix is released: https://github.com/GoogleCloudPlatform/google-cloud-java/issues/2275 It's necessary to first obtain credentials from within an App Engine request

[google-appengine] Re: Stability of Java 8 on Standard Environment

@James I can see that you are already getting responses from my colleague(s) on GitHub , you can continue troubleshooting on your GitHub thread or any

[google-appengine] Re: Stability of Java 8 on Standard Environment

Ah, I just found your issue on github and was writing up a reply with the same workaround. Automagic authentication does not work in a plain java thread pool, to avoid `UNAUTHENTICATED` errors you would need to use a PubSub client with explicit credentials, e.g.: ```

[google-appengine] Re: Stability of Java 8 on Standard Environment

Kenworth, Christian: I've posted reports of this issue in a few different places: https://github.com/GoogleCloudPlatform/google-cloud-java/issues/2275 https://stackoverflow.com/questions/45330377/pubsub-in-app-engine-standard-java-8-nullpointerexception-at-apiproxyimplcurre

[google-appengine] Re: Stability of Java 8 on Standard Environment

Christian, thanks for that interesting (and kind of scary) work-around ( https://gist.github.com/cmaan/7752e3c4fd0b1ba90a745cb6db232206). I was having the same problem but with the PubSub client rather than the Spanner client. By switching the thread factory I was able to avoid the NPE at

[google-appengine] Re: Stability of Java 8 on Standard Environment

Thank you all for the very interesting discussion points. Please note that if your post is either a suspected bug and/or feature request, it is highly recommended to file this on Public Issue Tracker for better tracking purposes. For

[google-appengine] Re: Stability of Java 8 on Standard Environment

We switched to the java8 runtime recently, and for the most part didn't experience any major issues (yet). Performance did definitely improve for us, compared to java7. On GAE Standard, we use a bunch of Google Cloud services, including Datastore, Vision API, GCS, Compute Engine, Memcache,

[google-appengine] Re: Stability of Java 8 on Standard Environment

We switched to the java8 runtime recently, and for the most part didn't experience any major issues (yet). Performance did definitely improve for us, compared to java7. On standard environment, we use a bunch of Google cloud services, including Datastore, Vision API, Storage, Compute Engine,

[google-appengine] Re: Stability of Java 8 on Standard Environment

Also using the native java8 https request, it throws an exception if you call conn.getInputStream() and the response code is 400 series. That code worked fine in java7 and java8 with urlfetch, but in java8 native you have to call conn.getErrorStream() after testing the response code to know

[google-appengine] Re: Stability of Java 8 on Standard Environment

One thing I have experienced with Java8 is that the mail service seems to only handle attachments smaller than 3.5MB. https://issuetracker.google.com/63371955 torsdag 6. juli 2017 21.45.38 UTC+2 skrev Patrick Jackson følgende: > > Super excited to see Java 8 support. The removal of the

[google-appengine] Re: Stability of Java 8 on Standard Environment

*Glitches*: Main glitch so far is that we needed to set urlfetch in our appengine-web.xml file for some reason. Still trying to figure out why we can make the request on java7 and 8 via urlfetch, but it doesn't work on native on java8. We could be doing something stupid but can't figure