We have an ASP client that invokes a COM component (developed in ATL). The COM component inturn wraps the IBM's AMI API. This is required as AMI does not have a support for VB/ASP environments. So the AMI library is wrapped into a COM component. The AMI library inturn accesses the transport MQSeries layer and is perfectly inter-operable with MQSeries's MQI library.
Now the resolution is : We could run the ASP application SUCCESFULLY connecting through a MQSeries 5.2 client when we compiled the component using a "Single" Threaded model only. For all other cases viz;, "Both" or "Free threaded" models, the ASP gives the same AMRC transport error as already explained. How do we overcome this? This leads us to suspect that the AmSession's open is occuring on one thread while the Session Factory creates the AmSession object on a different thread. (Refer to the client code snippet)
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum