Discussion:
[JIRA] Created: (MYO-73) Npgsql 2.0 compability
Ben Roberts (JIRA)
2008-12-10 16:07:52 UTC
Permalink
Npgsql 2.0 compability
----------------------

Key: MYO-73
URL: https://forge.continuent.org/jira/browse/MYO-73
Project: Myosotis
Type: Improvement

Components: PostgreSQL protocol
Environment: Ubuntu, Windows 2003, .NET 2.0
Reporter: Ben Roberts
Assigned to: Gilles Rayrat
Priority: Minor


Is there any plan to release a version of the connector that is compatible with the latest npgsql (2.0.1) for .NET 2.0 dll. This maybe in development already, if it is then great! If not is there any plans for this and are there any time lines?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Robert Hodges (JIRA)
2008-12-10 16:23:51 UTC
Permalink
[ https://forge.continuent.org/jira/browse/MYO-73?page=comments#action_15053 ]

Robert Hodges commented on MYO-73:
----------------------------------

Are you seeing specific issues with npgsql 2.0.1 that we need to look at carefully? Thanks!
Post by Ben Roberts (JIRA)
Npgsql 2.0 compability
----------------------
Key: MYO-73
URL: https://forge.continuent.org/jira/browse/MYO-73
Project: Myosotis
Type: Improvement
Components: PostgreSQL protocol
Environment: Ubuntu, Windows 2003, .NET 2.0
Reporter: Ben Roberts
Assignee: Gilles Rayrat
Priority: Minor
Is there any plan to release a version of the connector that is compatible with the latest npgsql (2.0.1) for .NET 2.0 dll. This maybe in development already, if it is then great! If not is there any plans for this and are there any time lines?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Ben Roberts (JIRA)
2008-12-10 16:34:51 UTC
Permalink
[ https://forge.continuent.org/jira/browse/MYO-73?page=comments#action_15054 ]

Ben Roberts commented on MYO-73:
--------------------------------

Yes I am finding that when I use the npgsql.dll 2.0.1 in my .NET application and query a database I get an error -

"02000 - No results were returned by the query"

When I change the reference to the npgsql 1.0.1 it works fine.

The connector is currently installed on a test bed at the moment. Setup as follows

DB is postgres 8.3
3 Linux (Ubuntu servers) , 1 as DB backend only, 2 as controllers also with DB backends running Continuent unicluster
1 Windows 2003 server running IIS with our test app a .net webservice application
The app accesses the Virtual DB via connector installed on uconnector Controller1 (Connector and unicluster was setup by Gilles Rayrat)

I can attach a log of the connector is required.
Post by Ben Roberts (JIRA)
Npgsql 2.0 compability
----------------------
Key: MYO-73
URL: https://forge.continuent.org/jira/browse/MYO-73
Project: Myosotis
Type: Improvement
Components: PostgreSQL protocol
Environment: Ubuntu, Windows 2003, .NET 2.0
Reporter: Ben Roberts
Assignee: Gilles Rayrat
Priority: Minor
Is there any plan to release a version of the connector that is compatible with the latest npgsql (2.0.1) for .NET 2.0 dll. This maybe in development already, if it is then great! If not is there any plans for this and are there any time lines?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Gilles Rayrat (JIRA)
2009-02-24 15:28:56 UTC
Permalink
[ https://forge.continuent.org/jira/browse/MYO-73?page=comments#action_15316 ]

Gilles Rayrat commented on MYO-73:
----------------------------------

Ben did a bit of debugging on this and it appears that sequoia doesn't like the following command:

INFO | jvm 1 | 2009/02/24 15:07:35 | TRACE [PostgreSQLProtocolHandler] - Processing query: unlisten *
INFO | jvm 1 | 2009/02/24 15:07:35 | ERROR [PostgreSQLProtocolHandler] - Error processing query: unlisten *
INFO | jvm 1 | 2009/02/24 15:07:35 | org.continuent.sequoia.common.exceptions.driver.DriverSQLException: Message of cause: Request unlisten * failed on backend ctl2b1 (No results were returned by the query.)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.driver.Connection.statementExecute(Connection.java:3059)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.driver.Statement.execute(Statement.java:484)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.driver.Statement.execute(Statement.java:461)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.myosotis.protocol.postgresql.PostgreSQLProtocolHandler.handleQueryCommand(PostgreSQLProtocolHandler.java:761)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.myosotis.protocol.postgresql.PostgreSQLProtocolHandler.handleCommand(PostgreSQLProtocolHandler.java:325)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.myosotis.protocol.postgresql.PostgreSQLProtocolHandler.handleClientRequest(PostgreSQLProtocolHandler.java:143)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.myosotis.protocol.postgresql.PostgreSQLConnectionHandler.run(PostgreSQLConnectionHandler.java:72)
INFO | jvm 1 | 2009/02/24 15:07:35 | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
INFO | jvm 1 | 2009/02/24 15:07:35 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
INFO | jvm 1 | 2009/02/24 15:07:35 | at java.lang.Thread.run(Thread.java:595)
INFO | jvm 1 | 2009/02/24 15:07:35 | Caused by: org.continuent.sequoia.common.exceptions.driver.protocol.BackendDriverException: Request unlisten * failed on backend ctl2b1 (No results were returned by the query.)
INFO | jvm 1 | 2009/02/24 15:07:35 | Caused by: org.continuent.sequoia.common.exceptions.driver.protocol.SerializableException: No results were returned by the query.
INFO | jvm 1 | 2009/02/24 15:07:35 | SerializableStackTrace of each cause:
INFO | jvm 1 | 2009/02/24 15:07:35 | org.continuent.sequoia.common.exceptions.driver.protocol.BackendDriverException: Request unlisten * failed on backend ctl2b1 (No results were returned by the query.)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.common.exceptions.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:48)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.loadbalancer.raidb1.RAIDb1.executeRequestOnBackend(RAIDb1.java:506)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.loadbalancer.raidb1.RAIDb1_LPRF.executeLPRF(RAIDb1_LPRF.java:216)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.loadbalancer.raidb1.RAIDb1_LPRF.execSingleBackendReadRequest(RAIDb1_LPRF.java:96)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.loadbalancer.raidb1.RAIDb1.statementExecuteQuery(RAIDb1.java:163)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.requestmanager.RequestManager.statementExecuteQuery(RequestManager.java:623)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.requestmanager.distributed.DistributedRequestManager.execLocalStatementExecuteQuery(DistributedRequestManager.java:1401)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.requestmanager.distributed.DistributedRequestManager.statementExecuteQuery(DistributedRequestManager.java:1425)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.virtualdatabase.VirtualDatabase.statementExecuteQuery(VirtualDatabase.java:593)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.virtualdatabase.VirtualDatabaseWorkerThread.statementExecute(VirtualDatabaseWorkerThread.java:2493)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.virtualdatabase.VirtualDatabaseWorkerThread.run(VirtualDatabaseWorkerThread.java:478)
INFO | jvm 1 | 2009/02/24 15:07:35 | Caused-by
INFO | jvm 1 | 2009/02/24 15:07:35 | org.continuent.sequoia.common.exceptions.driver.protocol.SerializableException: No results were returned by the query.
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:236)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.loadbalancer.AbstractLoadBalancer.executeStatementExecuteQueryOnBackend(AbstractLoadBalancer.java:927)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.loadbalancer.raidb1.RAIDb1.executeRequestOnBackend(RAIDb1.java:494)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.loadbalancer.raidb1.RAIDb1_LPRF.executeLPRF(RAIDb1_LPRF.java:216)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.loadbalancer.raidb1.RAIDb1_LPRF.execSingleBackendReadRequest(RAIDb1_LPRF.java:96)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.loadbalancer.raidb1.RAIDb1.statementExecuteQuery(RAIDb1.java:163)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.requestmanager.RequestManager.statementExecuteQuery(RequestManager.java:623)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.requestmanager.distributed.DistributedRequestManager.execLocalStatementExecuteQuery(DistributedRequestManager.java:1401)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.requestmanager.distributed.DistributedRequestManager.statementExecuteQuery(DistributedRequestManager.java:1425)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.virtualdatabase.VirtualDatabase.statementExecuteQuery(VirtualDatabase.java:593)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.virtualdatabase.VirtualDatabaseWorkerThread.statementExecute(VirtualDatabaseWorkerThread.java:2493)
INFO | jvm 1 | 2009/02/24 15:07:35 | at org.continuent.sequoia.controller.virtualdatabase.VirtualDatabaseWorkerThread.run(VirtualDatabaseWorkerThread.java:478)
INFO | jvm 1 | 2009/02/24 15:07:36 | ERROR [PostgreSQLConnectionHandler] - Socket error, closing connection: /91.192.194.163:4556
INFO | jvm 1 | 2009/02/24 15:07:36 | java.net.SocketException: Connection reset
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.net.SocketInputStream.read(SocketInputStream.java:168)
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.net.SocketInputStream.read(SocketInputStream.java:182)
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.io.DataInputStream.readByte(DataInputStream.java:241)
INFO | jvm 1 | 2009/02/24 15:07:36 | at org.continuent.myosotis.protocol.postgresql.PostgreSQLPacket.<init>(PostgreSQLPacket.java:54)
INFO | jvm 1 | 2009/02/24 15:07:36 | at org.continuent.myosotis.protocol.postgresql.PostgreSQLProtocolHandler.handleCommand(PostgreSQLProtocolHandler.java:320)
INFO | jvm 1 | 2009/02/24 15:07:36 | at org.continuent.myosotis.protocol.postgresql.PostgreSQLProtocolHandler.handleClientRequest(PostgreSQLProtocolHandler.java:143)
INFO | jvm 1 | 2009/02/24 15:07:36 | at org.continuent.myosotis.protocol.postgresql.PostgreSQLConnectionHandler.run(PostgreSQLConnectionHandler.java:72)
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.lang.Thread.run(Thread.java:595)
INFO | jvm 1 | 2009/02/24 15:07:36 | DEBUG [PostgreSQLConnectionHandler] - Stop serving client: /91.192.194.163:4556
INFO | jvm 1 | 2009/02/24 15:07:36 | ERROR [PostgreSQLConnectionHandler] - Socket error, closing connection: /91.192.194.163:4555
INFO | jvm 1 | 2009/02/24 15:07:36 | java.net.SocketException: Connection reset
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.net.SocketInputStream.read(SocketInputStream.java:168)
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.net.SocketInputStream.read(SocketInputStream.java:182)
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.io.DataInputStream.readByte(DataInputStream.java:241)
INFO | jvm 1 | 2009/02/24 15:07:36 | at org.continuent.myosotis.protocol.postgresql.PostgreSQLPacket.<init>(PostgreSQLPacket.java:54)
INFO | jvm 1 | 2009/02/24 15:07:36 | at org.continuent.myosotis.protocol.postgresql.PostgreSQLProtocolHandler.handleCommand(PostgreSQLProtocolHandler.java:320)
INFO | jvm 1 | 2009/02/24 15:07:36 | at org.continuent.myosotis.protocol.postgresql.PostgreSQLProtocolHandler.handleClientRequest(PostgreSQLProtocolHandler.java:143)
INFO | jvm 1 | 2009/02/24 15:07:36 | at org.continuent.myosotis.protocol.postgresql.PostgreSQLConnectionHandler.run(PostgreSQLConnectionHandler.java:72)
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.lang.Thread.run(Thread.java:595)
INFO | jvm 1 | 2009/02/24 15:07:36 | ERROR [PostgreSQLConnectionHandler] - Socket error, closing connection: /91.192.194.163:4554
INFO | jvm 1 | 2009/02/24 15:07:36 | java.net.SocketException: Connection reset
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.net.SocketInputStream.read(SocketInputStream.java:168)
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.net.SocketInputStream.read(SocketInputStream.java:182)
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.io.DataInputStream.readByte(DataInputStream.java:241)
INFO | jvm 1 | 2009/02/24 15:07:36 | at org.continuent.myosotis.protocol.postgresql.PostgreSQLPacket.<init>(PostgreSQLPacket.java:54)
INFO | jvm 1 | 2009/02/24 15:07:36 | at org.continuent.myosotis.protocol.postgresql.PostgreSQLProtocolHandler.handleCommand(PostgreSQLProtocolHandler.java:320)
INFO | jvm 1 | 2009/02/24 15:07:36 | at org.continuent.myosotis.protocol.postgresql.PostgreSQLProtocolHandler.handleClientRequest(PostgreSQLProtocolHandler.java:143)
INFO | jvm 1 | 2009/02/24 15:07:36 | at org.continuent.myosotis.protocol.postgresql.PostgreSQLConnectionHandler.run(PostgreSQLConnectionHandler.java:72)
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
INFO | jvm 1 | 2009/02/24 15:07:36 | at java.lang.Thread.run(Thread.java:595)
INFO | jvm 1 | 2009/02/24 15:07:36 | DEBUG [PostgreSQLConnectionHandler] - Stop serving client: /91.192.194.163:4555
INFO | jvm 1 | 2009/02/24 15:07:36 | DEBUG [PostgreSQLConnectionHandler] - Stop serving client: /91.192.194.163:4554

We might want to intercept notification-related commands and not send them to the cluster
Post by Ben Roberts (JIRA)
Npgsql 2.0 compability
----------------------
Key: MYO-73
URL: https://forge.continuent.org/jira/browse/MYO-73
Project: Myosotis
Type: Improvement
Components: PostgreSQL protocol
Environment: Ubuntu, Windows 2003, .NET 2.0
Reporter: Ben Roberts
Assignee: Gilles Rayrat
Priority: Minor
Is there any plan to release a version of the connector that is compatible with the latest npgsql (2.0.1) for .NET 2.0 dll. This maybe in development already, if it is then great! If not is there any plans for this and are there any time lines?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Gilles Rayrat (JIRA)
2009-03-06 14:55:56 UTC
Permalink
[ https://forge.continuent.org/jira/browse/MYO-73?page=all ]

Gilles Rayrat closed MYO-73:
----------------------------

Resolution: Fixed
Fix Version: 0.6.6

Fixed by a workaround (listen/notify/unlisten ignored), waiting for a better solution that would be to fix MYO-38
Post by Ben Roberts (JIRA)
Npgsql 2.0 compability
----------------------
Key: MYO-73
URL: https://forge.continuent.org/jira/browse/MYO-73
Project: Myosotis
Type: Improvement
Components: PostgreSQL protocol
Environment: Ubuntu, Windows 2003, .NET 2.0
Reporter: Ben Roberts
Assignee: Gilles Rayrat
Priority: Minor
Fix For: 0.6.6
Is there any plan to release a version of the connector that is compatible with the latest npgsql (2.0.1) for .NET 2.0 dll. This maybe in development already, if it is then great! If not is there any plans for this and are there any time lines?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Loading...