![]() | ![]() |
|
01-17-2012 02:57 PM
We are trying to install a new node on MQ server, with the Enterprise node located on another server/QM.
Channels are defined between the 2 QMs and we can exchange messages. When installing the node, the step that tries to contact the Registry services would fail because the Registry service would not respond within the time limit.
When looking at the problem, we discovered that the message sent by the process ends up in the DLQ of the Enterprise node QM because it tries to deliver to the MIM.NewNodeName.DIRECTORY.SERVICE, which of course doesn't exist.
Does anybody have an idea what is happening?
Solved! Go to Solution.
01-17-2012 09:17 PM
What version of MIM and MQ?
Can you post your config.rsp for your new node? Can you display the log of the failed Registry Service attempt?
01-18-2012 10:19 AM - last edited on 01-18-2012 10:20 AM
MIM 8.5.1 & MQ 7.0.1
config.rsp;
#########################
# DO NOT EDIT THIS FILE #
#########################
:Install
install_type = runtime,nodeagents,serveragents,workbench
install_path = D:\PM4DATA
data_path = D:\PM4DATA
this_install_version = 8.5.1.0
registry_type = mqserver
transport_type = mqserver
:Variables
local_qmgr = ENT_SVR
unique_node_name = ENT_SVR
q_prefix = MIM.
jmx_port = 10012
pm_webserver_port = 10010
pm_webserver_shutdown_port = 10011
user_registry = Application1
registry_qmgr = $(local_qmgr)
manager_qmgr = $(local_qmgr)
mqserver_hostname = MIMSERVER.test.com
mqserver_channelname = SYSTEM.DEF.SVRCONN
mqserver_port = 1414
local_hostname = $(mqserver_hostname)
DatabaseDriver
schema = PM4DATA
user = admin
password = ***_Removed_Password_***
Driver.dataSourceName = PM4DATA
Driver.type = db2luwdd
Driver.serverName = MIMSERVER
Driver.portNumber = 50000
Driver.databaseName = PM4DATA
nodeagent.log
INFO 17 Jan 2012 14:20:34,962 [main] - Node Agent Version: 8.5.2.0.20110506
INFO 17 Jan 2012 14:20:34,962 [main] - Build Date: 05/06/2011 11:04:26
FATAL 17 Jan 2012 14:21:07,838 [main] - Error reading Launcher.xml, exiting...
com.commercequest.xmdirectory.XMDirectoryIOExcepti
at com.commercequest.xmdirectory.client.XMDirectoryMQ
at com.commercequest.xmdirectory.client.XMDirectoryBa
at com.commercequest.xmdirectory.client.XMDirectoryBa
at com.commercequest.xmdirectory.client.XMDirectoryBa
at com.metastorm.nodeagent.NodeAgent.main(NodeAgent.j
01-18-2012 10:52 AM
Is this the config for the new node or the Enterprise Server? I noticed the local qmgr is ENT_SVR and the Registry uses the same qmgr.
01-18-2012 10:58 AM
That's the Entreprise node config. Couldn't find a config.rsp on the client node - maybe that's part of the problem.
01-18-2012 11:00 AM
What platform is it?
01-18-2012 11:05 AM
win 2003 for server and xp sp3 for client node.
01-18-2012 11:11 AM
The file is located at [install_dir]\bin\config.rsp.
If you don't see it, please post a listing of your bin directory.
By the way is your XP 32 bit or 64 bit?
01-18-2012 01:44 PM - last edited on 01-18-2012 01:44 PM
32 bits for client and server
We re-ran the install and got a config.rsp file this time;
:Install
install_type = runtime,nodeagents
install_path = C:\Program Files\Metastorm\MIM
data_path = C:\Program Files\Metastorm\MIM
this_install_version = 8.5.1.0
registry_type = mqserver
transport_type = mqserver
:Variables
local_qmgr = NODE_TEST
unique_node_name = NODE_TEST
q_prefix = MIM.NODET.
jmx_port = 10012
registry_qmgr = ENV_TEST
manager_qmgr = $(local_qmgr)
mqserver_port = 1400
local_hostname = client.test.com
01-18-2012 01:50 PM
This appears to be your problem:
q_prefix = MIM.NODET.
You need to use the same Queue Prefix as your server node.
You can either re-run the installation or simply edit the config.rsp and run the configure command shell program.
Ethan
![]() |
![]() |
![]() |
|
|
![]() |
![]() |
![]() |
















