Messages banner stuck

The notification banner that drops down momentarily while your in an app has recently began to drop down and never disappear until I either exit the app or press the notification. It looks like the only notification that has been doing this is Messages. Emails, Facebook and other app notifications seem to be working okay. Anyone else see this? Is there a fix?
Checked notification settings.
Exited Messages app on the multitasking bar.
Turned off & on the phone.

Turn off the feature.
Settings > Notifications > Messages > Alert Style > None
Hope that helps

Similar Messages

Messages getting stuck in SMQ2

Messages get stuck in SMQ2 with the Error msg "SQL error on database occurred when accessing a table".
This is happening on PI system 7.11 SP04 with Max DB version 7.7.06.07.
This typically happens when sending messages from one BPM to another although it has more of a random pattern.
A corresponding dump is also seen in ST22.
The dump details are as below:
Runtime error : DBIF_RSQL_SQL_ERROR
Exception : CX_SY_OPEN_SQL_DB
Database error text : Invalid numeric value for parameter/column (10)
Internal call code : "[RSQL/UPDT/SWFRXIHDR ]"
Any help is highly appreciated in resolving this issue.
Regards,
Murali Narayanan

> The dump details are as below:
> Runtime error : DBIF_RSQL_SQL_ERROR
> Exception : CX_SY_OPEN_SQL_DB
> Database error text : Invalid numeric value for parameter/column (10)
I would update the kernel (plus the database interface library lib_dbsl) to the latest patchlevels and try again. If the error persists I'd upgrade the database to the latest patchlevel. If it still doesn't work I'd open an OSS call (BC-DB-SDB).
Markus

Message getting stuck in XBQO queue - Time limit exceeded

Hi All,
We have a BPM scenario in our project (on PI 7.0 SP18), where bundle of PEXR2002 Payment IDocs are received as a single flat file. This file is then consumed by the BPM, to split the message into multiple payments using Java Mapping.
However, when we get an IDoc file of size greater than 5 MB (more than 500 IDocs), the message gets stuck in XBQO queue and eventually giving a SYSFAIL with the message "Time limit exceeded". Could you please let us know if you have encountered a similar issue and are aware of a possible solution.
Any pointers to this will be really appreciated.
Thanks & Regards,
ROSIE SASIDHARAN

H Rosie,
1) Goto SXMB_ADM-> Integration Engine Configuration->Parameter EO_MSG_SIZE_LIMIT->possible values 0 - 2,097,151 (KB)
The parameter EO_MSG_SIZE_LIMIT enables serial processing of messages of a particular size. This applies for messages with the quality of service Exactly Once (EO). If the message is larger than the parameter value, the message is processed in a separate queue.
2) Goto SXMB_ADM-> Integration Engine Configuration->Parameter HTTP_TIMEOUT->possible values n Seconds, where n is a whole number.
The parameter Specifies the timeout for HTTP connections (time between two data packages at line level). This value overrides the system profile parameter icm/server_port_n (for example, icm/server_port_0 : PROT=HTTP, PORT=50044, TIMEOUT=900). If you do not set the parameter HTTP_TIMEOUT or if you set the parameter to 0, then the setting for the system profile parameter is used.
See SAP Note 335162 for sysfail issue....
Hope these will help u....
Regds,
Pinangshuk.

Messages getting stuck in QRFC Queue

Hi,
Today I noticed that a message had gotten stuck with the status "Sheduled for Outbound Processing" (scenario IDOC->XI->File), XI 3.0 SP11.
This in turn had the effect that the whole QRFC queue got stuck, and all following messages got stuck with status "Sheduled".
I had to remove the first message from the queue manually so that XI could start to purge the other messages from the queue.
What could be the reason for the first messages getting stuck with this status ("Sheduled for Outbound Processing")?
The message was very small, just a couple of lines. One thing that comes into mind, is that XI received 4 IDOCS for the same interface, within one second. These 4 messages were assigned to different queues, but one of them got stuck. Could there be problems with XI when several messages arrive on the same interface within a very short time?
Is it possible to use Alerts to detect this kind of problem in the future? As I have understood, Alerts only handle XI "errors", but according to XI, this message did not have an "error status", it just had the status "Sheduled for Outbound processing"..
Thanks for any help,
Hans

