MSQ/UNX - dmqgcp exits when another group is recycled
(Doc ID 764635.1)
Last updated on JULY 03, 2018
Applies to:Oracle MessageQ / MessageQ /
Information in this document applies to any platform
PRODUCT: MessageQ for UNIX[R] V4.x OP/SYS: All Supported Platforms ISSUE: I am running DMQ V3.2a on a Digital Unix V4.0B system. Our configuration involves 2 DMQ groups, ncs01grp and x998grp. The ncs01grp is activated at boot time and is to remain active. The x998grp is brought up and down as our application needs to be cycled. In testing our application, repeated cycling of the x998grp and the processes in it eventually result in the exit of the gcp for the ncs01grp. Prior to this exit the x998grp doesn't seem to come up normally either. I am wondering if there is some sort of timing issue here if we do the cycling too quickly? Is there some process rundown associated with UNIX and/or the xgroup links? Or is there a potential resource problem with repeated cycling of xgroup connections? If so, what resource would it be?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document