| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| MQ v 7.0.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| mvic |
 Posted: Fri May 07, 2010 2:52 pm Post subject: Re: max reconnect time |
 |
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| George Carey wrote: |
From IBM 7.0.1 doco:
| Quote: |
Automatic client reconnection
You can make your client applications reconnect automatically, without writing any additional code, by configuring a number of components.
Auto-reconnection is inline, that is, the connection is automatically restored at any point in the client application program, and the handles to open objects are all restored. |
Here is the reference url:
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.csqzaf.doc/cs70190_.htm |
It's much more complicated, but the details are on another page.
Linked from the page you mentioned is this section: http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.amqzag.doc/fa70156_.htm#fa70156___PredictableRecovery entitled "Recovery of an automatically reconnected client" where there is a lot more detail about this.
I just pick out this one paragraph because it summarises the point that it is "more complicated" than that quote from the other page:
| Quote: |
| Not all program state is managed as part of a transaction, and therefore the consequences of reconnection become harder to understand. You need to know how reconnection changes the state of a WebSphere MQ client in order to design your client application to survive queue manager failover. |
|
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sat May 08, 2010 6:30 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| By re-instantiates do you mean reconnects ? Because that is what I mean. |
No. I thought you were focused on getting a client app restarted after it abended, not after the qmgr failed.
And I presumed that you were looking for something the MI qmgr could/would do to accomplish this without change to a client app or CCDT.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| George Carey |
| Posted: Sat May 08, 2010 1:39 pm Post subject: from earlier line |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
To bruce2350, as I said in an earlier reply:
| Quote: |
| IBM's client reconnection functionality for 7.0.1 is not talking about any case where the client failed ??!!! I don't think anyone would expect IBM to know how a to restart a client . |
To mvic: Yes, more complicated but I was looking to understand what the show stoppers are and if there was a feasible/plausible way to prevent the occurrence of the 2549 error in the (unfailed) reconnecting client to the new qmgr instance(that is using the same data files(queues and logs)).
As mentioned I would be happy to be educated.
Something to the effect ... This is not doable because ... and here is what is taking place 1,2,3 ... and thus you see it is not feasibile... . Or ... it would require an inordinate amount of overhead or impose to much of/many restriction on the client or server ...
I will reread the doco again when time but nothing I recall jumped out at me that allowed me to say, "Ooooh now I see!"
I mean I am just asking!!
Take AlbertE's time dilation ... that's complicated too ... but still understandable how and why so ... just trying to understand how and why 2549's a bit more.
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
| mvic |
| Posted: Mon May 10, 2010 1:19 am Post subject: Re: from earlier line |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| Quote: |
| Something to the effect ... This is not doable because ... and here is what is taking place 1,2,3 ... and thus you see it is not feasibile... . Or ... it would require an inordinate amount of overhead or impose to much of/many restriction on the client or server ... |
That manual page does contain a level of detail approaching what you say here. Particularly the section titled "Recovery of an automatically reconnected client".
If it falls short, tell IBM.. there's a "Feedback" link at the bottom of the page. |
|
| Back to top |
|
|
| George Carey |
| Posted: Mon May 10, 2010 8:10 am Post subject: reread |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
I will reread and see what I can see ...
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
| MB |
| Posted: Wed Jun 09, 2010 5:21 pm Post subject: Regarding file system support |
|
|
Acolyte
Joined: 25 Jun 2004
Posts: 52
|
Hi,
We are looking at setting up MQ7.0.1 multi-instance Queue Manager on Linux (RHEL 5.4). We are kind of stuck with the file system software to be used for storing the working data (i.e., /var/mqm shared by the multiple instances of the QM).
We have the hardware (contact admin, SAN) to be used as the shared disk (i.e., shared file system). But we are not sure on what software is needed on the Linux boxes to access this shared disk appropriately.
1. IBM documentation mentions "NFS v4", "IBM's General Parallel File System". Are these the names of software needed to be installed on the Linux boxes to access the shared disk?
2. Apart from these, are there any other options using which someone has implemented?
3. Our System Administrator mentioned clustered Filesystem softwares called OCFS2 (from Oracle), GFS (from Red Hat I guess). Has someone implemented using these on RHEL 5.4?
4. Does some software has to be installed on the shared disk as such?
Answers to the above questions or any other basics that I am grossly missing will be greatly appreciated!
Thank you!
Regards,
MB |
|
| Back to top |
|
|
| jeevan |
| Posted: Wed Jun 09, 2010 5:42 pm Post subject: Re: Regarding file system support |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| MB wrote: |
Hi,
We are looking at setting up MQ7.0.1 multi-instance Queue Manager on Linux (RHEL 5.4). We are kind of stuck with the file system software to be used for storing the working data (i.e., /var/mqm shared by the multiple instances of the QM).
We have the hardware (contact admin, SAN) to be used as the shared disk (i.e., shared file system). But we are not sure on what software is needed on the Linux boxes to access this shared disk appropriately.
1. IBM documentation mentions "NFS v4", "IBM's General Parallel File System". Are these the names of software needed to be installed on the Linux boxes to access the shared disk?
2. Apart from these, are there any other options using which someone has implemented?
3. Our System Administrator mentioned clustered Filesystem softwares called OCFS2 (from Oracle), GFS (from Red Hat I guess). Has someone implemented using these on RHEL 5.4?
4. Does some software has to be installed on the shared disk as such?
Answers to the above questions or any other basics that I am grossly missing will be greatly appreciated!
Thank you!
Regards,
MB |
There was a recent discussion on MI qmgr which you will find in the follwoing url:
http://www.mqseries.net/phpBB2/viewtopic.php?t=53819&start=0
The links provided in the dicussion will give you enough knowledge to implement MI qmgr.
Also, the following link may provide some useful info.
http://www-01.ibm.com/support/docview.wss?uid=swg21433474&myns=swgws&mynp=OCSSFKSJ&mync=R
I hope these will provide answers to your questions. |
|
| Back to top |
|
|
| George Carey |
| Posted: Thu Jun 10, 2010 4:54 pm Post subject: hardware |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
You say you have the hardware (contact admin,SAN) ... than assumedly you have someone who knows how to configure that hardware.
An example hardware vendor of HA media is Network Appliance Corp and the netapp devices management software allows admins to create flexible volumes (flexvols) that are NFS mountable. So they can be attached into ones server at specific mounts points such as /var/mqm ... these volumes can be shared between servers (meaning they can be mounted to two different servers simultaneously)thus giving the HA shared data volumes requirement for a multi-instance QMGR. The new functionality of the multi-instance QMGR in 7.0.1 makes sure that the primary and secondary(or backup I forget what it is called) are not both ever trying to startup and/or write to the data (queues/logs/etc) simultaneusly.
an fstab setting in linux like:(where the MQHA_varmqm volume was created and NFS exported with the contact admin vendors admin software)
netappserver01:/vol/MQHA_varmqm /var/mqm nfs proto=tcp,hard,intr
allows a command like:
mount /var/mqm
would mount the device volume and now just looks like a normal part of your directory tree. (as would any mounted volume). Different vendors have different features on their volumes and how to create them NFS export them etcetera, etcetera ....
MQ 7.0.1 has a requirement for NFSv4 which is a configuration task not an acquisition task ... for Linux versions or any contact admin or SAN hardware vendor.
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
