I am in the midst of troubleshooting an issue where I am getting huge numbers of FDC
files generated on one of our development Solaris machines. Some of these FDC files
are are REALLY large too.
The machine in question is an 8 CPU box with 32GB RAM.
There are currently 70+ queue managers *DEFINED* on the box, many in a "local" cluster
(ie the CLUSTER of queue managers is all on the same box - this is a DEVELOPMENT
machine... in the real world the cluster members would be on different physical
machines).
At the moment I am showing 27 active queue managers.
The kernel parameters have been updated to the followiung values:
set shmsys:shminfo_shmmax = 4294967295
set shmsys:shminfo_shmseg = 2048
set shmsys:shminfo_shmmni = 2048
set semsys:seminfo_semaem = 16384
set semsys:seminfo_semmni = 1024
set semsys:seminfo_semmap = 1026
set semsys:seminfo_semmns = 16384
set semsys:seminfo_semmsl = 10000
set semsys:seminfo_semopm = 100
set semsys:seminfo_semmnu = 2048
set semsys:seminfo_semume = 256
set msgsys:msginfo_msgmap = 1026
set msgsys:msginfo_msgmax = 4096
In addition to the FDC files in /var/mqm/errors, the AMQERROR0x files are also filled
with:
AMQ6119: An internal MQSeries error has occurred ('22 - Invalid argument' from semop.)
If anyone can shed some more light on the problem, I'd apreciate it. I am in the
process of reviewing the solaris kernel params to see if that (likely) is the root of
the problem.
Regards,
tonyB.
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