Hi,
If the message got struck in Queue, you try to activate the queues in smq2 to reprocess the data instead of deleting it. This is the final solution. But you should able to see a dump in ST22 for this problem.
thanks,
sasi

Messages getting stuck in tcp_local Channel

Hi All
Version
Sun Java(tm) System Messaging Server 6.1 HotFix 0.01 (built Jun 24 2004)
libimta.so 6.1 HotFix 0.01 (built 12:52:04, Jun 24 2004)
SunOS dakota 5.9 Generic_112233-12 sun4u sparc SUNW,Sun-Fire-V440
Background
In the last week we've been experiencing problems with outgoing messages getting stuck in our tcp_local channel. They can stay for up to 4 hours before dequeuing. We plan to install Patch 116568 which is the latest core patch for our version of the Messaging Server.
To date we haven't experienced any DNS problems and have not made any configuration changes.
However I was just wondering if anyone had come across this type of problem before? We're hoping the patch will resolve the issue but would be interested in other alternatives.
Thanks in advance
Paul

You'll have to do more research before I can offer help. . .
It's not unusual for some messages to be retried, and depending on the destination, that may take a while.
Some outside domains are always slow. If you have many messages queued for such outside domains, they can involve the whole server, and cause mails to queue up behind them.
Many installations create a new channel, such as, "tcp_slow", and use rewrite rules to move messages addressed to these domains (aol, hotmail, earthlink, etc.) into this separate channel. You can "tune" that channel differently, and messages there won't block tcp_local.

Messages are stuck in SMQ2

Hi,
Our messages are stuck in SMQ2, and I think this is due to high volume of messages. I have configured the IS to allow the QRF_RESTART_ALLOWED to 1, and scheduled the RSQIWKEX job to run periodically. But, the messages are still stuck in SMQ2.
Does anyone know what are the next steps we should look into to solve this problem?
Any help is greatly appreciated.
Thanks,
Karma

Just try - go to SXMB_ADM->Manage Queues and Deregister all the Queues. Then go to SMQ2 and try to activate all the queues by selecting the each lines and with activate button.
Then re-register the queues in SXMB_ADM and chek it..
Problem may be because of workprocess related. Also check transaction ST22 for if any dump in XI box.
btw what is the scenario ? Is it because of huge message processing ?
Regards,
Moorthy

Messages got stuck in inbound adapter engine queue

