Ignore message

Hi,
I am picking up files from R/3. In the receiver determination, I am selecting the service based on a cell ID. If the cell ID is invalid, I get a receiver not found error.
Is there a way to delete and/or ignore or cancel the messages that aren't defined to go to a service? There is a batch job that attempts to reprocess failed messages. If I don't manually cancel the messages, they retry until max attempts is reached.
Your ideas and suggestions are appreciated.
Thanks,
Lisa

hi Lisa,
Two ways:
1. you can create a dummy receiver...
then send all wrong messages to this one
2. you can have a look at sap note: 728151
which delas with similar to your case
Regards,
michal

Similar Messages

Messages linked to perf degradation : 'ignoring message from a previous generation' and 'got heartbeat...but did not find reference'

Hi,
We are facing a problem which implies bad response time from the WL server.
Our configuration is : Sun E4500, Solaris2.6, Oracle 7.3.4, WL oci driver,
no perf pack, Javasoft 1.1.7B_05 vm on server side and IBM 1.1.7B on client
side (W98 clients).
When multiple users connect to the server (let's say from 15 simultaneous
connections) and work on our application, after few mins, the server process
logs and outputs tons of messages like :
Mon Nov 15 16:12:26 GMT 1999:<E> <RJVM> Ignoring message from a previous
generation: JVMMessage from 8803290290807054313C146.100.8.34
to -6807808847876022584C146.100.100.84 with CMD_ONE_WAY, prtNum=5, ack=30,
seqNum=3151
and
Got heartbeat for -6807808847876022584/-1838914476/0/9209 but did not find
reference
Got heartbeat for -6807808847876022584/-1838914476/0/8979 but did not find
reference
This is strangely related to a real degradation of the WL server response
times and sometimes to 'PeerGoneExceptions' thrown to the client (while the
server is still alive...).
This happens either for connections on the LAN or on the WAN (frame relay
network) so I don't think this is network related. As of now, weblogic
support told us not to care about it but after analysing the messages, there
seems to be a real problem here :
What seems to happen is :
- The server considers that the client is dead so it's closing the
connection. Eventually, the DGC cleans up references that were held by this
client.
- The server recieves a query from the 'still alive client' and re-opens the
connection with the SAME id.
- If there is a heartbeat from a DGC cleaned up object, the DGC informs that
it 'did not find reference'.
- It ignores the messages from the previously closed connection and tries to
re-establish everything.
We desperately need some feed back on what is causing the server to close
the connection while the client is still alive. I've seen somewhere in this
list that there are some internal parameters in the WL server
('weblogic.system.idlePeriodUntilTimeout' and
'weblogic.system.periodLength') which indicates the WL server when to
consider a client as 'dead'. This is defaulted to 1 min for the first and to
4 for the second which implies that there must be at least 4 minutes during
which the client doesn't emmit 'heartbeats' for the server to know it is
alive.
few remarks :
1/ the client is not swapping nor GCing too long so the client vm is
available to emmit these heartbeats.
2/ we couldn't reproduce it in our test environement except when making the
client swap for minutes which is not the case in the production env.
3/ this really seems related to multiple clients connected simultaneously to
the server.
Thanks a lot for your help.
Vincent Vandenschrick
Obbisoft.

