Weblogic smtp connection timeout!

Hi, when I deployed my program in the weblogic server, everything is ok, but after somedays it can not send mail! I believe my code is available, because I can send mail in my tomcat server in the same machine. Can anyone help me or give me some clue?
Thanks a lot!
The following is exception:
javax.mail.SendFailedException: Sending failed;
nested exception is:
javax.mail.MessagingException: Could not connect to SMTP host: smtp.bea.com, port: 25;
nested exception is:
java.net.ConnectException: Connection timed out
at javax.mail.Transport.send0(Transport.java:219)
at javax.mail.Transport.send(Transport.java:81)
at com.bea.tuxedo.crinfo.businesslogic.Sev1Record.Sev1SubmitHandler.sendMail(Sev1SubmitHandler.java:281)
at com.bea.tuxedo.crinfo.businesslogic.Sev1Record.Sev1SubmitHandler.copyform(Sev1SubmitHandler.java:149)
at com.bea.tuxedo.crinfo.businesslogic.Sev1Record.Sev1SubmitHandler.doRequest(Sev1SubmitHandler.java:53)
at com.bea.tuxedo.crinfo.action.Sev1Record.UpdateSev1CRAction.execute(UpdateSev1CRAction.java:21)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:421)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:226)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:415)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

Just to be clear, you work for BEA, you're using WebLogic, you're trying
to send mail using the smtp.bea.com mail server, and you're asking for
help here? :-)
Assuming the server isn't actually down, and connections aren't timing out
when connecting from other applications or other machines, I would look
into whether there's a firewall that might be preventing you from connecting,
or possibly the mail server has decided that you've connected too often or
have too many open connections and so won't let you connect again.

Similar Messages

SMTP connection timeout

Hi,
This question might sound naive, but I just couldn�t find the answer.
For POP, IMAP and HTTP it is easy to setup idle connection timeout (just use configutil).
But what about SMTP connections?
It is set by default on some value (if I just telent on port 25 and live the connection idle, the message �Connection to host lost� will appear after aproximetly 5 minutes), but I cannot find where it can be changed.
On the other hand, what if connection is not idle, but the user is trying to send a bit biger mail but the link is really slow� how is this treated, what is the timeout for this situation and where this can be changed?
Thanks a lot, as always :)

The thing I�m having on my mind is to set this timeout to bigger number, and let slow connections to stay alive for more than 10 minutes.
The only parameter I found is MAX_IDLE_TIME in dispatcher.cnf file, by default it is set to 600.
But the explanation for this parameter is a bit confusing:
MAX_IDLE_TIME=integer
Specifies the maximum idle time for a server process. When an server process has had no active connections for this period, it becomes eligible for shutdown. This option is only effective if there are more than the value of MIN_PROCS server processes currently in the Dispatcher's pool for this service.
Anyway, for testing purposes I set this parameter to 6000 instead of 600, and did:
./imsimta cnbuild
./imsimta restart
Again I telnet to port 25 and live the connection idle, the message �Connection to host lost� appear again after approximately 10 minutes), so it seems like nothing was changed.
So, is this the wrong parameter, or for some other reason time is not expanded?
Btw,
./imsimta version
iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)
libimta.so 5.2 HotFix 1.21 (built 18:35:22, Sep 8 2003)

How to change the SMTP connection timeout in Thunderbird?

Go to Config Editor
(Tools | Options, select the Advanced panel, select the General tab, and click Config Editor)
and ...
Which parameter need to change?
If I connect to the Internet as:
Computer -> WiFi Router -> 3G Modem -> Internet
then Ping time is big, and OFTEN (but not always) there is an
"Sending of message failed. The message could not be sent because the connection to SMTP server mail.domain TIMED OUT".

Then what other software do you have that fills a security role or what setting on the router or modem need fixing. I use a wifi router and 3G box at work and while the service is not great it does function and ping times are quite reasonable (we are on the out limits of the 3G coverage 1 or 2 bars)

How does inactive connection timeout attribute in weblogic works ?

Lets say If there is a connection leakage in my application running on weblogic server 10.3.4 and I want to regain the unclosed connection.
After going through some documentation I found out that setting inactive connection timeout to a positive value can fix this issue.
With setting the above attribute will the weblogic server close any connection object which is inactive for specified number of seconds or it acts on only
those connection objects which has lost all the references to it ?
demonstrating the query by an example ,
Lets say I have two connection objects con1 & con2 taken from a defined datasource in the weblogic.
the inactive timeout has been set to 10 seconds.
In a given thread lets say con1 does some db operation and then after being done, con2 is used for another db operation for greater than 10 seconds.
Will the object con1 be still available for db operation or we need to take a fresh connection from the pool ?
Thanks,
Tarique
Edited by: user779368 on 30-May-2011 06:29

