| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQClient 5.3 problem with VB |
« View previous topic :: View next topic » |
| Author |
Message
|
| Ashok_holla |
 Posted: Thu Aug 26, 2004 2:43 am Post subject: MQClient 5.3 problem with VB |
 |
|
Newbie
Joined: 26 Aug 2004
Posts: 2
|
Hi,
I have no idea about MQ  , but my application uses MQ Client send data to a Mainframe system.
The problem is that at present we are using MQ 5.0 (Client only) and there is no problem. But we are planning to migrate to MQ 5.3 and here too all the data transfer happens smoothly but on closing the application the application just hangs.
could you please tell me why this is happening.
My application consists of a VB frontend and a C++ backend and there is some piece of code that hooks/unhooks the MQ client i guess (its a maintanence project so there's lots of code that does things that i dont know)
Thanks in advance
Ashok |
|
| Back to top |
|
 |
| JasonE |
| Posted: Thu Aug 26, 2004 3:09 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
What does the app do when it closes? Does it try to make any MQ calls for example.
Try drwtsn32 -p <pid from task manager> against the process, to see what the call stacks of the hung thread(s) are
Does the hang occur if you start the app and close it without doing any MQ activity? If no, what about if you connect then disconnect then exit? |
|
| Back to top |
|
|
| Ashok_holla |
| Posted: Mon Aug 30, 2004 10:08 pm Post subject: |
|
|
Newbie
Joined: 26 Aug 2004
Posts: 2
|
Hi Jason,
Thanks for the reply, the problem is that the MQ related calls/functions are handled thru comproxy dll's that we get from another interface, we just register them in the c++ component and call the methods provided in the dll to send data.
Also I tried drwtsn32 -p <pid> but did not get any output , I am using WINXP and did not get pid from task manager, got it frm spy++,
We are at present using MQClient 5.0 and there is no problem with it, the problem is only with 5.3 and only on exit, otherwise it functions as desired.
The application does not hang on exit if we have not made any MQ related transactions.
Thanks
Ashok |
|
| Back to top |
|
|
| JasonE |
| Posted: Tue Aug 31, 2004 12:54 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Well, the SPY++ process ids are in hex, and taskmgr / drwtsn32 expects them in decimal - Did you convert (You can add the process id into task manager process tab, by options->select columns)?
Note the drwtsn32 -p command just writes to the drwtsn32.log file (whose location varies depending on the windows version, but run drwtsn32 (no parms) and the location is the directory in the top text box).
As to the problem, thats a difficult one to answer without knowing a lot more about the setup. Are the company com proxy dlls calling MQ's VB interface (using cmqc.bas), or the COM interface (MQAX200). Are they running under MTS/COM+ when they are invoked (If yes, definitely test with a recent fixpack/CSD MQ level) |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
