run_pipeline() never completes when the server side closes the connection during the pipeline; call_timeout and asyncio.wait_for don't end it

Abierto
  • ¿Algo no está bien?
#630 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
postgresql, python
Área
backend-api-design, database

Línea de trabajo

Start by tracing the async run_pipeline() implementation and how it handles socket closure, call timeouts, and task cancellation; the report gives a Python 3.12 Thin mode reproducer using connect_async. Reproduce with a TCP proxy that closes the connection after login, then compare the result with a direct database connection. Done when the pipeline raises on connection closure and timeout or cancellation ends the wait.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Versions

  • python-oracledb 4.0.1, Thin mode (connect_async)
  • Python 3.12.3, Linux x86_64
  • Oracle Database 23ai Free (container image), reached through a TCP proxy

What happens

The connection goes through a TCP proxy that inspects SQL. When the proxy refuses the request carrying the pipeline, it closes both TCP connections without sending a reply. await conn.run_pipeline(pipeline) then never returns or raises: there is no error and no result.

Ten seconds in, the client process holds no TCP socket to the proxy, only what looks like asyncio's internal socket pair. So python-oracledb has seen the close and dropped its socket, but the pending pipeline is never completed.

What we tried (each in its own process, killed by an outside timeout at 150 s):

Setting Result through the proxy Direct to the database
none no answer, killed at 150 s 6 results, 0.2 s
conn.call_timeout = 5000 no answer, 150 s ok
expire_time=1 no answer, 150 s ok
asyncio.wait_for(conn.run_pipeline(p), 10) no answer, 150 s (the cancellation hangs too) ok
call_timeout + expire_time no answer, 150 s ok

Expected

When the connection is closed while a pipeline is waiting for replies, run_pipeline() should raise (for example DPY-4011, "the database or network closed the connection"), as other calls on a closed connection do. call_timeout and task cancellation should also end the wait.

Repro sketch

  1. Put any TCP proxy between the client and a 23ai database that forwards the login, then closes both sides when it receives the first request after login.
  2. Run: 
    import asyncio, oracledb

async def main():
    conn = await oracledb.connect_async(user=..., password=..., dsn="proxyhost:port/FREEPDB1")
    p = oracledb.create_pipeline()
    for _ in range(6):
        p.add_fetchone("select 1 from dual")
    print(await conn.run_pipeline(p))   # never returns

asyncio.run(main())

We can run a debug build or extra logging if that helps.

Lenguaje dominante
Python
Estrellas
457
Forks
120
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de oracle/python-oracledb

Todos los issues de oracle/python-oracledb

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.