Any connection that has been reserved by an application, and not used for longer than
the inactive timeout limit, will be taken back by the pool. All it's sub-objects will be closed etc.
In your case, you would lose con1 while con2 was being used. Ideally, you would get
any/either of those connections at the instant you really need it. Then, ideally use it
till you can close it. But if you are doing transactions or a job that need connections,
but can't avoid having them idle for X seconds, then set your inactive timeout larger than X.

Connection timeout in web service calls

Hi,
We have a clustered weblogic 10gR3 environment where two nodes are for ILOG rule engine, two nodes for Oracle BPM engine and four nodes for Oracle BPM workspace. All the webserices calls are SOAP over HTTP. All the webservices to rule engine and DBAdapter are hosted on Oracle Service Bus. Some of the webservice calls when invoked throw a connection timeout exception. Can any one help on how to debug this or the possible causes for this scenario? The same webservice call when invoked or retried after a few minutes is working fine. Below is the stack trace:
Stacktrace: java.net.ConnectException: Connection timed out: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
     at java.net.Socket.connect(Socket.java:519)
     at sun.reflect.GeneratedMethodAccessor212.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:153)
     at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:120)
     at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
     at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
     at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
     at org.apache.axis.client.Call.invoke(Call.java:2748)
     at org.apache.axis.client.Call.invoke(Call.java:2424)
     at org.apache.axis.client.Call.invoke(Call.java:2347)
     at org.apache.axis.client.Call.invoke(Call.java:1804)
     at fuego.soaptype.SoapCall.invoke(SoapCall.java:234)
     at fuego.soaptype.SoapObject.invoke(SoapObject.java:309)
     at fuego.lang.Invokeable.invokeImpl(Invokeable.java:234)
     at fuego.lang.Invokeable.invokeDynamic(Invokeable.java:188)
     at xobject.EDP.EDP.EDPObject.helpBusinessRules(EDPObject.xcdl:59)
     at oracle.EDPPROCESS.Default_6_6.Instance.CIL_checkRTDIInformation(Instance.xcdl:12)
     at oracle.EDPPROCESS.Default_6_6.Instance.CIL_checkRTDIInformation(Instance.xcdl)
     at sun.reflect.GeneratedMethodAccessor7653.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:1083)
     at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1278)
     at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.runCil(ComponentExecutionMicroActivity.java:126)
     at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.execute(ComponentExecutionMicroActivity.java:84)
     at fuego.server.execution.microactivity.MicroActivityEngineExecutionHandler.executeActivity(MicroActivityEngineExecutionHandler.java:57)
     at fuego.server.execution.ImmediateActivity.execute(ImmediateActivity.java:42)
     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
     at fuego.transaction.TransactionAction.startNestedTransaction(TransactionAction.java:527)
     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:548)
     at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
     at fuego.server.execution.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:62)
     at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42)
     at fuego.server.execution.ToDoItem.executeAutomaticWork(ToDoItem.java:261)
     at fuego.ejbengine.ItemExecutionBean$1.execute(ItemExecutionBean.java:223)
     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
     at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
     at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
     at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
     at fuego.ejbengine.ItemExecutionBean.processMessage(ItemExecutionBean.java:209)
     at fuego.ejbengine.ItemExecutionBean.onMessage(ItemExecutionBean.java:120)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4547)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:4233)
     at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3709)
     at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5058)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

EJP, thanks for confirming that the generated code is incorrect and that the finally block should be used.
Jschell, thanks for the suggestions and the trust in my technical skills... though writing my own generator seems a bit of too great enterprise for me haha!
The generator is not open source so I cannot modify it and using another one is not an option as it is the "standard" in the company.
In the end I decided for writing a post processor (in the form of a JDeveloper extension) to fix the code after it is generated. I will also probably be filing a bug for it with Oracle.
Cheers,
Luis

Web Service connection timeout

How to configure the web service connection timeout properties (eg. weblogic.wsee.transport.connection.timeout) in configuration files rather setting them at client's stub code?
Help is appreciated.

This might be due to following reasons.
Please check whether firewall exist between Pi and external system. If so check with network team weather port or connectivity is established between PI server and external system. This should be the main reason. Also check the target URL and see whether you can able to consume the webservice directly from Soapui without PI. If your workstation is within PI's landscape and you see the same timed out error, then the network connectivity is the issue. Ask them to enable the port.

Weblogic DB connection pool load balancing problem

