| Author |
Message
|
| JonasLarsen |
 Posted: Thu Nov 19, 2009 3:18 am Post subject: Anyone used JMS and WMQ Multi Instance Queueing? |
 |
|
Newbie
Joined: 19 Nov 2009
Posts: 4
|
Hi,
we are trying to set up XA connection factories via JNDI to point to
Multi Instance Queue Manageres useing WebSphere MQ 7.0.1 as JMS
provider.
We tried to set up XA Queue Connection Factory in JNDI useing JMSAdmin.
In the Infocenter page "Properties of WebSphere MQ classes for JMS objects" table ", Table 2, we find that these
properties can't be applied to XA Connection factories:
CONNECTIONNAMELIST
CLIENTRECONNECTOPTIONS
CLIENTRECONNECTTIMEOUT
We are allowed to use CONNECTIONNAMELIST and CLIENTRECONNECTTIMEOUT.
But not CLIENTRECONNECTOPTIONS, which fails with the following:
Unable to create a valid object, please check the parameters supplied
JMSADM4128 CROPT WMQ_CLIENT_RECONNECT
Is there a way to use XA JMS connections with multi intance queue managers?
Best regards |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Thu Nov 19, 2009 4:32 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| JonasLarsen |
| Posted: Thu Nov 19, 2009 4:55 am Post subject: |
|
|
Newbie
Joined: 19 Nov 2009
Posts: 4
|
Hi,
can be the case that the inflight transactions need to be solved manually, but it shouldn't stop us from useing JMS XA when the connection is working fine, and if failure occur there should be possible to do a reconnect to the standby queue manager, now the active one, useing the CONNECTION-parameters.
contact admin |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Nov 19, 2009 5:52 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
it seems these features XA-JMS and Multi instance are currently excluding each other.
Best verify with IBM support to be sure...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Nov 19, 2009 3:21 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Michael Dag wrote: |
it seems these features XA-JMS and Multi instance are currently excluding each other.
Best verify with IBM support to be sure... |
I would rather imagine that you'd have to rollback the current transaction and retry it on the failed over system... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Nov 19, 2009 5:26 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| fjb_saper wrote: |
| Michael Dag wrote: |
it seems these features XA-JMS and Multi instance are currently excluding each other.
Best verify with IBM support to be sure... |
I would rather imagine that you'd have to rollback the current transaction and retry it on the failed over system... |
my guess is that the development team had to make choices, knowing the people in Hursley they don't take things lightly... BUT
customer demand rules, if no one specifically asks for this functionality it will never get there.
so raise the question with support, find out if it is truly not supported now and raise a requirement to get it...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| JonasLarsen |
| Posted: Fri Nov 20, 2009 2:52 am Post subject: |
|
|
Newbie
Joined: 19 Nov 2009
Posts: 4
|
| Issue raised with IBM. Will update this thread when I get a good answer from IBM. |
|
| Back to top |
|
|
| JonasLarsen |
| Posted: Thu Nov 26, 2009 4:21 am Post subject: |
|
|
Newbie
Joined: 19 Nov 2009
Posts: 4
|
Response from IBM:
"The MQ client reconnect capability does not support XA.
Multi-instance queue managers can be used in an XA environment, however
in the event of a failover the clients would have to manually reconnect
to the alternate queue manager instance.
.
The following statement appears in the Application recovery section
of the MQ system admin guide.
.
"Reconnectable clients can use single phase transactions under the
control of the queue manager as the transaction coordinator. The
extended transactional client does not support reconnection. If
reconnection is requested when the transactional client connects, the
connection succeeds, but without the ability to be reconnected. The
connection behaves as if it is not reconnectable".
"
contact admin |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Nov 26, 2009 8:48 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
contact admin,
thanks for sharing, but does this give you what you need???
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| jabhijeet |
| Posted: Wed Oct 17, 2012 8:03 am Post subject: Any example please |
|
|
Newbie
Joined: 17 Oct 2012
Posts: 6
|
Hello
I want to use this clientConnectionList option for com.ibm.mq.MQQueueManager.
Could anyone help me here please?
an sample example in java will be appreciated.
Thanks in advance |
|
| Back to top |
|
|
|
|