Michael,
We are running WL Server 404. This is the version we were advised to use for
production. We are not using the performance pack because when we turn it
on, the server behaves correctly for the first 15 mins of use and then,
stops accepting new connections and even closes the existing ones. This
behaviour seems to happen only when the server is used by multiple
concurrent users. So the only "stable" configuration we found to run the
server is Javasoft 1.1.7B (Sunsoft's jdk 1.1.7 produces a core dump after a
few minutes use) + perf pack disabled.
We have support calls open for most of these issues but I thought I would
ask the group to benefit from its experience.
Thanks for your help.
Vincent.
Obbisoft.
Michael Girdley a écrit dans le message
<[email protected]>...
Vincent,
What version of the Server are you running? Why are you not using the
performance pack?
Thanks,
Michael Girdley
BEA Product Manager
Vincent Vandenschrick <[email protected]> wrote in message
news:[email protected]...
Hi,
We are facing a problem which implies bad response time from the WLserver.
Our configuration is : Sun E4500, Solaris2.6, Oracle 7.3.4, WL oci
driver,
no perf pack, Javasoft 1.1.7B_05 vm on server side and IBM 1.1.7B onclient
side (W98 clients).
When multiple users connect to the server (let's say from 15 simultaneous
connections) and work on our application, after few mins, the serverprocess
logs and outputs tons of messages like :
Mon Nov 15 16:12:26 GMT 1999:<E> <RJVM> Ignoring message from a previous
generation: JVMMessage from 8803290290807054313C146.100.8.34
to -6807808847876022584C146.100.100.84 with CMD_ONE_WAY, prtNum=5,
ack=30,
seqNum=3151
and
Got heartbeat for -6807808847876022584/-1838914476/0/9209 but did notfind
reference
Got heartbeat for -6807808847876022584/-1838914476/0/8979 but did notfind
reference
This is strangely related to a real degradation of the WL server response
times and sometimes to 'PeerGoneExceptions' thrown to the client (whilethe
server is still alive...).
This happens either for connections on the LAN or on the WAN (frame relay
network) so I don't think this is network related. As of now, weblogic
support told us not to care about it but after analysing the messages,there
seems to be a real problem here :
What seems to happen is :
- The server considers that the client is dead so it's closing the
connection. Eventually, the DGC cleans up references that were held bythis
client.
- The server recieves a query from the 'still alive client' and re-opensthe
connection with the SAME id.
- If there is a heartbeat from a DGC cleaned up object, the DGC informsthat
it 'did not find reference'.
- It ignores the messages from the previously closed connection and triesto
re-establish everything.
We desperately need some feed back on what is causing the server to close
the connection while the client is still alive. I've seen somewhere inthis
list that there are some internal parameters in the WL server
('weblogic.system.idlePeriodUntilTimeout' and
'weblogic.system.periodLength') which indicates the WL server when to
consider a client as 'dead'. This is defaulted to 1 min for the first andto
4 for the second which implies that there must be at least 4 minutesduring
which the client doesn't emmit 'heartbeats' for the server to know it is
alive.
few remarks :
1/ the client is not swapping nor GCing too long so the client vm is
available to emmit these heartbeats.
2/ we couldn't reproduce it in our test environement except when makingthe
client swap for minutes which is not the case in the production env.
3/ this really seems related to multiple clients connected simultaneouslyto
the server.
Thanks a lot for your help.
Vincent Vandenschrick
Obbisoft.

Oracle 10.2.0.4 MAXTRANS parameter ignored message

Hello all,
Does anybody have an idea why this error is occuring during an FULL export of the DB, all works well though.
Should i be increasing a parameter just not to have it reported in alert.log.
The value (30) of MAXTRANS parameter ignored.
kupprdp: master process DM00 started with pid=66, OS id=1360
to execute - SYS.KUPM$MCP.MAIN('SYS_EXPORT_FULL_01', 'SYSTEM', 'KUPC$C_1_20090622180005', 'KUPC$S_1_20090622180005', 0);
kupprdp: worker process DW01 started with worker id=1, pid=67, OS id=2920
to execute - SYS.KUPW$WORKER.MAIN('SYS_EXPORT_FULL_01', 'SYSTEM');
Thanks

From 10g onwards, there is no need to set the parameter Maxtrans as Oracle automatically puts the number of slots to 255. If you set a value for this for a segment specifically the message as like is shown , is written in the alert log and the value given is ignored.
HTH
Aman....

How Subscriber Can Ignore Messages When Publisher

Hello,
I have a few subscribers to a topic, however those subscribers can also be publishers for messages.
Is there an easy way for a subscriber to ignore any messages if that subscriber is the publisher of a particular message?
Regards,
Stoyan

Hi,
I don't see what getter I can use on the publisher to get its ID, also I don't see any ID
in the message that I can use. Would you be more precise about the IDs you're
referring to and how to extract them.
Thanks,
Stoyan

Ignoring MESSAGE while running via RFC

Hello everybody,
when I start a FM (or what ever) it will display an MESSAGE (Type: I) as Information. The User must quit the message, than the function goes to the end.
When I call this FM via RFC (from an other SAP) the MESSAGE would not display an the function goes automatically to the end.
How can I reach that the MESSAGE would be display by calling via RFC.
Thanks.
Thomas

Hi,
I dont think it is possible to display a message in RFC.
Messages are popped in the current system in RFC the system is changed
Sameena
Message was edited by: sameena attarwala

OpenMQ Memory Error - Drop / Ignore messages if Receivers are not listening

Hi,
I am using OpenMQ jms broker. Publishers are publishing data on topic1, topic2 & topic3.
Now if there are no receiver listening on these topics then after couple of hours openmq is crashing by eating all the memory (RAM) available in the system.
How can i configure openmq so that it can drop the messages coming on these topic if there are no receivers listening on them?
Is there any way to drop the messages coming on these topics if no receiver interested in these topics?
Please guide. This is bit urgent.
Thanks & regards,
Pawan Modi

