PI 7.0 SP15 alerts JMS Duplicate message error

Hi all,
We have a scenario where in we receive BAPI calls to R/3 from web through MQ and XI.
WEB -> MQ->XI->R/3 (Request / Response send back similarly)
We have modular configuration in the channel.
All these BAPI messages are queries needed to build an order for example product information / customer information etc.
We have PI 7.0 SP15
Sometimes we receive the error ' Duplicate JMS message with JMS ID##### detected.Duplicate will be ignored' in the sender JMS channel.Because of this error XI is not able to process subsequent messages and the channel keeps on throwing the same error.We need to clear the queue and then restart the channel to make it work.
Can any one please tell me what is the reason for occurence of this error..?
Is this ID generated in JMS or in XI?If so how this could be handled without clearing the queue's..?
When we analyzed the messages in the queue we found out same xml messages been send twice which i would imagine the query been send twice(which is a possiblity from the web) would that have caused this JMS duplcate message error??!!
Also because of this error XI is throwing multiple alert messages at the rate of 3 per second which is causing the huge performance hit as the alert inbox gets filled up..We did put the suppress multiple alert check..but before somebody reacts to these alerts there are numerous of them created..any suggestions on this is much appreciated..
Thanks for your help in advance
Larry

Larry,
Is that alert rule is generic or interface specific? If it is generic then please make it interface specific.
Thanks,
Sunil

Similar Messages

Alert for Inbound message errors

Hi
We are updating the inventory using ProductActivityNotification inbound XML message from SAP PI. But when it fails due to some error(e.g Shipping party invalid) , we need to raise an alert or send mail, Could you please let us know how to configure it.
Regards
Anandan

Hi Anandan,
You can make use of the below link to configure your
scenario
http://help.sap.com/saphelp_scm70/helpdata/EN/5b/5d1741b393f26fe10000000a1550b0/frameset.htm
Regards
R. Senthil Mareeswaran.

Duplicate Message exception in sender JMS comm channel

Hi,
Can any one please tell me what is stored in MSG_ID1 and MSG_ID2 in table XI_AF_SVC_ID_MAP
I could only find the schema of XI_AF_SVC_ID_MAP table in SDN which is as follows,
MSG_ID1 (varchar),
MSG_ID2 (varchar),
PERSIST_UNTIL (timestamp).
We have an interface in where MQ daily sends 2 files to PI but sometimes one msg is getting discarded by sender JMS adapter giving warning -
A duplicate message was received, it was received earlier and processed with XI Message ID - "xyz". It will be ignored and discarded from the JMS queue.
Also I found that setting option Time Period for Duplicate Check for EO(IO) (secs) to 0 does not always work.
We are getting this problem after upgrading PI from 3.0 to 7.1.
So if any one has solution to this problem please help me.
Thanks & Regards,
Shweta

Hi Shweta
Usually this kind of issue happens when the msg ID in the MQ message header is not unique.
Ask the MQ team to ensure that MQ msg ID is always unique.
Regards,
Giuseppe

Distributed topic - JMS adapter consuming duplicate messages

We have distributed topic thats consumed by a composite (JMSadpter in mediator).
We see for every one message sent the composite consumes the message twice. (With forwarding policy set to partitioned)
Is this an expected behavior? and how do we make the consumer (JMS adapter) consume only once per message
Thanks
Vijay