Hi Experts,
My senario is File - XI -SAOP reciever and we have 8 usecases of same type. For 7 usecase, we dont have any problem. But for only one use case we have having heavy delay in processing messages.
All my messages got stuck in inbound queue of Adapter engine in to be delivered state, wait state, delivering state.
Please see the below logs and suggest some solution.
To be delivered Message log :
Time Stamp Status Description
2008-06-30 06:54:20 Success Processing child message of multi-message with message ID 8c597510-466f-11dd-92f9-000f203c93e0
2008-06-30 06:54:20 Success Using connection AFW. Trying to put the message into the receive queue.
2008-06-30 06:54:20 Success Message successfully put into the queue.
Waiting Message log :
Audit Log for Message: 4864ad2b-cabd-5891-e100-00000aa3fdb2
Time Stamp Status Description
2008-06-30 06:42:24 Success Processing child message of multi-message with message I
2008-06-30 06:42:24 Success Using connection AFW. Trying to put the message into the receive queue.
2008-06-30 06:42:24 Success Message successfully put into the queue.
2008-06-30 07:46:16 Success The message was successfully retrieved from the receive queue.
2008-06-30 07:46:16 Success The message status set to DLNG.
2008-06-30 07:46:16 Success Delivering to channel: CC_SOAP_Receiver
2008-06-30 07:46:16 Success SOAP: request message entering the adapter
2008-06-30 07:51:24 Success SOAP: call failed
2008-06-30 07:51:24 Success SOAP: sending a delivery error ack ...
2008-06-30 07:51:24 Success SOAP: sent a delivery error ack
2008-06-30 07:51:24 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
2008-06-30 07:51:24 Error Exception caught by adapter framework: Read timed out
2008-06-30 07:51:24 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
2008-06-30 07:51:24 Success The asynchronous message was successfully scheduled to be delivered at Mon Jun 30 07:56:24 GMT 2008.
2008-06-30 07:51:24 Success The message status set to WAIT.
Delivering Message log :
Audit Log for Message: 4864ad2d-cabd-5891-e100-00000aa3fdb2
Time Stamp Status Description
2008-06-30 06:42:24 Success Processing child message of multi-message with message ID 7481f110-466f-11dd-b8ce-000f203c93e0
2008-06-30 06:42:24 Success Using connection AFW. Trying to put the message into the receive queue.
2008-06-30 06:42:24 Success Message successfully put into the queue.
2008-06-30 07:46:24 Success The message was successfully retrieved from the receive queue.
2008-06-30 07:46:24 Success The message status set to DLNG.
2008-06-30 07:46:24 Success Delivering to channel: CC_SOAP_Receiver
2008-06-30 07:46:24 Success SOAP: request message entering the adapter
2008-06-30 07:51:24 Success SOAP: call failed
2008-06-30 07:51:24 Success SOAP: sending a delivery error ack ...
2008-06-30 07:51:24 Success SOAP: sent a delivery error ack
2008-06-30 07:51:24 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
2008-06-30 07:51:24 Error Exception caught by adapter framework: Read timed out
2008-06-30 07:51:24 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
2008-06-30 07:51:24 Success The asynchronous message was successfully scheduled to be delivered at Mon Jun 30 07:56:24 GMT 2008.
2008-06-30 07:51:24 Success The message status set to WAIT.
Thank you
Subbu

Dear Subramanyam,
Some message might be struck in the queue. Because of this reason furthur processing is not performed on time.
Please try to do like this:
Go to SXMB_MONI, or SXi_monitor, select QueueID in the row, which is showing green flag. In the next window belongs to queue select the queue and press unlock button on the panel.
This could possibly release the queue which is struck.
Best Regards
Praveen

Messages got stuck in Adapter engine

We are doing http to RFC sysnchronous scenario
Message got stuck in adapter engine.so we are getting 500 HTTP timeout error in Http client.
Please help us to find why messages got stuck in Adapter engine.
Below Adapter engine audit log message is pasted for your reference.
Audit Log message:
Time Stamp Status Description
26.09.2008 06:33:54 Success Message successfully received by messaging system. Profile: XI URL: http://devsap01:51000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
26.09.2008 06:33:54 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
26.09.2008 06:33:54 Success Message successfully put into the queue.
26.09.2008 06:33:54 Success The message was successfully retrieved from the request queue.
26.09.2008 06:33:54 Success The message status set to DLNG.
26.09.2008 06:33:54 Success Delivering to channel: RFC_out_Test
26.09.2008 06:33:54 Success MP: entering
26.09.2008 06:33:54 Success MP: processing local module localejbs/RfcAFBean
26.09.2008 06:33:54 Success RFC adapter received a synchronous message. Attempting to send sRFC for ZFTestRFC
26.09.2008 06:33:54 Success RFC adapter received a synchronous message. Attempting to send sRFC for J2EE_GUEST
ime Stamp Status Description
26.09.2008 06:56:15 Success MP: leaving
26.09.2008 06:56:15 Error Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.MessageExpiredException: Sync application request expired.. Setting message to status failed.
26.09.2008 06:56:15 Error The message status set to FAIL.
26.09.2008 06:56:15 Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.MessageExpiredException: Sync application request expired..
Kindly advise us on this issue.

