We Keep Coding

Getting ClientException: Error during http request in download api the msgraph-sdk-java

I am using below code to download the OneDrive file.
oneDriveGraphClient.graphServiceClient.me().drive().items("oneDriveFileItemId").content()
.buildRequest()
.get().use {
it.buffered().copyTo(outputStream!!)
}
It used to work but recently we found out that it started giving com.microsoft.graph.core.ClientException: Error during http request error this exception is caused by Caused by: java.lang.IllegalStateException
In release we are using 2.3.0 msgraph-sdk-java version
On searching the similar result in StackOverflow I found this SO thread. And it seems to be a service change.
I have few queries regarding this change
When this change got rolled out? And is there any documentation for the same? Is this a phase rollout?
What is the purpose regarding this change?
Is there any behaviour change in the MS-Java sdk or testing impact that we should be aware of?
Can we disable this change from azure console? As we are getting error analytics regarding this and upgrading the msgraph-sdk-java will take time in testing

getting too many follow-up request as response of request

we have a Restful web service created using Jersey and running on TomEE 7.0.3
we are using Android platform for client-side and it's using Retrofit for having communication with the server.
our system is modular and contains more than 14 parts.
about 3 weeks (until now), sometimes the clients getting too many follow-up requests as the response.
we searched for it in here and retrofit issues in github.
they said that it might be server falt so we trace the request with ngrep command on the server.
we saw that server was getting the request and also responding to it correctly even when clients get follow-up.
we also test this matter with different networks and this matter still remains.
so what else could cause this problem?

after several tests, we realized that this error is only on Android platforms (we tested the APIs with Postman when Android platforms were receiving Too many follow up request.
so after some more tests, we found out, when Android platforms get 408 as a response code they show this message. we changed the status code and this problem fixed.
I put this issue on square/okhttp repository in github and they put the bug flag on it.
you can see it here
---- update ----
they said it fixed in OkHttp v3.10

Android AWS Cognito: unable to resolve host

I am having difficulty getting Cognito registration and login to work for my app in Android Studio using this sample. When I attempt to log in via the simulator, the app works for a few seconds, then displays an error message: "Unable to execute HTTP request: Unable to resolve host 'cognito-idp.us-east-1.amazonaws.com': No address associated with hostname". This same error is the only error that appears in the console. I have seen similar questions and tried solutions such as checking to ensure my app has the permissions android.permission.INTERNET and android.permission.ACCESS_NETWORK_STATE, but the error persists. It also doesn't seem to be a network issue. I have updated to the latest version of the Android SDK as well as the AWS SDK, and the problem persists.
I currently I have a Cognito user pool set up which works properly for login on the iOS version of my app. Following the instructions in the readme for the sample code, I added an app to my existing user pool, and then copied and pasted the newly generated app client ID and app client secret into AppHelper.java for clientId and clientSecret respectively. I also set userPoolId to the ID listed for my user pool under "pool details" in the Cognito conosle, and cognitoRegion to US East, since this is the region of my user pool. I noticed that there was no need for me to set the pool name, as there was in the iOS version, so I'm wondering if that's something I need to do.
Sorry if this counts as a duplicate, but I wanted to post a question with the exact error message I encountered and the steps I took, and I'm wondering if someone has managed to get this specific sample working and what I should do.

The problem has been resolved, but unfortunately I'm not quite sure what fixed it since I didn't change anything in the code. All I did was install an update, so anyone with a similar problem should probably ensure that all SDKs used in the sample are properly updated, along with the simulator. It's also worth noting that I was using a different network than in my previous tests, so it's possible that it was a network issue after all.

I had the same issue.
The issue occurred when I used a VPN with emulator to test my program. The reason was that the internet connection in the emulator was too slow when connecting through a VPN.
This could also happen if your internet connection is not strong enough.
The solution is, use a real android device to test your code, if your internet connection is not good enough.
More info: https://github.com/aws-amplify/aws-sdk-android/issues/567

Issues with Java EWS API

I am using Java EWS API in my web application to connect my application to MS Exchange and read user email requests. Also I am using a scheduler to pull subscription every 1 minute.
Problem is when I start my application, EWS-API works fine. It gets all new mails and processes it. But after few days, whenever the scheduler tries to pull the subscription inbox, the application throws the following error :
microsoft.exchange.webservices.data.ServiceResponseException: The specified subscription was not found.
Maybe it is thread issue or memory issue, I am not sure. Please suggest any reason for this issue.

Have a look at this article, the Client Access Server affinity issue it describes maybe what you are encountering.
http://blogs.msdn.com/b/exchangedev/archive/2011/07/20/client-access-server-affinity-and-network-load-balancing-considerations-for-programmatic-access-to-exchange-online.aspx
Supposedly if you use the EWS Java version 1.1 library (or later) you shouldn't get this particular issue however.
So I'd try checking your EWS library version, and if you still get the problem, add retry logic into your app to recreate the subscription when you encounter this error.

I have been using EWS Push subscription since 2017 so not sure if below might help or not but if you can share your code I can check and see if I can found something.
For Push Subscription I have seen many different errors and to avoid any issues I am using an Object Pool of connection and if I encounter any random error from Exchange Server, I discard current connection and create a new one which mostly solve these kind of issues.
Also you can try setting anchor mailbox while establishing connection it helps with some of the issues.
Also if you can share some sample code I am happy to check.

Has anyone gotten Recaptcha to run on the Google App Engine (in Java)?

I followed the recaptcha instructions and created a simple app that works if I run it in Eclipse using a local Tomcat server but the same files give an error (verify-params-incorrect) when validating the user's response when run in Eclipse using the local Google App Engine SDK.

Are you using the Java code linked to on the reCAPTCHA site? I took a quick look at it, and I suspect that the SimpleHttpLoader class uses some Java classes that are no allowed by Google's AppEngine.
So, here is what I know: Running locally, I get the same error as you.
But, when I deploy it to AppEngine, it works! For the forum posts I've read, I suspect it has to do with the remote IP address (127.0.0.1) when running locally.

This is sort of an impertinent answer, but are you sure you really need to pester your potential users with a captcha at all? There's a great article over on sitepoint entitled "10 Things to Check Before Using a CAPTCHA"

I had no problems at all locally with Google App Engine or deployed with recaptcha4j-0.0.8.jar and Google App Engine SDK 1.6.6. I followed the reCaptcha tutorial for Java at https://developers.google.com/recaptcha/docs/java.
Check here for recaptcha4j lastest version: http://code.google.com/p/recaptcha4j/downloads/list