If it works on A but not on B then B needs an environment adjustment.
Please refer to the opening post for details of the error and what I did to test it.
shashikanth_in came to the correct conclusion that .NET 4.0 breaks MQ client because they deliberately changed the behavior of Dns.GetHostEntry() method on which MQ client relies on.
Basically, I'm looking for:
- Are there newer versions of MQ client that have adapted to his change?
- Is there a workaround? (previous posts suggested that maybe changing connection parameters might do the trick)
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
SrdjanNjiric wrote:
lancelotlinc wrote:
SrdjanNjiric wrote:
the same app fails on a production server
Fails how ? What is the error message ?
If it works on A but not on B then B needs an environment adjustment.
Please refer to the opening post for details of the error and what I did to test it.
shashikanth_in came to the correct conclusion that .NET 4.0 breaks MQ client because they deliberately changed the behavior of Dns.GetHostEntry() method on which MQ client relies on.
Basically, I'm looking for:
- Are there newer versions of MQ client that have adapted to his change?
- Is there a workaround? (previous posts suggested that maybe changing connection parameters might do the trick)
My questions stand : Fails how ? What is the error message ? If it works on A but not on B then B needs an environment adjustment.
Everything has changed in three years. It seems before both your laptop and server did not work. Now laptop works but not server. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
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