R
rfdolson
I am attempting to integrate an ASP.NET application with PeopleSoft
through the use of the PeopleSoft (PS) API. Unfortunately, we are
having issues with this integration and do not have a clear
understanding as to what the issue might be. I suspect that the issue
maybe related to the fact that .NET inherantly runs in a Multi-threaded
Apartment, while the PS API runs in a Single Threaded Apartment. We
have set the aspcompat attribute to true in the Page Directive for all
web pages that interact with the PS API. Unfortunately, this did not
address the issue. Additionally, the code was synchronized prior to
the setting of the aspcompat attribute, which I thought would have
addressed the problem.
The symptoms of the problem are as follows:
1. TRY-CATCH block Exception Message: Server Threw Exception.
2. Source of Exception: MSCORLIB.dll
3. Problem does not occur when single user is hitting the application.
Problem only surfaces when there are multiple users hitting the
application at the same time.
4. The exception is thrown while calling PS APIs. The exception is not
always thrown on the same PS API call.
At this point, I have all but given up on the PS API. I am now
attempting to integrate via a web service.
Any suggestions?
Thanks,
Rob
through the use of the PeopleSoft (PS) API. Unfortunately, we are
having issues with this integration and do not have a clear
understanding as to what the issue might be. I suspect that the issue
maybe related to the fact that .NET inherantly runs in a Multi-threaded
Apartment, while the PS API runs in a Single Threaded Apartment. We
have set the aspcompat attribute to true in the Page Directive for all
web pages that interact with the PS API. Unfortunately, this did not
address the issue. Additionally, the code was synchronized prior to
the setting of the aspcompat attribute, which I thought would have
addressed the problem.
The symptoms of the problem are as follows:
1. TRY-CATCH block Exception Message: Server Threw Exception.
2. Source of Exception: MSCORLIB.dll
3. Problem does not occur when single user is hitting the application.
Problem only surfaces when there are multiple users hitting the
application at the same time.
4. The exception is thrown while calling PS APIs. The exception is not
always thrown on the same PS API call.
At this point, I have all but given up on the PS API. I am now
attempting to integrate via a web service.
Any suggestions?
Thanks,
Rob