From the documentation (provided here: http://download.oracle.com/docs/cd/E21764_01/integration.1111/e10231/adptr_jms.htm)
The JMS API specifies three types of acknowledgments that can be sent by the JMS publisher:
- DUPS_OK_ACKNOWLEDGE, for consumers that are not concerned about duplicate messages
- AUTO_ACKNOWLEDGE, in which the session automatically acknowledges the receipt of a message
- CLIENT_ACKNOWLEDGE, in which the client acknowledges the message by calling the message's acknowledge method
Could you check in the weblogic-ra.xml what acknowledge mode has been configured:
<property>
<name>AcknowledgeMode</name>
<value>AUTO_ACKNOWLEDGE</value>
</property>
...Note that when DUPS_OK_ACKNOWLEDGE is used it can happen that a message is consumed more than once.
Are you also sure that the message is not produced twice?
Seminar on Cloud Computing - http://middlewaremagic.com/weblogic/?p=7387

Duplicate message and Duplicate key error in Moni and RWB

Hi,
I am getting very frequent issues of Duplicate messages in production system moni and RWB.
Moni error: (IDOC to JMS) Errors are coming in call adapter step:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not insert message 005056aa-730e-1ed4-a6c9-a01ee2b86cb3(INBOUND) into duplicate check table. Reason: com.sap.sql.exception.OpenSQLException: Connection reset by peer: socket write error OpenSQLExceptionCategories: [RECOVERABLE]
RWB error: (File toIdoc) Errors are coming in sender channel.
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id a6d559cf-b00c-11e4-b786-00000daf354a(OUTBOUND) already exists in duplicate check table: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: Violation of PRIMARY KEY constraint 'PK__BC_MSG_D__99C1915D3DE9247A'. Cannot insert duplicate key in object 'SAPPGXDB.BC_MSG_DUP_CHECK'. The duplicate key value is (a6d559cf-b00c-11e4-b786-00000daf354a, OUTBOUND). OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION
Moni errors are manually reprocessed and RWB are automatic.
Can you please let me know if there is any solution available for these issues?
Thanks
Navneet.

I'm getting the same issue at my current client:-
Putting message into send queue failed, due to: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id e1d4a31b-f0cc-11e4-c7fb-0000029706f7(OUTBOUND) already exists in duplicate check table: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00188646) violated OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]
I've tried restarting the SOAP channel but this has not resolved the problem.
Just read on another thread that this may be a misleading error message (see last post on the link). It may be an idea to increase the trace level temporarily and look for any other issues that may be the cause.
So far I've not seen any post that describes the error on the SOAP channel - only seeing it for JDBC & File. However it seems to be a common problem across a number of sender channels.

Oracle AQ JMS Map messages Permissions

Hello,
I am trying to use a JMS Map message in a trigger but cannot get it to work. I have created i_aquser and given the following
privileges (after looking at the forums) however when I tried to compile my trigger, I get the following error
message := sys.aq$_jms_map_message.construct;
ERROR at line 4:
ORA-06550: line 4, column 40:
PLS-00302: component 'CONSTRUCT' must be declared
ORA-06550: line 4, column 5:
PL/SQL: Statement ignored
-- PLSQL
GRANT CONNECT TO i_aquser;
GRANT DBA TO i_aquser;
GRANT AQ_ADMINISTRATOR_ROLE TO i_aquser;
GRANT EXECUTE ON SYS.DBMS_AQADM TO i_aquser;
GRANT EXECUTE ON SYS.DBMS_AQ TO i_aquser;
GRANT EXECUTE ON SYS.DBMS_AQIN TO i_aquser;
GRANT EXECUTE ON SYS.DBMS_AQJMS TO i_aquser;
GRANT EXECUTE ON SYS.DBMS_AQJMS_INTERNAL TO i_aquser;
GRANT EXECUTE ON SYS.AQ$_JMS_HEADER TO i_aquser;
GRANT EXECUTE ON SYS.SYS.AQ$_JMS_MAP_MESSAGE TO i_aquser;
--Connect i_aquser/i_aquser
-- Trigger code Removed
DECLARE
message sys.aq$_jms_map_message;
BEGIN
message := sys.aq$_jms_map_message.construct;
-- Remaining stuff
COMMIT;
END;
What other permissions are required? Any help / suggestion is welcome.
Thanks and Regards
Amit
PS: Apologies for duplicate posting of this thread in two discussion forums

Is this against a 9i database or 10g database?

Duplicate Messages created on target with Multimapping(No BPM)

Hi
I am working on PI7.1 .
My sceniro
IDOC to JMS using message split
Receiving IDOC with Header and Items, PI splitting IDOC and sending to Multiple JMS queues, Header segment data to header queue, Item segment data to Item queue
PI Successfully Posting data to Queues, but duplicate messages creating on target sys(One IDOC with one header and one item date, PI sending 2 header messages , two item messages to target sys) .
I did following steps
ESR
1. Created two target messages
2. Created Two target inbound interfaces
3. Created Message mapping using with multiple target messages, changed signature occurrence to 0 : unbounded , and mapped to source node to target nodes
4. Created operation mapping with one source to two target interfaces
EB
1. Created one business components and assigned one sender and two receiver service interfaces
2. Created Two receiver communication channel
3. Created One receiver determination
4. Created One interface determination , added two inbound interfaces with one operation mapping (Multiplicity is blank )
5. Created two receiver agreement
Please help .

