App insight traces for one of micro servies shows System.OverflowException at System.IO.StreamWriter.write exception.Can help on this what will be the reason?
Related
The issue is been seen from two days that tomcat is not accessible though the process is running.
Due to this few functionalities are not working.
This is not new configuration.
May I know if someone could help me in finding the issue.
thanks
I have a problem with a webservice in Websphere ( although the same code is running quite fine in Wildfly ).
It is possible to generate a WSDL but I am not able to create a request in SOAPUI, because I always get the message:
User fault processing is not supported.The #WebFault faultbean is missing for ...
I do not have any annotation in my source code with #WebFault.
Is it possible to deactivate this "security" in Websphere without changing too much in the source code?
Since, it is running in Wildfly without any problems I think there must be an easy solution.
Maybe, somebody could help me please.
Thank you very much!
Developed an app using Xamarin.Android that periodically sends the location of the device through an API rest.
I randomly receive the following message in the UI: "My app is not responding, would you like to close it?"
I would like to know how to intercept the cause since I can not intercept it at development time.
Thank you.
Adding a crash reporter will definitely help you get to the bottom of your issue. Is there a chance that you are calling the REST service from the UI thread? If so, then if there is a network delay, it could "hang" the UI thread, this will result in Android killing the process because it thinks it is no longer working. To get around this issue use:
Task.Run(() => CallYourRESTService());
That way your UI thread won't be locked up. Just a suggestion. Of course it's hard to say without seeing a code sample.
I started getting 500 Internal Server Error(ISE) on Heroku, tried enabling debug level logs. The error is not consistent, it occurs for some request, for others it goes thru properly. When there is an ISE there is not even a single log line(even with debug on) in web dynos... I am able to see that the 500 response is given for the request.
From the client side am seeing the following
This exception has been logged with id 6gimbegj7
The above line tells that it should a response from Play! when it is running in production mode.
Attached New Relic monitoring plugin where it says the Exception occurred on NettyDispatcher (Netty IO server), not further info.
Any idea what could be the issue?
We have identified the problem here,
In play! we have a Global.java on the root of the packages, which has the methods like
onRequest(), onRequestRoute()
If there is any error at this place, and if we do not handle the exceptions, then Netty directly throws an 500 response to the request. This can happen from any part of the application. We did catch the exceptions in other part of the application but missed this one.
Mimicking the heoku env with the help of Foreman tool helped us to narrow down on the cause. As such setting the playframework log level to DEBUG did not throw any logs/stacktrace, Not sure why.
I have an AIR application that is causing me problems on a single client machine, and on a specific user account.
I have a debug interface that I developed to print traces to but apparently you can not get stack traces when not in a debugging environment.
I am seeing "TypeError #2007" with no additional information. I tried to output the error text using e.getStackTrace() and it returns null.
How can I get more information about this error on a client machine?
In this instance I was able to isolate the problem using a bunch of different try..catch statements and a lot of trace statements.
It took a lot of persistence and a lot of back and forth installing many different versions on the client machine and testing.
Obviously not an optimal solution in most cases, but one that worked.