I have a JOLT application according to the sample from tuxedo jolt official documentation. When I directly close Eclipse or pull out the net cable without push the Tomcat close button in Eclipse console, I find that the connection session of jolt is still in the result of pclt command in tmadmin as follows: (Note: "teller" is my jolt client name)
pclt -m dcs
LMID User Name Client Name Time Status Bgn/Cmmt/Abrt
---------------
--------
-------------
dcs dcsop WSH **:**:** IDLE 0/0/0
dcs dcsop JSH 95:24:46 IDLE 0/0/0
dcs dcsop JSH 95:24:46 IDLE 0/0/0
dcs dcsop WSH **:**:** IDLE 0/0/0
dcs User.1@20001 teller 25:16:13 IDLE/W 0/0/0
dcs User.0@20001 teller 64:59:55 IDLE/W 0/0/0
dcs User.0@20001 teller 3:48:08 IDLE/W 0/0/0
dcs User.0@20001 teller 63:19:18 IDLE/W 0/0/0
dcs User.0@20001 teller 29:25:11 IDLE/W 0/0/0
dcs User.0@20001 teller 68:45:28 IDLE/W 0/0/0
dcs User.0@20001 teller 68:47:03 IDLE/W 0/0/0
dcs User.0@20001 teller 0:44:32 IDLE/W 0/0/0
dcs dcsop tmadmin 0:00:04 IDLE 0/0/0
The result is that there maybe error:
"CMDTUX_CAT:4745: ERROR: Exceeded 110% of TUXEDO System Binary Licensed User Count (36/5), BBL lockout occurs, no new clients can join the application" and "WSNAT_CAT:1356: ERROR: A lockout has occurred because of license violation".
I doubt that the connection session of jolt is in status of not alive rather than waiting to run for the next time because of not closing the Tomcat shutdown button in Eclipse console. However, from Tuxedo jolt documentation, I find that the destroy() of client is only:
public void destroy() {
b_mgr = null;
}
There is not any other process for closing the connection session of jolt.
My question is whether there is any other method in configuration file like ubb or jolt client code to close session directly in order to decrease the session in pclt of tmadmin in correct time rather than increasing the number of jolt connection session until errors occur?
Thanks a lot.
--友情转载