Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitor Connection Timeout errors from mediator #992

Closed
5 tasks
Tracked by #990
cvarjao opened this issue Mar 22, 2023 · 2 comments
Closed
5 tasks
Tracked by #990

Monitor Connection Timeout errors from mediator #992

cvarjao opened this issue Mar 22, 2023 · 2 comments

Comments

@cvarjao
Copy link
Member

cvarjao commented Mar 22, 2023

  • Reproduce the error (Jason has created some scripts) consistently from non prod (dev or test)
    • (Optional) Can we also reproduce the error with just AFJ
  • Does time out happened on the client side only? or server side as well?
  • Where those timeouts are set? and can we increase? server time out should be shorter (30s) than client side (45s)
  • Come up with something we can use to track the connection timeout error (log files?)

March 17th 2023, 14:59:22.548	aries-mediator-agent	2023-03-17 21:59:22,548 aries_cloudagent.transport.inbound.ws ERROR Unexpected Websocket message type received: WSMsgType.CLOSED: None, None
March 17th 2023, 14:56:39.975	aries-mediator-agent	2023-03-17 21:56:39,975 aries_cloudagent.transport.inbound.ws ERROR Unexpected Websocket message type received: WSMsgType.CLOSED: None, None

@cvarjao
Copy link
Member Author

cvarjao commented Apr 13, 2023

@swcurran , can you add this to aca-py backlog?

@swcurran
Copy link

Added as issue 75 in the aries-mediator-service repository.

Closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants