Skip to main content

Acu4GL - Connection is busy with results for another hstmt

  • November 11, 2011
  • 2 replies
  • 0 views

[Migrated content. Thread originally posted on 10 November 2011]

Hi there,

We have upgraded to extend 9.0.1 and use Acu4GL for MSSQL (sql 2005) and have found that on occassions we are throwing an error about SQL being busy
09:46:19.869000 execute_with_COBOL_data
09:46:19.869000 Executing previously prepared statement f0d6d8 on server 'JUPITER\\MSSQL2005'
09:46:19.869000 report_status called from 3810
09:46:19.869000 [1] HY000 0 - Connection is busy with results for another hstmt
09:46:19.869000 No more messages

We do have other threads that perform read/write operations on data files in the background of the current session. I cannot say that this was ever noticeable with the 7.2.2 runtime

Has anyone come across this ?

2 replies

Stephen Hjerpe
  • Participating Frequently
  • 1100 replies
  • November 11, 2011

[Migrated content. Thread originally posted on 10 November 2011]

Hi there,

We have upgraded to extend 9.0.1 and use Acu4GL for MSSQL (sql 2005) and have found that on occassions we are throwing an error about SQL being busy
09:46:19.869000 execute_with_COBOL_data
09:46:19.869000 Executing previously prepared statement f0d6d8 on server 'JUPITER\\MSSQL2005'
09:46:19.869000 report_status called from 3810
09:46:19.869000 [1] HY000 0 - Connection is busy with results for another hstmt
09:46:19.869000 No more messages

We do have other threads that perform read/write operations on data files in the background of the current session. I cannot say that this was ever noticeable with the 7.2.2 runtime

Has anyone come across this ?
Hi Julie,

We believe this is a bug and that there may already be an RPI on this issue, please contact Customer Care. To answer your question, When a query is sent to the server on a statement handle, the program must either get all the results from that query, or somehow cancel the query.If you do something else besides one of those things, you get this error. Our interface should never do that.

I hope this helps.

  • Author
  • Rocketeer
  • 19312 replies
  • November 14, 2011

[Migrated content. Thread originally posted on 10 November 2011]

Hi there,

We have upgraded to extend 9.0.1 and use Acu4GL for MSSQL (sql 2005) and have found that on occassions we are throwing an error about SQL being busy
09:46:19.869000 execute_with_COBOL_data
09:46:19.869000 Executing previously prepared statement f0d6d8 on server 'JUPITER\\MSSQL2005'
09:46:19.869000 report_status called from 3810
09:46:19.869000 [1] HY000 0 - Connection is busy with results for another hstmt
09:46:19.869000 No more messages

We do have other threads that perform read/write operations on data files in the background of the current session. I cannot say that this was ever noticeable with the 7.2.2 runtime

Has anyone come across this ?
Thank-you. I have logged this with supportline.