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 Java / JMS » MI qmgr Channel issue

Post new topic  Reply to topic
 MI qmgr Channel issue « View previous topic :: View next topic » 
Author Message
Gideon
PostPosted: Thu Aug 29, 2013 2:53 pm    Post subject: MI qmgr Channel issue Reply with quote

Chevalier

Joined: 18 Aug 2009
Posts: 403

I have an failover issues taht only occurs when a java test program is running:

Without a test program:

I start a MI qmgr in both machines and failover successfully:

Instance 1:

Code:
-bash-4.1$ strmqm -x mqha2
WebSphere MQ queue manager 'mqha2' starting.
The queue manager is associated with installation 'Installation1'.
5 log records accessed on queue manager 'mqha2' during the log replay phase.
Log replay for queue manager 'mqha2' complete.
Transaction manager state recovered for queue manager 'mqha2'.
WebSphere MQ queue manager 'mqha2' started using V7.5.0.0.
-bash-4.1$
-bash-4.1$
-bash-4.1$ endmqm -s -r mqha2
Quiesce request accepted. The queue manager will stop when all outstanding work
is complete, permitting switchover to a standby instance.
-bash-4.1$
-bash-4.1$ dspmq -x -o standby -o status
QMNAME(WQM1)                                              STATUS(Status not available) STANDBY(Not applicable)
QMNAME(mqha2)                                             STATUS(Running elsewhere) STANDBY(Permitted)
    INSTANCE(btvm2) MODE(Active)
-bash-4.1$


As you can see the failover occurred without error

With a test program

I start off with both instances running:

Code:
-bash-4.1$ dspmq -x -o standby -o status
QMNAME(WQM1)                                              STATUS(Status not available) STANDBY(Not applicable)
QMNAME(mqha2)                                             STATUS(Running as standby) STANDBY(Permitted)
    INSTANCE(btvm1) MODE(Active)
    INSTANCE(btvm2) MODE(Standby)
-bash-4.1$


I start my java program sending messages to the mqha2 with these parameters


Code:
private static String conList   = "10.14.101.196(1414),10.14.101.197(1414)";
 ...
      cf.setStringProperty(WMQConstants.WMQ_CONNECTION_NAME_LIST, conList);
      cf.setIntProperty(WMQConstants.WMQ_CLIENT_RECONNECT_OPTIONS, WMQConstants.WMQ_CLIENT_RECONNECT);


After it sends about 2000 messages I switch over

Code:
-bash-4.1$ endmqm -s -r mqha2
Waiting for queue manager 'mqha2' to end.


and then I get the following errors roll accross the screen that was running my java program

Code:
08/29/2013 02:42:56 PM AMQ9508: Program cannot connect to the queue manager.
08/29/2013 02:42:58 PM AMQ9999: Channel 'SYSTEM.ADMIN.SVRCONN' to host '10.14.100.2 (10.14.100.2)'
ended abnormally.
08/29/2013 02:42:58 PM AMQ9508: Program cannot connect to the queue manager.
08/29/2013 02:42:56 PM AMQ9999: Channel 'SYSTEM.ADMIN.SVRCONN' to host '10.14.100.2 (10.14.100.2)'
ended abnormally.
Quiesce request accepted. The queue manager will stop when all outstanding work
is complete, permitting switchover to a standby instance.
-bash-4.1$ 08/29/2013 02:43:01 PM AMQ9999: Channel 'SYSTEM.ADMIN.SVRCONN' to host '10.14.100.2 (10.14.100.2)'
ended abnormally.
08/29/2013 02:43:01 PM AMQ9508: Program cannot connect to the queue manager.


Now what is interesting is that my connection list is composed of

Code:
conList   = "10.14.101.196(1414),10.14.101.197(1414)";


But the error complains of '10.14.100.2 (10.14.100.2)' (10.14.100.2 is the IP of the client where the java program is running. Looks like it is confused some how

What should I do next ?

Thanks
Back to top
View user's profile Send private message Send e-mail
Gideon
PostPosted: Thu Sep 05, 2013 1:04 pm    Post subject: Reply with quote

Chevalier

Joined: 18 Aug 2009
Posts: 403

I was able to fix this by switching from "endmqm -s" to endmqm -is".

The stream of messages prevented the qmgr from quiesing
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » MI qmgr Channel issue
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.