Messages in Buffered queue not beeing applied

Hi All,
Im running a streams environment. The receiving server crashed and was restarted. The apply process was restarted and the buffer was flooded with messages. Flow control initiatied on the sending database. The apply process doesn't show errors, but there are 5001 messages in the queue that arn't beeing applied. I' ve tried restarting the apply process and increased the number of parallel apply processes. Purging the queue doesn't seem like a good idea since the I will loose data. What can I do?
btw The messages in de queue seem to be in defered state. I dont know if this is of any importance...
Another thing that struck me as odd was the following:
Coordinator Low Watermark: 11063412548
Reader Oldest SCN: 11063412382
I would assume the Oldest SCN would be equal or higher that the Coordinator low watermark because messages are first beeing read, then coordinated then applied right?
and while I' m at it: it is no longer possible to disable the queue from Grid Control. If I try to, what happens is, that the status becomes disabled (red downward arrow) but the state remains:"DEQUEUEING MESSAGES"
kind regards,
Erik
Edited by: erikros on Apr 28, 2010 2:47 PM
Edited by: erikros on Apr 28, 2010 3:05 PM
Edited by: erikros on Apr 28, 2010 3:08 PM

Query 1
APPLY_NAME : P_APP1
Latency in Seconds : 29139
Message Creation : 2010-04-27 14:48
Apply Time : 2010-04-27 22:54
APPLIED_MESSAGE_NUMBER : 11063412548
Query 2
CAPTURE_NAME : P_CAP1
STATE : PAUSED FOR FLOW CONTROL
CAPTURE_TIME : 2010-04-29 07:41
CAPTURE_MESSAGE_NUMBER : 11063460122
CAPTURE_MESSAGE_CREATE_TIME : 2010-04-27 14:55
ENQUEUE_TIME : 2010-04-29 07:41
ENQUEUE_MESSAGE_NUMBER : 11063460122
ENQUEUE_MESSAGE_CREATE_TIME : 2010-04-27 14:55
AVAILABLE_MESSAGE_NUMBER : 11076534248
The second query had some fields in it that weren't supported by my version of Oracle 10.2. I replaced them with some others....
Edited by: erikros on Apr 29, 2010 8:24 AM

Similar Messages

Persisting Messages in Buffered Queues

Hello Everyone,
As per the oracle documentation http://docs.oracle.com/cd/B28359_01/server.111/b28321/strms_prop.htm#i1006905
LCRs that were captured by a capture process are always stored in a buffered queue, but LCRs that were captured by a synchronous capture are always stored in a persistent queue.
This means that if we use Capture process and server goes down( or is restarted), we will loose those messages in buffered queues as messages are stored in memory.
1) Is there a way to force capture process to persist the message into persistent queue?
2) Is there a way to recover the messages from buffered queue when we restart the server?
Please let me know if you have some ideas / some insights for above two cases.
Thanks
Nithin
Edited by: 906226 on Jan 5, 2012 11:20 AM

Hello,
This is really a Streams question.
When the database goes down the buffered messages are lost. However when the instance restarts the Capture re-mines the redo logs from the required_checkpoint_scn and then re-enqueues the LCRs. The apply also keeps track of where it was at via the apply progress So nothing is lost in the Streams scenario when an instance goes down. This is discussed in the documentation.
In the AQ world if you are using a buffered queue then the messages would be lost and the application would have to handle that situation.
Thanks
Peter

I recieved a notice that there was an update for Elements 13 but when I try to install it it stop's half way through then I get the error message that "updates could not be applied" I have tried several times and it continues to give me the error. What is

I get a message that an update is available and when I install it the update stops half way through and I get the error code: U44M1I210 for Camera Raw and Elements 13.1 updates. I get the message "UPDATES COULD NOT BE APPLIED" Can someone help with this? Thank you. David

