Message Queue Blocking/MSGMNI Confirmations

Hi All,
Firstly, many thanks to all that can assists. I am currently getting Message Queue
Blocking messages in my ULOG files in my Tuxedo Application. (Tux ver 7.1 in Unix).
I am not sure what is causing this, but started to look into the Tux Config (UBB.MP)
and System message queue setting. Detailed as follows:
1)
Listed below is the system message queue setting:
set msgsys:msginfo_msgmni=2000
set msgsys:msginfo_msgmax=128000
set msgsys:msginfo_msgmnb=100000
set msgsys:msginfo_msgssz=256
set msgsys:msginfo_msgseg=25088
set msgsys:msginfo_msgtql=1550
set msgsys:msginfo_msgmap=1000
According to the BEA site, the MSGMNI is determined by this formula:
MSGMNI = MAXACCESSERS + 7 + (no. of servers with REPLYQ) + (no. MSSQ sets) - (no.
of servers with MSSQ sets)
The following is my current Tux. Config (UBB.MP) is set as :
- MAXACCESSERS = 2300
- Each servers (4 types in total) has its own REPLYQ and RQADDR.
- The same type of servers are set the same across 4 application servers.
Hence, my MSGMNI should be a minimum 2339 (ie. MSGMNI = 2300 + 16 + 16 - 0 = 2339).
But my current MSGMNI is 2000.
Would this contribute to my Message Queue Blocking?
Is my understanding correct and is this something I should change to avoid Message
Queue Blocking? Any helps and advice is much appreciated.

Similar Messages

Message Queue Blocking / MSGMNI Setting

Hi All,
Firstly, many thanks to all that can assists. I am currently getting Message Queue
Blocking messages in my ULOG files in my Tuxedo Application. (Tux ver 7.1 in Unix).
I am not sure what is causing this, but started to look into the Tux Config (UBB.MP)
and System message queue setting. Detailed as follows:
1)
Listed below is the system message queue setting:
set msgsys:msginfo_msgmni=2000
set msgsys:msginfo_msgmax=128000
set msgsys:msginfo_msgmnb=100000
set msgsys:msginfo_msgssz=256
set msgsys:msginfo_msgseg=25088
set msgsys:msginfo_msgtql=1550
set msgsys:msginfo_msgmap=1000
According to the BEA site, the MSGMNI is determined by this formula:
MSGMNI = MAXACCESSERS + 7 + (no. of servers with REPLYQ) + (no. MSSQ sets) - (no.
of servers with MSSQ sets)
The following is my current Tux. Config (UBB.MP) is set as :
- MAXACCESSERS = 2300
- Each servers (4 types in total) has its own REPLYQ and RQADDR.
- The same type of servers are set the same across 4 application servers.
Hence, my MSGMNI should be a minimum 2339 (ie. MSGMNI = 2300 + 16 + 16 - 0 = 2339).
But my current MSGMNI is 2000.
Would this contribute to my Message Queue Blocking?
Is my understanding correct and is this something I should change to avoid Message
Queue Blocking? Any helps and advice is much appreciated.

