We're currently running on App Engine (Java) and want to test the new managed VMs that Google are beta testing.
Everything builds, but I can't get any of the endpoints to work.
When I build, the error that comes back is:
SEVERE: Endpoints configuration not updated. The app returned an
error when the Google Cloud Endpoints server attempted to communicate
with it.
In the admin logs I can see that it has attempted, but the error comes back:
API configuration update failed
The discovery docs get created locally, but there isn't anything in the logs.
I can see the POST to the getApiConfigs, but no details on the failure.
Hopefully someone else has encountered the same problem and can help?
In essence my question is, what do I need to do to get cloud endpoints running on a managed VM for App Engine?
Thanks
Have you checked your logs at https://console.cloud.google.com/logs/viewer ?
I had the same problem and after checking the logs I realized that I had two classes with the same API name and version but one had namespace and the other didn't.
All API classes with the same API name and version must have the exact same API-wide configuration.
I just set the namespace to be the same for both API's and it worked.
Related
I am trying to deploy my web application on my Payara 4.1 server. However I am getting the following error: java.lang.NoSuchMethodError: javax.faces.application.Application.addSearchKeywordResolver(Ljavax/faces/component/search/SearchKeywordResolver;)V
When I google this issue, I find a few people with the same problem, however they were all using outdated versions of Primefaces, but I am using the latest version (6.2) as you can see in the full logs below.
I've deployed my application before but I changed too much at one time so I don't know what triggered this error. However I did not change any of the library's/dependency's as for as I am aware.
If you need more information, let me know.
Full logs can be found here
I eventually deployed my application on a Glassfish 5 server and it worked again, I have no idea why though.
I am trying to use Bluemix monitoring and analytics service bounded to a java application running on Liberty runtime. But the service always shows application as unavailable (even though I can see and verify its working). And none of the stats on CPU/memory utilization & response/throughput times work. The application is started by calling the Main class and its NOT web application. Is there specific entry in manifest.yml for M&A to start working with the application. I have used M&A with node.js application and it worked well.
I thought I will just get an answer by simple google search but alas not able to find anything on this. Appreciate the help
The Monitoring & Analytics service generally assumes a web application. The availability tab is based on doing an http GET of your application's route as defined in Bluemix. Since yours is not a web application it presumably either doesn't have a route or doesn't respond to the one that it has if it does have one; this will cause M&A to report it as down.
Likewise for Liberty apps the performance data is gathered via Websphere application server JMX MBeans. If your app is not a web app, it is likely that it is invisible to these interfaces.
There was a temporary outtage due to network issues, but things should be resolved now. Restage your app and try again...
I have android application which is using multiple libraries (built into app: e.g. android support v7, barcode zxing, google play, and couple other less known).
Trying to resolve some functional issues, I detected that app periodically is doing web https requests to strange ec2.x.amazonaws.com addreses which are not mine servers at all.
Addresses are:
ec2.174-129-33-55.compute-1.amazonaws.com,
ec2.107-21-232-174.compute-1.amazonaws.com,
ec2.50-17-229-89.compute-1.amazonaws.com,
ec2.54-225-166-66.compute-1.amazonaws.com
In a quite large java code I cannot find explicit calls to these addresses.
So, question is, how to detect which component in my app is doing these requests?
I'm using android app "Network Log" to trace traffic.
Thank you for help.
You might see if stetho picks it up.
Was trying to use Stetho but no luck huking into tracing web requests. Was able to get chrome view but no info.
But I found what is doing requests: it's a Crashlytics crash monitoring service - I discovered this by trying to query ip in browser and checked ssl certificate info...
Back to SO after a long time :-).
I have deployed an ear for our application in Websphere (using this server for the first time). When I started the server, am getting a lot of errors (am not sure if it has got something to do with the bean configurations in the code).
I have attached the errors with this post. Can you please shed some light on it ? Am I missing something? Do jars need to be placed explicitly in some location?
Log 1
Log 2
I have been breaking head with this for more than 2 days now. Did all the search in Google but no clue where to start or what exactly is going wrong.
(i) I am able to deploy ear successfully.
(ii) When I start the server, am getting all the errors which I attached in the logs.
(iii) I am able to launch the application successfully (Can see the login page), but when I login, I get a 'WebPage CAnnot be found'. Well I can see the url changing as 'siteminderagent/forms/login.fcc'. This should be some kind of 3rd party authentication tool. I need to do some configuration for the same somewhere ?
First, WAS 7 is getting pretty old. For getting started with Websphere, if you can choose your version, use the current one. Second, read about the WAS class loaders because they may be a bit different than what you are familiar with from other app servers.
The error in log 1 looked like it may be associated with JPA. For JPA with WAS 7 IBM recommends installing a separate feature pack which provides Apache OpenJPA. If you still wanted/needed to use Hibernate there are instructions for how to configure an alternative JPA provider.
I have an android app with a GAE backend. I deploy the backend, and I used to be able to store entities in the datastore. However after the recent 1.7.6 sdk update, I can no longer do so. Connecting to the service, used to be https://1.myapp.appspot.com/_ah/api/, however that now generates a unverified error. I tried changing it to https://-1-myapp.appspot.com like the documentation said, however that just generates a 404 error. Anyway around this?