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.

Sign up for GitHub

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

Jump to bottom

When under load we are seeing a common error in our application logs: AdoNetCore.AseClient.AseException: There is no server listening at ... #215

Open
bbarry opened this issue Jun 23, 2021 · 1 comment · May be fixed by #216
Open

When under load we are seeing a common error in our application logs: AdoNetCore.AseClient.AseException: There is no server listening at ... #215

bbarry opened this issue Jun 23, 2021 · 1 comment · May be fixed by #216

Comments

@bbarry
Copy link

bbarry commented Jun 23, 2021

Describe the bug
This is going to be frustrating...

We have a scanning application performing compliance scans against our application which overnight makes a large number of requests to the application and eventually causes the application to become unavailable. When it becomes unavailable the exception is the one from

AdoNetCore.AseClient/src/AdoNetCore.AseClient/Internal/InternalConnectionFactory.cs

Line 163 in a0d87f8

throw new AseException($"There is no server listening at {_parameters.Server}:{_parameters.Port}.", 30294);

This exception hides the internal details of what is happening from us and we are unable to further diagnose our issue.

Can the internal exception that is here be added to the constructor of this exception on this line?
bbarry added a commit to bbarry/AdoNetCore.AseClient that referenced this issue Jun 23, 2021
@bbarry
pass the internal exception to the constructor
74da0cc 
fixes DataAction#215
@bbarry bbarry linked a pull request Jun 23, 2021 that will close this issue
Open
@Mies75
Copy link

Mies75 commented Oct 15, 2021

We still have this with version 0.19.2:
at AdoNetCore.AseClient.Internal.InternalConnectionFactory.CreateConnection(Socket socket, CancellationToken token) in C:\Users\tiennguyen\source\repos\AdoNetCore.AseClient.0.19.2\src\AdoNetCore.AseClient\Internal\InternalConnectionFactory.cs:line 166\r\n at AdoNetCore.AseClient.Internal.InternalConnectionFactory.GetNewConnection(CancellationToken token, IInfoMessageEventNotifier eventNotifier) in C:\Users\tiennguyen\source\repos\AdoNetCore.AseClient.0.19.2\src\AdoNetCore.AseClient\Internal\InternalConnectionFactory.cs:line 49\r\n at AdoNetCore.AseClient.Internal.ConnectionPool.Reserve(IInfoMessageEventNotifier eventNotifier) in C:\Users\tiennguyen\source\repos\AdoNetCore.AseClient.0.19.2\src\AdoNetCore.AseClient\Internal\ConnectionPool.cs:line 55\r\n at AdoNetCore.AseClient.AseConnection.Open() in C:\Users\tiennguyen\source\repos\AdoNetCore.AseClient.0.19.2\src\AdoNetCore.AseClient\AseConnection.cs:line 278\r\n at System.Data.Common.DbConnection.OpenAsync(CancellationToken cancellationToken)

Any idea?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

pass the internal exception to the constructor bbarry/AdoNetCore.AseClient
2 participants
@bbarry @Mies75