Malcolm,
Your information and explanations behind these error messages are very useful.
It allow me to further understand Tuxedo internal processing and at the same time
give me a chance to start analysing these fields.
I am reluctant to ask further questions at the mean time. I will use your suggestions
as a starting point.
I will certainly keep you posted of the outcome when I have made the changes in
my UBB config and machine parameters.
Many thanks with your help/explanations Malcolm. It helps alot!
Cheers.
David.
"Malcolm Freeman" <[email protected]> wrote:
>
Hi David,
The MSGTQL reference you give (Solution S-00488) refers to the BEA MessageQ
product
and is not relevant to Tuxedo.
The error messages indicate that the queue buildup is probably due to
a restartable
server failing. What happens is this:
When a restartable server fails its IPC queue remains in place and continues
to
receive messages (which will be processed when the server restarts).
Depending
on the time taken to restart, the queue could become full and unable
to receive
any more messages, and this is probably why you got the message CMDTUX_CAT:1380
indicating that the BRIDGE process was unable to put a message on the
server's
queue.
A server is only restarted when the BBL does a SANITYSCAN check. If,
for example,
your SANITYSCAN interval is 300 seconds and your server fails immediately
after
the previous scan, then there will be a delay of almost 5 minutes before
the failure
is detected and the server restarted - plenty of time for the queue to
fill up.
There are a few things you could do:
The key thing would be to find out why the server is failing, and fix
the problem.
If this is not possible immediately, consider some of the other ideas
below.
Have several servers form an MSSQ to service this queue; then if one
fails the
others will continue processing the messages while the failed server
restarts
(this assumes, of course, that your application does not require the
messages
to be processed in strict order through the server).
Reduce the SANITYSCAN interval (but don't make it too small). This would
reduce
the average time taken to restart the server.
Increase the size of the IPC queue (MSGMNB) so that it can hold more
messages.
I'm not sure why you got a LIBTUX_CAT:1485 message, but this could be
due to a
BRIDGE failure as a result of the congestion.
The NETLOAD parameter would reduce the number of messages going to the
remote
machine, but only if the local machine offers the same service. If the
remote
machine is the only source of the service then NETLOAD will have no effect.
I
recommend you do a search of this newsgroup for postings on "load balancing"
there's some good stuff which will explain how load balancing works.
Depending how things go, it might not be a bad idea to open a case with
BEA Support
and ask for guidance (remember to submit your ubbconfig (or preferably
do a tmunloadcf)
together with the complete ULOGs from both the master and the slave machine).
Hope this helps some.
Regards,
Malcolm.
"Dave" <[email protected]> wrote:
Hi Malcolm,
Thank you for your reply. Interesting point you have made about theMSGTQL
value.
Based on your suggestion I went hunting around the BEA site and found
the following
snipplet:
"- The MSGTQL parameter must be set to a value greater than or
equal to the MSGMNI setting."
(http://support.bea.com/application?namespace=askbea&origin=ask_bea_answer.jsp&event=link.view_answer_page_solution&answerpage=solution&page=msq/S-00488.htm)
If the above point is valid, then my MSGTQL is definitely way too low.
IF this
be the case, would you know of a method to work out what my MSGTQL bytes
value
should be?
Additionally, I have looked at other parameters which I could tune,and
would
adding a NETLOAD parameter in the *MACHINES section will reduce remote
servers
call? Which potentially, maybe reduce message queue blocking?
FYI:
The error messages I am seeing in my ULOG file are:
"LIBTUX_CAT: 1477 : ERROR .SysServerDied
LIBTUX_CAT: 1476 : ERROR: .SysServerRestarting"
Which then leads to message queue blocking
"CMDTUX_CAT: 1380 : ERROR: Message queue blocking prevented delivery,
Qaddr=..."
and potentially "LIBTUX_CAT: 1485 .SysNetworkDropped."
Many Thanks. Hope to hear from you (Malcolm) or other parties out there
that can
assists.
Thanks.
David

CMDTUX_CAT:1380: ERROR: Message queue blocking prevented delivery

Today, I changed a Tuxedo application (server) to the product systems(One master and two slaves). Only a small changes in code. But after a period of running, there are many errors in ULOG:
CMDTUX_CAT:1380: ERROR: Message queue blocking prevented delivery, Qaddr = 583902
And then, the server is died. After restart the server, this will happen again later.
I don't know why this happens? Thx.

Hi Bill,
This is happening because the BRIDGE process received a message from the network and was unable to place the message on the intended IPC queue. This could be because the server handling that message is backed up, or the system IPC resource settings are too low. Please check the recommended actions in:
http://download.oracle.com/docs/cd/E18050_01/tuxedo/docs11gr1/messages/cdtux/cdtux013.html
Regards,
Todd Little
Oracle Tuxedo Chief Architect

.SysMachineMsgq: message queue blocking

Hi,
I am getting the following error message:
064222.hostname!TMSYSEVT.14351.3071440608.0: WARN: .SysMachineMsgq: hostname message queue blocking
Is there anyway to pinpoint exactly which application and or which service is causing the blocking?
Thank you,
Ivan

Ivan,
You can look in the userlog for a "LIBTUX_CAT:672 ERROR: Message operation
failed because the message queue or the system is full" message. That will
tell you the process in which the msgsnd() failed, although it will not tell
you the specific queue that was full. If the queue full condition is not
something transient, you can use the "ipcs -q -a" command to examine the
number of bytes currently on each queue on the machine.
If you need to automate the process of searching the ULOG, the T_ULOG class
in TM_MIB(5) can be used.
The event message for the SysMachineMsgq event deliberatly contains very few
details, since the process where msgsnd() failed uses a message to inform
the event server of the failure and if a message queue is full, then there
might be a problem with sending a large message to the TMSYSEVT server.
(There is a check to prevent looping if the message send to TMSYSEVT fails.)
Ed
<Ivan Novick> wrote in message news:[email protected]..
Hi,
I am getting the following error message:
064222.hostname!TMSYSEVT.14351.3071440608.0: WARN: .SysMachineMsgq:
hostname message queue blocking
Is there anyway to pinpoint exactly which application and or which service
is causing the blocking?
Thank you,
Ivan

LIBTUX_CAT:681Failure ro create message queue

Hi,
We get this error when we start more than 3 Appserver.
(Solaris 8 + Oracle)
Any information would be appreciated. Thanks.
It's my /etc/system file...
set maxusers=80
set shmsys:shminfo_shmmax=8589934590
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=15
set semsys:seminfo_semume=500
set semsys:seminfo_semmns=500
set semsys:seminfo_semmnu=500
set semsys:seminfo_semmsl=70
set semsys:seminfo_semmap=500
set semsys:seminfo_semmni=32
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767
set semsys:seminfo_msgmap=780
set semsys:seminfo_msgmax=4096
set semsys:seminfo_msgmnb=8192
set semsys:seminfo_msgmni=500
set semsys:seminfo_msgssz=8
set semsys:seminfo_msgtql=40
set semsys:seminfo_msgseg=1024

And just to add to $0.02,
Oracle doesn't use message queues, only shared memory and semaphores. Here is the
/etc/system I use on my Solaris 7 system for development work:
* IPC Tunables - Shared memory
* max shared memory segment size (SHMMAX)
set shmsys:shminfo_shmmax=4294967295
* min shared memory segment size (SHMMIN)
set shmsys:shminfo_shmmin=1
* max attached shm segments per process (SHMSEG)
set shmsys:shminfo_shmseg=100
* shared memory identifiers (SHMMNI)
set shmsys:shminfo_shmmni=100
* IPC Tunables - Semaphores
* semaphores in system (SEMMNS)
set semsys:seminfo_semmns=4096
* semaphore identifiers (SEMMNI)
set semsys:seminfo_semmni=128
* entries in semaphore map (SEMMAP)
set semsys:seminfo_semmap=4096
* undo structures in system (SEMMNU)
set semsys:seminfo_semmnu=4096
* max semaphores per id (SEMMSL)
set semsys:seminfo_semmsl=2048
* max operations per semop call (SEMOPM)
set semsys:seminfo_semopm=256
* max undo entries per process (SEMUME)
set semsys:seminfo_semume=1024
* semaphore maximum value (SEMVMX)
set semsys:seminfo_semvmx=32767
* IPC Tunables - Messages - For Tuxedo
* entries in msg map (MSGMAP)
* set msgsys:msginfo_msgmap=2048
* max message size (MSGMAX)
* set msgsys:msginfo_msgmax=262144
* max bytes on queue (MSGMNB)
* set msgsys:msginfo_msgmnb=262144
* message queue identifiers (MSGMNI)
* set msgsys:msginfo_msgmni=1024
* message segment size (MSGSSZ)
* set msgsys:msginfo_msgssz=1024
* system message headers (MSGTQL)
* set msgsys:msginfo_msgtql=2048
* message segments (MSGSEG)
* set msgsys:msginfo_msgseg=2048
* Workstation Settings
* IPC Tunables - Messages - For Tuxedo
* entries in msg map (MSGMAP)
set msgsys:msginfo_msgmap=2048
* max message size (MSGMAX)
set msgsys:msginfo_msgmax=65535
* max bytes on queue (MSGMNB)
set msgsys:msginfo_msgmnb=512000
* message queue identifiers (MSGMNI)
set msgsys:msginfo_msgmni=1024
* message segment size (MSGSSZ)
set msgsys:msginfo_msgssz=1024
* system message headers (MSGTQL)
set msgsys:msginfo_msgtql=2048
* message segments (MSGSEG)
set msgsys:msginfo_msgseg=2048
Mervin Calverley wrote:
Fabrice:
The error implies that msgmni is set too low. msgmni is the total number of message
queues allowed in the system. Getting an error here implies that oracle or some
other process is consuming them.
For Tuxedo Classes we use the listed values as minimum for the kernel parameters
to perform the labs. In these classes the machine is only running Tuxedo. This
means the values are probably lower than those required by a production system or
one hosting Oracle as well as Tuxedo.
Message Queue Parameters:
MSGMAP 800
MSGMAX 32769
MSGMNB 42000
MSGMNI 400
MSGSSZ 64
MSGTQL 400
MSGSEG 2048
Semaphore Parameters:
SEMMAP 800
SEMMNI 800
SEMMNS 800
SEMMNU 800
SEMMSL 800
SEMOPM 64
SEMUME 64
SEMVMX 32769
SEMAEM 16384
Shared Memory Parameters:
SHMMAX 2097152
SHMMIN 1
SHMMNI 100
SHMSEG 64
SHMALL 2048
**Note: Some UNIX kernels do not support all of the above parameters or have additional
parameters not listed.
Hope this helps!
mervin
"Fabrice Poulard" <[email protected]> wrote:
Hi,
We get this error when we start more than 3 Appserver.
(Solaris 8 + Oracle)
Any information would be appreciated. Thanks.
It's my /etc/system file...
set maxusers=80
set shmsys:shminfo_shmmax=8589934590
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=15
set semsys:seminfo_semume=500
set semsys:seminfo_semmns=500
set semsys:seminfo_semmnu=500
set semsys:seminfo_semmsl=70
set semsys:seminfo_semmap=500
set semsys:seminfo_semmni=32
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767
set semsys:seminfo_msgmap=780
set semsys:seminfo_msgmax=4096
set semsys:seminfo_msgmnb=8192
set semsys:seminfo_msgmni=500
set semsys:seminfo_msgssz=8
set semsys:seminfo_msgtql=40
set semsys:seminfo_msgseg=1024
Brian Douglass
Transaction Processing Solutions, Inc.
8555 W. Sahara
Suite 112
Las Vegas, NV 89117
Voice: 702-254-5485
Fax: 702-254-9449
e-mail: [email protected]

Delete message queues

I had iconnection problems between one of the POA and MTA and I restored this connection after a couple days.
now I can see the poa open on the MTA bus the message between the post-offices are not working.
I thinking the delete the message queue because I believe that there is possible problem with the queue ( any bad message that blocked it).
How can I clean the POA queue ?
Tks.

* ffernandesv,
down the MTA, under the MTA directory, rename the MSLOCAL\MSHOLD\<postoffice>\ folder of the troubling PO. The folder will get recreated when you restart the MTA.
Also down the POA and rename the WPCSIn and WPCSOUT directory under the POA's directory structure.
HTH
Uwe

Queue Blocking and File picked Partially Problem ?

Hi All,
The File which is placed in FTP server having more 50000 to 65000 rows .
when XI picks the File the Partial Data is processed.
In SXMB_MONI if we check the message we are able to see some rows not full Data which was in file.
it's also blocking the Large message QUEUE -XBTM0000
while processing.
In QUEUE monitoring(SMQ2) the STATUS message is "Connnection CLosed No DATA" .
what could the reason here and also we are not able see any error related information(If it is having error) in SXMB_MONI.
it's urgent because of Production issue.
Regards
Nandan

Hi Indira,
In our scenario the Modification Check is set 5000 .
To resolve this problem what should i must do ?
Whether to decrease the present value or increase the present set value.
what will be the timing parameter Actually in Additional Parameter Tab?( SECONDS or MILLI SECONDS)

LIBTUX_CAT:681: ERROR: Failure to create message queue

I am getting the following error while starting PeopleSoft Application server for demo data base on Oracle Enterprise Linux 5.5 64 bit.
Can someone please help me what am I doing wrong here?
075417.localhost.localdomain!PSANALYTICSRV.4065.3909714272.0: LIBTUX_CAT:262: INFO: Standard main starting
075418.localhost.localdomain!PSRENSRV.4072.491399232.-2: 11-19-2010: Tuxedo Version 10.3.0.0, 64-bit
075418.localhost.localdomain!PSRENSRV.4072.491399232.-2: LIBTUX_CAT:681: ERROR: Failure to create message queue
075418.localhost.localdomain!PSRENSRV.4072.491399232.-2: LIBTUX_CAT:248: ERROR: System init function failed, Uunixerr = : msgget: No such file or directory
075418.localhost.localdomain!tmboot.4023.3569636960.-2: CMDTUX_CAT:825: ERROR: Process PSRENSRV at localhost.localdomain failed with /T tperrno (TPEOS - operating system error)
075418.localhost.localdomain!tmboot.4023.3569636960.-2: tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
075422.localhost.localdomain!BBL.4020.2558671968.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
075425.localhost.localdomain!PSADMIN.4014: End boot attempt on domain fdmo91

Never mind, I changed the kernel.msgmni to 1024, rebooted the server and then it started just fine.

Outbound queue blocked in CFM2

Hello folks,
I am trying to activate the integration model in CFM2 and I am getting message
"Outbound queue blocked"
Function/Q/SAPAPO/CIF_PROD_INBOUND
Text: NOSENDS
When I try to manually send the data in the queue in SMQ1 in the r/3, system asks me login to the SCM system and even though I give proper login, queue fails with the error message "Password logon no longer possible - too many failed attempts".But there is no issue with the login credentials.
Can you please helpme out here.
Thanks,
Vikram

Hi
Although you may be entering the correct user and password, the user may now be locked. You need to check if the RFC user is locked and if so unlock then try again.
Regards
Ian

Problem with GlassFish and Sun Java System Message Queue

Hi,
I used application server PE.8 and I upgraded to Sun Java System Application Server Platform Edition 9.0 Update 1 Patch 1, and I changed all my CLASSPATH and everything. My system is working fine, but the Sun Java System Message Queue that I used before is still showing the queues and physical queues of the previous application server, not the new one. Do you know if there is way to change that and link it to the new version?
thanks

Use an ESB like ServiceMix to bridge JMS providers
http://servicemix.org/
Or write your own MessageListener to consume from one JMS and publish on another one. Be careful with queues to avoid loosing the ordering - so you probably want to use a single MessageListener per subscription/queue - or to take advantage of Tibco's exclusive queues to ensure ordering is preserved. If ordering doesn't matter then don't worry too much about it and maybe have a pool of consumers to improve throughput
James
http://logicblaze.com/

Error message without blocking Input fields

Hi,
I want to display an error message in the selection screen. The error is for input date validation. But the once error displays in the status bar, it blocks the input fields in the selection screen. I want to display the error message without blocking any of the input parameter in the selection screen. Where should i write the code?
Thanks in advance.
Ezhil

Hi Ezhilhrh
I think you could have done a trial with different message types before posting this question.
Please try with success message(Type - S) and DISPLAY LIKE 'E'.
And also control the program flow using a flag or by checking the initiality of your internal table.
Regards
Hareesh Menon

Ile system or message queue is no longer available

Hi All,
We are using DB2 and AIX. We getting below error message in db2 log file.Please advise on this issue.
2014-08-13-05.09.08.624033+060 I12752832A1291     LEVEL: Error (OS)
PID     : 25756258             TID : 1           PROC : db2fmp (168768) 0
INSTANCE: db2fdf               NODE : 000
APPID   : 10.144.69.239.57155.140801190410
EDUID   : 1                    EDUNAME: db2fmp (168768) 0
FUNCTION: DB2 Common, OSSe, OSSMountListing::getNext, probe:90
MESSAGE : ECF=0x90000034=-1879048140=ECF_FILE_REMOTE_SYSTEM_NOT_ACTIVE
          File is on a remote system and the link to that system is not active
CALLED : OS, -, statvfs
OSERR   : ESTALE (52) "A file, file system or message queue is no longer available."
CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
[0] 0x09000000074F5548 pdOSSeLoggingCallback + 0x34
[1] 0x0900000008F0A6C4 oss_log__FP9OSSLogFacUiN32UlN26iPPc + 0x1C4
[2] 0x0900000008F0AB70 ossLogSysRC + 0x70
[3] 0x0900000008F2EB90 getNext__15OSSMountListingFCPC23OSSMountListingGetParamCP12OSSMountInfo + 0x4B0
[4] 0x09000000020314A4 db2sap_mount_info + 0x3C4
[5] 0x0900000007760EE4 sqloInvokeFnArgs + 0xB4
[6] 0x0900000007760D44 @76@sqlerRunRoutine__FP13sqleInvokerCBPi + 0x168
[7] 0x0900000007760AD0 sqlerDyload + 0x140
[8] 0x090000000774AA40 sqlerFmpListener + 0x154
[9] 0x0000000100001230 main + 0x910
Regards,
Raj

Hi,
I have checked with AIX team filesyetm every thing fine.Please tell me which filesystem caused thi issue.
Reagrds,
Raj

Oracle tuxedo and Oracle tuxedo message queue on top of a virtual machine.

Hi buddies.
how is it going?
A quick question.
So we are going to go live using Oracle Tuxedo 12.1.1.0 with Distinguished Bulletin Board Liaison and Oracle Tuxedo Message Queue 12.1.1.0 on top of a Virtual Machine (VMWARE) running Oracle Linux 6.2. However we want to know if there are any recommendations or mishaps in which we may face ahead by running Oracle Tuxedo on a virtual machine?
I mean, I am wondering if I have to worry about kernel parameters, virtual machine parameters or any other thing from which could mess up everything.
Another question.
Does oracle also provide virtual machines certification where Oracle tuxedo would run on top of ?
Todd Little-Oracle
Maurice G

Hi Bruno,
I'm not sure what you mean with Distinguished Bulletin Board Liaison. I'm guessing you mean a clustered or MP configuration? And is it truly a clustered configuration or just a single machine MP configuration?
Regarding configuration, are you using Tuxedo services as well or just Tuxedo Message Queue? The biggest issue related to OS configuration is around IPC resources. If you do a tmloadcf -c on your UBBCONFIG file, it will help you determine the minimum IPC resources required. In general I suggest configuring significantly more resources than the minimum to allow for future changes and for some of the parameters for heavier loads. In particular IPC message queue parameters are heavily dependent upon load. So make sure the maximum message size and queue size are large enough for your anticipated workload. You can monitor them under load using the ipcs command.
We don't certify virtual machine environment but support them as long as the VM vendor assures compatibility, which obviously VMware and Oracle VM both do.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

When I try to play youtube video I get the message of blocked plug-in, and I can not play video using Safari. (Youtube works fine with google chrome) I tried installing flash player HTML5 etc... but still no difference.

I just installed OSX Mountian Lion, and ever since then I can not play youtube video's. I get the message of 'Blocked Plug-in' in the youtube screen. I have tried installing Adobe Flash Player. HTML 5, also tried enabling/disabling java, but nothing worked out. Is there any way I can play youtbe vieos on Safar. (It works fine with Google Chrmoe, only safari has problem)

If you have the ClickToFlash extension installed, that can prevent Flash based video from streaming. Safari > Preferences > Extensions
It can also be installed as a plugin in /Library/Internet-Plug-Ins.
Try uninstalling the currently installled Flash plugin (required for most YouTube content) then reinstall new > Troubleshoot Flash Player | Mac OS
From your Safari menu bar top of your screen click Safari > Preferences then select the Advanced tab.
Select: Show Develop menu in menu bar
Now from the menu bar click Develop > Empty Caches

App Server Install fails - due to incompatible Message Queue

I had JES 2005 q1 installed in one of the test machines...now I am trying to set up JES 2005q4 on that. I cud install a Web Server on that ut when I tried to set up the App Server it throws up a msg stating that there is an incompatible version of Message Queue installed and hence installation cannot go ahead.
I am not able to find any instance of Message Queu setup....how do I detect and uninstall old versions of Message Queue??
thx
anand

I assume you are talking about appserver install on Solaris. Message Queue on Solaris is a package based install. The easiest way to uninstall the old version of MQ is: "pkginfo -i | grep Message" ---> "pkgrm all MQ packages".

Message Queue Blocking/MSGMNI Confirmations

Similar Messages

Maybe you are looking for