Have you already get Error -439 message ?????
Posted in 1999
Topics: Connectivity: ESQL/C, 4GL & Embedded SQL, Platform-Specific Issues
Hello, I've got a problem with a program written in ESQL/C. This program is a server (DCE server) that for each client request, connects to database then executes queries and before ending client request, disconnect from database. After several client request, i've got this error message when trying to connect to database: here is finderr contents: -439 Database server is currently processing an SQL task. You attempted to call an SQL routine or attempted to execute an SQL statement within a signal handling function/routine or a callback function/procedure. Use only the sqldone() and sqlbreak() library functions inside your INFORMIX-ESQL/C callback function. Use only the ECO-SQD and ECO-SQB library routines inside your ESQL/COBOL callback procedure. In addition, if you want to unregister your callback function in INFORMIX-ESQL/C, you can invoke the sqlbreakcallback() callback registration function within your callback procedure. If you want to unregister your callback procedure in ESQL/COBOL, you can invoke the ECO-SQBCB callback registration routine within your callback procedure. Have you already get this error message and if so, what is the reason why this problem occurr. I'm not sure to understand correctly this error Remark: i'm working with informix online 7.24 on HP-UX 10.20 Can you help me please. Thank you very much P. Gineste disconnect
pascal gineste wrote: > > Hello, > > I've got a problem with a program written in ESQL/C. > > This program is a server (DCE server) that for each client request, > connects to > database then executes queries and before ending client request, > disconnect > from database. > > After several client request, i've got this error message when > trying to > connect to database: > here is finderr contents: > > -439 Database server is currently processing an SQL task. Sounds like you did not actually successfully disconnect from the server after servicing the last client. Do you have error checking on the disconnect statement? Chances are it failed with an SQLCODE -439 also. This means that there is a query already in process that could not be interrupted. Call the library function sqlbreak() which will stop the query in process, then disconnect and reconnect to clean up the problem. Art S. Kagel