[ODBC-275] Faults after some time Created: 2020-03-18  Updated: 2020-04-21  Resolved: 2020-03-19

Status: Closed
Project: MariaDB Connector/ODBC
Component/s: General
Affects Version/s: 3.1.6
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Konstantinos Papadakis Assignee: Lawrin Novitsky
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

Windows 2019 / w3wp.exe 32bit

Issue Links:
Duplicate
is duplicated by ODBC-280 Process crashes after some time Closed

 Description   

For unknown reason, it stops to work and IIS application pool restarts.

From event log:
Faulting application name: w3wp.exe, version: 10.0.17763.1, time stamp: 0xa7ccada2
Faulting module name: maodbc.dll, version: 3.1.6.0, time stamp: 0x5e26d430
Exception code: 0xc0000409
Fault offset: 0x000a119f
Faulting process id: 0xefa0
Faulting application start time: 0x01d5fd16e3b51a2b
Faulting application path: C:\Windows\SysWOW64\inetsrv\w3wp.exe
Faulting module path: C:\Program Files (x86)\MariaDB\MariaDB ODBC Driver\maodbc.dll
Report Id: 49e10147-5e93-4ad5-82d3-62e87d1077cf
Faulting package full name:
Faulting package-relative application ID:

And after this:
Aborted connection xxxx to db: 'xxxxx' user: 'xxxxuser' host: 'server' (Got an error reading communication packets)

Any ideas,

Thanks
Costis

 Comments   
Comment by Konstantinos Papadakis [ 2020-03-18 ]

On server error log, I found the same errros:

[Warning] Aborted connection xxxx to db: 'xxxxx' user: 'xxxxuser' host: 'server' (Got an error reading communication packets)

Comment by Konstantinos Papadakis [ 2020-03-18 ]

After some testing, I found out that I use in connection string localhost that resolves as ::1. I changed that to 127.0.0.1 and it seems to solve the problem.

Comment by Lawrin Novitsky [ 2020-03-19 ]

Ok, I was about to ask more info, but you've solved your problem already.
It is strange though, that you had problem with ::1, and 127.0.0.1 solved it. But the reason can easily be somewhere not in the connector
Feel free to re-open the ticket, if you see the issue here, or if the problem persist

Generated at Thu Feb 08 03:27:30 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.