drmeyers381
Thanks for the follow up.
Is your Premiere Elements 13 on Mac computer?
I have not seen much in the way of alternatives coming from Adobe on the Premiere Elements 13.1 failed updates.
But there seems to be several discussions on U44M11210 in the CC products...one
Update failure. (U44M1I210) | Adobe Community
You could try the uninstall, free ccleaner, reinstall with antivirus and firewall(s) and then try for the Help Menu/Update for 13.1..
If Mac, https://www.piriform.com/mac/ccleaner
If Windows, CCleaner - PC Optimization and Cleaning - Free Download
The CC people seem to have the advantage of an online download of their update as well as the one via the Help Menu/Update.
Premiere Elements does not have that perk - update only via Help Menu/Update.
Please review and consider and please let us know of your progress as your schedule permits.
Thank you.
ATR

Dynamic access policy ACL not beeing applied to user

Hi all
I have just configured my ASA for ssl vpn
I have created a dynamic access policy with an ACL in it.
The user connects fine, and I can see on the logs that the DAP policy has applied to the user
However when I click on monitoring, it says no acl is applied to this session, and the client cannot get anywhere
why would this be?
cheers
Carl

When you go to dynamic access policies in ASDM is your NoVPN ACL at the top of the list (highest ACL priority)? These get processed in order and if your user is in both groups the first will be taken and the rest ignored.
Also, is your default policy at that bottom of this list deny access?

SXMB_MONI message fail causing Queue struck at SMQ2

Hi All,
If mapping error occured in SXMB_MONI, corresponding entry will be struck up in SMQ2 and saying that SYSFAIL.
When i drill down this into further, it is saying that Mapping error.
Because of this all messages coming later also getting strucked in this queue.
Why is this happening and what to do for not to get struck further messages
Regards

Hi Hetal,
>>Create a job which will restart message after some time if it is stuck because of connection problem or something, then queue will be clear.
It's because of Mapping problem, even though we schedule a job to restart, it won't resolve. again it comes into same error.
@Prateej:
>>Could you check the QoS for the following entry in SXMB_MONI? Is it EOIO ?
QOS is Exactly Once
@Madu:
>>This is the standard behavior of PI. When some message will fail in Integration Engine(either because of Receiver not found or mapping error),some of remaining message(not all messages) which will come in the same queue of failed message will stuck.
You can not predict which messages will stuck and which messages will not stuck.
YES, you are right.
>>If you are having some important interface, which you want to divert the messages in other queue. You apply exactly once in order in sender channel for other interfaces so that these messages will not stuck in SMQ2.
For me all are Important Interfaces only. I can't prioritize
I think the better solution is Monitor failed messages in MONI every day and if it is failed because of Mapping error means, we can delete that entry from SMQ2.because for mapping related errors we don't require that message to restart again.
so that nothing will be queued after wards.
Regards

I got the message "Preferred Credential has not been set"

Dear Madem/Sir,
When I use the OEM, I expand the "HTTP Servers" item and click the "rh8svr1:4443".
It will appear the something in the right pane.
When I select the "started" option and click the [Apply] button, I will get the message "Preferred Credential has not bee set".
How can I resolve this probelm?
thanks and regards,
Janus [email protected]

I did set preferred credentials for the 9i server SID, but the HTTP Server does not allow anything to be set . It states that "No credentials are required for HTTP server mrc-2k:80"
\\thnx

Buffering table not up to date error message when creating a Cart

Hi Folks,
We are getting a 'Buffering table not up to date' error message when attempting to create a Cart. The error message only happens to the one end user ID only with the others not getting this error, therefore suggesting that my SRM org plan set-up is correct.
Has anyone come across this previously and what checks are available in the system to resolve this? As mentioned, the attribute check is okay and I have also removed the user ID from the SRM org plan and reassigned again but this has not corrected the problem. We are on SRM 5.
Thanks. Mike.
Message:
Buffering table not up to date
Method: GET_STRUCTURE_PATHS_UP of program CL_BBP_ES_EMPLOYEE_MYS========CP
Method: IF_BBP_ES_EMPLOYEE~GET_RL_UNIT_IDS of program CL_BBP_ES_EMPLOYEE_MYS========CP
Method: IF_BBP_ES_PROFESSIONAL~GET_WORKPLACE_ADDRESS_IDS of program CL_BBP_ES_EMPLOYEE_MYS========CP
Method: IF_BBP_ES_PROFESSIONAL~GET_WORKPLACE_ADDRESS_ID of program CL_BBP_ES_EMPLOYEE_MYS========CP
Method: IF_BBP_ES_PROFESSIONAL~GET_WORKPLACE_ADDRESS of program CL_BBP_ES_EMPLOYEE_MYS========CP
Form: USER_DETAIL_GET of program SAPLBBP_SC_APP
Form: GLOBAL_FILL of program SAPLBBP_SC_APP
Form: SC_INIT of program SAPLBBP_SC_APP
Function: BBP_SC_APP_EVENT_DISPATCHER of program SAPLBBP_SC_APP
Form: APP_EVENT_HANDLER of program SAPLBBP_SC_UI_ITS
Edited by: Mike Pallister on Nov 5, 2008 11:44 AM

