I've seen that sometimes the OPTIONS request fails with an internal error (500) but i can't see any logs regarding it on the log viewer. It fails before reaching my Cloud Endpoint implementation and i don't even know where to start looking for the possible cause.
Is there any known reason/cause that could generate an OPTIONS request to fail with an Internal Error?
Note: I'm using JAVA runtime.
Thanks.
Related
There is currently a requirement for us to edit the text delivered error messages that the IBM Websphere throws when it could not access the application, we limited the IP addresses which can access the application.
in case of invalid IP address, Websphere looks for a custom error page which we added in our application but it can't access them so it throws
SRVE0260E: The server cannot use the error page specified for your application to handle the Original Exception printed below
also with 500 java.lang.RuntimeException: invalid host header
and 404 SRVE0295E: Error reported: 404
I already tried Webcontainer custom property com.ibm.ws.webcontainer.displayTextWhenNoErrorPageDefined which allows the display of the custom text when there is no error page defined at the application level, but it doesn't work.
and there is com.ibm.ws.webcontainer.suppressHtmlRecursiveErrorOutput which prevent printing stacktrace, but it's not a solution for me.
I just need to make these errors more human readable with just a simple text. and it needs to be done only in Websphere and not in the application code.
I opened a service request with IBM for this exact issue. I asked them if there is a way to customize the response for SRVE0260E. (that is, something similar to custom property com.ibm.ws.webcontainer.webgroupvhostnotfound for SRVE0017W)
IBM's response was, "I have discussed your concern with our SME, we don't have any property like that for SRVE0260E."
So, it appears the best we can do at the moment is suppress the stack trace with com.ibm.ws.webcontainer.suppressHtmlRecursiveErrorOutput.
here is the api response which works fine While posting data to the server I'm getting server volley error as response code but at the same time remaining API working fine.
HTTP 404 ordinary means "page not found" ...
host-name mydrivinglession.co.uk cannot even be resolved in DNS:
$ traceroute mydrivinglession.co.uk
mydrivinglession.co.uk: Name or service not known
... nor is it registered with co.uk
mydrivinglession.co.uk is available!
guess you would have to remove mydrivinglession.co.uk from your local hosts file... that most likely the only reason why the response, which you claim would be "working", appears to be "working".
one might want to establish a publicly available API, before attempting to perform requests... because your requests might run against a fantasy domain in the clouds, which nobody knows.
While calling endpoint API, sometimes we are getting 500 Unknown error from server, but most of the time API works fine. And also in case of 500 Unknown error, we are unable to see any logs in google console logs.
API response takes 2 sec approx. We are using App engine Java deployment.
Can anyone help me find the root cause of this problem?
Following is the chrome console error
/conge-portal/#!/dashboard/myage:1 XMLHttpRequest cannot load https://a-master-server.appspot.com/_ah/api/ageEndPoint/v1/aghie…5648/674390454714943921958166322392772?showTarget=true&month=May&year=2017. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost' is therefore not allowed access. The response had HTTP status code 500.
From the error message, it looks like browser rejected a preflight CORS OPTIONS request because "http://localhost" is not listed as the the allowed origins.
Are you using App Engine standard or App Engine Flex environment? CORS handling are different on these two platforms.
Issue stopped after migrating to endpoint framework 2.0
My website has suddenly started reporting this error when ever anyone logs in with Facebook:
HTTP Status 500 - Authorization is required for the operation, but the
API binding was created without authorization.
type Exception report
message Authorization is required for the operation, but the API
binding was created without authorization.
description The server encountered an internal error that prevented it
from fulfilling this request.
exception org.springframework.social.MissingAuthorizationException:
Authorization is required for the operation, but the API binding was
created without authorization.
I have not changed anything relating to Facebook logging in recently, so why might my website be suddenly giving this error?
It seems that version 2.2 of Facebook's Graph API (which is used for this kind of thing) ceased to be available on 25/3/17: See https://developers.facebook.com/docs/apps/changelog. Hence, the sudden change in behaviour in spite of there being no change to my website.
My website uses v1.1.0 of the spring-social-facebook library. I suspect this is the problem and that I ought to be using v2.0.3: http://projects.spring.io/spring-social-facebook/. However, I don't have the skills to take this any further.
I have a problem when try to send a message to a service bus topic through java azure sdk, I receive 500 Internal Server Error.
I prepared code based on this link: https://azure.microsoft.com/en-us/documentation/articles/service-bus-java-how-to-use-topics-subscriptions/ and my code looks like below:
Configuration config = ServiceBusConfiguration.configureWithSASAuthentication(
"NAMESPACE",
"SAS_NAME",
"SAS_KEY_VALUE",
".servicebus.windows.net");
ServiceBusContract service = ServiceBusService.create(config);
try {
BrokeredMessage message = new BrokeredMessage("Message content");
service.sendTopicMessage("TOPIC_NAME", message);
} catch (ServiceException e) {
e.printStackTrace();
}
I'm able to send a message with the same config values with .NET code.
And here is the exception that I receive: "com.sun.jersey.api.client.UniformInterfaceException: POST https://NAMESPACE.servicebus.windows.net/TOPIC_NAME/messages?api-version=2013-07 returned a response status of 500 Internal Server Error"
I have also a question about api-version. Why a library put so old api-version in the request? I use the latest version of azure sdk from maven repository:
<dependency>
<groupId>com.microsoft.azure</groupId>
<artifactId>azure-servicebus</artifactId>
<version>0.9.3</version>
</dependency>
I tried to reproduce your issue, but failed to not get any error information.
According to the REST API “Send Message”, the 500 status code means internal error that's not caused by your client source code.
So I think you can try to run the code again.
Could you share more information for helping analyze the issue if you still get the same error or others?
Any concern, please feel free to let me know.
I finally manage to find the reason of the issue. The real error is "There is no matching subscription found for the message with MessageId ..". This error occurs when in a topic configuration an option "Filter message before publishing" is checked and no matching subscription exists.
The problem is that a call to Azure REST API, which is used by Azure Java SDK, instead of information about no matching subscription found, returns just 500 Internal Server Error.. Only a call from Azure .NET SDK returns an exception with a useful comment.