hi all,
here is a strange issue. We have a clustered weblogic environment with2 servers. And the application is deployed to cluster. But strangely when we check the active connections for the connection pool that is being used by the application, we see that 2nd server has more connections when compared to 1st server, lets say 1st server has 4 active connections, 2nd server has 50 connections, What might be the problem.
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/jdbc-data-source" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/jdbc-data-source http://www.bea.com/ns/weblogic/jdbc-data-source/1.0/jdbc-data-source.xsd">
<name>##########</name>
<jdbc-driver-params>
<url>jdbc:oracle:thin:@hostname:portnumber:Schema</url>
<driver-name>oracle.jdbc.OracleDriver</driver-name>
<properties>
<property>
<name>user</name>
<value>#####</value>
</property>
<property>
<name>portNumber</name>
<value>#####</value>
</property>
<property>
<name>SID</name>
<value>######</value>
</property>
<property>
<name>serverName</name>
<value>hostname</value>
</property>
</properties>
<password-encrypted>##########</password-encrypted>
<use-xa-data-source-interface>false</use-xa-data-source-interface>
</jdbc-driver-params>
<jdbc-connection-pool-params>
<initial-capacity>0</initial-capacity>
<max-capacity>75</max-capacity>
<capacity-increment>5</capacity-increment>
<shrink-frequency-seconds>900</shrink-frequency-seconds>
<highest-num-waiters>2147483647</highest-num-waiters>
<connection-creation-retry-frequency-seconds>0</connection-creation-retry-frequency-seconds>
<connection-reserve-timeout-seconds>10</connection-reserve-timeout-seconds>
<test-frequency-seconds>60</test-frequency-seconds>
<test-connections-on-reserve>true</test-connections-on-reserve>
<profile-harvest-frequency-seconds>300</profile-harvest-frequency-seconds>
<ignore-in-use-connections-enabled>true</ignore-in-use-connections-enabled>
<inactive-connection-timeout-seconds>0</inactive-connection-timeout-seconds>
<test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
<login-delay-seconds>0</login-delay-seconds>
<statement-cache-size>10</statement-cache-size>
<statement-cache-type>LRU</statement-cache-type>
<remove-infected-connections>true</remove-infected-connections>
<seconds-to-trust-an-idle-pool-connection>10</seconds-to-trust-an-idle-pool-connection>
<statement-timeout>-1</statement-timeout>
<profile-type>0</profile-type>
<pinned-to-thread>false</pinned-to-thread>
</jdbc-connection-pool-params>
<jdbc-data-source-params>
<jndi-name>##########</jndi-name>
</jdbc-data-source-params>
</jdbc-data-source>

are you using any front end web server or hardware load balancer ? verify your load balancing if it's happening or not properly between your clustered managed servers.
Regards
Mukesh Negi
http://weblogicserveradministration.blogspot.com/

Connect timeout for InitialDirContext creation doesn't always work

Hi,
I've got a problem with the InitialDirContext creation timeout settings.
If I set com.sun.jndi.ldap.connect.timeout=5000, and I "mistype" the connection URL to something non-existent, or the port to something where nothing is listening, then this timeout kicks in, and the InitialDirContext creation fails (this is good so far).
However, if I set the URL to port 25 (for example), where another service (in this case SMTP) is listening, then the InitialDirContext creation will hang for ever waiting for a valid ldap response to the login request.
What other timeouts could I set for jndi to avoid this?
I've seen that this bug (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4410856) was closed as fixed, but I don't think it's really fixed (or if it is, I haven't found what the correct procedure would be to fix this issue)
java version is:
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode)
thanks for any help,
regards,
mitch
Message was edited by:
peter.radics

Szia P�ter!
B�nhegyi Kristof vagyok �s szeretn�k veled besz�lni, abban az esetben ha te vagy az a Radics P�ter aki a Magyar Tv 2 n�l dolgozt�l anno. K�rlek keress meg a krisban(kukac)msn.com mail cimen.
�dv�zlettel
B�nhegyi Kristof

SMTP Connection Broken

while trying to send some emails the message bounce back.
there's an error at the end of the bounced messages.
"The Sun SMTP Transport service failed to deliver the message to this recipient on server smtp.vera.be for the following reason: 1 SMTP connection broken (command)"
how could I troubleshoot this problem? i really don't know what is going on.

mario_garcia wrote:
while trying to send some emails the message bounce back.
there's an error at the end of the bounced messages.
"The Sun SMTP Transport service failed to deliver the message to this recipient on server smtp.vera.be for the following reason: 1 SMTP connection broken (command)"
how could I troubleshoot this problem? i really don't know what is going on.Let's start with -- what email client are you using?
Based on the error message I would guess this is Outlook running the Sun Outlook Connector.
What versions of Messaging Server (./imsimta version) and Outlook Connector are you running?
What was different about this particular message -- was it a large email, was the email sent from home (slow internet link etc.), was it to a particular problem user?
Can they reproduce this error?
Did you have MTA problems at the time, can you see the matching connection attempt in your mail.log_current?
Outlook Connector has a default 60 second timeout when attempting to delivery an email. If this timeout is exceeded the connection will be dropped and the customer will see this message. The following registry setting controls the timeout:
"HKEY_CURRENT_USER\Software\Sun Microsystems\Outlook Connector\Connection Time Out"
Regards,
Shane.

