Has anyone else had a problem where using AlphaDAO Connection Strings as Multi Tenant are causing Windows Event Viewer errors and / or freezing up the Application Server? Alpha 12 v4.6.1.9 build 6488. Windows 10.
I have tested this from more than one computer, and same results. I limited it to just my LocalHost, and the same results happen. The errors will throw in the Event Viewer, and often times Alpha will show "Not Responding." Sometimes I need to end the task and other times I can wait it out.
I eliminated every component and simply had an index.a5w page with 1 component. Same problem. I switched components on that page, and same problem. I then created a new project with the same connection strings (one connection string without the multi tenant and one with), and the same problem. I removed the MT connection string, and no more errors. I recreated it, and the errors return. I created the MT connection using the "MultiTenant" option, and I also tried it by following Selwyn's video on creating the MT connection. Same errors either way.
Again, remove the MT connection string, no more errors. Put it back in, errors return. Some freeze the application where I have to end the task and restart it. I removed the existing myConnection.MultiTenant.a5xbclass from Alpha, and followed Selwyn's video again allowing it to recreate. This does not happen on any specific component or page. It seems to be all about the MT connection.
I went back to my original project and removed the MT connection string, and the problem stopped (of course I see every client's data that way, so I cannot publish that). I put it back in, and errors and freezes return.
Exert from A5XbasicErrorStackLog.txt:
Event Log:
I have tested this from more than one computer, and same results. I limited it to just my LocalHost, and the same results happen. The errors will throw in the Event Viewer, and often times Alpha will show "Not Responding." Sometimes I need to end the task and other times I can wait it out.
I eliminated every component and simply had an index.a5w page with 1 component. Same problem. I switched components on that page, and same problem. I then created a new project with the same connection strings (one connection string without the multi tenant and one with), and the same problem. I removed the MT connection string, and no more errors. I recreated it, and the errors return. I created the MT connection using the "MultiTenant" option, and I also tried it by following Selwyn's video on creating the MT connection. Same errors either way.
Again, remove the MT connection string, no more errors. Put it back in, errors return. Some freeze the application where I have to end the task and restart it. I removed the existing myConnection.MultiTenant.a5xbclass from Alpha, and followed Selwyn's video again allowing it to recreate. This does not happen on any specific component or page. It seems to be all about the MT connection.
I went back to my original project and removed the MT connection string, and the problem stopped (of course I see every client's data that way, so I cannot publish that). I put it back in, and errors and freezes return.
Exert from A5XbasicErrorStackLog.txt:
HTML Code:
Sat Feb 29 09:03:01 2020
Thread priority reduced.
Thread was busy 92% of the last 82 seconds.
Raw Data: 340711025663,13906250,341491168221,88718750,78014255,74812500,82140873,75859375
The script causing this behavior is using a lot of CPU time.
You may want to review the page to make sure you have optimized any XBasic scripting.
Long running and processor intensive scripts tend to tie up available threads and adversely affect the perceived performance for multiple users.
Execution Stack:
0#1 evaluate_shared_private(
0#39 OOhttpdServerClientMIME(ptemp,"AppServerMain")
0#2 A5WCallResult = evaluate_a5w_to_response(page_contents,Response,quote(" " + eval_settings.global.Request.ScriptName),eval_settings,EVALUATE_A5W_TIMEOUT,RequestBundle.RequestInfo.Filename.Path)
0#62 x_out = a5_ajax_grid(tmpl)
HTML Code:
The description for Event ID 0 from source Alpha5 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Thread state is invalid
Running Thread: AppServerWorker1
Xbasic Stack dump:
Main
---------------------------------------------
<Empty Stack>
=============================================
AppServerMain
---------------------------------------------
sleep(2)
=============================================
AppServerWorker1
---------------------------------------------
evaluate_shared_private(
OOhttpdServerClientMIME(ptemp,"AppServerMain")
A5WCallResult = evaluate_a5w_to_response(page_contents,Response,quote(" " + eval_settings.global.Request.ScriptName),eval_settings,EVALUATE_A5W_TIMEOUT,RequestBundle.RequestInfo.Filename.Path)
x_out = a5_ajax_dialog2(tmpl)
Comment