Please advise on this problem. When I try to check the Approval Overview tab for these two shopping carts.
I got a dump.can anyone help me.
Information on where terminated
    Termination occurred in the ABAP program "CL_BBP_ES_EMPLOYEE_MYS========CP" -
     in "IF_BBP_ES_EMPLOYEE~GET_RL_UNIT_IDS".
    The main program was "SAPMHTTP ".
    In the source code you have the termination point in line 35
    of the (Include) program "CL_BBP_ES_EMPLOYEE_MYS========CM008".
    The termination is caused because exception "CX_BBP_ES_INTERNAL_ERROR" occurred
     in
    procedure "/SAPSRM/IF_PDO_DO_APV_EXT~GET_AGENT_DETAILS" "(METHOD)", but it was
     neither handled locally nor declared
    in the RAISING clause of its signature.
    The procedure is in program "/SAPSRM/CL_PDO_DO_APV_EXT=====CP "; its source
     code begins in line
    1 of the (Include program "/SAPSRM/CL_PDO_DO_APV_EXT=====CM00E ".

Unable to apply connection settings. The detailed error message is: 'NoCount' is not a recognized option

My corporate database wizards have created a login for my small subsidiary to use to read selected data from the HR database. It's meant to be used by an SSIS package to bring over data on who's a current employee and who's not.
The package has started returning connection errors, and when I try to log into the HR database via SSMS using this login I get the following message:
"Unable to apply connection settings. The detailed error message is" 'NoCount' is not a recognized option."
If I click on OK I can still log in, but it looks like this error is causing SSIS to produce an error. I've seen articles on vaguely similar errors logging onto an Azure database, but this one's on SQL Server 2012.
Anybody got any ideas? Is there something I can change at my end, or is it a change that has to be made in the remote DB?

I'm getting confused seeing this
The package has started returning connection errors, and when I try to log into the HR database via SSMS using this login
I get the following message:
Whats the purpose of SSIS package if you're trying to connect to DB using SSMS?
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Messages in queue not being delivered

Hi
I am using IMS 5.2. After a recent migration of user accounts to an new login ID, some user's emails are not being delivered to thier accounts and are accumulating in the ims-ms queue. When I did the migration, I copied the user's email to thier new account. I did reconstruct -f -r a couple of times, and emails appeared to be delivered to the new login accounts.
There were a few emails left in the queue but now there are close to 6000 and users are not getting emails delivered. When I look at the message in the queue, they state the user is overquota. I checked the user's account and they are not overquota.
Any suggestions on how to correct the problem or get the message to be delivered?
Thanks
Randy

Jay,
iPlanet Messaging Server 5.2 (built Feb 21 2002)
libimta.so 5.2 (built 15:07:23, Feb 21 2002)
SunOS cpmail 5.8 Generic_108528-27 sun4u sparc
SUNW,Ultra-60
This is the original release. There have been over thirty patch/hotfix releases, and hundreds of fixes. I URGE you to go to Sun's download site, and get 5.2p2, and install it immediately.Thanks for the advice Jay. The product is installed as part of the portal we are using(which I upgraded last June). I was unaware of the versioning and patches that are associated with the version of IMS that was installed. I will move forward with confirming with our portal vendor that the latest sp and patches will support the integrated IMS.
>>
>>
How did you "migrate" your users to new login id?When you "copied" the files, did you re-set
ownership/permisions of the files?
I used the following process in a script to migrate
the users from old login to new login:
1. created the new login mailbox with mboxutil -c
2. moved new mailbox to different partitions
There is a utility/command that does all of this for you.
mboxutil -r
When you "moved" the mailbox, I assume you use unix cp, right? Bad Idea.
current versions of mboxutil do this all for you, and don't need reconstruct afterwards.
I suspect that you have either not properly "moved" your user in LDAP, folder database, or have gotten file ownership or permissions wrong after the move.
Unix files are owned by a user and group, and have various read/write permissions set by the OS. YOu're on a Unix system, so you should know about such.I tried using the mboxutil -r initially but was getting a lot of errors with it in my test environment. In hindsight, I am thinking this had to do with the version of IMS I have installed. The unix file move was done with the IMS admin so would also own all the the messages etc on the OS side. I have obviously made a mess of things! So again, I will put in a support call to our portal vendor about how to proceed on this. I really appreciate your input into this.
3. retrieved hashed directory information for old and
new mailbox for user
4. copied files from old to new mailbox with cp -R
oldmailbox/* newmailbox/
5. after all users were migrated, I did a reconstruct
-f -r, and a reconstruct -f -m
I am not sure what you mean by re-set
ownership/permissions.
Have you looked at the "default" log for an errormessage?
I found the following errors in the default log:
default.60.1093908097:[31/Aug/2004:04:15:01 -0600]
cpmail stored[28697]: Store Critical: Error checking
mailbox database: Ignoring log file:
/usr/iplanet/ims52/msg-cpmail/store/mboxlist/log.00000
00543: magic number 0, not 40988
default.62.1094084554:[02/Sep/2004:04:15:02 -0600]
cpmail stored[20883]: Store Critical: Error checking
mailbox database: Ignoring log file:
/usr/iplanet/ims52/msg-cpmail/store/mboxlist/log.00000
00543: magic number 0, not 40988
Your reconstruct command may have been wrong, too. That's what the errors are telling you.
Also, there are other problems in your system. Permission problems, most likely.
I would do a reconstruct -m, first. and see if the above goes away.I will proceed with what you suggested, and let you know the results. Again, thank you very much for your time and input for this.
>>
>>
AS well, when I do a mboxutil -u on an affected user,
the quota information says the user is well under
quota. For example:
$ mboxutil -u xxxxxxxxx
diskquota size(K) %use msgquota msgs %use user
25600 2604 10% no quota 19
19 xxxxxxxxxxx
The error message doesn't really have anything todo with quota.>>
>>
In imta/queue/ims-ms, the user has 183 messages
waiting to be delivered. All of the messages say the
user is over quota.
Any suggestions?
Randy, you need to re-think how you're moving users. You have somewhat messed up your mailstore. . . I will in re-think things. In fact, I have a number of users to migrate. I will stop what I am doing and get this right before I proceed! There is no sense compounding the problem when there is a better alternative. One thing for sure, I will continue using this forum before I proceed with messing with a production system!
You may need to contact tech support for the immediate help you will need to straighten this all out.>>
>>
RandyThanks Jay.
Randy

Message posted from BPEL not found in oc4j JMS queue

Hi,
I am facing a weird problem when I try to post a message in oc4j JMS from a BPEL process.
There is no exception(Not even in the logs) and the BPEL process gets completed. But the message is missing(Could not find it while monitoring the queue).
I am using SOA suite 10.1.3.5 and the oc4j JMS queue which comes with the installation.
Can someone help me please.
Saptarishi
Edited by: saptarishi on May 25, 2010 3:51 PM

Got a solution.

MQ Adapter does not clear the rejected message from the queue

Hi All,
I'm using a MQ Adapter to fetch the message from the queue without any Backout queue configured. However, whenever there is any bad structured message found in the queue, MQ adapter rejects the message and moves the message to the rejmsg folder but does not clear it off the queue, as a result of which it keeps retrying the same hence, filling the logs and the physical memory. Somehow we do not have any backout queue configured so I can move the message to blackout queue. I have tried configuring the jca retry properties and global jca retry as well but to no avail.
- Is it not the default behaviour of MQ Adapter to remove the rejected message from the queue irrespective of Backout queue is configured or not? The same behaviour working well with the JMS and File Adapter though.
- Is there any way I can make MQ Adapter delete the message from that queue once it is rejected?
Regards,
Neeraj Sehgal

Hi Jayson,
Check this URL which answers a problem with com.sap.engine.boot.loader.ResourceMultiParentClassLoader problem:
http://209.85.175.132/search?q=cache:RnFZ9viwuKkJ:https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fcom.sap.sdn.folder.sdn!2fcom.sap.sdn.folder.application!2fcom.sap.sdn.folder.roles!2fcom.sap.sdn.folder.navigationroles!2fcom.sap.sdn.role.anonymous!2fcom.sap.sdn.tln.workset.forums!2fforumtest!2fcom.sap.sdn.app.iview.forumthread%3FQuickLink%3Dthread%26tstart%3D45%26threadID%3D1020700+com.sap.engine.boot.loader.ResourceMultiParentClassLoader&hl=en&ct=clnk&cd=3&gl=in&client=firefox-a
Please check that the JDK compliance level is at 5.0
Window->Preferences->Java->Compiler->Compiler compliance level set this to 5.0
Set the installed JRE to the one you have mentioned JDK 5.0 update 16
Window->Preferences->Java->Installed JRE's->
Click on the add button to select the path of your JDK.
once completed click on the check box next to it.
regards,
AKD

MDB is not picking up messages in the Queue

Hi ,
I am trying to implement a MDB (Producer) , that acts as a Message Producer also . This MDB pickes up a message from a Queue and sends it to another Queue(Queue 2) after some processing. The MDB listening to the Queue 2 is not being able to pick this message.
The Weblogic console shows that the message is pending.
The transaction-type is Container and transaction-attribute is 'Required' for the Producer (MDB) ...
I am creating a QueueSession as con.createQueueSession(true, Session.AUTO_ACKNOWLEDGE) . I also tried specifying queuesession.commit() ...
even then the Message is not picked by the MDB listening on the other side...
Please help me out

any one

Weblogic 10.3 Not Removing Expired Messages from JMS Queues

Dear All,
We have an application that is running on Weblogic 10.3.
This application (let us call this application Y) receives messages on a JMS queue. These messages are placed on the queue by another application (let us call this application X). We would like to have these messages expire within a certain amount of time (i.e. 90000 ms) if they are not consumed.
Now when application X places the messages onto the queue for application Y to consume, the JMS producer sets the time to live to 90000 ms. We can see that expiration time has been set appropriately in the weblogic console. If a message sits on the queue for longer than 90000 ms the state string of the message is changed to "receive expired". What we don't understand is why the expired messages still end up being consumed from the queue.
We understand that Weblogic is supposed to have an 'Active Message Expiration' thread that will remove expired messages from the queue. The Expiration Scan Interval for the JMS Server is set to 30 (seconds).
Can anyone tell us why our expired messages don't seem to be deleted from the queues?
Tim

Thank you for the response Rene.
We have set up both the active expiration scan and the message expiration policy. The active expiration scan is set for every 30 seconds. The message expiration policy is set to "discard". However, the expired messages are still being consumed. Is it possible we are doing something wrong? See a portion of our configuration files below.
We have set up the expiration scan time interval. See a portion of our config.xml below:
<jms-server>
<name>brokerJMSServer</name>
<target>AdminServer</target>
<persistent-store xsi:nil="true"></persistent-store>
<store-enabled>true</store-enabled>
<allows-persistent-downgrade>false</allows-persistent-downgrade>
<hosting-temporary-destinations>true</hosting-temporary-destinations>
<temporary-template-resource xsi:nil="true"></temporary-template-resource>
<temporary-template-name xsi:nil="true"></temporary-template-name>
<message-buffer-size>-1</message-buffer-size>
*<expiration-scan-interval>30</expiration-scan-interval>*
<production-paused-at-startup>false</production-paused-at-startup>
<insertion-paused-at-startup>false</insertion-paused-at-startup>
<consumption-paused-at-startup>false</consumption-paused-at-startup>
</jms-server>
<jms-system-resource>
<name>broker-jms</name>
<target>AdminServer</target>
<sub-deployment>
<name>EhrBrokerRequestQueue</name>
<target>brokerJMSServer</target>
</sub-deployment>
<descriptor-file-name>jms/broker-jms.xml</descriptor-file-name>
</jms-system-resource>
<admin-server-name>AdminServer</admin-server-name>
We have set up the message expiration policy in our jms descriptor. See a portion below:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-jms http://www.bea.com/ns/weblogic/weblogic-jms/1.0/weblogic-jms.xsd">
<queue name="EhrBrokerRequestQueue">
<delivery-params-overrides>
<redelivery-delay>-1</redelivery-delay>
</delivery-params-overrides>
<delivery-failure-params>
<redelivery-limit>-1</redelivery-limit>
*<expiration-policy>Discard</expiration-policy>*
</delivery-failure-params>
<jndi-name>EhrBrokerRequestQueue</jndi-name>
</queue>
</weblogic-jms>
What could we be doing wrong?
Kind Regards,
Tim

QueueBrowser not scaning all messages in JMS queue (ie not showing inprogre

Hi all,
I am using JMS in jboss-3.2.3, when scaning for pending messages i am using QueueBrowser.
But QueueBrowser not scaning all messages in JMS queue (ie not showing inprogress message)
But i need to know all messages including ongoing messages..
Antone plz help me
I am using Queuesender and QueueReceiver ..But some Exception or Error causes my JMS server(QueueReceiver listening for onMessage()) hanged up..and not responding to remaining messages...So i need to find pending messags in JMS queue..How can find?
Now i am using QueueBrowser to get list of pending msgs in queue... But doesn't contains Message which passed for processing (called onMessage())
.. But i need to find this also..How can?
Thanks,
Thilsen

You're right in thinking that the behaviour you describe looks wrong.
Take a look at the QueueBrowser interface which can be used to inspect a queue. You get one using QueueSession.createBrowser(Queue). The QueueBrowser allows you to scan a queue without consuming the messages. However note that the state of the queue may change while you're observing it through the QueueBrowser so what you see might not always be a 100% accurate representation of the queue at any given time.
Other things to check:
- message selectors - are you setting a message selector on your queue receiver which is resulting in not all of the messages 'matching'.
- expired messages - are you setting a time-to-live on the messages that you publish.
Hope this helps,
David Ingham
http://www.arjuna.com

Dequeue with OCCI does not remove the message from the queue

Hey there,
I have this problem where no matter what dequeue option I try the messages never seem to be removed from the queue... I tried looking around and found only a similar un-answered question...
Thanks in advance...
void TryAnydataDequeue(oracle::occi::Connection * conn)
     try
          std::cout << "Dequeue Commence..." << std::endl;
          Consumer cons(conn);
          //Settings de dequeue
          cons.setCorrelationId("SPPC");
          cons.setQueueName("Anydata_queue");
          cons.setConsumerName("SNOOP");
          cons.setDequeueMode(cons.DEQ_REMOVE);
          //cons.setDequeueMode(cons.DEQ_LOCKED);
          std::cout << "Reception du message..." << std::endl;
          Message m2 = cons.receive(Message::ANYDATA);
          AnyData any(conn);
          any = m2.getAnyData();
          if(!any.isNull())
               oracle::occi::TypeCode type = any.getType();
               if(type == OCCI_TYPECODE_VARCHAR2)
                    std::string msg = any.getAsString();
                    std::cout << "Message Reçu: ";
                    std::cout << msg << std::endl;
               else
                    std::cout << "Format du message invalide..." << std::endl;
               std::cout << "Fin du message... (Press a key)" << std::endl;
          else
               std::cout << "Message invalide..." << std::endl;
          System::String * theInput = System::Console::ReadLine();
     catch(SQLException ex)
          std::cout << "Exception: " << ex.getErrorCode() << " - " << ex.getMessage() << std::endl;
          System::String * tnput = System::Console::ReadLine();
}

The message from the queue will be removed when you do a commit after a successful dequeue call, depending upon your message retention settings.
After you have done this processing and successfully performed a commit, what is the output of the following query:
SQL> connect AQADMIN/password
SQL> select msg_state from aq$<your_queue_table_name_goes_here> ;?
If it is PROCESSED, check your queue retention settings.
Additionally, make sure that the init.ora parameter AQ_TM_PROCESSES is set to a NON-ZERO value for this to happen.

Messages in Buffered queue not beeing applied

Similar Messages

Maybe you are looking for