Connection resets on PgSqlAlerter.Start() without SSL options
Posted: Wed 19 Mar 2014 23:35
I'm using dotConnect for PostgreSQL 5.0.449.0 with PostgreSQL server 9.1.
I have a PgSqlDataSet which connects to my server through a shared PgSqlConnection. This connection is shared with a PgSqlAlerter component. My alerter's list is preloaded during design time with a few alerts and another one is amended after the PgSqlConnection is successfully opened. The alerter is only started for the first time after this supplemental alert is added. This is where the unexpected behaviour occurs.
At this point dbMonitor show a new connection request with almost the same parameters, only SslOptions are not copied. This results in a fatal error since my server is configured to refuse non-SSL connections. Disabling connection pooling doesn't help, a new connection is opened anyways.
I have a PgSqlDataSet which connects to my server through a shared PgSqlConnection. This connection is shared with a PgSqlAlerter component. My alerter's list is preloaded during design time with a few alerts and another one is amended after the PgSqlConnection is successfully opened. The alerter is only started for the first time after this supplemental alert is added. This is where the unexpected behaviour occurs.
At this point dbMonitor show a new connection request with almost the same parameters, only SslOptions are not copied. This results in a fatal error since my server is configured to refuse non-SSL connections. Disabling connection pooling doesn't help, a new connection is opened anyways.
Code: Select all
2014.03.20. 0:26:27 n/a dotConnect for PostgreSQL monitoring is started Complete
2014.03.20. 0:26:27 0,717 Open connection: "User Id=Y;Password=X;Host=0.0.0.0;Database=Z;Unicode=True;Character Set=UTF8;Pooling=True;SSLMode=Allow;" Complete
2014.03.20. 0:26:27 0,000 Connect: "User Id=Y;Password=X;Host=0.0.0.0;Database=Z;Unicode=True;Character Set=UTF8;Pooling=True;SSLMode=Allow" Complete
2014.03.20. 0:26:28 0,031 Execute: SELECT version() Complete
2014.03.20. 0:26:28 0,016 Execute: show integer_datetimes Complete
2014.03.20. 0:26:28 0,015 Execute: show bytea_output Complete
2014.03.20. 0:26:28 0,016 Execute: SET autocommit=true Complete
2014.03.20. 0:26:28 0,015 Execute: SET datestyle=ISO ; SET client_encoding='UTF8' Complete
2014.03.20. 0:26:28 0,016 Execute: SELECT oid FROM pg_type WHERE typname like 'geometry' Complete
2014.03.20. 0:26:28 0,016 Prepare: SET ROLE Y Complete
2014.03.20. 0:26:28 0,015 Execute: SET ROLE Y Complete
(log entries omitted) -> application executes PgSqlAlerter.Start() here
2014.03.20. 0:26:36 0,000 Creating pool with connections string: "User Id=Y;Password=X;Host=0.0.0.0;Database=Z;Unicode=True;Character Set=UTF8;Pooling=True;SSLMode=Disable" Complete
2014.03.20. 0:26:36 0,000 Creating object Complete
2014.03.20. 0:26:36 0,000 Creating pool with connections string: "User Id=Y;Password=X;Host=0.0.0.0;Database=Z;Unicode=True;Character Set=UTF8;Connection Timeout=0;Pooling=True;SSLMode=Disable" Complete
2014.03.20. 0:26:36 0,000 Creating object Complete
2014.03.20. 0:26:36 n/a Open connection: "User Id=Y;Password=X;Host=0.0.0.0;Database=Z;Unicode=True;Character Set=UTF8;Connection Timeout=0;Pooling=True;SSLMode=Disable;" Pending
2014.03.20. 0:26:36 0,000 Connect: "User Id=Y;Password=X;Host=0.0.0.0;Database=Z;Unicode=True;Character Set=UTF8;Connection Timeout=0;Pooling=True;SSLMode=Disable" Complete
2014.03.20. 0:26:37 0,000 Disconnect Complete