400 bad request while deploying to app engine - java

While deploying to app engine, I got this error message:
400 Bad Request
Creating an index failed for entity_type:
"GeoLocationStat"ancestor: falseProperty { name: "ZoomLevel"}
Property { name: "GeoPt" mode: 3}:
Permission denied for creating a search index
Does anyone have any idea?

Well, apparently GeoPt and ZoomLevel datatypes were NOT the cause.
The root cause of this error message is Eclipse is unable to update datastore-indexes-auto.xml in WEB-INF\appengine-generated folder.
I delete the file and the deployment proceed just fine. :)

According to issue11963#c14 on the app engine issue tracker:
Geo-spatial queries are a new feature currently under development, and
expected to launch as Alpha sometime soon. When it does launch, it
will be for a limited group of apps; during Alpha, only those apps
will have "permission" to use it, which is why you're seeing this
confusing error message now...the SDK development server does
currently support the feature. So it works locally, but not in
production.

Related

After deploy Google App Engine returns HTTP response code 403

I've done another deploys and all was fine, but after finishing the app, I'm getting this error. And the page request keeps loading.
Do I need to configure something in "IAM"?
Java 11
Standard Environment
h2 DB
Spring boot
The stack trace from Google Cloud:
java.io.IOException: Server returned HTTP response code: 403 for URL: https://clouddebugger.googleapis.com/v2/controller/debuggees/register at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1919) at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1515) at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:250)
at com.google.devtools.cdbg.debuglets.java.GcpHubClient.registerDebuggee (Unknown Source)
I've got new data using Stackdriver debug.
"message": "Stackdriver Debugger API has not been used in project
929024293238 before or it is disabled. Enable it by visiting
https://console.developers.google.com/apis/api/clouddebugger.googleapis.com/overview?project=929024293238
then retry. If you enabled this API recently, wait a few minutes for
the action to propagate to our systems and retry.",
Just a note if somebody else stumbles across this error: I had the same message in Google's App Engine dashboard popping up up to 60 times in a couple of minutes.
Enabling the Stackdriver Debugging API, as linked above, solved it. No more error logs (of that kind) were being produced. The weired thing is that the Stackdriver Debugging API should have been turned on by default for my standard environment.
The log wasn't very informative.
I change the application port from 8000 to 8080.
application.properties:
server.port=${PORT:8080}
Now the app is running fine.

Java, App Insights: "I/O Exception: Invalid Argument or cannot assign requested address" only when I run using docker. No error locally with gradle

i have a java spring app that runs just fine locally with gradle, but when i run the image version of it, i get a strange error that i am not sure how to resolve or debug
docker run -it --rm myregistry.azurecr.io/my-app:latest
is the command that i get the following error on:
I/O exception (java.net.SocketException) caught when processing request to {s}->https://rt.services.visualstudio.com:443: Invalid argument or cannot assign requested address
ive found out thru googling that this url https://rt.services.visualstudio.com:443 is associated with Application Insights (azure logging) which is one of my dependencies. does this mean something is wrong with logback?
the thing is, when i run with gradle, i see trace logs in the app insights instance i am trying to log to, so i know that connection is working outside of docker.
one thing to note is that in the deployed dockerized instance, i see the same logs on startup as the successful local gradle output, but then it dies after it sets the profile. maybe meaning that it is dying during the tomcat initialization.
what to do/try here?
this ended up being due to a web proxy issue, switching networks or creating a proxy rule are solutions.

How to fix error "Enrollment failed" when trying WSO2 IoT 3.3.0 android enrollment?