Thanks Gouri ,
My IDOC structure (Source Message Type)
HEADER_SEG Node (0:9999) -
> MT_HEADER ( 0:unbounded) (this one of target message type)
                                                                HEADER_FLDS (Element - Main hierarchy)
         FLDS----
> FLDS
ITEM_SEG Node (0:9999) -
>MT_ITEM(0:unbounded ) (this is another message type)
                                                                ITEM_FLDS (Element - Main hierarchy)
         FLDS----
> FLDS
I tried with the below mappings
                HEADER_SEG Node -
>MT_HEADER
                HEADER_SEG Node -
> HEADER_FLDS (element )
                ITEM_SEG Node -
>MT_HEADER
                ITEM_SEG Node -
> ITEM_FLDS (element )
2. method
                HEADER_SEG Node -
>MT_HEADER
                                                       HEADER_FLDS (element )(not mapped)
                ITEM_SEG Node -
>MT_HEADER
                ITEM_SEG Node   ITEM_FLDS (element )(not mapped)

Duplicate messages/database inserts despite XA

I have a simple test application which reads a single message at a time from WebSphere MQ, calls a tux service to insert into a database and writes an output MQ message (again via a tux service). The app is duplicating database inserts and MQ puts despite it being configured to use XA.
I am running with AUTOTRAN=Y and can see the XA transactions in the trace.
If I cause a DB failure (oracle 11g -> dataguard with fast start failover) , the servers exit and are re-started (this appeared to be the best way of cleaning up) however I get duplicates, despite the XA trace implying the global transaction was rolled back:
124530.tuxtestmachine!s_mq.1016002.1.0: gtrid x0 x4aec30de x8d3: ...MQ Read->GPU POC TEST MSG18313<0> <<<<<<MQGET here
124530.tuxtestmachine!s_mq.1016002.1.0: gtrid x0 x4aec30de x8d3: ...................calling <getu>
124530.tuxtestmachine!server.864336.1.0: gtrid x0 x4aec30de x8d3: getu started
124530.tuxtestmachine!server.864336.1.0: gtrid x0 x4aec30de x8d3: ..Input<GPU POC TEST MSG18313>
124530.tuxtestmachine!server.864336.1.0: gtrid x0 x4aec30de x8d3: Conver string
124530.tuxtestmachine!server.864336.1.0: gtrid x0 x4aec30de x8d3: .............................getu<GPU POC TEST MSG18313->GPU POC TEST MSG18313>
124530.tuxtestmachine!server.864336.1.0: gtrid x0 x4aec30de x8d3: getu complete
124530.tuxtestmachine!s_mq.1016002.1.0: gtrid x0 x4aec30de x8d3: ..returned from getu
124530.tuxtestmachine!s_mq.1016002.1.0: gtrid x0 x4aec30de x8d3: ..calling mqwrite
124530.tuxtestmachine!s_mq.1016002.1.0: gtrid x0 x4aec30de x8d3: ...................calling <mqwrite>
124530.tuxtestmachine!s_mqwrite.651446.1.0: gtrid x0 x4aec30de x8d3: TRACE:at: { tpservice({"writemq", 0x10, 0x20077930, 22, 0, -2147483648, {0, -2, -1}})
124530.tuxtestmachine!s_mqwrite.651446.1.0: gtrid x0 x4aec30de x8d3: ...in mqwrite
124530.tuxtestmachine!s_mqwrite.651446.1.0: gtrid x0 x4aec30de x8d3: +++++Writing to MQ<GPU POC TEST MSG18313><GPU POC TEST MSG18313> <<<This is the MQPUT
124530.tuxtestmachine!s_mqwrite.651446.1.0: gtrid x0 x4aec30de x8d3: TRACE:at: { tpreturn(2, 0, 0x20077930, 0, 0x0)
124530.tuxtestmachine!s_mq.1016002.1.0: gtrid x0 x4aec30de x8d3: ..insert to database
124530.tuxtestmachine!s_mq.1016002.1.0: gtrid x0 x4aec30de x8d3: ..............Calling dbinsert with <GPU POC TEST MSG18313><21>
124530.tuxtestmachine!s_mq.1016002.1.0: gtrid x0 x4aec30de x8d3: ...................calling <db_insert>
124530.tuxtestmachine!s_ora.897234.1.0: gtrid x0 x4aec30de x8d3: TRACE:xa: { /ò!(0x20019b74, 0, 0x0)
124530.tuxtestmachine!s_ora.897234.1.0: gtrid x0 x4aec30de x8d3: TRACE:xa: } /ò! = -7
124530.tuxtestmachine!s_ora.897234.1.0: gtrid x0 x4aec30de x8d3: TRACE:xa: { xa_open(0x2002035c, 0, 0x0)
124530.tuxtestmachine!s_ora.897234.1.0: gtrid x0 x4aec30de x8d3: TRACE:xa: } xa_open = 0
124530.tuxtestmachine!s_ora.897234.1.0: gtrid x0 x4aec30de x8d3: TRACE:xa: { xa_start(0x20019b74, 0, 0x0)
124530.tuxtestmachine!s_ora.897234.1.0: gtrid x0 x4aec30de x8d3: TRACE:xa: } xa_start = 0
124530.tuxtestmachine!s_ora.897234.1.0: gtrid x0 x4aec30de x8d3: ...Calling dbinsert<GPU POC TEST MSG18313>
124530.tuxtestmachine!s_ora.897234.1.0: gtrid x0 x4aec30de x8d3: Database failure : ORA-25408: can not safely replay call <<<<As a result of the DB failure
124640.tuxtestmachine!MQXA.778310.1.0: gtrid x0 x4aec30de x8d3: TRACE:xa: { xa_rollback(0x200196b4, 0, 0x0)
124640.tuxtestmachine!TMS_ORA.1085652.1.0: gtrid x0 x4aec30de x8d3: TRACE:xa: { xa_rollback(0x2001a454, 0, 0x0)
124640.tuxtestmachine!s_mq.1016002.1.0: gtrid x0 x4aec30de x8d3: !!!Error calling<db_insert><13>
124640.tuxtestmachine!MQXA.778310.1.0: gtrid x0 x4aec30de x8d3: TRACE:xa: } xa_rollback = 0 <<<< This looks to me like a succesful rollback by the TMS
124640.tuxtestmachine!TMS_ORA.1085652.1.0: gtrid x0 x4aec30de x8d3: TRACE:xa: } xa_rollback = -7 <<Resource manage unavailable, DB is still unavailable here
124640.tuxtestmachine!TMS_ORA.1085652.1.0: gtrid x0 x4aec30de x8d3: TRACE:xa: { xa_open(0x20020c3c, 0, 0)
124640.tuxtestmachine!TMS_ORA.1085652.1.0: gtrid x0 x4aec30de x8d3: TRACE:xa: } xa_open = 0
124640.tuxtestmachine!TMS_ORA.1085652.1.0: gtrid x0 x4aec30de x8d3: TRACE:xa: { xa_rollback(0x2001a454, 0, 0x0)
124640.tuxtestmachine!TMS_ORA.1085652.1.0: gtrid x0 x4aec30de x8d3: TRACE:xa: } xa_rollback = 0
$
Anyone with any ideas as to where I go from here ? Your time is much appreciated.
Thanks.

Hi Dan,
Thanks for the question.
Currently the Messaging Pattern implementation does not use/implement JTA/XA or Coherence transactions. It's much like regular JMS in that it provides it's own transaction framework, that neither uses JTA or XA. While the JMS specification provides an XA API, the implementation of this is optional, as are Queues or Topics.
The original goal of the Messaging Pattern implementation was to demonstrate that JMS-like messaging is possible with Coherence. When we looked at constructing the Messaging example, most people we talked to said they didn't want JMS and especially they didn't want transactions. They simply wanted a simple messaging implementation. So it's initial goal was to demonstrate a high-scalable messaging layer. Unfortunately that meant no "real" transaction support, especially in terms of things like XA and/or JTA.
That said given the way that the pattern is currently implemented one could easily implement an XA resource so that it could be used as a last resource. That's probably the quickest way to get what you would like at the moment.
Of course I'm certainly interested in implementing XA support, but we know that is non-trivial. It's not currently on our roadmap for the pattern, but it could be. Our next release will provide persistent messaging, but we could investigate XA after that.
-- Brian
Brian Oliver | Architect | Oracle Coherence Engineering
Oracle Fusion Middleware

Duplicate Messages sent

Hi there,
I am trying to figure out why I receive duplicate messages from my message queue. We have our Entity Beans send out messages when their state changes. When the beans are deployed first, and their state changes, only a single message is sent out, but if the state of the bean is changed again, then multiple messages are sent out. I guess the message queue does not get flushed after the delivery of the messages. Can any one shed some light on this issue?
Here is my client code, which is gui.
try {
TopicConnectionFactory factory = serviceLocator.getTopicConnectionFactory("jms/TopicConnectionFactory");
Topic topic = serviceLocator.getTopic("jms/jtTopic");
TopicConnection connect = factory.createTopicConnection();
TopicSession session = connect.createTopicSession(false, Session.CLIENT_ACKNOWLEDGE);
TopicSubscriber subscriber = session.createSubscriber(topic);
subscriber.setMessageListener(this);
System.out.println("Listening for messages on topic/rhythm-employee...");
// calls onMessage();
connect.start();
} catch (NamingException ne) {
ne.printStackTrace();
} catch (JMSException jme) {
jme.printStackTrace();
} catch (Exception e) {
e.printStackTrace();
And here is the onMessage code:
public synchronized void onMessage(Message message) {
try {
ObjectMessage oMsg = (ObjectMessage) message;
String jobName = oMsg.getStringProperty("jobName");
String scnName = oMsg.getStringProperty("scnName");
if (oMsg.getStringProperty("actionType").equals("scene")) {
SceneTO sceneTO = (SceneTO) oMsg.getObject();
System.out.println("Scene Name: " + sceneTO.getSceneName());
final Object obj = oMsg.getObject();
Hashtable hash;
if (obj instanceof SceneTO) {
JTBase.jobLock.lock();
hash = (Hashtable) JTBase.Jobs.get(jobName);
if (!hash.containsKey(scnName)) {
hash.put(scnName,new Hashtable());
hash = (Hashtable) hash.get(scnName);
if (!hash.containsKey("Scene Info")) {
hash.put("Scene Info",new Hashtable());
hash = (Hashtable) hash.get("Scene Info");
if (hash.containsKey("data")) {
hash.remove("data");
hash.put("data",obj);
JTBase.jobLock.releaseLock();
// Refresh if needed
if(JTBase.jobName.equals(jobName) && JTBase.scnName.equals(scnName)) {
SwingUtilities.invokeLater(new Runnable() {
public void run() {
updateHeader(obj);
if (JTBase.tabName.equals("Scene Info")) {
updateMain("Refresh");
oMsg.clearBody();
message.acknowledge();
} catch(JMSException jmsE) {
JTBase.jobLock.releaseLock();
jmsE.printStackTrace();
Thanks in advance
-r

Hi,
<rhajikhani1>
When the beans are deployed first, and their state changes, only a single message is sent out, but if the state of the bean is changed again, then multiple messages are sent out
</rhajikhani1>
Does this not sound like a problem at the sending-side (your Entity Bean) rather than the receiving-side (the GUI code you have below).
You say that when the Entity Bean is deployed it sends one message which (I assume) is handled OK by the GUI code. Then, when the Entitiy Bean changes it starts sending multiple messages, isn't this a problem with the Entity Bean message sending code?
Anyway, if you are sure it is the receiver side I suggest placing a try catch (Throwable) around the code in the onMessage and printing the stack trace. At the moment you only catch JMSExceptions. The reason I say this is that maybe the message.acknowledge line is not being called which has resulted in a redelivery for some reason.
I can see several points in your code where a NullPointerException could be raised which would result in the message not being acknowledged. For example if the message does not contain the property "scnName" then a NullPointerException will be thrown by the call to hash.containsKey(scnName). If you were to catch Throwables then you can tell if there is a problem with the onMessage method (or the messages it is receiving).
Hope this helps,
Tom Jenkinson
Arjuna Technologies Limited

Duplicate messages in sender mail adapter

Hi,
We are using the sender mail adapter to retrieve messages from an IMAP mail server. Messages are being picked up correctly, but when we have large messages (with e.g. PDF attachments) things go wrong.
The time it takes to retrieve the mail message is longer than the poll time. In this case the adapter logs in again in the mail server to retrieve the first new message from the inbox. However the first adapter threat is already retrieving that message. This results in a duplicate message in XI. (messages are set to be deleted when read).
We have tried all kind of settings in the adapter but without any results. The adapter works fine with very small messages.
Does anyone recognize this problem?
PS. please do not post links to sap help or the mail adapter FAQ. Useful answers will be rewarded.
Thanks,
Christiaan Schaake

Hi Christiaan !
I understand your problem. Could you set your IMAP account to avoid multiple simultaneous sessions?? maybe if there is only one session allowed per user or per time, then parallel XI threads will not be able to start downloading the messages.
If you cannot use a longer poll interval, then you could develop an adapter module for the Mail sender adapter that could be used to verify if the current mail is just being downloaded by other thread. This adapter module could check the unique mail data (date/time + subject + etc.) against a local table.
Regards,
Matias.
PD: please award points if helpful.
Message was edited by:
Matias Denker

TS2755 I have 2 phones on my apple id acct. And when I text message that person I am getting a duplicate message to myself. How do I stop this from happening

I have 2 phones attached to my apple ID account and when I text message that person, I am getting a duplicate message sent back to me. How do I stop this from happening?

Make 3 different iCloud accounts and use ONLY for iMessage. That will permanently fix your issue.

Need suggestion on implementing JMS message error recovery

Hi,
Our application has a JMS topic where we publish application events. Now, there can be scenarios where the consumers cannot process the message due to some infrastructure issues and would error out. We need a way so that those messages can be reprocessed again later. we are thinking of the following design for JMS message error recovery
1. Use a persistent TOPIC (this would ensure guaranteed delivery)
2. Configure a error destination on JMS topic e.g a jms queue
3. Have an error handling MDB listening to the Error destination. An error handling MDB would dequeue the errored messages from error destination and persist it to a Data base "error" table..
4. Provide a mechanism to republish those messages to topic (e.g a scheduler or admin ui or a command line utility) .. The messages would deleted from database "error" table and published to topic again....
A. Are there any issues with the above design which we need to handle?
B. Are there any additional steps required in a Cluster environment with a distributed topic and distribute error destination? (our error mdb will have one-copy-per-application setting)
B. From a performance angle, Is it OK to use persistent TOPIC ? Or will it better to persist the message to the db table and then publish it as a non persistent message ... ? (But i guess the performance should be more or less the same in both of these approaches)
C. Are there any other recommended design patterns for error recovery of JMS messages
Please advise.
Regards,
Arif

Thanks Tom !
We may not be able to go with the approach of delaying/pausing redelivery of the messsage because
1. Pausing entire MDB approach: Our MDB application consumes messages generated by different producers and our MDB needs to continue processing the messages even if messages corresponding to one producer is erroring out
2. Redelivery delay : This would only delay the retry of an errored message. But there would still be a problem if the message fails during all retries (i.e redelivery limit count). We don't want to lose this message. In our case, It is possible that a particular message cannot be processed due to unavailability of a third party system for hours or may be a day.
Basically, i am looking on approaches for a robust and performant error recovery/retry framework for our application (refer details in my first post on this thread) while fully making use of all features provided by middleware (WLS). Please advise.
Regards,
Arif

How can I Delete a MobileMe Email Account and Kill Duplicate Messages?

When I select "All Inboxes" on my iPhone 4s, I see duplicates of each and every message I receive. Furthermore, the duplicate can't be deleted and I get an error message informing so! I suspect this phenomenon is occurring because I have both an iCloud and a MobileMe account. I want to cancel the MobileMe one.
Here's the deal:
My iPhone 4s lists three email accounts, including a "MobileMe" one that I want to delete because I believe it is delivering duplicate messages. However, I can't seem to figure out how to delete the MobileMe's email account or, for that matter, MobileMe itself. Apple support screens refer to cancelling a MobileMe account but are not clear on how to actually do it.
1. On the iPhone 4s, I click on the "Mail" icon at the bottom of the screen
2. On a screen under the heading "Mailboxes," under "Inboxes," there are two that read exactly the same (I think one is iCloud and the other MobileMe).
3. On the same screen, under "Accounts," I see an iCloud account logo, a Bellsouth/Yahoo account logo and a MobileMe account logo.
4. I want to keep the iCloud and Bellsouth/Yahoo accounts but delete the MobileMe one but I can find no way on this screen or any other iPhone 4s screen to do so. Nor do I see any path to do so in iTunes. And the MobileMe account doesn't even show up in the Apple email app on the laptop to which I sync my iPhone.
If I go to www.me.com and log into my MobileMe account, there is no apparent way to disable, delete or otherwise cancel it. Why?
I am convinced that the simultaneous presence of both iCloud and MobileMe accounts is responsible for the double email messages when I select to view "All inboxes" on my iPhone. (A workaround is to simply select just one of the accounts, say, the iCloud one. Then I see only one copy of each message. That's OK but surely there is some way to kill off this redundant MobileMe account AND the duplicate messages, yes???

First, thanks for the reply. And, I believe you are exactly right that the names are the same. However, when I go (on my iPhone) as you suggest to "Settings," "Mail, Contacts, Calendars," only two accounts are showing; my Mac account and my Bellsouth one. If I select either, I get an option to delete but the duplicate "MobileMe" account does not appear. It only shows up, as described above, if I:
1. On the iPhone 4s, I click on the "Mail" icon at the bottom of the screen
2. On a screen under the heading "Mailboxes," under "Inboxes," there are two that read exactly the same (I think one is iCloud and the other MobileMe).
3. On the same screen, under "Accounts," I see an iCloud account logo, a Bellsouth/Yahoo account logo and a MobileMe account logo.
It's nutso, I admit, but true. Any other suggestions would be most welcome.

When using Message Filters on an IMAP account I often get duplicate messages in my local folder where important messages are put. How can I stop this?

Since switching to IMAP and using message filters, I often get duplicate messages in my local folders. I think this is a bug.
That is my guess as to what is happening.
When the IMAP part starts syncing with the server to fill in the inbox, the message filter system starts working before it is done syncing. I appears that the filters runs too quickly because as the filter moves a msg to a local folder, the sync thread think it need to download it again from the server. If the sync with the remote server takes a long time, I could end up with 5 or more copies of the exact same email.
This has always happened for years now but I figured someone would have noticed it and fix it by now. Now I am wondering it it has something to do with my filters or my settings.
Has anyone run into this before?

Toys,
I was just doing a search to see if anyone else was feeling this way! I am also at a university and I don't really like see thousands of unread messages in mail. (Fortunately, with Leopard you can select the dock icon to show only the messages in your inbox but I still don't like having the public folder in there).
Please let me know if you find out anything and I will do the same for you. If I have time later I am going to run by our IT office later and ask them.

How can I prevent Mail from applying actions (moving/copying/flagging/marking read) to duplicate messages?

I use Mail to check multiple accounts. When I receive the same e-mail in multiple accounts, actions applied to an e-mail in one account often (though not always) affect duplicate messages in other accounts.
Example 1
Someone sends an e-mail to both me and my wife. Mail is set up to check both accounts. If I open the message in my Inbox, it marks it as read in my Inbox as well as in my wife's Inbox.
Example 2
For historical reasons, I have chosen to have all my e-mail forwarded (by the server) to a second account, to be used essentially as an un-touched archive of all incoming mail. If I manually move a message from my main account Inbox to another mailbox, the destination mailbox will end up with 2 copies, one from my main account Inbox and the other from the "un-touched archive" Inbox (which has obviously now been altered unintentionally).
Does anyone know of a way to prevent this behavior. I can manage my own duplicates. I don't want Mail to do it for me.
(Btw, I already have the "AlwaysShowDuplicates" option set using "defaults delete com.apple.mail AlwaysShowDuplicates")

There are certainly many ways of organizing things so that Mail never has to deal with multiple accounts and duplicate messages (separate user accounts, separate computers, separate mail clients, etc., etc). That's just not what I was asking. I'd like to know how to fix Mail's behavior when it does have to deal with multiple accounts and duplicate messages.
I was hoping there might be another hidden preference or something (and by the way my original post should have said "defaults write com.apple.mail AlwaysShowDuplicates -bool true", instead of the "defaults delete ...")

PI 7.0 SP15 alerts JMS Duplicate message error

Similar Messages

Maybe you are looking for