[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | NAS Message Queuing Bus |
| Notice: | KITS/DOC, see 4.*; Entering QARs, see 9.1; Register in 10 |
| Moderator: | PAMSRC::MARCUS EN |
|
| Created: | Wed Feb 27 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2898 |
| Total number of notes: | 12363 |
2787.0. "Urgent - semaphores not being deleted at group shutdown" by WHOS01::ELKIND (Steve Elkind, Digital SI @WHO) Tue Feb 25 1997 14:30
We are having a problem with v3.2A, ECO1, on HP-UX 10.20 at my customer.
When we kill the group (by killing the bus with dmqmonc or kill), 4 semaphores
do not get deleted. They appear to be for the gcp input queue, the qe
input queue, a queue for global naming services (gns.sem?), and something
else (glt.sem).
There is an echo server application attached to a permanent queue in the
group, almost always in a get_wait. It exits after it detects the group
is down. These semaphores do get deleted successfully if we kill the
echo server before we stop the group.
Shouldn't these semaphores go away even if applications are running when
the group shuts down?
For the time being we are stopping the echo server first, but that only works
if the sysadmins use our stop script, which I can't guarantee. It will
probably also not apply to platforms I have no control over.
Appended are the directories of the dmq bin directory, group init file
for one of the two groups involved, ipcs -a listing and ls -lR listing of
/var/tmp/dmq after the groups are shutdown, a list of the IPC resource keys
based on the resource key files, and the group log file.
While I'm here, I have a second question - the use had the fully
qualified domain name in the Xgroup entry for itself - which used to work,
but stopped working today; replacing it with the unqualified name did work
(nj27xyz vs. nj27xyz.foo.bar.com). I did an nslookup and both resolved
(The name goes with an IP address stacked on the interface of the machine
by ServiceGuard). Any hints as to what might have happened?
The semaphore question is urgent, as this is being put into production this
weekend at four sites.
Thanks much.
ls -l /usr/kits/DMQ32A/bin
total 5514
-rwxr-xr-x 1 root sys 145 Feb 24 09:01 STARTDEC
-rwxr-xr-x 1 root sys 349 Jan 9 12:30 STOPDEC
-rwxrwxrwx 1 root sys 20328 Feb 25 13:11 dmq_key
-r-xr-xr-x 1 bin bin 53248 Nov 25 18:34 dmqbcp
-r-xr-xr-x 1 bin bin 45056 Nov 25 18:34 dmqclconf
-r-xr-xr-x 1 bin bin 106496 Nov 25 18:34 dmqclmrsu
-r-xr-xr-x 1 bin bin 200704 Nov 25 18:35 dmqcls
-r-xr-xr-x 1 bin bin 110592 Nov 25 18:34 dmqcltest
-r-xr-xr-x 1 bin bin 36864 Nov 25 18:34 dmqclwatch
-r-xr-xr-x 1 bin bin 167936 Nov 25 18:34 dmqgcp
-r-xr-xr-x 1 bin bin 143360 Nov 25 18:34 dmqivp
-r-xr-xr-x 1 bin bin 81920 Nov 25 18:34 dmqivpipc
-r-xr-xr-x 1 bin bin 163840 Feb 21 09:42 dmqjdump
-r-xr-xr-x 1 bin bin 155648 Feb 21 09:42 dmqjourn
-r-xr-xr-x 1 bin bin 159744 Feb 21 09:41 dmqjplay
-r-xr-xr-x 1 bin bin 131072 Feb 21 09:41 dmqld
-r-xr-xr-x 1 bin bin 147456 Nov 25 18:34 dmqmonc
-r-xr-xr-x 1 bin bin 311296 Nov 25 18:34 dmqmonm
-r--r--r-- 1 bin bin 98304 Nov 24 00:52 dmqmonm.uid
-r-xr-xr-x 1 bin bin 65536 Nov 25 18:34 dmqqe
-r-xr-xr-x 1 bin bin 143360 Nov 25 18:34 dmqscript
-r-xr-xr-x 1 bin bin 147456 Nov 25 18:34 dmqtestc
-r-xr-xr-x 1 bin bin 270336 Nov 25 18:34 dmqtestm
-r--r--r-- 1 bin bin 57344 Nov 24 00:38 dmqtestm.uid
-rwxr-xr-x 1 root sys 464 Feb 20 11:34 startdmq
-rwxr-xr-x 1 root sys 464 Feb 20 11:34 startdmqjit
-rwxr-xr-x 1 root sys 470 Feb 20 11:34 startdmqtrain
!******************************************************************************
! NOTE !
!
! This is a template file. It is not intended to be edited. The file protec-
! tion is set to prevent accidental editing of this file.
!
! If you need to edit this file, make a copy and edit the copy. If you edit
! this template file directly you may no longer have a valid template file. You
! can restore this template file after accidental editing by reinstalling the
! DECmessageQ Run-Time Environment.
!
!******************************************************************************
!
! HISTORY
! 24-jul-95 s. elkind fixes recommended by Ian Kinkade:
! threshold 320,000,000 -> 32,000,000
! reconnect timer on own group 1 -> 30
! added this history section to keep track
! of changes
! 21-aug-95 s.elkind copied over and rebuilt for bus 121 group 102
! and DMQ v3.0B (bus 121 => IMSDEHX region on
! mainframe)
! 7-sep-95 s.elkind copied over and rebuilt for bus 114 group
! GROUP INITIALIZATION FILE FORMAT
!
! The DECmessageQ for U*ix Group Control initialization file format closely
! follows the format used by the DECmessageQ for OpenVMS COM Server, with
! extensions to support DECmessageQ for U*ix. Group Control Initialization
! Files are plain text, and can be created with any editor. Parameters in the
! file are whitespace delimited, with the lines terminated by "newline" charac-
! ters. Blank lines are ignored, as are lines with a "!", "#", ";", or "*" as
! the first non-whitespace character. All parameters are required; parameters
! are positional and appear in order from left to right. All text appearing
! between the last parameter and the "newline" is ignored. The Group Control
! Initialization File is divided into five sections; each section begins with
! a section identifer in the form "%section_name". The valid sections are dis-
! cussed below.
! VERSION SECTION
!
! The Version Section begins with %VERSION, and consists of a single line iden-
! tifying the initialization file version. V3.0 accepts init files with a ver-
! sion of 1.0, 2.0, or 3.0
!
%VERSION 3.0
! PROFILE SECTION
!
! The Profile Section begins with %PROFILE, and contains lines defining the
! group-wide configurable limits. The values given below are examples, and do
! not represent "real" values.
%PROFILE
ACCEPT_KILL_COMMAND NO ! accept kill commands from DMQ Monitor
ENABLE_XGROUP YES ! allow cross-group communications
XGROUP_VERIFY NO ! do not verify cross group links
NAME_TABLE_SIZE 100 ! size of Group Name Table
FIRST_TEMP_QUEUE 200 ! Number of first Temporary Queue
GROUP_MAX_LINKS 200 ! 250 ! Size of Group Link Table
GROUP_MIN_GROUP_NUMBER 001 ! 001 ! Lowest Group Number used on this bus
GROUP_MAX_GROUP_NUMBER 9999 ! 15000 ! Highest Group Number used on this bus
GROUP_MAX_USER_QUEUE 999 ! 999 ! Highest User Queue Number
GROUP_MAX_MESSAGE_SIZE 32000 ! largest message size permitted in this group
ENABLE_MRS YES ! Start Recoverable Messaging Servers
%EOS
%MRS
MRS_JOURNAL_PATH /usr/kits/BUS/groups/bus109/group1186/journal/ ! path for recovery journal
MRS_POST_CONFIRMATION_PATH /usr/kits/BUS/groups/bus109/group1186/journal/ ! path for post confirmation
! journal
MRS_DEAD_LETTER_PATH /usr/kits/BUS/groups/bus109/group1186/journal/ ! path for dead-letter journal
%EOS
! XGROUP SECTION
!
! The Xgroup Section begins with %XGROUP, and contains lines defining the
! cross-group connections that will be established by this group. Each line in
! the XGROUP section defines a single cross-group connection. All parameters
! for a given connection must appear on the same line. The general format of a
! cross-group connection is given below, followed by an explanation of each
! parameter.
!
! GNAME - Name by which the remote DECmessageQ Group is known to the local
! group.
!
! GNUMBER - DECmessageQ Group Number of the remote group.
!
! NODE - Name by which the remote node is known to the local node.
!
! INITIATE - "Y" or "N" value indicating whether connections to this node
! should be initiated when the group starts up.
!
! THRESHOLD - Value for dynamic memory consumption at which congestion control
! will begin for this cross-group connection.
!
! RECONNECT - Interval, in seconds, between reconnect attempts when this cross-
! group link is not connected.
!
! DELAY - Delay, in seconds, that a sender must wait before using a new
! window when the receiver is congested.
!
! WINDOW - Maximum transmission window size for this cross-group link.
!
! TRANSPORT - Network protocol stack used. For DECmessageQ V3.0 this is one
! of DECNET, TCPIP, or ADSP. The DECNET transport is only avail-
! able on ULTRIX and OSF/1 platforms. The ADSP transport is only
! available on the Macintosh platform.
!
! ADDRESS - Protocol dependent - for the TCPIP transport, it is the internet
! port number of the remote link listener process. For the DECNET
! transport it is left blank. For the ADSP transport it is the
! ADSP object name.
!
! A sample xgroup table can be seen below:
%XGROUP
CCP_JIT 1186 nj37absg.bns.att.com N 32000000 60 30 25000 TCPIP 10986
GROUP700 700 bmptrain.mt.att.com Y 5000000 60 30 35000 TCPIP 10700
GROUP710 710 bmptrain.mt.att.com Y 5000000 60 30 35000 TCPIP 10710
GROUP720 720 bmptrain.mt.att.com Y 5000000 60 30 35000 TCPIP 10720
GROUP730 730 bmptrain.mt.att.com Y 5000000 60 30 35000 TCPIP 10730
GROUP740 740 bmptrain.mt.att.com Y 5000000 60 30 35000 TCPIP 10740
!IA!QMB1408 1408 mh50pkg2.ims.att.com Y 5000000 60 30 35000 TCPIP 10908
%EOS
! CLS SECTION
!
! you can start any number of client library server processes (one per line)
! by enumerating each process and its endpoint below.
!
! ENDPOINT defines the TCP/IP port number or DECnet object name
! that the server uses to accept incoming connections.
! for TCP/IP the value is limited to 1024-65535 inclu-
! sive. for DECnet the value is limited to 1-99999 in-
! clusive.
!
! TRANSPORT the name of the network protocol stack to be used for
! the server. valid values are DECnet and TCP/IP.
!
! MAX_CLIENTS the maximum number clients the server will server at
! any given time. valid value are 1-512 inclusive.
!
! SECURITY_FILE the full path name of the security file. if no file
! is specified then a default file name is used. see
! documentation for details.
%CLS
! Max Security
! EndPoint Transport Clients File
19100 TCPIP 512
%EOS
! ROUTING SECTION
!
! The Routing Section begins with %ROUTE, and contains lines defining the
! DECmessageQ static routing data base. All parameters for a given queue must
! appear on the same line. The general format of a routing definition is given
! below, followed by an explanation of each parameter.
!
! TARGET_GROUP ROUTE_THROUGH_GROUP
!
! TARGET_GROUP - Group for which traffic must be routed.
!
! ROUTE_THROUGH_GROUP - Group to which traffic for the target_group must be
! sent.
!
! Note that the sample routing entries are commented out in this example
! file
!
%ROUTE
! 7 1
! 10 2
%EOS
! QUEUE CONFIGURATION SECTION
!
! The Queue Configuration Section begins with %QCT, and contains lines defining
! the permanent queues. Each line in the QCT section defines a single queue.
! All parameters for a given queue must appear on the same line. The general
! format of a queue definition is given below, followed by an explanation of
! each parameter.
!
! QNAME QNUMBER BYTE_QUOTA MSG_QUOTA QUOTA_ENBL UCB_SEND TYPE OWNER CONF_STYLE
! PERM_ACT SCOPE SECURITY
!
! QNAME - A name for this queue, 252 characters max
!
! QNUMBER - Number of this queue. Queue numbers must be less than the value
! established in the %PROFILE section for FIRST_TEMP_QUEUE and may
! appear only once in the QCT section. Queues 99 and 100 are res-
! erved and may not appear in this table
!
! BYTE_QUOTA - The maximum number of uncollected bytes that may reside in this
! queue. if the value is -1 then the default value (the value for
! queue 0) is used. if there is no queue 0 then a default value
! of 64000 is used.
!
! MSG_QUOTA - The maximum number of uncollected messages that may reside in
! this queue. if the value -1 then the default value (the value
! for queue 0) is used. if there is no queue 0 then a default
! value of 100 is used.
!
! QUOTA_ENBL - Controls the enabling/disabling of queue quotas.
! "All" - all queue quotas on
! "None" - all queue quotas off
! "Byte" - only byte quota enabled, msg quota disabled
! "Msg" - only msg quota enabled, byte quota disabled
! "." - take the default which is "All"
!
! UCB_SEND - This field is not used
!
! TYPE - Type of queue
! P - primary queue
! S - secondary queue
! M - multi-reader queue.
!
! OWNER - Number of controlling primary queue, if type = "S"
!
! CONF_STYLE - Controls the method by which msgs can be confirmed.
! "II" - Implicit, in-order confirmations
! "EI" - Explicit, in-order confirmations
! "EO" - Explicit, out-of-order confirmations
! "." - take default which is "EO"
!
! PERM_ACT - Permanently active queue: setting this value to "Y" allows proc-
! esses to insert messages into this queue even if it is not cur-
! rently attached by any client process.
!
! SCOPE - Scope of queue name:
!
! L - Local; the name is loaded into the Group Name Table, but not the
! distributed naming service. It can be translated by the service
! PAMS_LOCATE_Q and by other processes in this group.
!
! G - Global; the name is loaded into the distributed naming service.
! It can be translated by the PAMS_LOCATE_Q service by other proc-
! esses in this network.
!
! SECURITY - Attach security
!
! N - no attach security
!
! Y - acl security on attach. an ACL file must be present
! and openable for read/write in order to attach the queue
!
! based on con call info 16 Aug 95 with Mike Carlo, Shiv et al. No permanent
! queues in use on this end at the present - leave one permanent queue for
! DmQ echo server (tbsl)
%QCT
TEMPLATE 0 84000 100 None . P 0 . N L N
echoReply 105 128000 200 None . P 0 . N L N
cpDecMon 106 128000 200 None . P 0 . N L N
! The DEAD_LETTER_QUEUE is the target for UMA modes of
! xx_DLQ. A user process may attach this queue to collect
! undeliverable messages for application-specific proces-
! sing
DEAD_LETTER_QUEUE 96 100000 500 None . P 0 . Y L N
%EOS
! GROUP NAME TABLE SECTION
!
! The Group Name Table Section begins with %GNT, and contains lines that define
! name-to-queue translations for names and queues that do not necessarily
! appear in the QCT. Each line in the GNT section defines a single name-to-
! queue translation. The general format of a GNT entry is given below, follow-
! ed by an !explanation of each parameter.
!
! NAME GROUP.QUEUE SCOPE
!
! NAME - Equivalence name
!
! GROUP.QUEUE - Group and Queue number to be returned to the calling process
! when this name is translated via the PAMS_LOCATE_Q service.
! Specifying zero for the 'GROUP' implies the local group num-
! ber
!
! SCOPE - Scope of name
!
! L - Local; the name is loaded into the Group Name Table, but not
! the distributed naming service. It can be translate by the
! PAMS_LOCATE_Q service by other processes in this group.
!
! G - Global; the name is loaded into both the Group Name Table and
! the distributed naming service. It can be translated by the
! PAMS_LOCATE_Q service by other processes in this network.
! (NOTE: Global Naming is not available in this release)
%GNT
! DECmessageQ for UNIX is case sensitive, but VMS is not. Add both
! upper and lower case for people porting applications from VMS
!timer_queue 0.92 L
!avail_server 0.100 L
!om_server 0.100 L
!queue_server 0.100 L
!connect_server 0.100 L
!TIMER_QUEUE 0.92 L
!AVAIL_SERVER 0.100 L
!COM_SERVER 0.100 L
!QUEUE_SERVER 0.100 L
!CONNECT_SERVER 0.100 L
!BMP
BMPMO_CircuitSvc 700.1 L
BMPMO_CircuitSvc_2 702.1 L
BMPMO_FacilitySvc 700.2 L
BMPMO_InboundSvc 700.3 L
BMPMO_OutboundSvc 700.4 L
BMPAlm_OnDemand 710.1 L
BMPTest_Subscription 720.2 L
BMPTest_OnDemand 720.1 L
BMPTkt_Ticket 730.1 L
BMPTkt_Subscription 730.2 L
BMPSA_ServiceAssurance 740.1 L
BMPSA_NSSSAInterface 740.2 L
BMPRpt_Ticket 750.1 L
%EOS
ipcs -a | grep x51
s 17103 0x511c07ec --ra-ra-ra- root root root root 3 13:32:54 13:29:12
s 13084 0x511c07f2 --ra-ra-ra- root root root root 3 13:32:54 13:29:13
s 15095 0x511c080c --ra-ra-ra- root root root root 3 13:32:54 13:29:13
s 17106 0x511c080f --ra-ra-ra- root root root root 3 13:32:54 13:29:13
s 11078 0x511c0872 --ra-ra-ra- root root root root 3 13:32:54 13:29:19
s 10074 0x511c0878 --ra-ra-ra- root root root root 3 13:32:54 13:29:19
s 10075 0x511c087b --ra-ra-ra- root root root root 3 13:32:54 13:29:19
s 10076 0x511c087d --ra-ra-ra- root root root root 3 13:32:54 13:29:19
ls -lR /var/tmp/dmq
total 0
drwxrwxrwx 4 root root 96 Feb 25 13:29 b_0109
drwxrwxrwx 4 root root 96 Feb 25 13:29 b_0118
/var/tmp/dmq/b_0109:
total 0
drwxrwxrwx 3 root root 96 Feb 25 13:29 g_01186
drwxrwxrwx 2 root root 96 Feb 25 13:32 ipc
/var/tmp/dmq/b_0109/g_01186:
total 2
drwxrwxrwx 2 root root 1024 Feb 25 13:32 ipc
/var/tmp/dmq/b_0109/g_01186/ipc:
total 0
-rw-rw-rw- 1 root root 0 Feb 25 13:29 gi.s
-rw-rw-rw- 1 root root 0 Feb 25 13:29 glt.s
-rw-rw-rw- 1 root root 0 Feb 25 13:29 gns.sem
-rw-rw-rw- 1 root root 0 Feb 25 13:29 qi.s
/var/tmp/dmq/b_0109/ipc:
total 0
/var/tmp/dmq/b_0118:
total 0
drwxrwxrwx 3 root root 96 Feb 25 13:29 g_01186
drwxrwxrwx 2 root root 96 Feb 25 13:32 ipc
/var/tmp/dmq/b_0118/g_01186:
total 2
drwxrwxrwx 2 root root 1024 Feb 25 13:32 ipc
/var/tmp/dmq/b_0118/g_01186/ipc:
total 0
-rw-rw-rw- 1 root root 0 Feb 25 13:29 gi.s
-rw-rw-rw- 1 root root 0 Feb 25 13:29 glt.s
-rw-rw-rw- 1 root root 0 Feb 25 13:29 gns.sem
-rw-rw-rw- 1 root root 0 Feb 25 13:29 qi.s
/var/tmp/dmq/b_0118/ipc:
total 0
IPC resource keys based on above files:
For path "/var/tmp/dmq/b_0109/g_01186/ipc/gi.s" key for DmQ resource is 511c07ec
For path "/var/tmp/dmq/b_0109/g_01186/ipc/glt.s" key for DmQ resource is 511c080f
For path "/var/tmp/dmq/b_0109/g_01186/ipc/gns.sem" key for DmQ resource is 511c080c
For path "/var/tmp/dmq/b_0109/g_01186/ipc/qi.s" key for DmQ resource is 511c07f2
For path "/var/tmp/dmq/b_0118/g_01186/ipc/gi.s" key for DmQ resource is 511c0872
For path "/var/tmp/dmq/b_0118/g_01186/ipc/glt.s" key for DmQ resource is 511c087d
For path "/var/tmp/dmq/b_0118/g_01186/ipc/gns.sem" key for DmQ resource is 511c087b
For path "/var/tmp/dmq/b_0118/g_01186/ipc/qi.s" key for DmQ resource is 511c0878
group log file
************ dmqgcp (29948) 25-FEB-1997 12:30:46 ************
gcp, group control process for group 1186 is running
************ dmqqe (29949) 25-FEB-1997 12:30:46 ************
qe, queuing engine is running
************ dmqgcp (29948) 25-FEB-1997 12:30:46 ************
gcp, no xgroup entry for local group
************ dmqcls (29951) 25-FEB-1997 12:30:47 ************
cls, DECmessageQ Client Lib Server, Version 3.2.006
************ dmqjourn (29950) 25-FEB-1997 12:30:47 ************
jrn, journal process for group 1186 is running
************ dmqcls (29951) 25-FEB-1997 12:30:47 ************
cls, Using DmQ bus id 109, and group id 1186
************ dmqcls (29951) 25-FEB-1997 12:30:47 ************
cls, Using 19100 as Listener endpoint
************ dmqcls (29951) 25-FEB-1997 12:30:47 ************
cls, Listener created and initialized
************ dmqgcp (1421) 25-FEB-1997 12:45:40 ************
gcp, group control process for group 1186 is running
************ dmqqe (1426) 25-FEB-1997 12:45:41 ************
qe, queuing engine is running
************ dmqjourn (1446) 25-FEB-1997 12:45:42 ************
jrn, journal process for group 1186 is running
************ dmqcls (1448) 25-FEB-1997 12:45:42 ************
cls, DECmessageQ Client Lib Server, Version 3.2.006
************ dmqcls (1448) 25-FEB-1997 12:45:42 ************
cls, Using DmQ bus id 109, and group id 1186
************ dmqcls (1448) 25-FEB-1997 12:45:42 ************
cls, Using 19100 as Listener endpoint
************ dmqld (1449.0) 25-FEB-1997 12:45:42 ************
ld, link sender for group 1186 to group 700 is running
************ dmqcls (1448) 25-FEB-1997 12:45:42 ************
cls, Listener created and initialized
************ dmqld (1451.0) 25-FEB-1997 12:45:42 ************
ld, link sender for group 1186 to group 720 is running
************ dmqld (1452.0) 25-FEB-1997 12:45:42 ************
ld, link sender for group 1186 to group 730 is running
************ dmqld (1454.0) 25-FEB-1997 12:45:42 ************
ld, link sender for group 1186 to group 740 is running
************ dmqld (1450.0) 25-FEB-1997 12:45:42 ************
ld, link sender for group 1186 to group 710 is running
************ dmqld (1447.0) 25-FEB-1997 12:45:43 ************
ld, link listener for group 1186 is running
************ dmqld (1454.0) 25-FEB-1997 12:45:43 ************
ld, operation failed to complete
************ dmqld (1452.0) 25-FEB-1997 12:45:43 ************
ld, operation failed to complete
************ dmqld (1450.0) 25-FEB-1997 12:45:43 ************
ld, operation failed to complete
************ dmqld (1451.0) 25-FEB-1997 12:45:43 ************
ld, operation failed to complete
************ dmqld (1449.0) 25-FEB-1997 12:45:43 ************
ld, operation failed to complete
************ dmqld (1454.0) 25-FEB-1997 12:46:43 ************
ld, operation failed to complete
************ dmqld (1451.0) 25-FEB-1997 12:46:44 ************
ld, operation failed to complete
************ dmqld (1450.0) 25-FEB-1997 12:46:44 ************
ld, operation failed to complete
************ dmqld (1449.0) 25-FEB-1997 12:46:44 ************
ld, operation failed to complete
************ dmqld (1452.0) 25-FEB-1997 12:46:44 ************
ld, operation failed to complete
************ dmqld (1454.0) 25-FEB-1997 12:47:44 ************
ld, operation failed to complete
************ dmqld (1450.0) 25-FEB-1997 12:47:44 ************
ld, operation failed to complete
************ dmqld (1449.0) 25-FEB-1997 12:47:44 ************
ld, operation failed to complete
************ dmqld (1452.0) 25-FEB-1997 12:47:44 ************
ld, operation failed to complete
************ dmqld (1451.0) 25-FEB-1997 12:47:44 ************
ld, operation failed to complete
************ dmqld (1454.0) 25-FEB-1997 12:48:44 ************
ld, operation failed to complete
************ dmqld (1451.0) 25-FEB-1997 12:48:45 ************
ld, operation failed to complete
************ dmqld (1450.0) 25-FEB-1997 12:48:45 ************
ld, operation failed to complete
************ dmqld (1449.0) 25-FEB-1997 12:48:45 ************
ld, operation failed to complete
************ dmqld (1452.0) 25-FEB-1997 12:48:45 ************
ld, operation failed to complete
************ dmqgcp (3802) 25-FEB-1997 13:05:30 ************
gcp, group control process for group 1186 is running
************ dmqqe (3803) 25-FEB-1997 13:05:31 ************
qe, queuing engine is running
************ dmqgcp (3802) 25-FEB-1997 13:05:31 ************
gcp, no xgroup entry for local group
************ dmqjourn (3804) 25-FEB-1997 13:05:31 ************
jrn, journal process for group 1186 is running
************ dmqcls (3805) 25-FEB-1997 13:05:31 ************
cls, DECmessageQ Client Lib Server, Version 3.2.006
************ dmqcls (3805) 25-FEB-1997 13:05:31 ************
cls, Using DmQ bus id 109, and group id 1186
************ dmqcls (3805) 25-FEB-1997 13:05:31 ************
cls, Using 19100 as Listener endpoint
************ dmqcls (3805) 25-FEB-1997 13:05:31 ************
cls, Listener created and initialized
************ dmqgcp (6787) 25-FEB-1997 13:29:12 ************
gcp, group control process for group 1186 is running
************ dmqqe (6795) 25-FEB-1997 13:29:13 ************
qe, queuing engine is running
************ dmqcls (6808) 25-FEB-1997 13:29:14 ************
cls, DECmessageQ Client Lib Server, Version 3.2.006
************ dmqcls (6808) 25-FEB-1997 13:29:14 ************
cls, Using DmQ bus id 109, and group id 1186
************ dmqcls (6808) 25-FEB-1997 13:29:14 ************
cls, Using 19100 as Listener endpoint
************ dmqcls (6808) 25-FEB-1997 13:29:14 ************
cls, Listener created and initialized
************ dmqld (6809.0) 25-FEB-1997 13:29:14 ************
ld, link sender for group 1186 to group 700 is running
************ dmqld (6811.0) 25-FEB-1997 13:29:14 ************
ld, link sender for group 1186 to group 720 is running
************ dmqjourn (6806) 25-FEB-1997 13:29:14 ************
jrn, journal process for group 1186 is running
************ dmqld (6807.0) 25-FEB-1997 13:29:14 ************
ld, link listener for group 1186 is running
************ dmqld (6812.0) 25-FEB-1997 13:29:14 ************
ld, link sender for group 1186 to group 730 is running
************ dmqld (6813.0) 25-FEB-1997 13:29:14 ************
ld, link sender for group 1186 to group 740 is running
************ dmqld (6810.0) 25-FEB-1997 13:29:14 ************
ld, link sender for group 1186 to group 710 is running
************ dmqld (6811.0) 25-FEB-1997 13:29:15 ************
ld, operation failed to complete
************ dmqld (6812.0) 25-FEB-1997 13:29:15 ************
ld, operation failed to complete
************ dmqld (6813.0) 25-FEB-1997 13:29:15 ************
ld, operation failed to complete
************ dmqld (6810.0) 25-FEB-1997 13:29:15 ************
ld, operation failed to complete
************ dmqld (6809.0) 25-FEB-1997 13:29:15 ************
ld, operation failed to complete
************ dmqld (6812.0) 25-FEB-1997 13:30:15 ************
ld, operation failed to complete
************ dmqld (6811.0) 25-FEB-1997 13:30:15 ************
ld, operation failed to complete
************ dmqld (6809.0) 25-FEB-1997 13:30:15 ************
ld, operation failed to complete
************ dmqld (6813.0) 25-FEB-1997 13:30:15 ************
ld, operation failed to complete
************ dmqld (6810.0) 25-FEB-1997 13:30:15 ************
ld, operation failed to complete
************ dmqld (6810.0) 25-FEB-1997 13:31:16 ************
ld, operation failed to complete
************ dmqld (6812.0) 25-FEB-1997 13:31:16 ************
ld, operation failed to complete
************ dmqld (6813.0) 25-FEB-1997 13:31:16 ************
ld, operation failed to complete
************ dmqld (6809.0) 25-FEB-1997 13:31:16 ************
ld, operation failed to complete
************ dmqld (6811.0) 25-FEB-1997 13:31:16 ************
ld, operation failed to complete
************ dmqld (6809.0) 25-FEB-1997 13:32:16 ************
ld, operation failed to complete
************ dmqld (6810.0) 25-FEB-1997 13:32:16 ************
ld, operation failed to complete
************ dmqld (6811.0) 25-FEB-1997 13:32:16 ************
ld, operation failed to complete
************ dmqld (6813.0) 25-FEB-1997 13:32:16 ************
ld, operation failed to complete
************ dmqld (6812.0) 25-FEB-1997 13:32:16 ************
ld, operation failed to complete
************ dmqcls (6808) 25-FEB-1997 13:32:49 ************
cls, Client Lib Server using TCP/IP transport and endpoint 19100 exiting
************ dmqld (6807.0) 25-FEB-1997 13:32:54 ************
ld, link listener for group 1186 is exiting
************ dmqld (6813.0) 25-FEB-1997 13:32:54 ************
ld, link sender for group 1186 to group 740 is exiting
************ dmqjourn (6806) 25-FEB-1997 13:32:54 ************
jrn, caught signal 15
************ dmqld (6810.0) 25-FEB-1997 13:32:54 ************
ld, link sender for group 1186 to group 710 is exiting
************ dmqld (6811.0) 25-FEB-1997 13:32:54 ************
ld, link sender for group 1186 to group 720 is exiting
************ dmqld (6809.0) 25-FEB-1997 13:32:54 ************
ld, link sender for group 1186 to group 700 is exiting
************ dmqld (6812.0) 25-FEB-1997 13:32:54 ************
ld, link sender for group 1186 to group 730 is exiting
************ dmqjourn (6806) 25-FEB-1997 13:32:54 ************
jrn, journal process for group 1186 is exiting
************ dmqgcp (6787) 25-FEB-1997 13:32:54 ************
gcp, group control process for group 1186 has exited
************ dmqqe (6795) 25-FEB-1997 13:32:54 ************
qe, queuing engine has exited
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2787.1 | | XHOST::SJZ | Kick Butt In Your Face Messaging ! | Tue Feb 25 1997 14:45 | 11 |
|
if depends on how the echo server exits. if after the group
has shutdown the echo server just exits then yes you will
have sempahores left behind. if on the other hand the echo
server issues a pams_exit call before exiting then the sema-
phores should go away. since the group is down and there
is no one left to clean up after the application when it
exits the onus is on that application to clean up after it-
self by calling pams_exit.
_sjz.
|