I set up a new server windows 2012R2 in a VM machine. The latest active-mq and Apache-ant are downloaded. Oracle JDK 8u192 is used. After installation and setup of the WSO2 IoT application, I cannot enroll an android device.
I installed the WSO2IOT by following the instructions in the online documentations for version 3.3.0.
CARBON_HOME and JAVA_HOME are set up in environment variables already.
The process of steps that I go are as follows:
I start the activemq by running it inside a cmd window as instructed by the documentation.
I start broker.bat in another cmd window
I start iot-server.bat in another cmd window
I start analytics.bat in another cmd window
Everything starts and I end up with the text "Carbon .. has stared in ** milliseconds.
I open my management console on https port 9443\devicemgt and login as admin no problem.
After that I connect my galaxy A5 2016 model with android 7.0 to the same network via WiFi. Download the app via QR code from my PC screen to the mobile phone. Install the app and try to register. The IP which I enter is static in the VM and of course I add 8280 port in the wso2 management app on the phone. Then I login with admin/admin credentials which logins successfully but right after that it posts an message on the phone that it is receiving policy and here it stops. The little circle spins (loading) and nothing happens for few minutes after which I get an error "Enrollment failed. Contact the administrator. Enrollment failed." no other message or anything.
On the analytics cmd window I got the following error inside my VM:
[2018-12-20 11:00:00,037] [IoT-Analytics] ERROR {org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter} - Error in executing task: nulljava.lang.NullPointerException
at org.wso2.carbon.analytics.spark.core.CarbonAnalyticsProcessorService.executeQuery(CarbonAnalyticsProcessorService.java:256)
at org.wso2.carbon.analytics.spark.core.CarbonAnalyticsProcessorService.executeScript(CarbonAnalyticsProcessorService.java:206)
at org.wso2.carbon.analytics.spark.core.AnalyticsTask.execute(AnalyticsTask.java:60)
at org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:67)
at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
And that is basically it I cant move on forward from here. I tried with different java jdk versions as old as 8u144 and I tried with openJDK 8 LTSu191 to no avail.
Other things like creating policies in the devicemgt portal, creating users and browsing the portal works fine.
Did anyone encounter this issue and manage to solve it?
Thanks.
I used WM windows10. The situation fully corresponded to that described by you, with only one difference - I also had an error on the page with the preservation of policies for Android. I also saw that the default policies for windows are reflected in the platform configuration section, and the android policies are missing and cannot be saved due to the error you described. However, in the wso2 home directory I found the Android configuration file in which the default policy !!! was done.
Next, I used ADB to watch the log from the Android device, at the time of binding (enrollment). He only confirmed the previously received information. I saw a 404 http error at the time the device attempted to get a policy agreement. Point.
Unexpected outcome. I downloaded version 3.1.0 instead of the current version 3.3.0. I started the batch file. I went to the platform configuration section, to the Android configuration - the default agreement policy was displayed correctly and you can change it and save the changes. The binding procedure (enrollment) passed without problems - the policy was obtained by the device and then everything went according to official instructions. I fully realize that this is not the answer to the question you raised, but at the same time it can help with a quick start. I hope.
p.s. I tried versions 3.3.1 and 3.3.0 - in both there is a similar problem with the enrollment. Version 3.1.0 does not have this problem. Versions tested on Ubuntu and WM Windows10.
Of course it would be great if the developer representatives tell you where to dig, to use a more current version. Have a nice day.
additionaly - also good work with 3.2.0

GWT-SyncProxy for android : No remoteService in the classpath

In android client consuming my LoginService remote service, in order to connect user to the application.
I use gwt-syncproxy librairie to acces to my remote interface. And the following warning occured:
RpcPolicyFinder:No RemoteService in the classpath
followed by :
java.io.FileNotFoundException:
http:// localhost: . . . /. . ./application/application.nocache.js
Is there someone who had experienced this type of trouble ?
Please review the Android and CommonIssues wiki pages for the project as these clarify some common issues with the library.
In the meantime, more specifically, I often see this type of issue (though not this exactly) when the library has not been GWT-compiled or if the local server is not running where the Android app is expecting to find it. If you're not using App-Engine and are testing locally, make sure you are using Android's host Loopback interface with the #setLoginUrl method (GAELogin, Android Emulator networking).
Try posting the full error with details so we can see where it might be pointing wrong.
I think this issue is caused by a few reason:
1. You site is required login. And I checked the code of SyncProxy(0.5), it doesn't support if a site is secure.
2. SyncProxy will download some files from server side, for example:
compilation-mappings.txt
*.nocache.js
*.cache.html
*.gwt.rpc
If SyncProxy cannot download them, this error may occur, please check it these files can be download and the uri and name format of them is as default.
I was contacting with the owner of SyncProxy to improve this feature to support basic cookie/sessionid checking of auth.
https://github.com/jcricket/gwt-syncproxy/issues/46#issuecomment-89271311

Google App Engine instance crashing with ErrorCode 121

My GAE app suddenly stopped working last friday. I tried several times to start an instance in background, (both using cron and manually) but after a minute since the instance starts I get this error:
/cron/spreadsheet 500 4660ms 0kb instance=0 AppEngine-Google;
(+http://code.google.com/appengine)
0.1.0.1 - - [17/Feb/2013:12:40:05 -0800] "GET /cron/spreadsheet HTTP/1.1" 500 0 -
"AppEngine-Google; (+http://code.google.com/appengine)"
"backend.myclimagest.appspot.com" ms=4661 cpu_ms=692 queue_name=__cron
task_name=5ed789ec52683cb170ed3c2cc4ec48c9 pending_ms=3651 exit_code=121
instance=0
W 2013-02-17 12:40:05.268
A problem was encountered with the process that handled this request,
causing it to exit. This is likely to cause a new process to be used
for the next request to your application. (Error code 121)
I don't know what to do since this error code is undocumented. I also tried to redeploy but no luck. Are you experiencing the same problem and have you maybe found a solution?
I don't think it matters but the app is developed in Java using Eclipse.
The app is in production so I really need to solve this issue as quickly as I can.
Thank you
It seems your App Engine scheduler got problem. Try this, Removing the automatic settings from Performance settings which seeems to help. Google Groups
Check this Official Google page too Managing Your App's Resource Usage

Categories

Resources