"Hello". Please allow me to make this post to ask for help. I suspect I have XBIS configured incorrectly.
Here is the contents of the SRF:
{{ // There must be no whitespace before the XML header, hence the newline-eating comment tags. }}
{{ Handler * }}{{//}}
{{ Trace(start,file,DIR=/dms/src/DIPO/ptrace,exchfiles) }}{{//}}
{{ RunPath(/dms/obj,/dms/dmsdata,/dms/dmsmast) }}{{//}}
{{ StartService(DIPOAPPDRVR -A='WHI' -v) }}{{//}}
{{ XMLExchange }}
{{ SessionComplete }}
Here are the contents of the trace file:
MODBIS2|1532979782.25|--------S-T-A-R-T--O-F--R-E-Q-U-E-S-T------- from 69.176.97.175 at 2018-07-30 14:43:02 -0500
SERVICE|1532979782.36|Generated XML file name: /var/local/liant/bis/bisL7Hh4C-aQ8EK1RUSDSRxeQ-0000.xml
ServMsg|1532979782.36|Trace "/var/local/liant/bis/trcL7Hh4C-aQ8EK1RUSDSRxeQ"
ServMsg|1532979782.36|Trace on
ServMsg|1532979782.36|SetProgramDir /var/www/html/dms/services/dipo/prod/
ServMsg|1532979782.36|RunPath /var/www/html/dms/services/dipo/prod,/dms/obj,/dms/dmsdata,/dms/dmsmast
ServMsg|1532979782.36|StartService DIPOAPPDRVR -A='WHI' -v
SERVICE|1532979782.36|Service program started (command is "DIPOAPPDRVR -A='WHI' -v")
SERVICE|1532979782.36|Session ID=L7Hh4C-aQ8EK1RUSDSRxeQ, Service ID=0000, Service number=69
SERVICE|1532979782.36|Process ID=32666, User ID=0, Group ID=0
SERVICE|1532979782.36|Current directory=/dms/services/dipo/prod
SERVICE|1532979782.36|$HOME=/root
SERVICE|1532979782.36|$RUNPATH=/var/www/html/dms/services/dipo/prod:/dms/obj:/dms/dmsdata:/dms/dmsmast
SERVICE|1532979782.36|BIS Service - Version 12.12 for Linux Intel 32-Bit.
SERVICE|1532979782.36|Xcentrisity Business Information Server issued to DPC Systems Inc.
SERVICE|1532979782.36|Configured for 20 users.
SERVICE|1532979782.36|DPC Systems Inc.
SERVICE|1532979782.36|Copyright (c) 2016 Micro Focus. All rights reserved.
SERVICE|1532979782.36|Registration Number: 6E-1000-73758-0020
SERVICE|1532979782.36|
SERVICE|1532979782.38|BIS: Dynamic libraries loaded:
SERVICE|1532979782.38| ($EXEDIR=/usr/local/liant/bis/bin)
SERVICE|1532979782.38| $EXEDIR/librminfox.so - RM/InfoExpress Client (v12.12/r19994)
SERVICE|1532979782.38| $EXEDIR/librmconfig.so - No Automatic Configuration File (v12.12/r19994)
SERVICE|1532979782.38| $EXEDIR/autoload/librmnet.so - RMNet HTTP Client (v12.12/r19994)
SERVICE|1532979782.38| $EXEDIR/autoload/xmlif.so - XMLIF Library (v12.12/r19994)
SERVICE|1532979782.38|
SERVICE|1532979782.38|BIS: User root running on machine ws1.dpcsi.com (Linux)
SERVICE|1532979782.38|BIS: License ID LSRV:106563
SERVICE|1532979782.38|BIS: Locale: Decimal_point(2E)
SERVICE|1532979782.38|BIS: Build date and type: Mar 17 2016 Release
SERVICE|1532979782.38|BIS: Build number: 19994
SERVICE|1532979782.38|
DISPLAY|1532979782.41|"Launching service program 07/30/2018 14:43:02:41 "
DISPLAY|1532979782.41|"System: Linux Ver:2.39542 Username:root ProcessID:32666 "
DISPLAY|1532979782.41|"Runtime: Ver:12.12.0 UseCount:20 InUse:0 Reg#:6E-1000-73758-0020 "
DISPLAY|1532979782.41|"Program Code:WHI "
DISPLAY|1532979782.52|"Configuration Record found "
DISPLAY|1532979782.52|"Inactivity Timer set to ' 350' seconds "
DISPLAY|1532979782.52|"Service Timeout set to ' 35' seconds "
DISPLAY|1532979782.52|"Reading request from BIS. "
SERVICE|1532979782.52|ReadRequest, no timeout
ServMsg|1532979782.52|SetExchFilesDir /dms/src/DIPO/ptrace
ServMsg|1532979782.52|XMLExchange "<?xml version="1.0" encoding="UTF-8"?>\\n<bis:request xmlns:bis="htt..."
ServMsg|1532979782.52|XMLExchange (new request data available)
DISPLAY|1532979782.52|"Importing XML request 07/30/2018 14:43:02:52 "
DISPLAY|1532979782.78|"2014:Import of WHI Request using 'DIPO_WHI_Driver_SS.xsl' = Successf"
DISPLAY|1532979782.78|"ul "
DISPLAY|1532979782.86|"Incoming request from IP=69.176.97.175 Port=64144 "
DISPLAY|1532979782.88|"Request HTTP-Method = POST "
DISPLAY|1532979782.88|"Dispatching method request "
DISPLAY|1532979782.88|"Namespace=ws1.dpcsi.com/.../ "
DISPLAY|1532979782.88|"Method ='ipoacctstatus' "
DISPLAY|1532979782.89|"Password is correct "
ServInt||Service timeout alarm!
At our data-hub, we had 31 processes "hung" ranging in date from July 18 thru July 30th. In each case I looked into, there was a "Service timeout alarm" condition and it appears the cobol program never ended. I looked for any "runcobol" processes suspecting a cobol program in an infinite loop, but there were no "runcobol" processes running on the server. It's like the cobol program had ended, but the process was still running. (from this example, ProcessID:32666 on Linux Ver:2.39542)
Judging from the SRF and the trace file, is there something wrong with the configuration I'm using?
#BIS#RMCOBOL#XBISHmm, I don't see anything obvious with your SRF file. I'd have to do some research about what "Service timeout alarm!" is trying to tell us. I think that it means that the runcobol did indeed not terminate, and the service engine decided to kill it, but then the service engine didn't terminate its own thread properly. At a guess, it issued the kill and was waiting on confirmation that the process had terminated, which never came.
Do you see this problem a lot? If yes, we might enable some more tracing to see if we can pin down the issue. If we're going to do that, then I'd want you to contact Tech Support and open a support incident. But, before we do that, I notice that the version you are using is 12.12. It is possible that this problem has been corrected, so I first suggest that you get the latest version of BIS and see if that doesn't fix your problem.
"Hello". Please allow me to make this post to ask for help. I suspect I have XBIS configured incorrectly.
Here is the contents of the SRF:
{{ // There must be no whitespace before the XML header, hence the newline-eating comment tags. }}
{{ Handler * }}{{//}}
{{ Trace(start,file,DIR=/dms/src/DIPO/ptrace,exchfiles) }}{{//}}
{{ RunPath(/dms/obj,/dms/dmsdata,/dms/dmsmast) }}{{//}}
{{ StartService(DIPOAPPDRVR -A='WHI' -v) }}{{//}}
{{ XMLExchange }}
{{ SessionComplete }}
Here are the contents of the trace file:
MODBIS2|1532979782.25|--------S-T-A-R-T--O-F--R-E-Q-U-E-S-T------- from 69.176.97.175 at 2018-07-30 14:43:02 -0500
SERVICE|1532979782.36|Generated XML file name: /var/local/liant/bis/bisL7Hh4C-aQ8EK1RUSDSRxeQ-0000.xml
ServMsg|1532979782.36|Trace "/var/local/liant/bis/trcL7Hh4C-aQ8EK1RUSDSRxeQ"
ServMsg|1532979782.36|Trace on
ServMsg|1532979782.36|SetProgramDir /var/www/html/dms/services/dipo/prod/
ServMsg|1532979782.36|RunPath /var/www/html/dms/services/dipo/prod,/dms/obj,/dms/dmsdata,/dms/dmsmast
ServMsg|1532979782.36|StartService DIPOAPPDRVR -A='WHI' -v
SERVICE|1532979782.36|Service program started (command is "DIPOAPPDRVR -A='WHI' -v")
SERVICE|1532979782.36|Session ID=L7Hh4C-aQ8EK1RUSDSRxeQ, Service ID=0000, Service number=69
SERVICE|1532979782.36|Process ID=32666, User ID=0, Group ID=0
SERVICE|1532979782.36|Current directory=/dms/services/dipo/prod
SERVICE|1532979782.36|$HOME=/root
SERVICE|1532979782.36|$RUNPATH=/var/www/html/dms/services/dipo/prod:/dms/obj:/dms/dmsdata:/dms/dmsmast
SERVICE|1532979782.36|BIS Service - Version 12.12 for Linux Intel 32-Bit.
SERVICE|1532979782.36|Xcentrisity Business Information Server issued to DPC Systems Inc.
SERVICE|1532979782.36|Configured for 20 users.
SERVICE|1532979782.36|DPC Systems Inc.
SERVICE|1532979782.36|Copyright (c) 2016 Micro Focus. All rights reserved.
SERVICE|1532979782.36|Registration Number: 6E-1000-73758-0020
SERVICE|1532979782.36|
SERVICE|1532979782.38|BIS: Dynamic libraries loaded:
SERVICE|1532979782.38| ($EXEDIR=/usr/local/liant/bis/bin)
SERVICE|1532979782.38| $EXEDIR/librminfox.so - RM/InfoExpress Client (v12.12/r19994)
SERVICE|1532979782.38| $EXEDIR/librmconfig.so - No Automatic Configuration File (v12.12/r19994)
SERVICE|1532979782.38| $EXEDIR/autoload/librmnet.so - RMNet HTTP Client (v12.12/r19994)
SERVICE|1532979782.38| $EXEDIR/autoload/xmlif.so - XMLIF Library (v12.12/r19994)
SERVICE|1532979782.38|
SERVICE|1532979782.38|BIS: User root running on machine ws1.dpcsi.com (Linux)
SERVICE|1532979782.38|BIS: License ID LSRV:106563
SERVICE|1532979782.38|BIS: Locale: Decimal_point(2E)
SERVICE|1532979782.38|BIS: Build date and type: Mar 17 2016 Release
SERVICE|1532979782.38|BIS: Build number: 19994
SERVICE|1532979782.38|
DISPLAY|1532979782.41|"Launching service program 07/30/2018 14:43:02:41 "
DISPLAY|1532979782.41|"System: Linux Ver:2.39542 Username:root ProcessID:32666 "
DISPLAY|1532979782.41|"Runtime: Ver:12.12.0 UseCount:20 InUse:0 Reg#:6E-1000-73758-0020 "
DISPLAY|1532979782.41|"Program Code:WHI "
DISPLAY|1532979782.52|"Configuration Record found "
DISPLAY|1532979782.52|"Inactivity Timer set to ' 350' seconds "
DISPLAY|1532979782.52|"Service Timeout set to ' 35' seconds "
DISPLAY|1532979782.52|"Reading request from BIS. "
SERVICE|1532979782.52|ReadRequest, no timeout
ServMsg|1532979782.52|SetExchFilesDir /dms/src/DIPO/ptrace
ServMsg|1532979782.52|XMLExchange "<?xml version="1.0" encoding="UTF-8"?>\\n<bis:request xmlns:bis="htt..."
ServMsg|1532979782.52|XMLExchange (new request data available)
DISPLAY|1532979782.52|"Importing XML request 07/30/2018 14:43:02:52 "
DISPLAY|1532979782.78|"2014:Import of WHI Request using 'DIPO_WHI_Driver_SS.xsl' = Successf"
DISPLAY|1532979782.78|"ul "
DISPLAY|1532979782.86|"Incoming request from IP=69.176.97.175 Port=64144 "
DISPLAY|1532979782.88|"Request HTTP-Method = POST "
DISPLAY|1532979782.88|"Dispatching method request "
DISPLAY|1532979782.88|"Namespace=ws1.dpcsi.com/.../ "
DISPLAY|1532979782.88|"Method ='ipoacctstatus' "
DISPLAY|1532979782.89|"Password is correct "
ServInt||Service timeout alarm!
At our data-hub, we had 31 processes "hung" ranging in date from July 18 thru July 30th. In each case I looked into, there was a "Service timeout alarm" condition and it appears the cobol program never ended. I looked for any "runcobol" processes suspecting a cobol program in an infinite loop, but there were no "runcobol" processes running on the server. It's like the cobol program had ended, but the process was still running. (from this example, ProcessID:32666 on Linux Ver:2.39542)
Judging from the SRF and the trace file, is there something wrong with the configuration I'm using?
#BIS#RMCOBOL#XBISMike,
You ask: "Do you see this problem a lot"
No, this is the first time I have ever witnessed this behavior. Our company has been using BIS for only a few years (which I consider a short time) where I have written every application running on that server. To me, BIS seems vast and I don't consider myself fluent with it. Steve Jolivet and Tom Morrison have supported me every step of the way on every BIS project I've ever dealt with. I could not have done any of this without their help .
Below is a list of the "hung" processes we found. My first reaction was "Wow, look at the date". I will recommend to my manger that we upgrade the BIS runtime to the latest version. I don't believe we should spend time opening a support ticket knowing (1) I cannot reproduce this behavior and (2) the runtime version is "older". I believe it's in our best interest to upgrade that box to the latest runtime and continue to monitor for errors.
Thanks!
Process List:
root 1508 1655 14 Jul30 ? 1-09:39:58 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 1654 1 0 Jun26 ? 00:01:49 /usr/local/liant/bis/bin/xbissesd -f /etc/xbis.conf -n
root 1655 1 0 Jun26 ? 00:01:31 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 1819 1655 12 Jul30 ? 1-05:30:55 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 13816 1655 18 Jul24 ? 2-23:05:00 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 13824 1655 18 Jul24 ? 2-20:14:42 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 13833 1655 18 Jul24 ? 2-21:58:48 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 13837 1655 18 Jul24 ? 2-19:51:27 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 13842 1655 18 Jul24 ? 2-22:32:05 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 13848 1655 18 Jul24 ? 2-23:04:45 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 14216 1655 17 Jul24 ? 2-19:01:40 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 14227 1655 17 Jul24 ? 2-18:44:27 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 14241 1655 18 Jul24 ? 2-21:47:53 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 26216 1655 33 Jul18 ? 7-11:31:54 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 26217 1655 32 Jul18 ? 7-09:54:53 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 26222 1655 33 Jul18 ? 7-10:18:06 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 26223 1655 33 Jul18 ? 7-10:55:40 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 26225 1655 33 Jul18 ? 7-11:05:42 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 26226 1655 33 Jul18 ? 7-10:41:47 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 29620 1655 14 Jul30 ? 1-10:29:51 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 29692 1655 13 Jul30 ? 1-07:35:25 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 29693 1655 14 Jul30 ? 1-10:36:18 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 30706 1655 14 Jul30 ? 1-10:20:38 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 31238 1655 13 Jul30 ? 1-09:03:50 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 31259 1655 13 Jul30 ? 1-07:10:06 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 31387 1655 14 Jul30 ? 1-10:06:16 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 31634 1655 13 Jul30 ? 1-08:58:54 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 32533 1655 14 Jul30 ? 1-09:51:36 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 32603 1655 13 Jul30 ? 1-06:57:27 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 32640 1655 14 Jul30 ? 1-09:56:05 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
root 32666 1655 13 Jul30 ? 1-08:49:30 /usr/local/liant/bis/bin/xbisengd -f/etc/xbis.conf
