ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ API Support » MQ Client 6.0 a step back for .NET developers?

Post new topic  Reply to topic
 MQ Client 6.0 a step back for .NET developers? « View previous topic :: View next topic » 
Author Message
premierapps
PostPosted: Tue Sep 18, 2007 3:20 am    Post subject: MQ Client 6.0 a step back for .NET developers? Reply with quote

Newbie

Joined: 18 Sep 2007
Posts: 2

We were previously using MQ 5.3 with FixPack 13, and would receive helpful error messages (like MQRC_Q_FULL). After upgrading to 6.0.2.1, the message returned is always 'Error in the application', which doesn't provide much help. Does anyone know if a fix is available for this issue? Or, is there something we need to do differently with the new version?

It looks a lot like http://www-1.ibm.com/support/docview.wss?uid=swg1IC38458 , but that is an old 5.3 document.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue Sep 18, 2007 4:39 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

I'd suggest that it's not likely the MQ code that is producing this error dialog, and more likely that it's the application.

You may need to rebuild the application, to bind against the new client libraries.

But if you read that note, you see that it is saying that the problem is with how the VB sample is coded - that it's not handling exceptions correctly.

So that's the place to start, really. Where in your application is this message being thrown?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
premierapps
PostPosted: Tue Sep 18, 2007 5:30 am    Post subject: Reply with quote

Newbie

Joined: 18 Sep 2007
Posts: 2

I read that note differently than you did. It is discussing two issues. One, their VB sample is coded incorrectly, resulting in an unhandled exception (unrelated to my current issue).

Two, the .dll provided by IBM for .NET connectivity is coded incorrectly - 'Also, the IBM.WMQ.MQException class did not
implement the 'Message' method correctly, resulting in "Error in
the application" being issued rather than an MQ message.'

The application has been rebuilt against the new client .NET library.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue Sep 18, 2007 5:40 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

It could be a regression.

You'd have to open a PMR to find out for sure.

It's still more likely that your application is catching the wrong exception, or not catching it at all.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ API Support » MQ Client 6.0 a step back for .NET developers?
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.