D
dbeavon
Guest
We are doing some load-testing using .Net against PASOE. The PASOE instance runs on windows with OE 11.7.4 . Our .Net proxies are generated using 11.6.3 (file version of Progress.o4glrt.dll is 11.6.0.1408). The load-testing involves running a bunch of SSRS reports. Internally they use the OpenClient proxies, and are failing with Open4GLExceptions; we get an enormous number of failures that look like so: processing!WindowsService_1!136c!12/21/2018-14:33:39:: e ERROR: An exception has occurred in data set 'Whatever'. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset 'Whatever'. ---> Progress.Open4GL.Exceptions.Open4GLException: Communication layer message: Invalid state for read: Current state = STATE_ALLOCATED (7249) . (7175) This is happening on the openclient side of things, not on the server. I haven't seen any errors yet on the PASOE server side. There doesn't appear to be any "good" reason for failures. I'm thinking there is some sort of concurrency issue when using more than one openclient connection on several threads at the same time. I found a KB article, but it seems no more useful than the error message itself. Progress KB - How to trouble shoot an Invalid state for read:Current state = STATE_ALLOCATED (7249) Is anyone familiar with this error? I'm hoping that whoever created the KB might be able to contribute more information. It seems like the KB describes the process of getting half-way to a solution, but doesn't provide any meaningful conclusions. The amount of load that we are placing on PASOE is not unreasonable, and there don't appear to be any "good" reasons for the error messages. I will probably be spending a lot of time at this, but was hoping someone might give me tips or point me in the right direction. Any help would be appreciated.
Continue reading...
Continue reading...