Hi krish,
when i send a http request it got stuck in adapter engine with status "delivering" for some time....
We found that RFC got successfully executed in R/3 system but the synchronous message is not delivered to PI.since adapter engine message is having status "delivering"
after some time we got adapter engine message status as "cancelled with error"
Error is Message expired exception which you can see audit log message I have pasted in my previous post.
Meanwhile we also got HTTP timeout error in Http client.
Could you please tell me why it got stuck in Adapter engine with status "delivering" since RFC is executed successfully.
Why we are not getting synchronous message reply back to PI?

Messages are stucked in EOIO Backlog, please help me...

Dear Expert,
I am facing an issue the messages are stucked in EOIO Backlog, Those stucks are not flowing. why it is stucking in Engine status or backlog monitor.
and how it will reprocess those messages.
Regards,
Kiran Polani

Dear Friends,
Actually we developed an Idoc to soap synchronous using BPM in sap pi 7.0. suddenly required changed in field lever at sap r/3 side that's why we stopped communication channel for that interface.
But when we are stopped that interface it is stuked in EOIO Backlog and it is stayed in Holding state. Daily the message count is increasing. But here from sap they are triggering data for same idoc.
For that i have discussed with our team and deleted that interface in existing production enviroment.
now those signals are not stucked in Engine status EOIO Backlog. But my problem is how to delete or cancel existing not flown EOIO messages in Engine status.
Please find the screen shot for your reference.
Regards,
Kiran Polani

JMS Message Queue - stuck in

