I just new to spring boot project using STS 4.14, it seem the error message is represent different on local and remote.
For example, below is missing Service class declaration on web controller, so end up it display error message:
500 Error - No message available - java.lang.NullPointerException
However, if I run the project on LocalHost, the error message is much more helpful and explicit to show what cause the error.
So I would like to know is it anyway to make error message display on remote site as same as localhost? Because it is a Shopify plugin and relay on remote development.
Related
I have deployed a Spring Boot application onto a Google Kubernetes Engine workload. First, I pushed an image to Artifact Registry. Then, I ran the image using the docker run command in the gcloud command line. My GET request worked perfectly fine then, but once I deployed the image to a Kubernetes workload, the same GET request to the LoadBalancer returned a 500 Internal Server HTTP error.
Everytime I try going on Google's Error Reporting, it tells me to setup Error Reporting, but I don't really understand how to, and besides I thought HTTP errors automatically went to Error Reporting.
I'm sorry if there's too many extra details, I mainly want to know how to see the cause of an HTTP 500 error on a GKE deployment?
We are trying to make a connection from PowerBI Desktop, to the Google Big Query Database. Upon starting the app and immediately after trying to make the connection to the Google Data Source, we get the error below:
Unable to Connect
We encountered an error.
Details: "ODBC: ERROR [HY000] [Microsoft][DriverOAuthSupport] (8701) Error interacting with REST API: Couldn't resolve host name
ERROR [HY000] [Microsoft][DriverOAuthSupport] (8701) Error interacting with REST
API: Couldn't resolve host name"
I suppose that it has something to do with the proxy used inside our corporate environment but i haven't found anything so far on what urls/ports should be opened in order for this connection to work.
Please do keep in mind that this is a new business need and it is not something that worked and stopped working.
I am testing a deployment of MQ 9.0.1 using Docker, and trying to administer this instance using the Web console. However I am receiving a warning when attaching widgets stating the "Queue manager unavailable".
Warning messages
In the console I can see my Queues are running and have created local queues and can run commands against them.
Also if I try to modify the Queue security records I get another error:
Failed to get authority recordsWMQWB0003E: The request could not be completed due to an internal web application server error.
Any thoughts or suggestions around this issue?
There is no definitive fix for MQ9.0.1 but upgrading to use MQ9.0.2 will resolve issues with hosting MQ Console on linux.
I am trying to put my laravel project from localhost to server. On my localhost I run it as this:
http://localhost/nih/public/bassengweb/hvertime
But when I uploaded it to the server:
http://student.cs.hioa.no/~s180393/nih/public/bassengweb/hvertime
I get this error:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, amirahm#cs.hioa.no and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
thats not a laravel issue but a server issue. So lets trace it, according to your error information its a mostly is a configuration issue.
Set the server to read from the public folder and not the root.
When I try to call the Google places API using the Jersey REST standalone client it works fine and I am able to retrieve data. But the same code when made part of the web application deployed on weblogic server it throws a 500 internal error. I have tried calling the url directly as well, but that did not work. When the code tries to call the Google Places API it gets 500 internal error as response. I have also set host name verifier as none on weblogic server, that resolves the ssl exception but the 500 internal error is still there.