EDC8121I Connection reset. (errno2=0x76650446) issue while trying to send mail using MS Graph API (java)

Question

EDC8121I Connection reset. (errno2=0x76650446) issue while trying to send mail using MS Graph API (java)

B Jayachithra 51

Hello Team,

Application to send mail via MS Graph API (written in java) is deployed on websphere server and while trying to connect Microsoft site login.microsoftonline.com:443 via proxy server ,it fails with below error message.

"Caused by: java.io.IOException: java.util.concurrent.ExecutionException: com.microsoft.aad.msal4j.MsalClientException: reactor.core.Exceptions$ReactiveException: io.netty.handler.proxy.ProxyConnectException: http, none, httppxgot.xxx.xxxxx.com/xxxxxxx => login.microsoftonline.com:443, java.io.IOException: EDC8121I Connection reset. (errno2=0x76650446)"

This issue happens randomly when multiple http post request to send mail placed within short period to connect Microsoft site

Please let us know how to fix issue

Thanks,

Jaya

B Jayachithra 51 Reputation points

2023-05-03T14:38:41.85+00:00

Hello,

Can you reply on how to fix issue?
Antonio 250 Reputation points Microsoft External Staff

2023-05-05T21:59:35.41+00:00

Please see the below answer.

--please don't forget to upvote and Accept as answer if the reply is helpful--

1 answer

Your answer

B Jayachithra 51 Reputation points

2023-05-03T14:38:41.85+00:00

Hello,

Can you reply on how to fix issue?
Antonio 250 Reputation points Microsoft External Staff

2023-05-05T21:59:35.41+00:00

Please see the below answer.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 1

Hi B Jayachithra,

Thanks for posting on Q&A forum. The error code given was returned to JAVA from the WebSphere server connection to login.microsoftonline.com:443.

Upon researching that error (EDC8121I Connection reset. (errno2=0x76650446)) on the IBM documentation it was noted as caused by "The connection was forcibly closed by the peer"

Upon looking further into the JAVA errors (java.util.concurrent.ExecutionException & io.netty.handler.proxy.HttpProxyHandler.HttpProxyConnectException) indicates that an error code was thrown via code executed in in Future that wasn't handled.

To capture more information from the exception, create launderThrowable method that take care of unwrapping generic ExecutionExceptions. See here for more details with JAVA code.

Also, as this seems to relate more to the connection/proxy/server setup. It would also be good to review a tcpdump/Wireshark. You can also do this via JAVA parser code.

Due to being mentioned as this is occurring when multiple POST requests for (sendMail) are placed in a short period of time. Further the HTTPS error 500 indicates more of an internal server error and review:

Throttling limit exceed for request calls in a certain time period.
- https://learn.microsoft.com/en-us/graph/throttling
- https://learn.microsoft.com/en-us/graph/throttling-limits
- Note: That throttling limits are applicable to all services. Internal limits (or lack of) within the organization are separate from throttling limits of GRAPH API. Also note that to extract a large volume of data from Microsoft Graph should use Microsoft Graph Data Connect instead of the Microsoft Graph REST APIs. Microsoft Graph Data Connect allows organizations to extract Microsoft 365 data in bulk without being subject to throttling limits.
Mail server limit exceeded sending messages in a certain time period.
- https://learn.microsoft.com/en-us/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#receiving-and-sending-limits
Review Network Topology and Load Balancing
- https://learn.microsoft.com/en-us/azure/developer/java/migration/migrate-websphere-to-virtual-machines#determine-the-network-topology
- https://www.ibm.com/docs/en/mfci/7.6.2?topic=haas-websphere-application-server-network-deployment-load-balanced-clustering

We recommend using JSON batching implemented with try...catch logic to mitigate potential throttling issues (if applicable). See this learning path for a real-world training example using NET Core and JAVA Tutorial showing listing of an inbox with catch...try logic.

Also, to review the email sending limits of the email server in question.

One last item for consideration is a new preview product Microsoft Graph Developer Proxy v0.7 which allows you to simulate behaviors on any API. using a list of API URLs to simulate errors (including throttling & server issues).

Finally, if a further review/analysis of Proxy/Network/API setup is required.

Please redirect with all details on specific 3rd party server setup or for Azure support.

Open a support request with IBM WebSphere

Open a support request with Azure Support

--please don't forget to upvote and Accept as answer if the reply is helpful--

B Jayachithra 51 Reputation points

2023-05-08T11:15:29.4533333+00:00

Hello,

I checked our organization Azure team and understand that no limit has been set for application in our organization tenant. so throttling limit will not be an issue.

Below is error message returned from graph api to Mainframe log.This is how HTTP response received when concurrent request placed at same time. here May 1st 17:45,17:46,17:46

"Response is : HTTP/1.1 200 OK Date: Mon, 01 May 2023 17:45:21 GMT X-Powered-By : Servlet/3.0 Content-Length: 64 Connection: close Content-Language: en-US <GRPHAPIMSGS>Message sent </GRPHAPIMSGS><GRPHAPIRC>0</GRPHAPIRC>

Response is : HTTP/1.1 500 Internal Server Error Date: Mon, 01 May 2023 17:46:41 GMT X-Powered-By: Servlet/3.0 $WSEP: Content-Length: 81 Connection: close Content-Type: text/html;charset=ISO-8859-1 Content-Language: en-US Error 500: com.microsoft.graph.core.ClientException: Error executing the request

Response is : HTTP/1.1 200 OK Date: Mon, 01 May 2023 17:46:51 GMT X-Powered-By : Servlet/3.0 Content-Length: 64 Connection: close Content-Language: en-US <GRPHAPIMSGS>Message sent </GRPHAPIMSGS><GRPHAPIRC>0</GRPHAPIRC> "

can you provide how to add logging request in JAVA to trace below

a.full HTTP headers for both the request and the response.

b.full JSON payload for both the request and the response.

Also I tried with try-catch logic as below and it just says

Error sending mail

Error executing the request"

Please let me know how to fix this issue

_app.users(user) .sendMail(UserSendMailParameterSet .newBuilder() .withMessage(message) .withSaveToSentItems(null) .build()) .buildRequest() .post(); }catch(Exception e) { e.printStackTrace(); System.out.println("Error sending mail"); System.out.println(e.getMessage()); }
Antonio 250 Reputation points Microsoft External Staff

2023-05-08T16:59:48.4866667+00:00

Added further items in original post with some further instruction on additional support (if needed).

--please don't forget to upvote and Accept as answer if the reply is helpful--

Share via

EDC8121I Connection reset. (errno2=0x76650446) issue while trying to send mail using MS Graph API (java)

1 answer

Your answer