I am on SOA SUITE 11.1.17
I have a jms queue set up and am able to successfully send messages to it using the SOA JMS Adapter. I am able to succesfully listen to a queue using a JMS adapter in a different project.
However, here when I try to "listen" to the queue using a java program, the message is "received" in my java program and processed as it should be. The java program is running in a while loop, so it stays running.
On the queue, when the java program reads it, the message is moved to the "Messages Pending" column. When I kill the java program, the message is returned to the "Messages Current"
Would anyone have any ideas about this? We have an existing java based program isn't properly "closing" the message.
I tried:
1. placing msg.acknowledge() in the code, since the documentation states that messages that are in "Messages Pending" have been read, but not acknowledged or committed -- but this does nothing.
2. Setting the expiration on the message to 1, but that is a hack. I would rather fix the problem than use a hack.
Anyone have any ideas what is wrong?
Thank you,
Stuart
import java.io.IOException;
import java.io.InputStreamReader;
import javax.jms.Connection;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageConsumer;
import javax.jms.MessageListener;
import javax.jms.Session;
import javax.jms.TextMessage;
public class JMSListenAndRespond extends JMSQueueHandler implements MessageListener {
private Session jmsSession = null;
private MessageConsumer jmsMessageConsumer = null;
private Connection jmsConnection = null;
int counter = 1 ;
public static void main(String[] args) throws Exception {
    InputStreamReader commandBuffer = null;
    char command = '\0';
      // first listen for any messages
      JmsDataObject q = new JmsDataObject();
      q.setJmsCF("jms/TestConnectionFactory");
      q.setJmsQueue("jms/TestJMSQueue");
      q.setServerPwd("welcome1");
      q.setServerLogin("weblogic");
      q.setUrl("t3://localhost:7101");
      q.setJmsMsg("na -- we are listinging...");
    JMSListenAndRespond lis = new JMSListenAndRespond();
     lis.consumeMessage(q);
    System.out.println("(type q to exit at any time...)\n");
    try {
      // Now just loop, waiting for messages until user types 'q' to quit
      commandBuffer = new InputStreamReader(System.in);
    while (!(command == 'q')) {
       try {
          command = (char)commandBuffer.read();
          System.out.println("Command: "+command);
          lis.stopListening();
        } catch (IOException e) {
          System.err.println("I/O Exception: ");
          e.printStackTrace();
       } //while
    } finally {
            lis.stopListening();
      lis.stopListening();
   public void stopListening() {
    try {
      if (jmsMessageConsumer != null) {
        jmsMessageConsumer.close();
      if (jmsSession != null) {
        jmsSession.close();
      if (jmsConnection != null) {
        jmsConnection.close();
    } catch (JMSException e) {
      System.err.println("Couldn't properly close all resources.\n");
      e.printStackTrace();
private void prepareToConsumeMessage() {
    // create JMS connection, session, consumer and register listener - then start session
        try {
      // create connection
      jmsConnection = getJmsConnectionFactory().createConnection();
      // create session
      jmsSession =   jmsConnection.createSession(false, javax.jms.Session.AUTO_ACKNOWLEDGE);
      jmsMessageConsumer = jmsSession.createConsumer(getJmsDestination());
      // register a message listener (onMessage)
      jmsMessageConsumer.setMessageListener(this);
      // initiate connection - make sure to register your listener first or you might lose messages
      jmsConnection.start();
      System.out.println("\n...listening for message!\n");
    } catch (JMSException e) {
      System.err.println("Problem initializing JMS session");
      e.printStackTrace();
      System.exit(-1);
     * onMessage
     * The callback function invoked upon message reception
public void onMessage(Message msg) {
    try {
      String msgText;
      if (msg instanceof TextMessage) {
        msgText = ((TextMessage)msg).getText();
        // this method expects a CSV string with the following makeup:
        // firstName,lastName,gender,birthdate,address,city,zipcode,state,insurancePolicyId
        String messageId = msg.getJMSMessageID();
      // code to process goes here.....
      } else {
        // if message is not a TextMessage, attempt a conversion to string
        System.out.println("\n** NEW MESSAGE (" + msg.getClass().getName() +
                           "):\n" +
            msg.toString());
    } catch (JMSException e) {
      e.printStackTrace();
public void consumeMessage(JmsDataObject q ) {
    initializeJndiProperties(q);
    initializeJNDIandCF(q.getJmsQueue());
    prepareToConsumeMessage();
import java.util.Properties;
import javax.jms.Connection;
import javax.jms.ConnectionFactory;
import javax.jms.Destination;
import javax.naming.InitialContext;
import javax.naming.NamingException;
public abstract class JMSQueueHandler {
protected void initializeJNDIandCF(String destinationQueueName) {
    // initialize JNDI context and lookup connection factory and destination
    try {
      // Initialize JNDI context
      jndiContext = new InitialContext(jndiProperties);
    } catch (NamingException e) {
      e.printStackTrace();
    try {
      // lookup JMS connection factory in JNDI
      jmsConnectionFactory =
          (ConnectionFactory)jndiContext.lookup(jndiProperties.getProperty("factory.name"));
      // lookup JMS destination in JNDI
      jmsDestination = (Destination)jndiContext.lookup(destinationQueueName);
    } catch (NamingException e) {
      System.err.println("Problem during the JNDI lookup\n");
      e.printStackTrace();
      System.exit(-1);
public void initializeJndiProperties(JmsDataObject qdo ) {
    // set JNDI properties
    jndiProperties.put("java.naming.factory.initial","weblogic.jndi.WLInitialContextFactory");
    jndiProperties.put("java.naming.provider.url", qdo.getUrl() );
   // jndiProperties.put("java.naming.security.principal", NAMING_PRINCIPAL);
    jndiProperties.put("java.naming.security.principal", qdo.getServerLogin() ) ;
    // jndiProperties.put("java.naming.security.credentials", NAMING_CREDENTIAL);
    jndiProperties.put("java.naming.security.credentials", qdo.getServerPwd() );
    //jndiProperties.put("factory.name", JMS_CONNECTION_FACTORY);
    jndiProperties.put("factory.name", qdo.getJmsCF() );
//protected static final String NAMING_PROVIDER_URL = "t3://localhost:7101";
//protected static final String NAMING_PRINCIPAL = "weblogic";
// protected static final String NAMING_CREDENTIAL = "welcome1";
// protected static final String JMS_CONNECTION_FACTORY = "jms/patientsJmsCF";
// protected static final String JMS_CONNECTION_FACTORY = "jms/TestConnectionFactory";
ConnectionFactory jmsConnectionFactory = null;
Destination jmsDestination = null;
InitialContext jndiContext = null;
Properties jndiProperties = new Properties();
public void setJmsConnectionFactory(ConnectionFactory jmsConnectionFactory) {
    this.jmsConnectionFactory = jmsConnectionFactory;
public ConnectionFactory getJmsConnectionFactory() {
    return jmsConnectionFactory;
public void setJmsDestination(Destination jmsDestination) {
    this.jmsDestination = jmsDestination;
public Destination getJmsDestination() {
    return jmsDestination;

Thanks for the reply. There are no errors what so ever regarding MDB issues. Not in the weblogic / console logging, nor in the logging of the component itself.
The MDB itself is setup to have 16 concurrent beans per component deployment. The component is clustered over 4 server instances. So there are quite some concurrent MDBs running. However since the messages get stuck for weeks eventhough the component only has bursts of messages to process, one would think that the the stuck messages would be processed whenever the component has some spare time (which it has a lot between the bursts).
Therefor i doubt it has anything to do with too little MDBs running. But frankly I have no idea what's wrong.

Using Pop3. See 4 messages on webmail server. Run Th, says downloading 1 of 5 messages, never completes. One message is stuck in the pipe. How to clear?

I'm using Pop3. I can see 4 messages on webmail.frontier.com server. I run Thunderbird, it says "Downloading 1 of 5 messages", but the green bar just sits there and never completes any of the downloads. One message is stuck in the pipeline somewhere. This has gone on for many days now. I have my wife use web mail until I can clear her local Thunderbird. How can I clear the stuck message in the download?

Try with Thunderbird new profile
*http://www-archive.mozilla.org/support/thunderbird/profile#new
If its works fine, transfer your data's from old profile to new profile
*http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Thunderbird

While using gmail a message appears asking to Increase Database Size? No message is stuck on my screen. Why?

While using gmail on my ipad a message appears "Increase Database Size?". After pressing cancel the message is stuck on my screen.
How do I get rid of the message so I can access my mail?

Here's a fix just in case other users have this problem and still sticks around:
In your passbook app- choose the Belly "Card." Tap the "i" icon on the bottom right corner and turn off the notification sliders. Passbook seems to go over the general notifications and just makes it's own rules in this regard.

While updating ipod touch 4 i got an error message now stuck with apple symbol and empty bar. can i restart ipod?

while updating ipod touch 4 i got an error message now stuck with apple symbol and empty bar. can i restart ipod?

- What was the error message?
- Try closing iTunes and then disconnect the iPod from the computer. Then reconnect the iPod. If the iPod shows in iTunes then you can try again. However, You should try to resolve the error message first.
- If iTunes does not see the iPod try reetting the iPod:
Reset iPod touch: Press and hold the On/Off Sleep/Wake button and the Home
button at the same time for at least ten seconds, until the Apple logo appears.
- I recommend that you come back with the what the error message said and the condition of the iPod and if it is visible in iTunes.

Pictures sent to my iphone 6 via text messaging are stuck in downloading phase

Pictures that are being sent to me via text messaging are stuck in "downloading" phase. I can not receive any pictures on my new iphone6. Is anyone else experencing this?

Found a great post that had a bunch of possible solutions (over at https://uk.answers.yahoo.com/question/index?qid=20131217195803AAOe6WV )
Lucky for me the first one worked--went into settings->messages and turned iMessage off, waited a few seconds, turned it back on. Images came through just fine after that. We'll see if it lasts.

From time to time, my outgoing mail messages get stuck in the "outbox". I'm having trouble resolving the problem.

From time to time, my outgoing mail messages get stuck in the "outbox". I'm having trouble resolving the problem.

I use Comcast. My computer (Mac Air) also uses my iCloud and Me accounts. The message I get back says they are all offline.

Messages banner stuck

Similar Messages

Maybe you are looking for