Pawan,
The term "durable" applies to a TopicSubscription, not a Topic. There are essentially two methods to create a TopicSubscription on a Topic: one to create a durable subscription and one to create a non-durable subscription.
TopicSession.createSubscriber(Topic topic)
TopicSession.createDurableSubscriber(Topic topic, String name) (See [http://java.sun.com/javaee/5/docs/api/javax/jms/TopicSession.html|http://java.sun.com/javaee/5/docs/api/javax/jms/TopicSession.html])
So there isn't really a default.
A durable subscription continues to exist (accumulating messages) even if the client disconnects and goes away, whereas a non-durable subscription disappears the moment the client disconnects.
Nigel

Memory Leak, Receiver Got Null Message & Consumer limit exceeded on destina

When running program that adds an Object message to a JMS queue and then recieves it. I get the following.
1) interminitent NULL messages recieved.
2) jms.JMSException: [C4073]: Consumer limit exceeded on destination interactionQueueDest. Even though only one receiver can be receiving via the supplied program.
3) After many message are added to the queue 1000's the Message Queue goes to Out Of Memory exception. It should swap to disk!!
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
RUN this program via a JSP call in the application server.
JSP
<%@ page language="java" import="jms.*"%>
<html>
<head>
<title>Leak Memory</title>
</head>
<body>
<hr/>
<h1>Leak Memory</h1>
<%
   LeakMemory leakMemory = new LeakMemory();
   leakMemory.runTest(10000,1000);
