Messages are sent with a considerable delay on my ...

The sending message indicator appears on my mobile for a long time..some times upto 10-15 sec...additonally the phone takes a long time to open a new message.. i dont have this problem with another N86. i already have the latest firm ware installed. I have around 22mb free phone memory.. How can I resolve the problem?

do you have many text in your phone?if so remove them.
If i have helped at all a click on the white star below would be nice thanks.
Now using the Lumia 1520

Similar Messages

MDB cannot loads enitities if more than 10 concurrent messages are sent tog

Hello,
I have seen a weird behavior of the MDB in Jboss or perhaps in transaction management.
Here is a my scenario
I have a session bean sb, an entity bean e and a message driven bean mb
When a request comes to sb , it persists a new entity e and send a message (primary key) to mb
mb then loads e from the database using one of the findByXX method and does something else.
If 10 concurrent request comes to sb, 10 different entities are persisted and 10 different messages are sent to mb
mb are able to load 10 different e from the database
Everything works fine as long as there are 10 concurrent request. If there are 13 concurrent request, then one or two mb
cannot load e from the database. It seems that the session bean has persisted the entities but some of them are still unload able from mb. They have been persisted , (I saw in the logs), but mb cannot load them.
Initially I thought that a transaction mishap might be happening, so instead of persisting the entity and sending the message in one method in sb , I separated these two tasks in two methods a and b, in which both a and b uses RequiresNew transaction attribute. But the problem still remains. Please note if the number of parallel request are less than 10 then everything works fine. Is there something I am missing or is Jboss doing something buggy?
The above situation is reproducible .
Here is some more information about the problem along with some code snapshots. Note that the code is trimmed for clarity purposes.
Request is a simple entity (e as mentioned in the problem before) that is persisted in session bean . Here is a trimmed snapshot
Request.java
package gov.fnal.ms.dm.entity;
import java.io.Serializable;
import javax.persistence.Column;
import javax.persistence.Entity;
@Entity
@NamedQueries({@NamedQuery(name = "Request.findById", query = "SELECT r FROM Request r WHERE r.id = :id"),
@NamedQuery(name = "Request.findAll", query = "SELECT r FROM Request r"),
@Table(name = "cms_dbs_migration.Request")
@SequenceGenerator(name="seq", sequenceName="cms_dbs_migration.SEQ_REQUEST")
public class Request implements Serializable {
private String detail;
@Id
@GeneratedValue(strategy = GenerationType.AUTO, generator="seq")
@Column(nullable = false)
private Long id;
private String notify;
.....The session bean is MSSessionEJBBean.
MSSessionEJBBean.java
@Stateless(name="MSSessionEJB")
@WebService(endpointInterface = "gov.fnal.ms.dm.session.MSSessionEJBWS")
public class MSSessionEJBBean implements MSSessionEJB, MSSessionEJBLocal, MSSessionEJBWS {
@PersistenceContext(unitName="dm")
private EntityManager em;
.......    The methods that is called concurrently in this bean is
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
public Request addRequest(String srcUrl, String dstUrl, String path,
String dn, String withParents, String withForce, String notify) throws
Exception {
Request r = addRequestUnit(srcUrl, dstUrl, path, dn, withParents, withForce, notify);
if (r != null) sendToQueue(r.getId());
return r;
}    It first adds the request entity and then sends a message to the queue in separate methods each using TransactionAttributeType.REQUIRES_NEW (I don't think this TransactionAttributeType is needed . I was just playing to see if this resolves the problem)
Here is the method that actually persist the entity
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
public Request addRequestUnit(String srcUrl, String dstUrl, String path,
String dn, String withParents, String withForce, String notify) throws
Exception {
....// Does something before persisting
Request r = new Request();
r.setNotify(notify);
r.setPath(path);
r.setPerson(p);
r.setWithForce(withForce);
r.setWithParents(withParents);
r.setProgress(new Integer(0));
r.setStatus("Queued");
r.setDetail("Waiting to be Picked up");
em.persist(r);
System.out.println("Request Entity persisted");
System.out.println("ID is " + r.getId());
return r;
}I can see that the log files has messages
*{color:#800000}"Request Entity persisted" "ID is " 12 (or some other number){color}*
. So it is safe to assume that the request entity is persisted properly before the message is sent to the queue. Here is how the message is sent to the queue
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
private void sendToQueue(long rId) throws Exception {
QueueSession session = null;
QueueConnection conn = null;
try {
conn = factory.createQueueConnection();
session = conn.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
MapMessage mapMsg = session.createMapMessage();
mapMsg.setLong("request", rId);
session.createSender(queueRequest).send(mapMsg);
} finally {
if (session != null) session.close();
if(conn != null) try {
conn.close();
}catch(Exception e) {e.printStackTrace();}
System.out.println("Message sent to queue");
}I can see the message
{color:#800000}*"Message sent to queue"*{color}
in the log file right after I see the
*{color:#800000}
"Request Entity persisted"{color}*
message. So it correct to assume that the message is infact sent to the queue.
Here is the md bean that gets the message from the queue and process it
@MessageDriven(activationConfig =
@ActivationConfigProperty(propertyName="destinationType",
propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination",
propertyValue="queue/requestmdb")
public class RequestMessageDrivenBean implements MessageListener {
@EJB
private MSSessionEJBLocal ejbObj;
public void onMessage(Message message) {
try{
System.out.println("Message recived ");
if(message instanceof MapMessage) {
System.out.println("This is a instance of MapMessage");
MapMessage mMsg = (MapMessage) message;
long rId = mMsg.getLong("request");
List<Request> rList = ejbObj.getRequestById(new Long(rId));
System.out.println("rList size is " + rList.size());
for(Request r: rList) {
//Does something and print something in logs
System.out.println("Finsihed onMessage");
}catch(Exception e) {
System.out.println(e.getMessage());
}    One thing to note here is that getRequestById is another method in the same session bean MSSessionEJB. Can that be the reason for not loading the request from the database when many concurrent request are present? Here is what it does
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
public List<Request> getRequestById(Long id) throws Exception {
System.out.println("Inside getRequestById id is " + id);
return em.createNamedQuery("Request.findById")
.setParameter("id", id)
.getResultList();
}    In the logs I do see
{color:#800000}*"This is a instance of MapMessage"*{color}
and I do see the correct Rid that was persisted before in the log
*{color:#800000}
"inside getRequestById id is 12"{color}*
. Finally I do see
*{color:#800000}
"Finsihed onMessage"{color}*
for all the request no matter how many are sent concurrently.
*{color:#ff0000}Here is where the problem is . rList size is 1 for most of the cases but it returns 0 when the number of concurrent message exceeds 10.*
*{color}*
So you see there is no exception per se, just that entity does not get loaded from the database. I would like to mention this again, it does work properly when the number of concurrent request are less than 10. All the invocation of onMessage in MB are able to load the entity properly in that case. Its only when the number of concurrent request increases more than 10, the onMessage is unable to load the entity and the rList is 0.
FYI I am using jboss-4.2.2.GA on RedHat enterprise linux 4 with jdk1.6.0_04
Please let me know if there is more information required on this.
Thank you

Hello,
I have seen a weird behavior of the MDB in Jboss or perhaps in transaction management.
Here is a my scenario
I have a session bean sb, an entity bean e and a message driven bean mb
When a request comes to sb , it persists a new entity e and send a message (primary key) to mb
mb then loads e from the database using one of the findByXX method and does something else.
If 10 concurrent request comes to sb, 10 different entities are persisted and 10 different messages are sent to mb
mb are able to load 10 different e from the database
Everything works fine as long as there are 10 concurrent request. If there are 13 concurrent request, then one or two mb
cannot load e from the database. It seems that the session bean has persisted the entities but some of them are still unload able from mb. They have been persisted , (I saw in the logs), but mb cannot load them.
Initially I thought that a transaction mishap might be happening, so instead of persisting the entity and sending the message in one method in sb , I separated these two tasks in two methods a and b, in which both a and b uses RequiresNew transaction attribute. But the problem still remains. Please note if the number of parallel request are less than 10 then everything works fine. Is there something I am missing or is Jboss doing something buggy?
The above situation is reproducible .
Here is some more information about the problem along with some code snapshots. Note that the code is trimmed for clarity purposes.
Request is a simple entity (e as mentioned in the problem before) that is persisted in session bean . Here is a trimmed snapshot
Request.java
package gov.fnal.ms.dm.entity;
import java.io.Serializable;
import javax.persistence.Column;
import javax.persistence.Entity;
@Entity
@NamedQueries({@NamedQuery(name = "Request.findById", query = "SELECT r FROM Request r WHERE r.id = :id"),
@NamedQuery(name = "Request.findAll", query = "SELECT r FROM Request r"),
@Table(name = "cms_dbs_migration.Request")
@SequenceGenerator(name="seq", sequenceName="cms_dbs_migration.SEQ_REQUEST")
public class Request implements Serializable {
private String detail;
@Id
@GeneratedValue(strategy = GenerationType.AUTO, generator="seq")
@Column(nullable = false)
private Long id;
private String notify;
.....The session bean is MSSessionEJBBean.
MSSessionEJBBean.java
@Stateless(name="MSSessionEJB")
@WebService(endpointInterface = "gov.fnal.ms.dm.session.MSSessionEJBWS")
public class MSSessionEJBBean implements MSSessionEJB, MSSessionEJBLocal, MSSessionEJBWS {
@PersistenceContext(unitName="dm")
private EntityManager em;
.......    The methods that is called concurrently in this bean is
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
public Request addRequest(String srcUrl, String dstUrl, String path,
String dn, String withParents, String withForce, String notify) throws
Exception {
Request r = addRequestUnit(srcUrl, dstUrl, path, dn, withParents, withForce, notify);
if (r != null) sendToQueue(r.getId());
return r;
}    It first adds the request entity and then sends a message to the queue in separate methods each using TransactionAttributeType.REQUIRES_NEW (I don't think this TransactionAttributeType is needed . I was just playing to see if this resolves the problem)
Here is the method that actually persist the entity
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
public Request addRequestUnit(String srcUrl, String dstUrl, String path,
String dn, String withParents, String withForce, String notify) throws
Exception {
....// Does something before persisting
Request r = new Request();
r.setNotify(notify);
r.setPath(path);
r.setPerson(p);
r.setWithForce(withForce);
r.setWithParents(withParents);
r.setProgress(new Integer(0));
r.setStatus("Queued");
r.setDetail("Waiting to be Picked up");
em.persist(r);
System.out.println("Request Entity persisted");
System.out.println("ID is " + r.getId());
return r;
}I can see that the log files has messages
*{color:#800000}"Request Entity persisted" "ID is " 12 (or some other number){color}*
. So it is safe to assume that the request entity is persisted properly before the message is sent to the queue. Here is how the message is sent to the queue
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
private void sendToQueue(long rId) throws Exception {
QueueSession session = null;
QueueConnection conn = null;
try {
conn = factory.createQueueConnection();
session = conn.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
MapMessage mapMsg = session.createMapMessage();
mapMsg.setLong("request", rId);
session.createSender(queueRequest).send(mapMsg);
} finally {
if (session != null) session.close();
if(conn != null) try {
conn.close();
}catch(Exception e) {e.printStackTrace();}
System.out.println("Message sent to queue");
}I can see the message
{color:#800000}*"Message sent to queue"*{color}
in the log file right after I see the
*{color:#800000}
"Request Entity persisted"{color}*
message. So it correct to assume that the message is infact sent to the queue.
Here is the md bean that gets the message from the queue and process it
@MessageDriven(activationConfig =
@ActivationConfigProperty(propertyName="destinationType",
propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination",
propertyValue="queue/requestmdb")
public class RequestMessageDrivenBean implements MessageListener {
@EJB
private MSSessionEJBLocal ejbObj;
public void onMessage(Message message) {
try{
System.out.println("Message recived ");
if(message instanceof MapMessage) {
System.out.println("This is a instance of MapMessage");
MapMessage mMsg = (MapMessage) message;
long rId = mMsg.getLong("request");
List<Request> rList = ejbObj.getRequestById(new Long(rId));
System.out.println("rList size is " + rList.size());
for(Request r: rList) {
//Does something and print something in logs
System.out.println("Finsihed onMessage");
}catch(Exception e) {
System.out.println(e.getMessage());
}    One thing to note here is that getRequestById is another method in the same session bean MSSessionEJB. Can that be the reason for not loading the request from the database when many concurrent request are present? Here is what it does
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
public List<Request> getRequestById(Long id) throws Exception {
System.out.println("Inside getRequestById id is " + id);
return em.createNamedQuery("Request.findById")
.setParameter("id", id)
.getResultList();
}    In the logs I do see
{color:#800000}*"This is a instance of MapMessage"*{color}
and I do see the correct Rid that was persisted before in the log
*{color:#800000}
"inside getRequestById id is 12"{color}*
. Finally I do see
*{color:#800000}
"Finsihed onMessage"{color}*
for all the request no matter how many are sent concurrently.
*{color:#ff0000}Here is where the problem is . rList size is 1 for most of the cases but it returns 0 when the number of concurrent message exceeds 10.*
*{color}*
So you see there is no exception per se, just that entity does not get loaded from the database. I would like to mention this again, it does work properly when the number of concurrent request are less than 10. All the invocation of onMessage in MB are able to load the entity properly in that case. Its only when the number of concurrent request increases more than 10, the onMessage is unable to load the entity and the rList is 0.
FYI I am using jboss-4.2.2.GA on RedHat enterprise linux 4 with jdk1.6.0_04
Please let me know if there is more information required on this.
Thank you

Hello. after updating to Ios 8 my iPhone is terribly! Discharged very quickly, many transitions between applications, the program takes off, ringtones do not work - works a standard call, the keyboard freezes, bad messages are sent, often loses the n

Hello. after updating to Ios 8 my iPhone is terribly! Discharged very quickly, many transitions between applications, the program takes off, ringtones do not work - works a standard call, the keyboard freezes, bad messages are sent, often loses the network. what have you done with your phone moym ?! solve all these problems! I beg of you!

Hello. after updating to Ios 8 my iPhone is terribly! Discharged very quickly, many transitions between applications, the program takes off, ringtones do not work - works a standard call, the keyboard freezes, bad messages are sent, often loses the network. what have you done with your phone moym ?! solve all these problems! I beg of you!

You can't send SMS or text messages to a non-Apple phone (such as an Android, Windows, or BlackBerry phone), because the messages are sent as iMessage

You can't send SMS or text messages to a non-Apple phone (such as an Android, Windows, or BlackBerry phone), because the messages are sent as iMessage

Yes, you can. I do it many, many times a day. If you're trying to send a message to someone who used to have an iPhone and who didn't disable iMessage before switching phones, they will need to unregister their number with iMessage:
https://selfsolve.apple.com/deregister-imessage
You also need to have SMS enabled with your carrier to send messages to non-iPhones.

Messages not sent with my iPhone 5S

Hi there, If I have Show Subject Field selected in Settings, Messages, my phone will not send a message. If I deselect it my messages are sent OK. Is it me or is there a bug in IOS7.03 or is it because I'm sending to a 3GS with IOS 6 that doesn't have a subject field? Thanks, Peter.

my phone will not send a message.
Not much infomation in your post.
iMessage, SMS, or MMS?
Exactly what happens when you try?
Is this problem sending to all recipients or just this particular iPhone?

My phone was recently updated to 8.1. After the update, when text messages are sent when my phone is off, I no longer receive when my phone is turned on. Is there something in Settings that needs to be changed? I never had this problem before the updat

My phone was recently updated to 8.1. After the update, when text messages are sent when my phone is turned off, they no longer appear when I turn the phone on. Is there something in Settings that needs to be changed?

MetsFanGirl,
Thanks for verifying. Are you having issues receiving both iMessages and standard text messages when they are sent when the phone is turned off? Try this and test... http://vz.to/1qjiOs7
LindseyT_VZW
Follow us on Twitter @VZWSupport

How can I see exactly what time messages are sent or received from IPhone 4

Is there any way to view exact times that messages are sent and received from an iPhone 4 running iOS 7?

If you are using iOS 7, then slide the text bubble to the left and you can see the time stamp to the right of the bubble.

[svn] 3406: Tweaks to ZipCodeValidator to ensure error messages are consistent with pre-patch behavior .

Revision: 3406
Author: [email protected]
Date: 2008-09-29 13:25:10 -0700 (Mon, 29 Sep 2008)
Log Message:
Tweaks to ZipCodeValidator to ensure error messages are consistent with pre-patch behavior. Mustella tests pass (verified via cyclone).
Reviewer: Deepa
QA: Yes
Localization: Yes ***
Modified Paths:
flex/sdk/branches/3.0.x/frameworks/projects/framework/bundles/en_US/src/validators.proper ties
flex/sdk/branches/3.0.x/frameworks/projects/framework/src/mx/validators/ZipCodeValidator. as

Hi,
Found a note explaining the significance of these errors.
It says:
"NZE-28862: SSL connection failed
Cause: This error occurred because the peer closed the connection.
Action: Enable Oracle Net tracing on both sides and examine the trace output. Contact Oracle Customer support with the trace output."
For further details you may refer the Note: 244527.1 - Explanation of "SSL call to NZ function nzos_Handshake failed" error codes
Thanks & Regards,
Sindhiya V.

Mail deception - says messages are sent out but are not delivered

The Mail program appears to send my outgoing e-mail messages but does not actually do so. When I send a new message or reply to a message, Mail behaves as though the message has been sent: the spinner runs and the swoosh sound occurs when the message leaves my Outbox. The message then appears in my Sent folder. However, the mail is never received by the intended recipients. I apparently operated like this for weeks until my sister mentioned my lack of response to her e-mail a couple of weeks prior. (Honest, I really did reply.) Upon investigation I learned that others had not received messages I had sent. I then tried sending a message to myself at the same account and at my work account (different ISP) and the messages were not received.
I am using a POP account at core.com. If I access my account via the core.com webmail site, I am able to actually send messages. Getting them from the Mail program on my computer is the problem.
I noticed several other questions posted about Mail not sending messages but those queries mentioned receiving an error message or the program timed out trying to send and knowing immediately the mail was not sent. My situation seems unique in that the program is behaving deceptively - it tells me a message is sent but it is not.
I followed the steps Apple posted regarding Leopard Mail not sending messages but no success. I am using OS X5.6 on an Intel MacBook.
I have spoken with the core.com technical support staff and they assure me the problems is with the Mail program or my iMac. They are most likely correct. As an experiment I set up MS Entourage as an e-mail client for my core.com account. Entourage had no trouble sending messages to intended recipients.
I have double and triple checked the settings in Mail Preferences. The core.com technical support representative confirmed I am using the correct settings and suggested I use a different e-mail client program and forget about Apple Mail. However, I understand it is not possible to export information from Mail to a different e-mail client program so I am reluctant to make the change. The representative also suggested I remove Mail and reinstall it as a way of possibly correcting the problem. I do not want to go that route if I can avoid doing so. If that is the best approach, how do I go about saving my messages and addresses in Mail before removing Mail? Other suggestions to get Mail to behave properly?
Thank you!

I am thinking your messages have been sent, but stopped somewhere along the path of server, perhaps even by your provider, due to some sudden lack of trust of your messages or identity.
Try sending a message only in Plain Text -- you could simply open one of your messages to your sister, click on Message in the menubar and choose Send Again. Then before sending click on Format, and choose Make Plain Text. Before sending click on Window and choose Activity. Watch the report of Activity as transmission of the message should be taking place.
Do you use a Signature, and if so, does it contain any links or HTML? Also, do this test only with a message you composed, and not one you Forwarded or a Reply.
Ernie

How messages are sent in SOST

Hi there!
We have implemented a workflow system. It was working fine before until I noticed that there are no more messages that can be seen in transaction SOST.
Before, when a user creates a document, there is a notification message that is being sent or queued and I can find it in transaction SOST. But now, it seemed that the messages are no longer queued. The last was Nov 3, 2009. The approvers however are still able to approve the documents via
Can anybody help? What are the processes that I need to check.
Thanks in advance.
Jun

Hi,
1. Check the SCOT settings for Sending the mails.
2. Execute the transaction SCOT and check the INT node settings. Confirm if these settings are in place.
3. If yes then Check SOST entries by specifying 'SENDER NAME' 'SEND METHOD' Under Sender Tab.
4. Select Send Status Tab and check all the checkboxes, click on Further.. Pushbutton to select The entries which are not in queue. I guess you can get it with either of the status.
Regards,
Vaishali.

Is there any way to determine what device text messages are sent from? Do free text messaging apps relate to the apple ID, or the iPod?

My son had a friend give him his apple ID username and password, and downloaded a texting app. Now, some text messages were sent, and they are both denying it. Is there any way to know if the text messages came from my son's iPod? The app and texts are deleted, so I can't look at a history to see who typed them.

I could not find anything one the developer's upport page. Contact the developer and ask
http://pinger.zendesk.com/categories/2067-need-help-with-textfree

Question about iMessage retrieval when messages are visible with "Search" feature

Hello everyone,
Today when I got off of work, I noticed that over 1,000 iMessages from my girlfriend had been deleted, dating as far back as when I purchased my iPhone 4 in June. Of course, I am in the process of freaking out, as we had some great conversations in there that I would like to save. The last time I backed up my iPhone was in September.
The thing is, when I search for her name with the iPhone "Search" function, all of those conversations appear as if they should be in the iMessage list, but they are not. Is there anyway for me to exploit this and restore these iMessages onto my phone?
I'm an Air Force pilot in Texas and don't get to see her much, so I would love to be able to save these messages. I also went to school for electrical engineering, and I'm stumped.
tl;dr iMessages accidentally deleted but still appear in the iPhone "Search" function - is there anyway to restore them?

Unfortunately, not that I'm aware of. The cached data you are seeing in Spotlight search is separate from the messages data on your phone, and you can't restore from one to the other.
Messages are, however, included in the iPhone backup (whether done with iTunes or iCloud). If these messages were on your phone when you last backed up, restoring to the entire backup should recover them.

After importing received and set messages from Opera Mail, Thunderbird works fine but does not save sent messages to Sent folder, even though messages are sent

I successfully imported messages from Opera Mail. Initially the Sent mailbox was not showing in Thunderbird. A quick removal and fresh installation solved that, but Thunderbird does not save the sent messages to the Sent box, where the imported Opera Mail messages are stored. Even though messages are not saved, they are sent correctly. The image attached shows the error message.

Probably a name-confuse If you store sent on mailserver it has to have the right name. (subscribe)
You could set up under Account settings / copies and folders (maps) Sent pointing to the right local folder.

How can you tell if messages are blocked with ios7

how can i tell if imessages are blocked with ios7 and can it block facebook im?

Selected guides should become light blue when they're selected. My guides are using the default color of cyan and the guide on the right is selected in the image below.
If you have your guides set to the light blue selection inside the Guides Color drop down menu then you won't see a difference because that specific light blue is the color the guide changes to when it's selected. You can also click on the swatch in the Guides and Grids preferences to select any color you want from a color picker.

Calls with zero duration are sent with 1/1/1970 timestamp

Hello.
We are configuring billing on a third-party server for a hospitality projects.
All is fine so far. However we saw that calls with zero duration (such as missed calls, busy tones etc) are tagged with a wrong timestamp of 1/1/70.
Since we are passing this over to the hotel PMS, they are having trouble interpret it and often their interface crashes.
Has someone encountered any similar issue?
Our System version: 9.1.1.20000-5

I only see the 1970 date in fields like Call Connection time. And for a missed/busy call, that's the best you can do as the call didn't connect, so the call can't have a connection time. Either the field has the 1970 date, or it has NULL in it. Either way, if your third party software can't cope with it, it's broken as this is all as per Cisco's spec.
The use of the 1970 date is (OK, a time of zero) is clearly documented
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/9_1_1/cdrdef/CUCM_BK_C268EF1B_00_cucm-cdr-admin-guide-91/CUCM_BK_C268EF1B_00_cucm-cdr-admin-guide-91_chapter_010.html#CUCM_RF_T0347117_00
GTG
Please rate all helpful posts.

Messages are sent with a considerable delay on my ...

Similar Messages

Maybe you are looking for