| Author |
Message
|
| simon |
 Posted: Wed Apr 20, 2011 3:19 am Post subject: reconnecting to MQ using xms.net |
 |
|
Novice
Joined: 13 Aug 2009
Posts: 16
|
WOndering if anyone has come across a simliar problem as this.
set up connection factor in .net3.5 windows service using mq client tools 7.0.1.4
consume some message fromteh que using ImessageConsumer.consume();
then i cause the MQ connection to close
iMessageconsumer.close()
IConnection.close()
IConnectionFactory = null
wait a period of time and try to reconnect using hte same connectiong method that worked the first time. This all works with out an execption. Until i try and consume the next message on the Queue . at which point the sercices just hangs.
My question is there and flaw in teh logic for how to do this or ??? |
|
| Back to top |
|
 |
| mvic |
| Posted: Wed Apr 20, 2011 3:07 pm Post subject: Re: reconnecting to MQ using xms.net |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| simon wrote: |
| net3.5 windows service |
Are you using XMS? WCF?
A hang sounds like a defect, in any language or environment.
I suggest you collect traces, and open a PMR. |
|
| Back to top |
|
|
| shashikanth_in |
| Posted: Wed Apr 20, 2011 7:47 pm Post subject: |
|
|
Centurion
Joined: 26 Feb 2009
Posts: 123
|
Simon is using XMS .NET. 3 questions to ask:
1) Is this specific to .NET Framework 3.5?
2) Does this happen only when XMS .NET is used in a service. Other words does it work when running as a console application?
3) What does the logs say?
PMR is a better option. |
|
| Back to top |
|
|
| simon |
| Posted: Wed Apr 27, 2011 6:05 am Post subject: |
|
|
Novice
Joined: 13 Aug 2009
Posts: 16
|
) Is this specific to .NET Framework 3.5?
no means to easily test other and this is the framework rest of the systems are built on
2) Does this happen only when XMS .NET is used in a service. Other words does it work when running as a console application?
happens in both a console and winforms app
3) What does the logs say?
nothin that i can see the app just sits there and never returns and error. Xms logs dont have any mention of an error either.
This seems like something that should be easy to do.
Connection create to MQ
MQ connection broken for some reason. Server reboots/ network problems
Then reconnect to the MQ when it comes back up but with out having to manually restart the .net application |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Apr 27, 2011 6:25 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| simon wrote: |
| This seems like something that should be easy to do. |
Agreed.
Did you open the PMR? What did IBM say? |
|
| Back to top |
|
|
| simon |
| Posted: Wed Apr 27, 2011 6:28 am Post subject: |
|
|
Novice
Joined: 13 Aug 2009
Posts: 16
|
havent done yet want to see if i was missing something in the configuration or that the was a work around that some one had found.
but what ever i search for on google gives me no help as it all prtobems in older versions of XMs.net and i'm using the latest MQ client tools 7.0.14.. |
|
| Back to top |
|
|
|
|
