If this ever happened to you, that XMLtoolkit doesn’t want
to stop normally or gives you other issues related to creating connection to
itself, it must be registry error.
Here’s the symptom:
|
[netcool@tbsm61 bin]$ ./tbsmrdr_stop.sh
GTMCL5478W:
The request could not be delivered, the toolkit may be down. If the toolkit
is busy processing data, allow it to complete and shutdown gracefully. If the
toolkit is idle but will not stop, reissure the request with the -f flag.
The
exception was: Exception creating connection to: 172.16.1.103; nested
exception is:
java.net.NoRouteToHostException: No
route to host
retCode:
4
|
So I try to stop my XMLtoolkit instance and the script fails
and the toolkit itself keeps running.
This is mainly because of XMLtoolkit failover capability feature.
Each instance registers itself by IP of the machine it runs on, and it’s
usually IP configured for the first network interface. You can check on this at
any time:
|
[netcool@tbsm61 bin]$ ./registryupdate.sh -U db2inst1
-P smartway -v
GTMCL5457I:
Toolkit registry table information.
ID:
1
Name: 172.16.1.103
Primary: true
Action: 0
LastUpdate: Thu Jan 01 01:00:00 CET
1970
ID:
2
Name: null
Primary: false
Action: 0
LastUpdate: Thu Jan 01 01:00:00 CET
1970
GTMCL5358I:
Processing completed successfully.
retCode:
0
|
The corresponding value is written to
xmltoolkitsvc.properties under DL_Toolkit_Instance_ID property.
It may happen especially on a virtual machine, which is
being reconfigured as moved to new networks. There’s quick remedy for this:
update DL_Toolkit_Instance_ID property with a new value, like static IP or a unique
hostname in xmltoolkitsvc.properties file and register that value in the
database:
|
[netcool@tbsm61
bin]$ ./registryupdate.sh -U db2inst1 -P smartway -s 1
GTMCL5458I:
Setting the toolkit registry table
GTMCL5358I:
Processing completed successfully.
retCode:
0
[netcool@tbsm61 bin]$ ./registryupdate.sh -U db2inst1
-P smartway -v
GTMCL5457I:
Toolkit registry table information.
ID:
1
Name: 10.10.10.21
Primary: true
Action: 0
LastUpdate: Thu Jan 01 01:00:00 CET
1970
ID:
2
Name: null
Primary: false
Action: 0
LastUpdate: Thu Jan 01 01:00:00 CET
1970
GTMCL5358I:
Processing completed successfully.
retCode:
0
|
The second run of the script with associated –v flag will
help you verify if value was set ok.
Now it’s time to stop the toolkit without issues:
|
[netcool@tbsm61 bin]$ ./tbsmrdr_stop.sh
GTMCL5443I:
The script toolkit_stop.xml has been submitted for processing.
retCode:
0
|
And this is it.
