|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Problem with MQI Control Center - TIMEOUT |
« View previous topic :: View next topic » |
Author |
Message
|
1000101011 |
Posted: Tue Mar 22, 2005 11:56 am Post subject: Problem with MQI Control Center - TIMEOUT |
|
|
Newbie
Joined: 10 Mar 2005 Posts: 7
|
Hi there
I am new to WebSphere MQ/MQI (no training or hand over etc) and have been building my way through the product. I have been following the IBM Redbooks installing DB2, MQ and finally WMQI in order to configure a broker domain.
PACKAGE DETAILS:
=============
Solaris Packages
IBM DB2 V7.1 FP3U4, FP10A (UDB Enterprise Server)
IBM WebSphere MQ 5.3.0 CSD5, CSD7 (MQ Server, Man Pages, Sample programs, Client Libraries)
IBM WebSphere MQI 2.1 CSD5, CSD7 (WMQI Runtime)
Windows (2000) Packages
DB2 V7.2 FP10A
WebSphere MQ V5.3 CSD1, CSD5
WebSphere MQI V2.1 CSD4
CONFIGURATION:
============
Solaris (TSTVXVM1)
DB2
db2inst1
MQSICMDB: Configuration Repository DB
$ db2 connect to MQSIBKDB
$ db2 bind /export/home/db2inst1/sqllib/bnd/@db2cli.lst grant public CLIPKG 5
$ db2 connect to MQSICMDB
$ db2 bind /export/home/db2inst1/sqllib/bnd/@db2cli.lst grant public CLIPKG 5
dbadm authorisation granted to all three databases also for user wmqi.
Windows
CATALOG TCPIP NODE TSTVXVM1 REMOTE 10.244.81.27 SERVER 50000 REMOTE_INSTANCE db2inst1 OSTYPE Sun
CATALOG TCPIP NODE TCP0000 REMOTE TSTVXVM1 SERVER 50000
CATALOG TCPIP NODE TCP0001 REMOTE TSTVXVM1 SERVER 50000
CATALOG DB MQSICMDB AT NODE TCP0000
CATALOG DB MQSIMRDB AT NODE TCP0001
CONNECT TO MQSICMDB USER db2inst1 USING password
SUCCESSFULLY CONNECTS
CONNECT RESET
Defined ODBC connection for MQSIMRDB in Admin Tools, Data Sources (ODBC)
Increased dbheap size on ALL databases to 900.
CREATED CONFIG MANAGER:
mqsicreateconfigmgr -i wmqi -a wmqi -q MQSI_CONFIG_QM -d WINDOWS_IP -n MQSICMDB -m MQSIMRDB
Queue manager started, default objects created, successful command completion.
SOLARIS:
Create the broker:
mqsicreatebroker MQSI_SAMPLE_BROKER -i wmqi -a wmqi -q MQSI_SAMPLE_QM -n MQSIBKDB -u db2inst1 -p db2password
Success
mqsilist
BIP8071I: Successful command completion
START SERVICES:
SOLARIS:
runmqlsr -t tcp -p 1415 -m MQSI_SAMPLE_QM &
WINDOWS:
runmqlsr -t tcp -p 1414 -m MQSI_CONFIG_QM &
DEFINE CHANNELS:
SOLARIS:
$ runmqsc MQSI_SAMPLE_QM
define qlocal(MQSI_CONFIG_QM) usage(xmitq)
define channel(BROKER.CONFIG) chltype(sdr) trptype(tcp) +
conname('WINDOWS_IP(1414)') xmitq(MQSI_CONFIG_QM)
define channel(CONFIG.BROKER) chltype(rcvr) trptype(tcp)
end
WINDOWS:
C:\ > runmqsc MQSI_CONFIG_QM
define qlocal(MQSI_SAMPLE_QM) usage(xmitq)
define channel(CONFIG.BROKER) chltype(sdr) trptype(tcp) +
conname('SOLARIS_IP(1415)') xmitq(MQSI_SAMPLE_QM)
define channel(BROKER.CONFIG) chltype(rcvr) trptype(tcp)
end
START CHANNELS:
SOLARIS
$ runmqchl -c BROKER.CONFIG -m MQSI_SAMPLE_QM &
WINDOWS
C:\ > runmqchl -c CONFIG.BROKER -m MQSI_CONFIG_QM &
C:\ > mqsistart ConfigMgr
START SOLARIS BROKER:
$ mqsistart MQSI_SAMPLE_BROKER
START WINDOWS CONTROL CENTER
Start -> Programs -> IBM WebSphere MQ Integrator 2.1 -> Control Centre
LOGIN:
localhost (or windows ip or windows FQDN/host name)
1414
MQSI_CONFIG_QM
Hour glass timer for about 5secs or so and then a timeout message is received stating that my request maybe queued but that it timed out and I cannot connect.
MQSIMRDB: Message Repository DB
MQSIBKDB: Broker Database
MQSICMDB: Configuration Repository DB
MORE INFO:
Created DB2 databases on Solaris using db2inst1 user.
Setup Windows as wmqi user.
Both wmqi users on Solaris and Windows share same password.
Windows wmqi member of appropriate groups.
Fixed odbc core dump problem using 32bit library.
Fixed language issue in profile.sol.
I would appreciate any help you guys could provide! I have gotten this workig intermittantly, last time I started the COMMAND SERVER as it had not started, then it worked, this time it makes no difference. Another time it just worked after about 10mins - I didnt do anything.
Any ideas?
Cheers!
Last edited by 1000101011 on Tue Mar 22, 2005 12:55 pm; edited 1 time in total |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Mar 22, 2005 12:05 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Are there errors in Event Viewere->Application on the ConfigManager machine?
Is the control center on a different machine than the configmgr? Can you establish a client connection from the Control Center machine to the ConfigMgr machine using something like amqsputc? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
1000101011 |
Posted: Tue Mar 22, 2005 12:50 pm Post subject: |
|
|
Newbie
Joined: 10 Mar 2005 Posts: 7
|
Hi
The only errors I have noticed are one mentioning that NNSY is not installed (ConfigMgr) but ConfigMgr will continue to run as long as it is not required by me, as far as I know I dont need it anyway for CC to run ok.
One other was an error regarding domain rights for the user who I specified when creating the config manager service (insufficient rights) and that it should be a domain administrator, but it is in the Administrators group (I have since rebooted).
Its difficult to remember as I am not at work right now and dont have access to the error logs un-fortunately, I will paste the exact errors tomorrow if thats ok, but these were random one time errors. Since then, whenever I try to restart configmgr and then open up control center and it times out, there is nothing in the application logs other than the shutting down/starting of the service.
The control center is on the same machine as the configuration manager. Windows 2000.
I have not tried amqsput, I will give it a try first thing.
Do you have any more suggestions on what the problem might be?
I appreciate your response, thanks!
Martin |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Mar 22, 2005 12:52 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Confirm that the configmgr is running with mqsilist.
See if there are messages piled up on any SYSTEM.BROKER.* queues.
Read the 2.1 documentation for how to enable control center tracing. (I think mqsichangetrace.. but boy it's been a while). _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
1000101011 |
Posted: Tue Mar 22, 2005 1:01 pm Post subject: |
|
|
Newbie
Joined: 10 Mar 2005 Posts: 7
|
I am 99% positive the configmgr was running, basically I was documenting the entire build for the team, before I try and jumpstart script most of the Solaris side, (since I got it working before) and that was one of the checks I put in (mqsilist) but this timeout is constantly tripping me up, must be something simple.
I didnt know you could trace the control center so I will look that up and give it a shot tomorrow, thanks!
I'll copy and paste the application logs, try amqsput, trace and check the SYSTEM.BROKER queues also.
I really appreciate your quick responses! |
|
Back to top |
|
 |
1000101011 |
Posted: Wed Mar 23, 2005 2:49 pm Post subject: |
|
|
Newbie
Joined: 10 Mar 2005 Posts: 7
|
Ok, having tried many different things we finally got the error logs working in the event log and it turned out to be an incorrectly specified security domain for authorising the users:
specified during the mqsicreateconfigmgr command (-d flag), it should be the security domain itself (pre 2000 format) as opposed to the hostname as specified by the RedBook!!!
Thanks to Jeff and Vignesh for there help and suggestions!!! |
|
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
|
|
|
|