What are the other network messages that need to be acted upon by mxosrvr? ODBC/JDBC APIs are blocking. Other than cancelling query, there should no other messages from the driver sent to the server at least on behalf of the application. The messages between mxosrvr and the ESPs are encapsulated in Trafodion's own IPC mechanism. I believe mxosrvr is capable of alternatively listening between the IPC messages and the messages from the driver via TCP/IP.
Are you planning to make mxosrvr multi-threaded or just want to way to process the any other message when mxosrvr is stuck processing the query. Selva -----Original Message----- From: Dave Birdsall <[email protected]> Sent: Tuesday, March 27, 2018 8:26 AM To: [email protected] Subject: RE: Question about Trafodion MXOSRVR Hi, This is an accident of history. The predecessor product was developed on a platform that did not support operator multi-threading. Yes, it is certainly possible to rearchitect mxosrvr to make it multi-threaded. This can be tricky and must be done carefully. One must take into account any global variables the code uses and decide whether to leave them as globals (and co-ordinate access with mutex), make them thread-globals, or refactor them into some object that is not a global instead. Dave -----Original Message----- From: Song, Hao-Lin <[email protected]> Sent: Tuesday, March 27, 2018 8:20 AM To: [email protected] Subject: Question about Trafodion MXOSRVR Hi all I found that mxosrvr could not handle other network messages when a query is processing , since network processing and data processing are in the same thread. I am confused about this. Can we put them in different threads to make the program more clear and potential? Best, Haolin
