Dead message queue
Intial information:
SUN MQ 4.3
Local installation
Purpose: use dead message queue.
As per refered in SUN MQ admin guide have updated the broker
imqcmd update dst -t q -n TestQueue1 -o useDMQ=true
imqcmd update dst -t q -n TestQueue1 -o MaxBytesPerMsg=150000
Also java program sending message to the queue and data is of size 171KB(171000)
With above setting I expect the message to go to mq.sys.dmq, however its not? Any one have answer?
Or any one have used dead message queue with SUN MQ?
Any help will be appreciated.
Madhav
Edited by: user10111912 on Jan 20, 2011 4:18 PM
In this case, the message will be rejected, that is it does not get into the destination, which is different from a message in the destination becomes "dead" - dead message.
Similar Messages
-
Howto config msg policies for dead message queue (dmq) outside Glassfish?
The one thing I really love about OpenMQ is that I can have a centralized message store with a cluster of JMS nodes interacting with it.
I'm now at a contract gig which is pretty much a Tomcat/Spring only shop. I've setup OpenMQ 4.3 w/ MySQL message store and am using Bitronix Transaction Manager (BTM) to pool my XA connections and manage the transactions that are instrumented via AspectJ from the Spring configuration.
I have two issues really ...
1) The Spring DefaultMessageListenerContainer does not seem to think it needs to pull messages off the queue unless there is more than one message in the queue. It behaves as if it needs to be primed with messages. I would blame it on DefaultMessageListenerContainer if not for the fact that when I do the same thing with ActiveMQ it works fine.
2) ActiveMQ has this cool [RedeliveryPolicy object|http://activemq.apache.org/redelivery-policy.html] that you can associate with the connection factory. The com.sun.messaging.XAQueueConnectionFactory has no such settings. What limited amount of similar setting exist in OpenMQ seem to be associated with the ActivationSpec which seems to be more related to resource adapters as run from within an app server like Glassfish. My guess that it is outside the realm of configuration for OpenMQ is based on the fact that the default for endpointExceptionRedeliveryAttempts is 6 and when I enable transactions for my queue the messages will thrash indefinitely when they start hitting exceptions.
So, how do I configure a message delivery policy for OpenMQ outside of Glassfish? Or is the notion of a dead message queue (dmq) completely useless for OpenMQ without Glassfish?
Thanks,
Steve MaringOpenMQ does not have such a feature. The only thing you can do is to disable or enable DMQ delivery per destination. There is no way of configuring the number of redeliveries before message gets moved to DMQ.
Tom -
Dead message queue - DLQ for foreign JMS providers
Is there a way to configure Error-queue or 'Dead message/letter queue' in MDB listening to foreign JMS provider like JBoss? (Automatic routing of failed messages to error-queue after specified retries to preserve JMS messages)
I did all the docs from BEA and it doesn't cover this DLQ for foreign JMS providers :). For Weblogic JMS service, DLQ can be configured in the config.xml. But for <ForeignJMSServer> there is no way to configure dead-queue.
Could some please validate this before I start coding this piece in the application instead of appserver configuration.
JMS provider is Tibco and JMS destinations are pre-defined and can't/doesn't need to be created
Thanks in advance.Interesting idea! But no, there's no facility for redirecting failed foreign provider messages to a DLQ. This is a feature normally supplied by the foreign provider itself.
Some foreign providers, in addition to WebLogic 9.0 JMS, provide a "redelivery count" property in the message. If the foreign provider provides no automatic DLQ capability, you might be able to leverage this property to have your MDB application code automatically forward messages with high redelivery counts to the DLQ.
Tom -
Strange, I think - Tuxedo 6.5 message queues have different owner, creator
All -
I realize that version 6.5 is ancient software now, but it's what we're running. I'm also a very inexperienced Tuxedo user, but I have worked with Unix and databases for many years now.
We have the occasional LIBTUX_CAT:476 (lost message)
and LIBTUX_CAT:477 (server died)
errors now, and they've been occurring every few minutes
since last Thursday for no apparent reason. These errors
in the ULOG are accompanied by a restart of the dead
server. Our users, however, complain of massive waits in
their applications, and we can't go on like this in our
production system.
Checking the tuxedo message queues, we see a few lines
like this when doing "ipcs -qa":
T ID KEY MODE OWNER GROUP CREATOR CGROUP <snip>
q 134853 0 --rw-rw-rw- tuxedo admin oraGCMN dba <snip>
I've edited this slightly to eliminate confusion.
My concern is that the OWNER and CREATOR values are different. I've never seen that before. The STIME
and RTIME values for these errant queues (not shown above)
correspond to the "server died" entries in the ULOG, and
this is surely not coincidental.
The queues should be owned and created by the "tuxedo"
user, I think. Our oraGCMN user is an Oracle user
that owns the application server and makes a user-defined
exit to the Tuxedo application. Frankly, I don't see
how this OS user could possibly ever create a tuxedo
queue.
Do you have any suggestions on how I should proceed?You may want to compare the IDs of these queues against the IDs of all
Tuxedo server and client queues to see if these are Tuxedo queues or if they
are queues used by Oracle or some other application. You can get the IDs of
all Tuxedo queues using the command
tmadmin <<!
verbose
psr
pclt
(It is also possible to get the same information using the MIB if you plan
on doing this frequently and need to parse the output programatically.)
<Tom Gaines> wrote in message news:[email protected]..
All -
I realize that version 6.5 is ancient software now, but it's what we'rerunning. I'm also a very inexperienced Tuxedo user, but I have worked with
Unix and databases for many years now.
>
We have the occasional LIBTUX_CAT:476 (lost message)
and LIBTUX_CAT:477 (server died)
errors now, and they've been occurring every few minutes
since last Thursday for no apparent reason. These errors
in the ULOG are accompanied by a restart of the dead
server. Our users, however, complain of massive waits in
their applications, and we can't go on like this in our
production system.
Checking the tuxedo message queues, we see a few lines
like this when doing "ipcs -qa":
T ID KEY MODE OWNER GROUP CREATOR CGROUP <snip>
q 134853 0 --rw-rw-rw- tuxedo admin oraGCMN dba <snip>
I've edited this slightly to eliminate confusion.
My concern is that the OWNER and CREATOR values are different. I've neverseen that before. The STIME
and RTIME values for these errant queues (not shown above)
correspond to the "server died" entries in the ULOG, and
this is surely not coincidental.
The queues should be owned and created by the "tuxedo"
user, I think. Our oraGCMN user is an Oracle user
that owns the application server and makes a user-defined
exit to the Tuxedo application. Frankly, I don't see
how this OS user could possibly ever create a tuxedo
queue.
Do you have any suggestions on how I should proceed? -
Configure backout queue and Dead letter queue in weblogic JMS provider
Hi,
How to configure the JMS backout queue and dead letter queue in weblogic JMS provider in weblogic application server console?
Any links or documents are highly appreciated.
Thanks.Thanks anon. When i say backout message the poisonous message , A poison message is one which cannot be processed by a receiving MDB application. If a poison message is encountered, the JMS MessageConsumer and ConnectionConsumer objects can requeue it according to two queue properties, BOQUEUE, and BOTHRESH.
Normally this happens in the websphere MQ . Where we will configure the backout queue and dead letter queue.
The dead letter queue was always used in MQSeries (the last time I used MQ) to store messages that arrived at the queue manager but the queue didn't exist. For eample, if the message was address to queue manager X and queue Y, it would arrive via a channel at manager X. If the receiver channel discovered there was no queue Y, it would be placed in the dead letter queue.
The backout queue, on the other hand, is more of an application-level thing (at least in terms of MQ). When an MQ client cannot process the message for some reason, it can back it out for later processing (back to it's original queue).If it's backed out too many times (the threshold can be configured), it gets moved to the backout queue.
The Dead Letter Queue behaves the same as a Backout. I treat the Dead Letter Queue as the Crematorium for messages that cannot be recovered in the Error or Backout queues and have some last, non-business specific data that need be collected. Once the info is captured, the message is put down for good. Backout is good for analyzing messages for data that may need to be recovered to completely reprocess or be sent back to an application area for them to decision on.
How we configure these in weblogic server both Backout and Deadletter queue , whether this is a simple queue in which we will set the error destination in case of any poisonous message so that it will logged in those queue?
Thanks. -
Backout queue or dead letter Queue in MQ
We need to monitor the backout queue in a J2EE environment. Can we treat the queue as a regular queue and have a consumer "listen" to the queue?
Can we do the same way on the "dead letter Queue "?
If yes, how we set up the JNDI?
Your advice is greatly appreciated.
Bsun.Thanks anon. When i say backout message the poisonous message , A poison message is one which cannot be processed by a receiving MDB application. If a poison message is encountered, the JMS MessageConsumer and ConnectionConsumer objects can requeue it according to two queue properties, BOQUEUE, and BOTHRESH.
Normally this happens in the websphere MQ . Where we will configure the backout queue and dead letter queue.
The dead letter queue was always used in MQSeries (the last time I used MQ) to store messages that arrived at the queue manager but the queue didn't exist. For eample, if the message was address to queue manager X and queue Y, it would arrive via a channel at manager X. If the receiver channel discovered there was no queue Y, it would be placed in the dead letter queue.
The backout queue, on the other hand, is more of an application-level thing (at least in terms of MQ). When an MQ client cannot process the message for some reason, it can back it out for later processing (back to it's original queue).If it's backed out too many times (the threshold can be configured), it gets moved to the backout queue.
The Dead Letter Queue behaves the same as a Backout. I treat the Dead Letter Queue as the Crematorium for messages that cannot be recovered in the Error or Backout queues and have some last, non-business specific data that need be collected. Once the info is captured, the message is put down for good. Backout is good for analyzing messages for data that may need to be recovered to completely reprocess or be sent back to an application area for them to decision on.
How we configure these in weblogic server both Backout and Deadletter queue , whether this is a simple queue in which we will set the error destination in case of any poisonous message so that it will logged in those queue?
Thanks. -
Dead letter queue - QRFC.
Hi All,
Do you know if we can configure Dead Letter queue for qRFC ?
As you know, In XI if one message fails in queue, XI will block all subsequent messages for the same queue. Is there any option that we can move that failed message to some Dead Letter Queue as well as trigger some alert so that other message from the same source system can continue processing.
Thanks & Regards,
Dijesh Tanna.Hi,
I think in XI we already have the ALERT Framework to trigger various alert notifications based on failures.
You can use this Alert Notification.
About Dead letter queue, this can be applicable in other applications as those messages are interdependent on next messages.
But in XI, subsequent messages are independent, so rather than to allow it to fail, catch the error and send the message to a dead letter queue. Its preferable to use the ALERT Framework.
Thanks
Swarup -
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?
thanksUse 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/ -
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,
RajHi,
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 GHi 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 -
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
anandI 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".
-
Clearing JAVA Message Queue in PI 7.1
Hi Experts
I am working on a file to File Scenario, and file has been picked up on the sender CC and mesaages have been sent to JAVA queues, But the messages are stuck on the JAVA queues,
Java Queue name: File_http://sap.com/xi/XI/SystemRecv
How can I clear the JAVA message queue in PI 7.1
Thanks
PRIf the messages are on the queue, usually one of the actions must be performed: a) Fix the related scenario and restart the messages or b) Manually cancel the messages. This is also advised on the note below under item "3. Troubleshooting Archiving / Deletion in the Adapter Framework"
[Note 872388 - Troubleshooting Archiving and Deletion in PI|https://service.sap.com/sap/support/notes/872388]
If you are having performance problems, please check if the messages are taking long time in TBDL/Holding status. Let us know if this is the case. -
Get/set message Queue ID in PI 7.1 Adapter module
Hello,
I have a special requirment to get and set message Queue ID in PI 7.1 adapter module.
I tried to use the method setConversationID for the Message Class, but this doest seem to available any more.
Any pointers to which class and method can be used.
Thanks in advance
Regards,
AbhishekHi, try [setSequenceId|http://help.sap.com/javadocs/pi/pi711sp03/com/sap/engine/interfaces/messaging/api/Message.html#setSequenceId(java.lang.String)]. Maybe you have to use setDeliverySemantics before in order to set EOIO.
regards, Martin -
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 -
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.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.
Maybe you are looking for
-
Mail keeps crashing after SL install, even after Mail folder moved to trash
I have also just upgraded to 10.6 and Mail crashes every time on launch. In my case, even moving the Mail folder in Library to trash has not worked. Every time I do this Mail regenerates the folder with all the old information, which I suspect is whe
-
IPhone 4 not recognised on iTunes 11.2.2
I've updated to iTunes 11.2.2, tried to sync my iPhone 4 with my USB cable, but it only charges and doesn't come up in devices. I've read MANY other complaints about this issue, and it's a huge oversight to whoever designed the update. I've already f
-
Hi, So I have a late 2006 1.83 ghz Intel Core 2 Duo MacBook A1185. And last night I upgraded my software to Mac OS X Snow Leopard 10.6.8. And then this morning when I went to start doing work on it, my trackpad wouldn't allow me to click on anything.
-
Trying to add a new region to an Oracle seeded page
Hi, I have a requirement in my project where I have to add a sub tab region to standard OAF page. I have created an independent region for the same and using XML importer loaded the page on server. Through personalization, I am trying to add region o
-
Hi problem with Oracle 10g On windows 2003 SR1
Hi, I am installing NW2004S on windows 2003 SR1 (Std.Edition). After the installation of Oracle 10g I am getting the error "I*SQLPlus service" can't be started. Any help on this regard is greatly appreciated. Regards, Rao.M