Re: Issue with the new i2b2 Web Client when long-running queries transition to background execution?

6 views
Skip to first unread message

Mendis, Michael E.

unread,
Jan 23, 2026, 11:08:23 AMJan 23
to i2b2-ins...@googlegroups.com
What version of i2b2 are you using?

-mike

From: i2b2-ins...@googlegroups.com <i2b2-ins...@googlegroups.com> on behalf of Md.Saber Hossain <shossa...@gmail.com>
Date: Thursday, January 22, 2026 at 12:24 PM
To: i2b2 Install Help <i2b2-ins...@googlegroups.com>
Subject: Issue with the new i2b2 Web Client when long-running queries transition to background execution?

        External Email - Use Caution        
Has anyone else encountered this issue with the new i2b2 Web Client when long-running queries transition to background execution?

The new i2b2 Web Client does not correctly handle queries that transition to background execution. Instead of remaining in a Processing state, the UI displays an error, even though the backend continues executing the query successfully.


When a long running query transitions to background execution:

The CRC service returns HTTP 200
The response includes the following statuses:
Query Instance Status
<query_status_type>
    <status_type_id>4</status_type_id>
    <name>ERROR</name>
    <description>ERROR</description>
</query_status_type>

and in Result Instance Status

<query_status_type>
    <status_type_id>10</status_type_id>
    <name>TIMEDOUT</name>
    <description>TIMEDOUT</description>
</query_status_type>

The Web Client interprets these statuses as fatal errors.
The UI displays an error instead of continuing background polling.
Backend processing completes successfully, but results are not surfaced automatically.
Users must re-drag or re-run the query to view results.


Reference:
ProcessQueue.java line 100
```
 initializeSql =
 "update " + dslookup.getFullSchema() + ".qt_query_instance " +
 " set batch_mode = 'ERROR'" +
 " where batch_mode = 'PROCESSING'";
 
 preparedStmt2 = conn.prepareStatement(initializeSql);
 preparedStmt2.executeQuery();
```
--
You received this message because you are subscribed to the Google Groups "i2b2 Install Help" group.
To unsubscribe from this group and stop receiving emails from it, send an email to i2b2-install-h...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/i2b2-install-help/c20cb439-e2fd-4ca2-b660-4e224b422113n%40googlegroups.com.

The information in this e-mail is intended only for the person to whom it is addressed.  If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Mass General Brigham Compliance HelpLine at https://www.massgeneralbrigham.org/complianceline .


Please note that this e-mail is not secure (encrypted).  If you do not wish to continue communication over unencrypted e-mail, please notify the sender of this message immediately.  Continuing to send or respond to e-mail after receiving this message means you understand and accept this risk and wish to continue to communicate over unencrypted e-mail. 

Md.Saber Hossain

unread,
Jan 23, 2026, 1:46:47 PMJan 23
to i2b2-ins...@googlegroups.com

Hi Mike, 

we’ve recently upgraded to v1.8.2. Initially, I thought the issue was with the web client, but after further investigation I found it was actually related to our PHP configuration. This started after we switched the web client base image to amazonlinux:2023, and it appears when the web client starts polling for long-running queries. That’s why I deleted the earlier posts—I realized they were not relevant.

Thanks,
Saber

Reply all
Reply to author
Forward
0 new messages