Is there a risk of setting a console connection timeout and what is the recommended setting?

Is there a risk of setting a console connection timeout and what is the recommended setting? Please suggest if there is any best prctice documentation that can be referred.

Hi Henrik
depend on what you need or what your security policy says for my lab gear i use 60 minutes. because i know how can access this. if you have gear outside in insecure space set it to a minimum or disable the console. everybody how can access your gear can break in. simple restart and boot w/o config. and you are in.
it realy depends how secure is your space and how much security you need.
and than the settings for policy have to match, what sec do you have if your console login and logout is secure. but when you restart you can simple break in by starting w/o config and than load it.
HTH
Patrick

I am getting a "connection timeout" message when trying to access my Airport Extreme with various laptops, Play Station 3 and Wii. My Airport Extreme is about a month old; it was working fine until about a week ago. C

I am getting a "connection timeout" message when trying to access my Airport Extreme with various laptops, Play Station 3 and Wii. My Airport Extreme is about a month old; it was working fine until about a week ago. Suddenly, the "timeout" is not allowing me to connect to my wireless network.

It could be that there's a new source of interference.
Use the advice in the second message of this thread to investigate the signal and noise levels that each client sees:
http://discussions.apple.com/thread.jspa?threadID=2347845&start=1
By the way, you've been misled by the poor field labeling into trying to type your entire message into the subject field, instead of putting a one-line topic description there.

Why do I keep getting a "connection timeout" error on my macbook pro?

What seems to be on some kind of time schedule, my network connection times out. The message "a connection timeout occured" is displayed, rendering my attempts at re-connection useless. After hours of troubleshooting(my router included) and checking out other Mac forums, I have no solutions but to power cycle my router. This pretty much makes my MB useless unless using a wired internet connection outside of my home network. I've done tons of research online and have encountered hundreds of people with the same problem. My machine is a late 2011 Macbook Pro. PLEASE HELP

Check the time and date, updates with apple' time servers
https://discussions.apple.com/docs/DOC-3046

Time Capsule woes -- Connection timeouts and can't connect with one Macbook

This is my second Time Capsule. Here's the scenario:
I have a Netopia 3347 DSL modem. That feeds into the Time Capsule in bridge mode. There is a MacBook (metal case), iBook (yes, it's old), two iphones, a color printer and an iPad that can all connect to the Time Capsule just fine. The problem is my MacBook can't connect. The offending computer is a 2.2Ghz Intel Core 2 Duo running SL 10.6.6. This computer can connect to the Netopia just fine, so I know its internal Airport works. After several go arounds with Apple tech support, I'm still nowhere.
Here are the symptoms:
1. I can see the TC's network SSID in the airport pull down menu. If I select the TC, a popup appears and asks for a password. If I enter the password, I'll get a connection timeout error.
2. On the rare occasions where it does connect, I can't open a webpage. Network diagnostics has red dots for ISP Internet and Server
3. On the even rarer occasions where it does connect, and I can access a webpage, it's unbearably slow, and the no-surf problem reappears after a few seconds. The red dots on the Network Diagnostics reappear.
Apple tech support was not helpful. I've power cycled everything a million times (and that doesn't explain why other computers can connect.) I know it's not my computer, because it can connect to the Netopia just fine.
I am STUMPED.

Magnificent! Problem solved... Isn't there a "this solved my problem" button somewhere?? Thanks and thanks again!

Macbook pro keeps saying connection timeout, and it used to connect to the internet fine. what's up, why can't it find and automatically connect to the internet anymore???

Macbook Pro keeps saying connection timeout and it used to connect to the internet fine. What's up, why can't it find and automatically connect to the internet anymore???

Like this: https://discussions.apple.com/thread/2775868?tstart=0 ?

Connection Timeout after updating to 10.6.6

Dear Friends
I've got Macbook Pro mid 2010, when I was on 10.6.5 there was no problem connecting to Wi-Fi but after the magic update, I always got "Connection Timeout". another thing to add, I can connect to any network via windows 7 I installed on my macbook.
Message was edited by: mutant59

My two cents is that I have had some type of network problem since install Snow Leopard. I even went back wiped drive and did clean install. Seems their is a problem but not sure if its multiple problems or just one. Safari seems to load pages at a crawl at times. I did several speed tests and found the WIFI connection noticeably slower (about half) compared to my Windows Vista computers running WIFI. Even though my MacBook has N version connection and the Vista ones G.
I have tried different DNS servers and nothing seems to help. The router is the second one I tried. I had a Linksys wrt54 then bought a Belkin F5d8236-4 and both have no effect on the problem. Even a different browser did not help. I have simply determined that Apple needs to fix something in Snow leopard.

Weblogic smtp connection timeout!

Similar Messages

Maybe you are looking for