// NOTE will brake but slower with setting leakMemory.runTest(10000,100);
%>JMS resources must be created:
jms/queueConnectionFactory
jms/interactionQueue
must be created first.
Class:
package jms;
import javax.naming.*;
import javax.jms.*;
public class LeakMemory implements Runnable {
private QueueConnectionFactory queueConnectionFactory = null;
private Queue interactionQueue = null;
private boolean receiverRun = true;
private QueueConnection queueConnection;
private int totalMessageInQueue = 0;
public LeakMemory() {
    init();
   * initialize queues
public void init(){
    try {
      InitialContext context = new InitialContext();
      this.queueConnectionFactory = (QueueConnectionFactory)context.lookup("jms/queueConnectionFactory");
      this.interactionQueue = (Queue) context.lookup("jms/interactionQueue");
    catch (NamingException ex) {
      printerError(ex);
public void runTest(int messageCount, int messageSize){
    this.receiverRun = true;
    Thread receiverThread = new Thread(this);
    receiverThread.start();
    for (int i = 0; i < messageCount; i++) {
        StringBuffer messageToSend = new StringBuffer();
        for (int ii = 0; ii < messageSize; ii++) {
          messageToSend.append("0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789\n");
        QueueConnection queueConnectionAdder = null;
        QueueSession queueInteractionSession = null;
        QueueSender interactionQueueSender = null;
        try {
            //Get a queue connection
            queueConnectionAdder = this.getQueueConnection();
            queueInteractionSession = queueConnectionAdder.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
            interactionQueueSender = queueInteractionSession.createSender(this.interactionQueue);
            ObjectMessage objectMessage = queueInteractionSession.createObjectMessage(messageToSend);
            objectMessage.setStringProperty("PROPERTY", "" + System.currentTimeMillis());
            //Send object
            interactionQueueSender.send(objectMessage,DeliveryMode.PERSISTENT,5,0);
            totalMessageInQueue++;
            //Close Resources
            interactionQueueSender.close();
            queueInteractionSession.close();
            interactionQueueSender = null;
            queueInteractionSession = null;
        } catch (JMSException ex) {
           printerError(ex);
   * run
public void run() {
    while(this.receiverRun){
            try {
              QueueSession interactionQueueSession = this.getQueueConnection().createQueueSession(false, Session.CLIENT_ACKNOWLEDGE);
              QueueReceiver queueReceiver = interactionQueueSession.createReceiver(this.interactionQueue);
              ObjectMessage message = (ObjectMessage)queueReceiver.receive(100);
              if(message != null){
                StringBuffer messageRecived = (StringBuffer)message.getObject();
                //Simulate Doing Something
                synchronized (this) {
                  try {
                    Thread.sleep(400);
                  catch (InterruptedException ex1) {
                    //Can Safely be ignored
                message.acknowledge();
                totalMessageInQueue--;
              } else {
                printerError(new Exception("Receiver Got Null Message"));
              queueReceiver.close();
              interactionQueueSession.close();
              queueReceiver = null;
              interactionQueueSession = null;
            catch (JMSException ex) {
              printerError(ex);
    * Get's the queue Connection and starts it
    * @return QueueConnection The queueConnection
   public synchronized QueueConnection getQueueConnection(){
       if (this.queueConnection == null) {
         try {
           this.queueConnection = this.queueConnectionFactory.createQueueConnection();
           this.queueConnection.start();
         catch (JMSException ex) {
           printerError(ex);
     return this.queueConnection;
   private void printerError(Exception ex){
     System.err.print("ERROR Exception totalMessageInQueue = " + this.totalMessageInQueue + "\n");
     ex.printStackTrace();
}Is there something wrong with the way I'm working with JMS or is it just this unreliable in Sun App Server 7 Update 3 on windows?

1) interminitent NULL messages recieved.Thanks that explains the behavior. It was wierd getting null messages when I know there is messages in the queue.
2) jms.JMSException: [C4073]: Consumer limit exceeded
on destination interactionQueueDest. Even though only
one receiver can be receiving via the supplied
program. No other instances, Only this program. Try it yourself!! It works everytime on Sun Application Server 7 update 2 & 3
heres the broker dump at that error point
[14/Apr/2004:12:51:47 BST] [B1065]: Accepting: [email protected]:3211->admin:3205. Count=1
[14/Apr/2004:12:51:47 BST] [B1066]:   Closing: [email protected]:3211->admin:3205. Count=0
[14/Apr/2004:12:52:20 BST] [B1065]: Accepting: [email protected]:3231->jms:3204. Count=1 [14/Apr/2004:12:53:31 BST] WARNING [B2009]: Creation of consumer from connection [email protected]:3231 on destination interactionQueueDest failed:
B4006: com.sun.messaging.jmq.jmsserver.util.BrokerException: [B4006]: Unable to attach to queue queue:single:interactionQueueDest: a primary queue is already active
3) After many message are added to the queue 1000's
the Message Queue goes to Out Of Memory exception. It
should swap to disk!!The broker runs out of memory. Version in use
Sun ONE Message Queue                   Copyright 2002
Version: 3.0.1 SP2 (Build 4-a)              Sun Microsystems, Inc.
Compile: Fri 07/11/2003         All Rights ReservedOut of memory snippet
[14/Apr/2004:13:08:28 BST] [B1089]: In low memory condition, Broker is attempting to free up resources
[14/Apr/2004:13:08:28 BST] [B1088]: Entering Memory State [B0022]: YELLOW from previous state [B0021]: GREEN - current memory is 118657K, 60% of total memory
[14/Apr/2004:13:08:38 BST] WARNING [B2075]: Broker ran out of memory before the passed in VM maximum (-Xmx) 201326592 b, lowering max to currently allocated memory (200431976 b ) and trying to recover [14/Apr/2004:13:08:38 BST] [B1089]: In low memory condition, Broker is attempting to free up resources
[14/Apr/2004:13:08:38 BST] [B1088]: Entering Memory State [B0024]: RED from previous state [B0022]: YELLOW - current memory is 128796K, 99% of total memory [14/Apr/2004:13:08:38 BST] ERROR [B3008]: Message 2073-192.168.0.50(80:d:b6:c4:d6:73)-3319-1081944517772 exists in the store already [14/Apr/2004:13:08:38 BST] WARNING [B2011]: Storing of JMS message from IMQConn[AUTHENTICATED,[email protected]:3319,jms:3282] failed:
com.sun.messaging.jmq.jmsserver.util.BrokerException: Message 2073-192.168.0.50(80:d:b6:c4:d6:73)-3319-1081944517772 exists in the store already
[14/Apr/2004:13:08:38 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:38 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:39 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:39 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:39 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:39 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:40 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:40 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:40 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:40 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:41 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:42 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:42 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:42 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:42 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:43 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:43 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:43 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:43 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:44 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:44 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:44 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:45 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:45 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:46 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:46 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:47 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:47 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:47 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:47 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:48 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:49 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:49 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:49 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:49 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:50 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:50 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:50 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:50 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:51 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:51 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:51 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:51 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:52 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:52 BST] WARNING [B2076]: Broker is rejecting new producers, because it is extremely low on memory
[14/Apr/2004:13:08:53 BST] ERROR [B3107]: Attempt to free memory failed, taking more drastic measures : java.lang.OutOfMemoryError
[14/Apr/2004:13:08:53 BST] ERROR unable to deal w/ error: 1
[14/Apr/2004:13:08:53 BST] ERROR TRYING TO CLOSE [14/Apr/2004:13:08:53 BST] ERROR DONE CLOSING
[14/Apr/2004:13:08:53 BST] [B1066]:   Closing: [email protected]:3319->jms:3282. Count=0

Mail messages disappear from the Inbox, but are still in ~/Library/Mail

Folks,
I'm encountering a perplexing problem on my parent's eMac; any input would be very much appreciated...here's the story:
Over the weekend, I upgraded my Dad's 1.25GHz eMac G4 to Tiger (it had been running 10.3.9). The upgrade went smoothly, and all seemed well. I applied all the latest Apple Software Updates to get the eMac to 10.4.6, and once again, all seemed well. I performed the usual Disk Utility "permission fixing," as well, and nothing came up that seemed unusual. I did notice that I encountered the "spinning beach ball" a fair amount during routine operations, but I attributed this to the fact that the eMac only has 512MB of RAM (it's going to receive another 512 in a few days), and that I was just being impatient, given that I am accustomed to my own machine, which is a relatively snappy dual 2.5GHz G5 with the full complement of 8GB of RAM. A day or so later, Dad reported that the Mail app was not starting; upon clicking the Mail icon, it simply bounced several times, and then simply stopped bouncing. I looked at the crash logs and found that Mail could not locate a needed file/library located in /System/Library/Frameworks/SyncServices.framework. In addition, I noticed that the iCal app and the Address Book app were also crashing (the icons of each would bounce, just like Mail's, then stop, without the apps actually firing up). The crash logs revealed that those apps were also looking for this mysterious file, which apparently had somehow been misplaced/lost. I used the "Pacifist" program to reinstall the contents of that particular directory (using the Tiger install CD). Much to my relief, once that directory was reinstalled, the apps once again started up and worked normally. HOWEVER, I noticed some odd behavior with the Mail app. The first thing that became evident was that the Inbox did not show all the messages that had been there before. Looking under the ~/Library/Mail/POP-Dad's account/INBOX.mbox/Messages directory, however, it was clear that all the messages were indeed there (in the form of the individual .emlx files). They just did not seem to be displayed in the Inbox of the Mail app. I tried doing a "rebuild" of the mailbox, but this did not result in any additional messages being displayed. Any thoughts?
The other perplexing behavior is this: the Mail app on the eMac can send and receive mail, but, once you click on a newly-received (unread) message, and then go to another mail box (say, for example, the "Drafts" or "Sent" folders), and then return to the Inbox, the message that was just received is no longer displayed/listed in the Inbox. Once again, looking in the ~/Library/Mail/POP-Dad's account/INBOX.mbox/Messages directory reveals that the message IS there (again, in its own .emlx file), but is simply not being displayed in the Inbox. I can click on the individual .emlx files, and they open new windows in Mail, from which you can hit "reply" or "forward," as normal; it just won't display the actual message that was originally in the Inbox. Sent messages, however, seem to be saved/displayed normally.
I've searched through the Mail discussion forum, and while I've found discussions along generally similar lines, I have not located an entry dealing with these particular symptoms. As such, any input/suggestions would be greatly appreciated.
Thanks in advance for your time.
-Javier

Regarding the missing package that you reinstalled with Pacifist, it would have been better to fix the problem by reinstalling the Mac OS X 10.4.6 Combo Update. Actually, you're going to have to do that anyway, as the package you installed came from an older version of Mac OS X and could now be out-of-sync with the rest of the system. Not only that, but if there was something amiss with that package, chances are that something else went awry as well, so you should really reinstall the latest Combo Update. Read the following articles for guidelines on how to properly install system updates:
Troubleshooting installation and software updates
Installing software updates
Basically, you should verify/repair the boot volume (not just permissions) before installing the update, and no applications should be running while installing it.
As to the missing messages, the conversion from Mail 1.x to Mail 2.0 is broken. Take a look at the following thread to better understand the problem:
Help! "You need to take this account online in order to download it."
If you see a strangely named Messages-XXXXXX folder within any of the *.mbox folders in the Finder, that means the conversion didn't proceed as it should, so be careful about deleting the old files, as they may contain messages that didn't come through. Better just move them out of there if you wish.
I partially disagree with Allan (and with Ernie, who also has troubleshooted a lot of similar cases and believes the old files could still be troublesome after a successful conversion as well) in that I don't think the problem with Mail 2.0 is the presence of the old files, but rather that, as a result of the improper conversion, there is something wrong with Envelope Index and with some of the converted messages themselves. IMO, the old files shouldn't be a problem if the conversion worked properly. Mail should just ignore those files when it sees a proper Messages folder in the mailbox folder.
The reason you cannot see in Mail some messages for which an *.emlx file exists is precisely that there is something wrong with Envelope Index. Mail will simply ignore any *.emlx file for which a corresponding entry does not exist in Envelope Index. Actually, Mail doesn't look into the Messages folder at all when displaying the mailbox contents, it just loads whatever there is in Envelope Index. If that information is wrong, the information displayed by Mail will be wrong as well; it may refer to messages that no longer exist, ignore messages that do exist, display one message but load a different one when you open it, etc.
Re-creating Envelope Index without cleaning up the mailboxes first would probably fail and it could even make things worse, though. That's what makes troubleshooting these issues harder than it should be.

How to return the message in MTI and bitmap?

Here we receive xml message from client but the problem is this coding is for the first time it receive MTI message, so how can i do if i receive from client in xml type then convert to MTI then response it as xml again to client.
Is it too hard to understand?????
     * Waits and receive an ISOMsg over the TCP/IP session
     * @return the Message received
     * @exception IOException
     * @exception ISOException
    public ISOMsg receive() throws IOException, ISOException {
        byte[] b=null;
        byte[] header=null;
        LogEvent evt = new LogEvent (this, "receive");
        ISOMsg m = createMsg ();
        Socket socket = getSocket();
        m.setSource (this);
        try {
            if (!isConnected())
                throw new ISOException ("unconnected ISOChannel");
            synchronized (serverIn) {//read byte/array of byte
                int len = getMessageLength();
                int hLen = getHeaderLength();
                if (len == -1) {
                    if (hLen > 0) {
                        header = readHeader(hLen);//read in message header
                    b = streamReceive();
                else if (len > 0 && len <= 10000) {
                    if (hLen > 0) {
                        // ignore message header (TPDU)
                        // Note header length is not necessarily equal to hLen (see VAPChannel)
                        header = readHeader(hLen);//header lenght read the message header
                        len -= header.length;
                    b = new byte[len];
                    serverIn.readFully(b, 0, len);//get the input from user with byte type,0 length into lenght,read the byte to server in.
                    getMessageTrailler();
                else
                    throw new ISOException(
                        "receive length " +len + " seems strange");
            *// TODO:*
*         // prefix with standard ISO MTI and bitmap*
            *// using ISOMsg setters*
            m.setPackager (getDynamicPackager(b));//msg receive
            m.setHeader (getDynamicHeader(header));
            if (b.length > 0 && !shouldIgnore (header)) // Ignore NULL messages
                m.unpack (b);//raw message
            m.setDirection(ISOMsg.INCOMING);//set the direction for incoming msg into isoMsg
            m = applyIncomingFilters (m, header, b, evt);//remove the incoming filter to isoMsg
            m.setDirection(ISOMsg.INCOMING);
            evt.addMessage (m);
            cnt[RX]++;
            setChanged();
            notifyObservers(m);
       catch {
        return m;
    }

check this link, and use as per you requirement
XI: How-to on JDBC receiver response
JDBC Receiver Adapter -- Synchronous Select Step by Step
Regards
Chilla

IOS5.0.1 constant error "iPhone can not make or receive calls. Restore from iTunes": I get this message and the phone will no longer work (happend once while on airplain mode and now once while in wifi only area, out of cell range). help!

All- I get this message ("iPhone can not make or receive calls. Restore from iTunes" (happend once while on airplain mode and now once while in wifi only area, out of cell range)). iPhone 4. Newest OS. Never happened with old OS! Cycling phone on/off does not help. Ignoring message causes phone to cycle off then on. After first time this happened, I restored. Six days later...same problem! Clearly a new fix is necessary. Suggestions?

I have not tried that...I will look up the process so that I can do it correctly (and still transfer all of my files, contacts, etc). Any suggestions? What is the advantage of restoring as a new device..is this more akin to a complete wipe of a hard drive?

Mail is not downloading messages from two accounts but the messages are in the server.

Hello, I'm having this problem. Mail is not downloading messages from two accounts. I don't know why but there're two accounts working so bad. If I click with the right button on the account and click to see the account details, I can see the messages on the server but not in inbox. I made a sync with this account and my iphone and then the iphone downlad the messages with out problems. Not my imac at work or my imac at home... what can be wrong?
Thanks.

For Gmail, this is normal, there is nothing you can do about it -- just type Mail AND Gmail in the search box to see threads discussing how Gmail works.
As for the other accounts, this shouldn't happen. I wonder if what you're seeing is just that Mail is ignoring this setting for mail that was already on the server when you started using it. I've seen something like this happen when playing with that setting, e.g. changing it from "After one day" to "After one week". Mail would just ignore messages that fell in the timeframe where the two settings could interfere and I didn't notice it until some time later, when Mail "forgot" those messages had already been downloaded and, being faced with them again, dutifully downloaded them as if they were all new.
I believe that, if you leave the setting however you wish and stop playing with it, then Mail shall correctly process any mail that arrives from now on. In order to manually delete old messages that Mail seems to be ignoring, you can invoke the Account Info window (this is probably what you meant when you said "I can delete messages individually"; if that's not the case and want more info on this, just ask).

DUPLICATE POST - DELETE/IGNORE

DUPLICATE POST - DELETE/IGNORE
Message was edited by: BallisticJack

transact wrote:
The administrator, can he delete this post? Because it's here 3 per.
Thanks.
TransactNo, but you can hit the "edit" button on the first message in the thread and change the subject to something like "Duplicate post, please igonre". These double and triple posts are not that uncommon around here and most people understand (and have done it themselves). It seems to be due to slow response from the server and people hitting "post" button again and again, thinking it didn't "take" the first time.

ISE continue to receiving authentication message after removed the radius host test configuration on a IOS router

I have two issues but related and need help:
anyone know how to disable or stop a radius host test message send every seconds from a IOS router after the test statement removed and all radius server information removed from the configuration? I have this odd testing for the new ISE server. the purpose of testing is not for load balancing, but find out if IOS support different protocol using radius other than PAP if PPP is not used. after the test, I cannot stop it. I have a case opened with Cisco, the answer is no way to stop it other than reboot the router. I tried to remove aaa new model and add it back, no help. I have put an access-list on the LAN interface deny the IP any to the radius host and port, no match found.
On the ISE (version 1.1.1), due to the IOS router test cannot be stopped, the alive authentication page fills up all the authentication failure messages. anyone know how to block the host from ISE live authentication log (the router has been removed from the device page)?
below is part of messages from the IOS router (version 15.0.1M6) debug. where 10.2.2.144 is the ISE IP and totally removed from the config. there is no any radius or the ISE IP in the config.
Aug 28 10:21:15.384: AAA/SG/TEST(Req#: 1): Sending test AAA Access-Request.
Aug 28 10:21:15.384: AAA/SG/TEST(Req#: 1): Sending test AAA Accounting-Request.
Aug 28 10:21:15.384: AAA/SG/TEST: Verifying if further testing required to determine server state.
Aug 28 10:21:15.384: AAA/SG/TEST: DEAD state verification already in progress for server (10.2.2.144:1645,1646).
Aug 28 10:21:15.384: AAA/SG/TEST: Server (10.2.2.144:1645,1646) assumed DEAD. Dead time updated to 60 secs(s).
Aug 28 10:21:33.752: AAA/SG/TEST: No Test response from server (10.2.2.144:1645,1646)
Aug 28 10:21:33.976: AAA/SG/TEST: No Test response from server (10.2.2.144:1645,1646)
Aug 28 10:21:33.976: AAA/SG/TEST: Necessary responses NOT received from server (10.2.2.144:1645,1646).
Aug 28 10:21:33.976: AAA/SG/TEST: Server (10.2.2.144:1645,1646) marked DEAD. Dead time set for 60 sec(s).
Aug 28 10:21:33.976: AAA/SG/TEST: Server (10.2.2.144:1645,1646) removed from quarantine.
Aug 28 10:22:33.976: AAA/SG/TEST: Verifying if further testing required to determine server state.
Aug 28 10:22:33.976: AAA/SG/TEST: Server (10.2.2.144:1645,1646) quarantined.
Aug 28 10:22:33.976: AAA/SG/TEST: Sending 1 Access-Requests, 1 Accounting-Requests in current batch.
Aug 28 10:22:33.976: AAA/SG/TEST(Req#: 1): Sending test AAA Access-Request.
Aug 28 10:22:33.976: AAA/SG/TEST(Req#: 1): Sending test AAA Accounting-Request.
Aug 28 10:22:33.976: AAA/SG/TEST: Verifying if further testing required to determine server state.
Aug 28 10:22:33.976: AAA/SG/TEST: DEAD state verification already in progress for server (10.2.2.144:1645,1646).
Aug 28 10:22:33.976: AAA/SG/TEST: Server (10.2.2.144:1645,1646) assumed DEAD. Dead time updated to 60 secs(s).
Aug 28 10:22:52.760: AAA/SG/TEST: No Test response from server (10.2.2.144:1645,1646)
Aug 28 10:22:53.176: AAA/SG/TEST: No Test response from server (10.2.2.144:1645,1646)
Aug 28 10:22:53.176: AAA/SG/TEST: Necessary responses NOT received from server (10.2.2.144:1645,1646).
Aug 28 10:22:53.176: AAA/SG/TEST: Server (10.2.2.144:1645,1646) marked DEAD. Dead time set for 60 sec(s).
Aug 28 10:22:53.176: AAA/SG/TEST: Server (10.2.2.144:1645,1646) removed from quarantine.
Aug 28 10:21:15.384: AAA/SG/TEST(Req#: 1): Sending test AAA Access-Request.
Aug 28 10:21:15.384: AAA/SG/TEST(Req#: 1): Sending test AAA Accounting-Request.
Aug 28 10:21:15.384: AAA/SG/TEST: Verifying if further testing required to determine server state.
Aug 28 10:21:15.384: AAA/SG/TEST: DEAD state verification already in progress for server (10.2.2.144:1645,1646).
Aug 28 10:21:15.384: AAA/SG/TEST: Server (10.2.2.144:1645,1646) assumed DEAD. Dead time updated to 60 secs(s).
Aug 28 10:21:33.752: AAA/SG/TEST: No Test response from server (10.2.2.144:1645,1646)
Aug 28 10:21:33.976: AAA/SG/TEST: No Test response from server (10.2.2.144:1645,1646)
Aug 28 10:21:33.976: AAA/SG/TEST: Necessary responses NOT received from server (10.2.2.144:1645,1646).
Aug 28 10:21:33.976: AAA/SG/TEST: Server (10.2.2.144:1645,1646) marked DEAD. Dead time set for 60 sec(s).
Aug 28 10:21:33.976: AAA/SG/TEST: Server (10.2.2.144:1645,1646) removed from quarantine.
Aug 28 10:22:33.976: AAA/SG/TEST: Verifying if further testing required to determine server state.
Aug 28 10:22:33.976: AAA/SG/TEST: Server (10.2.2.144:1645,1646) quarantined.
Aug 28 10:22:33.976: AAA/SG/TEST: Sending 1 Access-Requests, 1 Accounting-Requests in current batch.
Aug 28 10:22:33.976: AAA/SG/TEST(Req#: 1): Sending test AAA Access-Request.
Aug 28 10:22:33.976: AAA/SG/TEST(Req#: 1): Sending test AAA Accounting-Request.
Aug 28 10:22:33.976: AAA/SG/TEST: Verifying if further testing required to determine server state.
Aug 28 10:22:33.976: AAA/SG/TEST: DEAD state verification already in progress for server (10.2.2.144:1645,1646).
Aug 28 10:22:33.976: AAA/SG/TEST: Server (10.2.2.144:1645,1646) assumed DEAD. Dead time updated to 60 secs(s).
Aug 28 10:22:52.760: AAA/SG/TEST: No Test response from server (10.2.2.144:1645,1646)
Aug 28 10:22:53.176: AAA/SG/TEST: No Test response from server (10.2.2.144:1645,1646)
Aug 28 10:22:53.176: AAA/SG/TEST: Necessary responses NOT received from server (10.2.2.144:1645,1646).
Aug 28 10:22:53.176: AAA/SG/TEST: Server (10.2.2.144:1645,1646) marked DEAD. Dead time set for 60 sec(s).
Aug 28 10:22:53.176: AAA/SG/TEST: Server (10.2.2.144:1645,1646) removed from quarantine.
Thanks in advance,

It seems reload is the only way to fix it. I don't think there is any way to stop or ignore messages for specific host in live authentication page of ISE. From security point of view it is required to logs all the authentication hits.
Regards,
~JG
Do rate helpful posts!

Can't turn off warning messages, tried trhough preferences, about:confing. Messages still appear. Please advice.

Using Firefox version 19.0.2 on MAC. Appears message: "Although this page is encrypted, the information you have entered is to be sent over an unencrypted connection and could easily be read by a third party.
Are you sure you want to continue sending this information?"
In preferences there is no option to choose what warning messages display or not display.
Through about:config tried to change security.warn is set to 'false' by default; security.warn_viewing_mixed - too set by default to 'false'.

I have seen discussions of this issue that run over years.
Basically the programmer is deciding to show this warning to protect you, but they are not considering that by poping up this warning all the time, the user will ignore it and basically waste time clicking past the warning.
In effect it is not a warning but an ignored message. I spent hours working on something using firefox and I just got more angry as I was required to click the pop up again and again.
Programmers - this does not work and only annoys your customers. I know it seems like a good idea but in reality it isn't. Give the customer the ability to turn off and then you have met your security concern - since the customer will have to look up how to disable and the customer won't want to through out the software.
Enough years have passed, fix it.

Distributed maintenance is not active; IDoc ignored

Hi
i am using LSMW to load Equipment BOM using IDOCs Basic type- /ISDFPS/BOMEQU01 Message type - /ISDFPS/BOMEQU.
i am getting error mesage status - 51 Distributed maintenance is not active; IDoc ignored
Message no. /ISDFPS/PM083
i have maintained inbound parameters,Kindly help to resolve this issue.
Thanks
Seenu

The System Package EA-DFPS need to be activated, If this is missing in the system.
Enterprise Addon not active*
SAP DFPS component enhances the standard SAP functions by providing functions for the following business tasks and processes:
Organizational Flexibility (mapping organizational structures and material and personnel resource planning)
The different business processes of armed forces, police, and aid organizations (organization, Human Resources Management, Materials Management, Maintenance, and so on) run along organizational structures.
Each organizational element (department or unit, for example):
Has certain properties, responsibilities, tasks, and missions
Requires personnel, material, and financial resources in order to perform its tasks
Is included in different organizational structures (organizational structure, command and support relationships, and so on) and works in conjunction with other organizational elements in accordance with the relationships thereby defined
You can use the functions in the Organizational Flexibility area of the Defense Forces & Public Security component to map these organizational bases and to carry out your resource planning.
This complete and integrated mapping provides you with the required basis in the system to:
Control processes in Human Resources, Logistics, Accounting, and Funds Management
Enable organizational changes to take effect automatically in the relevant processes
Enable you to plan and execute operations and exercises from the domestic base
Accounting and Funds Management
The Defense Forces & Public Security component provides armed forces, police, and aid organizations with the functions they need to carry out account assignment and budgeting for objects in the domestic base and operations in a distributed system landscape.
Materials Management
In the Defense Forces & Public Security component, Materials Management (MM) supports you when supplying armed forces, police, and aid organizations with non-consumable, individual consumable, and bulk consumable goods.
Material planners and MRP controllers can plan and carry out initial supplies and other supplies for the domestic base as well as for operations and exercises.
All tasks relating to supplies can be carried out in a distributed system landscape.
Support for Flight Operations
The Support for Flight Operations area supports processes carried out by airborne units in the domestic base, operations, and exercises. This includes the planning, control, and coordination of flight operations, the execution and control of maintenance, and administration. As a result, you can execute flights, from planning through to technical debriefing.
Maintenance
The Maintenance area of the Defense Forces & Public Security (DFPS) component supports armed forces, police, and aid agencies in performing maintenance tasks in the domestic base, operations, and exercises and enables the consistent distribution of maintenance data in a multi-system landscape.

Ignore message

Similar Messages

Maybe you are looking for