ContextSwitchDeadlock

01-15-2010, 4:27 PM
Hello,

I am in the process of upgrading to AR6. Most reports converted and work fine, but now I am getting a ContextSwitchDeadlock error. The report is only 9 pages long...not large by any means.

I see that there was a post about this about 5 months ago that had no resolution...is there any updated information about why reports take longer in AR6 and what is causing this error?

Thank you

Re: ContextSwitchDeadlock

01-18-2010, 12:27 AM
Chrisgaber,

Could you kindly provide us some more information about the exception message which you are getting? If possible kindly provide us the stack trace for the same. Which build of ActiveReports 6 are you using to convert the projects and what is the version of ActiveReports used for the creation of the original projects? Is this happening with the windows project or web projects?

Also, I would appreciate if you could provide us some detailed information about the time taken for the reports creation. What difference are you getting in time taken for the report creation and which version are you comparing ActiveReports 6 with?

Regards,
Sankalp
Sankalp Sen
GrapeCity- DataDynamics

Re: ContextSwitchDeadlock

01-19-2010, 1:42 PM
Hello Sankalp,
Thank you for your reply. Here is the information you requested:

Current Version 6.0.2250.0
Previous Version 4.3.0.1260

This is happening in our windows project

The report in the previous version took about a second...I get this error after 60 seconds have passed and still no report.

Stack Trace:
[Managed Debug Assistant triggered on Unmanaged Thread]

I have noticed that all the reports that do not get this error are taking a much longer time to run (5+ seconds) and most are only a page or two long.

Thank you.
Christine

Re: ContextSwitchDeadlock

01-19-2010, 3:58 PM
An additional note. I get this error when running in Debug mode. I am able to get the report to display if I run the executable. A 9 page report takes 90 seconds to display...prior to the upgrade to 6 it was almost instant..a second at most.

Thanks

Re: ContextSwitchDeadlock

01-20-2010, 12:41 AM
Christine,

Thank you for providing the requested information. Unfortunately I was not able to reproduce the error at my end. You may want to attach a small sample application demonstrating the issue, so that we may analyze it at our end. Also you have mentioned that you have upgraded your projects from Active Reports for .NET 2.0. Could you kindly confirm whether you have this version installed on your machine along with ActiveReports 6? If yes then we do not recommend so and you may check this link for more information.

Also is this happening with the projects upgraded from Active Reports for .NET 2.0 or any project which you create in ActiveReports 6? The exception which you are getting is explained here and you can stop this exception from being thrown this by removing the tick mark from the Throw column under Debug-->Exceptions-->Managed Debugging Assistants. Any further information provided to isolate the issue would be appreciated.

Regards,
Sankalp
Sankalp Sen
GrapeCity- DataDynamics

Re: ContextSwitchDeadlock

01-20-2010, 7:38 AM
I'll try to create a sample application. Our product is not a simple one so to create a sample to illustrate what we are doing is not really possible. But I'll see what I can do.

Only AR6 is installed on my machine.

This is happening with projects upgraded to AR6. Nothing new has been developed in AR6. I've researched the error and understand how to fix it so it is not thrown. This does not help with the issue of a 9 page report that appears instantly in AR2 now taking a minute and half to appear in AR6.

Have you had others contact you about report response time being longer in AR6?

Thank you
Christine

Re: ContextSwitchDeadlock

01-21-2010, 1:23 PM
Additional information:

The report that I'm seeing the dramatic change in response time has quite a few subreports and nested subreports. The datasource is XML.

I've tried using .Run(true) but the report viewer doesn't appear until the report renders (this is a requirement of our application).

What ideas can you give me?? We are about to scrap the upgrade to 6.0 right now since the reports are running so much slower.

Thank you
Christine

Re: ContextSwitchDeadlock

01-21-2010, 3:01 PM
Hello Christine,

Would you please provide us a sample which replicates the issue so that we can test it at our end. Also please let us know the steps you followed to convert the report. You mentioned that the concerned report has a few sub-reports. Did you add this sub-reports after conversion or you already had it while in ActiveReports2.

Regards,
Subodh

Re: ContextSwitchDeadlock

01-24-2010, 6:41 PM
I'm unable to provide a sample due to the complexity of this report. This report's data is provided via a dataset. Within that dataset there is a field in one of the tables that contains XML. There are 2 subreports on the main report and then nested subreports in those subreports for a total of 11 subreports.

All reports were converted to AR 6. Prior to the conversion to AR 6 this report took less than 2 seconds to appear. It now takes 90 seconds. I have no idea what to do next. Like I said, this issue is going to prevent us from upgrading to AR6. Also..all of our reports are taking on average twice as long to render in AR6.

You help and assistance would be greatly appreciated!

Re: ContextSwitchDeadlock

01-25-2010, 9:01 AM
UPDATE...after much work and dumping our dataset to create a DB to use in a sample application, I have located the problem.

Our application implements Application.AddMessageFilter. This has no effect on the reports using AR2 but it has a major effect with AR6.

Re: ContextSwitchDeadlock

01-25-2010, 9:46 AM
Hello,

In the previous post you mentioned that you want to render the partially however it was not rendering even after setting Report.Run(true). Regarding this query I would like to give you the steps how you can achieve that. Just setting Report.Run(true) will not work. To achieve this we will need to add a summery-field in the Page footer showing current-page no. Then the report will be shown partially. I have also attached a sample demonstrating this. Please go through the sample and let me know if it works for you.

Regards,
Subodh

Re: ContextSwitchDeadlock

02-02-2010, 7:42 AM
Hello,

Due to the complex nature of our reports it is not possible to give you an example that truly demonstrates how this report is working.

I went ahead and upgraded our web application to use the flash viewer to get that part working at least. Interesting...both our smart client and web product use the same reports. This particular report appears immediately in our web application that uses the flash viewer...but it takes 90 seconds in our smart client. Same code, same report..the only difference is that the smart client uses the document and in our online app the report is saved as .rdf and the flash viewer displays that.

?????

Thanks
Chris

Re: ContextSwitchDeadlock

02-08-2010, 7:25 PM
UPDATE....

Have located the problem. It has to do with the license verification somehow. I am doing development work via a VPN. If I am not logged in to the VPN the reports will run (looks like it will immediately timeout trying to verify the licensing).