Connection rejected by server

Hi Everyone,
i have installed FSM2 and IISwin2003 and Flash8 on the same
server,
my rtmp is : rtmp://127.0.0.1/myapp2/myapp2.flv
it works fine on local, but when a clinet tries to browse it
over same LAN , the client gets the error below :
Connection rejected by server. Reason : [ Server.Reject ] :
(_defaultRoot_, _defaultVHost_) :
Application (myapp2) is not defined.
what im doing wrong ? pls help..

It because you're using the localhost IP, where you should be
using your LAN IP.

Similar Messages

Connection rejected, the server is in a running state.

Have deployed webservice within weblogic. WLS starts up fine. Users can access the webserver, after a period of time, webservice hangs up and users that try to connect recieve this following message, I also see this in the weblogic.log
The server is not able to service the request. Connection rejected, the server is in a running state. Starting service weblogic.application.internal.BackgroundDeploymentService$WaitForBackgroundCompletion, 110 of 112. Last service weblogic.deploy.service.internal.adminserver.HeartbeatService took 2ms.
I have no idea what to do. Right now the only way to bring back the webservice is to stop the WLS process and then restart. The service can fail anywhere from within about 20 mins of WLS start-up or about within 12hrs.
Any Ideas what this error is trying to tell me.. Is there a more permanent fix other that restarting the WLS process.
Thank you

wow same case here in weblogic 10.2. But I have not deployed any EJB or JMS service . It shows in Console that "Mejb" Stateless service is running. I use https port from SSL mostly.
the error was:
The Server is not able to service this request: [Server:002623]Connection rejected, the server is in the RUNNING state. Starting service weblogic.jms.JMSServicePostDeploymentImpl, 120 of 122. Last service weblogic.ejb.container.timer.EJBTimerStarterActivator took 2ms.
The client could not connect to https pages then.
It occured for hours.
I saw a solution that said:
BEA-002623
Notice: Connection rejected, the server is in the state state.\r\n Starting service svr, num of total.\r\n Last service last took timems.
Description
Clients are trying to connect to the server before it is in the RUNNING state.
Cause
Clients are trying to connect to the server before it is in the RUNNING state.
Action
When I was not starting any service why should it say so?
I am in a big mess in my production server .
Dear oracle weblogic geeks please come forward and show your ability.
I cannot restart my server every 1 hour or 4 hour or 12 hour.
I use Jrockit 1.6
ojdbc6 driver
I also use a connection pool from with in Weblogic to test my Oracle 10.2 RAC.
let me know asap if any solution exist.

Connection rejected by server. Reason; Warning

Hello,
When I connect from FMLE to FMSS server I see warning in /var/log/messages.
Oct 23 18:44:56 post Javascript[1951]: Connection rejected by server. Reason : [ AccessManager.Reject ] : [ code=403 need auth; authmod=adobe ] :
Oct 23 18:44:56 post Javascript[1951]: Connection rejected by server. Reason : [ AccessManager.Reject ] : [ authmod=adobe ] : ?reason=needauth&user=administrator&salt=WT9Vaw==&challenge=6JSMIg==&opaque=6JSMIg==
Everything works fine. Should I be concerned about this message?
FMLE is win XP SP3 versin 3.2
FMSS is Linux RH6 version 4.0

Darius, I think you'll get a better answer in the Flash Media Live Encoder forum:
http://forums.adobe.com/community/flash/flash_media_live_encoder?view=discussions

Javascript[9970]: Connection rejected by server.

Dec 7 07:20:38 networkvision Javascript[9970]: Connection rejected by server. Reason : [ Server.Reject ] : Virtual host my domain is not available.
i cant logint to the admin console,
centos 6.4
32 gb ram
zpanel

Darius, I think you'll get a better answer in the Flash Media Live Encoder forum:
http://forums.adobe.com/community/flash/flash_media_live_encoder?view=discussions

HELP! connection rejected by server

A client with Contribute 3.1 suddenly cannot connect to the
server. "Contribute could not connect because the server is down or
not accepting connections."
I've removed all the Contribute
settings and reinstalled them.
the client has updated to the latest version of 3.
rollbacks have been disabled
ftp optimization has been
disabled
passive ftp is NOT enabled, but then
I don't use it with my regular ftp software

Have you contacted your provider to see if anything has
changed on their part?
Has your client installed new software/hardware concerning
the connection?
Have you tried passive ftp?

Upgrade FMS2 - Streaming Server 3.5 - Video not streaming - NetConnection.Connect.Rejected

I have Flash Media Server 2 set up with a simple bandwidth detection application (with serverside code), and a videoplayer application (no serverside code). I have upgraded to Flash Media Streaming Server 3.5 and have managed to successfully get video to stream using the basic examples on the startup screen both locally and from another machine. However, when I try and connect to either the bandwidth detection application, or the videoplayer I get the error message:
NetConnection.Connect.Rejected
[ Server.Reject ] : (_defaultRoot_, _defaultVHost_) : Application (**my appname**/) is not a valid signed application; loading access denied.
I saw another post in this forum saying that for custom applications you need Flash Media Interactive Server instead of Streaming Server. This worries me as I'm quite far down this route now and don't want to tell my boss that actually we need to find another £2k to make this a viable solution! But looking at the credentials of Flash Media Streaming server (http://www.adobe.com/products/flashmediaserver/compare/), it seems to be that what I want to do is viable. At worst I would have thought that only the bandwidth application would be a problem as it has serverside code. But even so, the Streaming Server apparently does have bandwidth detection. How does this work then?
By having the Steaming Server am I somehow tied into Adobe video players if I want to use the streaming capabliities? Am I not able to have my own named application? Or is it simply likely that there is some setting somewhere I have missed which is causing the error.
Any advice would be much appreciated as I'm struggling to get to the root of these answers on my own.

You just need to define handlers specially onBWDone on client side to do Bandwidth detection. Just check example "Bandwidth" in documentation/samples/Bandwidth/Bandwidth.as.
Since you are using VOD, i think you can just pass "true" as second parameter when you make nc.connect call in you client side and VOD application would make call to checkBandwidth and would call onBWDone when it finishes bandwidth detection. Read more about this in Client API documentation in SSLR.pdf and Dev_Guide.pdf.
Also Adobe has come with advanced Bandwidth detection which you can do using client-side Flash Player API's - Please check this link for more info:http://www.adobe.com/devnet/flashmediaserver/articles/dynstream_on_demand.html
Also you can NetStreamInfo documentation which should be present in AS3LR (check documentation folder of FMS)

Connection to db rejected.Cannot connect to MySQL server

here is the excaption
connectToDb:02 - connection to db rejected.Cannot connect to MySQL server on localhost:3306. Is there a MySQL server running on the machine/port you are trying to connect to? (java.net.BindException)
and her is the class
import java.io.*;
import java.sql.*;
import java.util.*;
public class DBconnect
{ final static private String _url        = "jdbc:mysql://localhost:3306/diamonds";     //final static private String _driver     = "sun.jdbc.odbc.JdbcOdbcDriver";
    //final static private String _url        = "jdbc:odbc:diamonds";     //final static private String _driver     = "sun.jdbc.odbc.JdbcOdbcDriver";
    public Connection     _con                     = null;
     //private static Driver          driver          = null;
     private static Properties     properties     = null;
     Statement stmt                                 = null;
     public PrintStream     out;
        **connectToDb **
        public void connectToDb()        throws IOException
        //connect to the server and open the database
         try{
               Class.forName("org.gjt.mm.mysql.Driver");
               //Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
               //driver = (Driver)Class.forName (_driver).newInstance();
               properties = new Properties();
            properties.put("user","sa");
               properties.put("password","");
        catch (ClassNotFoundException e)
               System.out.println("class not found:");
               e.printStackTrace();
          catch (Exception e) {
                    e.printStackTrace();
             throw new IOException("connectToDb:01- JDBC driver not found."+e.getMessage());
     synchronized void open()throws Exception
          try
               if(_con == null)
                    try
                         _con = DriverManager.getConnection(_url,properties);
                         //_con = driver.connect(_url,properties);
                    catch (SQLException e)
                         e.printStackTrace();
                         System.out.println("connectToDb:02 - connection to db rejected."+e.getMessage());
                    stmt = _con.createStatement();
          catch (Exception e)
               e.printStackTrace();
               System.out.println("connectToDb:02 - connection to db rejected."+e.getMessage());
     synchronized void close()
          try
               if(_con != null)
                    if(!_con.isClosed())
                         stmt.close();
                         _con.close();
                         _con = null;
          catch (Exception e)
               System.out.println("es:fail to close connection!!");
}the problem occars when there are a lot of queries that the project is sending to the DB (about 10000) the last half queries fails and send an excaption .
after 2 minutes the system seems like working fine.
I am stack with this problem about a year and cann't resolve it.
any idea????
regards
amnon m

well...new it seems to work fine, but is it ok to
keep connection open for good ???
isn't there any other alternative ???I am bit confused are you pooling the connections?
If so, actually the connections will not always stay open.. they will time out after a while when they are not in use but to specifically answer your question.. how could it possible be a bad thing. If the server/your app was getting bogged down with opening and closing connections then pooling solves this..
Finally as to your question of the alternatives... if the problem was opening and closing connections and reusing them through a pool solved this then I think the answer is no. If you don't like a specific part of the way the pool works it is probably configurable in some way and you could always implement your own pool.. although I wouldn't overly recommend that. The bottom line is that you need to keep your connections open for reuse.. pooling is the simplest way to achieve this.. but no there is no alternative to keeping your connections open if you are having the load problems you described.

Radius connection being rejected by server

From my Cisco 881 k9 router I run test aaa group radius server 10.20.1.10 username password legacy - -and I get user authentication request was rejected by server --
using windows 2008 as Radius server -- the IP address of Cisco Router is configured as client on server end -- Are the AAA parameters supposed to be set a certain way for access to an external Radius server for authentication?

Mar 5 09:41:05.184: RADIUS: Pick NAS IP for u=0x8524DF98 tableid=0 cfg_addr=10.20.1.250
Mar 5 09:41:05.184: RADIUS(00000000): Config NAS IPv6: ::
Mar 5 09:41:05.184: RADIUS: ustruct sharecount=1
Mar 5 09:41:05.184: Radius: radius_port_info() success=0 radius_nas_port=1
Mar 5 09:41:05.184: RADIUS(00000000): Send Access-Request to 10.20.1.10:1645 id 1645/25, len 58
Mar 5 09:41:05.184: RADIUS(00000000): Sending a IPv4 Radius Packet
Mar 5 09:41:05.184: RADIUS(00000000): Started 5 sec timeout
Mar 5 09:41:05.188: RADIUS: Received from id 1645/25 10.20.1.10:1645, Access-Reject, len 20
Mar 5 09:41:05.188: RADIUS: saved authorization data for user 8524DF98 at 0

How can I adjust iPad settings when I get message, "Sender rejected by server"?

I have recently had difficulty sending and receiving mail on my iPad, but not at the same time! This was NOT the case for the first 8 months I had my iPad. I changed nothing but suddenly (Oct 6th, 2011) could not get my mail. Bellsouth said, "User name/or password is incorrect", but it was NOT. Thinking this was a Bellsout issues, I got some help from AT&T Tech support. Updates have been synced on laptop & iPad.
As of Oct 12, 2011, I can receive mail BUT I CANNOT SEND MAIL & I get a message saying, "...the sender address was rejected by server." This must be an iPad setting isuue b/c I can send and receive mail at the same address on my laptop.
I have verified all settings but need to know if there should be ONLY ONE OUTGOING SERVER TURNED ON (Primary Server) even though there are other SMTP servers listed that are not turned on. (There IS a notation that says, "If mail is unsuccessful using the primary server, it will try the other SMTP servers in succession." This is what makes me wonder if they should be turned ON or OFF.) Nothing seems to work. I humbly seek your enlightenment!! THANK YOU.

It is seen when I connect cable from ipad to dekstop then I see the message as "Ipad is in recovery mode." How can be solved this problems ?

[Forum FAQ] "Unable to connect to the server by using Windows PowerShell Remoting" error while installing RDS roles on Server 2012 R2

When you try to install RDS role on server 2012 R2 using standard deployment, this issue may occur (Figure 1).
“Unable to connect to the server by using Windows PowerShell remoting”.
Figure 1: Unable to connect to the server by using Windows PowerShell remoting
First of all, we need to verify the configurations as it suggested:
1. The server must be available by using Windows PowerShell remotely.
2. The server must be joined to a domain.
3. The server must be running at least Windows Server 2012 R2.
4. The currently logged on user must be a member of the local Administrators group on the server.
5. Remote Desktop Services connections must be enabled by using Group Policy.
In addition, we need to check if the “Windows Remote Management “service is running and related firewall exceptions have been created for WinRM listener.
To enabling PowerShell remoting, we can run this PowerShell command as administrator (Figure 2).
Enable-PSRemoting -Force
Figure 2: Enable PowerShell Remoting
However, if issue persists, we need to check whether it has enough memory to work.
By default, remote shell allots only 150 MB of memory. If we have IIS or SharePoint App pool, 150 MB of memory is not sufficient to perform the remoting task. Therefore, we need to increase
the memory via the PowerShell command below:
Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000
Then, you need to restart the server and the issue should be resolved.
You can get more information regarding Remote Troubleshooting by below link:
about_Remote_Troubleshooting
If you need further assistance, welcome to post your questions in the
RDS forum.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

i found another possible reason, this solution worked for me:
http://oyvindnilsen.com/solution-for-powershell-remoting-error-it-cannot-determine-the-content-type-of-the-http-response-from-the-destination-computer/
I tried to set up powershell remoting on a server and kept getting this error:
Enter-PSSession : Connecting to remote server failed with the following error message : The WinRM client cann
ot process the request. It cannot determine the content type of the HTTP response from the destination comput
er. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help to
pic.
After a bit of troubleshooting I discovered that the problem was that the authentication packets was to big (over 16k), this will cause WinRM to reject the request. The reason for authentication packets getting too big can be because the user is member of very
many security groups or in my case because of the SidHistory attribute.
The solution was to increase the MaxFieldLength and MaxRequestBytes keys in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters
If the keys does not exists you can create them, be sure to use the DWORD type.
I sat MaxFieldLength to DEC value 40000 and MaxRequestBytes to DEC value 32768 and rebooted the server. Problem solved.

Re: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

Hi,
I'm encountering an issue with "Named Pipes Provider, error: 40 windows" and am having problems determining how to fix it due to the environment I'm using. I have two SQL Servers installed on two separate Win2K3 Server boxes, one is SQL Server 2000 and the other is SQL Server 2005. The SQL Server 2000 contains the actual application data. The 2005 database is used only for Reporting Services. I've set up the reports on SSRS such that their datasources hit the 2000 server. This is using SQL Server authentication.
When testing the reports via SSRS (in Visual Studio 2005), the connection to the data works and the reports are generated fine. When I deploy them to the reporting server and launch IE to test locally (still on the 2005 box), I get this "Named Pipes Provider, error 40" issue. I made sure that Named Pipes and TCP were enabled and the port set at 1433 (to match that on the 2000 box).
Now I changed the datasource's authentication from SQL Server to Windows authentication. I tested this in SSRS and this works too. When I redeployed the reports with this authentication change, testing the reports via IE locally (on the 2005 box) worked. Great. Now when I open IE on an external box, i.e. on the 2000 box, and try to test the reports, I get this same error 40 issue. I've been through a few threads describing the error 40, fiddling around with the SQL Server configuration as well as SSRS, to no avail. I have a feeling this error 40 issue has to due with permissions/authentication between the SQL Server boxes but I can't really be sure. Anyone have any ideas on how to troubleshoot my situation. Thanks.
larry

Named Pipes Provider, error: 40 - Could not open a connection to SQL Server :
I. Incorrect connection string, such as using SqlExpress.
Check out: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=558456&SiteID=17
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1245564&SiteID=1
The typical error when dealing with Express includes:
a. User is not aware of SqlExpress was installed as a named instance, consequently, in his/her connection string, he/she only specify ".","localhost" etc instead of ".\SqlExpress" or "<machinename>\Sqlexpress".
b. Np was disabld by default after installing SqlExpress.
c. If Sqlexpress was installed on the remote box, you need to enable remote connection for Express.
Please read the following blog for best practice of connecting to SqlExpress.
http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx
II. Named Pipes(NP) was not enabled on the SQL instance.
Check out: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=136253&SiteID=1
Oppose to SQL 2000 which turn on all protocols, SQL 2005 SKUs turn off NP by default. So, when you see this error, please check:
1) Go to SQL Server Configuration Manager, See Server has NP enabled.
2) %windir%\program files\microsoft sql server\mssql.1\mssql\log, notepad ERRORLOG, see whether Server is listening on NP. You should see "Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ] or [\\.\pipe\mssql$<InstanceName>\sql\query]"
3) Notice that "sql\query" is the default pipe name, so you need to know server is listening on which pipe name. eg: if you specify server pipe name is "sql\query1", then you would see in the errorlog that server listening on [ \\.\pipe\sql\query1 ], and go to SQL Server Configuration Manager, click client Named Pipe properties, see whether the pipe name is same with the one server listening on.
4) If you are using SQL Native Client ODBC/OLEDB provider({SQL Native Client} or SQLNCLI), go to SQL Configuration Manager, click client protocols, make sure NP and TCP are both enabled. Right click properties of NP, make sure client is using the same pipe name as server for connection.
5) If you are using MDAC ODBC/OLEDB({SQL Server} or SQLOLEDB) provider, in command line, launch "cliconfg.exe" and make sure NP enabled and right pipe name specified.
III. Remote connection was not enabled.
Check out: when you right click on the Server in SQL Server Management Studio, in Connections, the Remote server connections part, you have enabled the "Allow remote connections to this server" check box
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=322792&SiteID=1
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=763875&SiteID=1
If you are making a remote connection, namely, your target SQL Server is on the different box as client application, you might need to check whether:
a. "File and Printer Sharing" was opened in Firewall exception list.
b. Please see the blog for enabling remote connection for express and troubleshooting tips of remote connection.
http://blogs.msdn.com/sql_protocols/archive/2005/11/14/492616.aspx
http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx
IV. Server not started, or point to not a real server in your connection string.
Check out: Open SQL Server Surface Area Configuration and ensure all the required services are started, Remote Connections are configured.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=348662&SiteID=1
a. use "sc query mssqlserver" for default instance or "sc query mssql$<instancename>" to make sure SQL Server was started. Sometimes, reseason behind the broken of your client application w/ this error:40 might be SQL server restarted and failed, so, it'd better for you to double check.
b. User specified wrong server in their connection string, as described in the forum discussion, "MSSQLSERVER" is an invalid instance name. Remember, when you connect to default instance, <machinename> could be best representitive for the instance, when you connect to a named instance such as sqlexpress, you should specify <machinename>\<instancename> as data source in your connection string.
V. Other reasons such as incorrect security context.
Check out: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=192622&SiteID=1
Such error also occured during user operation such as moving database or db mirroring or cluster, any DB OP that might invovle different sql instances, namely, the destination database is located in another sql instance and user is not aware of the state of the destination. I recommend you first isolate whether this fail is during connection stage or data operation stage.
a. During data operation, you are normally asked to type in the destination server name whether it is default to "(local)" or another server "<remotemachinename>". So, remember the exact string that represent the target instance, then when the error repros, open command line, use "sqlcmd -S<representitive> -E" ,see what happens, if the connection fail, please follow up above I - IV troubleshooting lists. otherwise continue.
b. If you can make basic conection, but still face the error, then there must be something that server reject the connection or client close the connection for some reason.
VI. Please try basic connectivity tests between the two mahcines you are working on. One simple way to verifty connectivity is to use command line tools, such as osql.exe. For example, osql -E -Stcpervername\instancename. If it connects cross-machine successfully, please also verify that your connection string in your scenario is correct.
Here are some blogs which could be helpful: just follow the basic connectivity troubleshooting guidelines on the SQL Protocols blog, see:
SQL Server 2005 Connectivity Issue Troubleshoot - Part I
http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx
and
SQL Server 2005 Connectivity Issue Troubleshoot - Part II
http://blogs.msdn.com/sql_protocols/archive/2005/10/29/486861.aspx
Hope this helps.

WEBLOGIC 5.1SP9 : ListenThread Connection rejected: 'Login timed out after 5000 msec.

I'm running WL Express 5.1SP9 on a NT 4 server, Oracle 8.1.7 and an j2EE
application from an editor.
With the previous version of the application i wasn't having any problem,
since I installed the new version in the same environnement, I'm getting the
message when running the application :
"<E> <ServletContext-General> Warning: One of the getParameter family of
methods called after reading from the ServletInputStream(), can't mix these
two! "
"<W> <ListenThread> Connection rejected: 'Login timed out after 5000 msec.
The socket came from [host=10.56.13.202,port=1539,localport=80] See property
weblogic.login.readTimeoutMillis to increase of decrease timeout. See
property weblogic.login.logReadTimeoutsProp to turn off these log
messages.'"
The editor says it comes from WL configuration
Please Help !
Christophe

hi.
I'm not clear on this - what do you mean you are running a J2EE application from
an editor?
Also the error is coming from a servlet. Is one of your servlets calling a
getParameter() method after reading from the ServletInputStream()? If it is it
should be corrected.
Regards,
Michael
Christophe Chastang wrote:
I'm running WL Express 5.1SP9 on a NT 4 server, Oracle 8.1.7 and an j2EE
application from an editor.
With the previous version of the application i wasn't having any problem,
since I installed the new version in the same environnement, I'm getting the
message when running the application :
"<E> <ServletContext-General> Warning: One of the getParameter family of
methods called after reading from the ServletInputStream(), can't mix these
two! "
"<W> <ListenThread> Connection rejected: 'Login timed out after 5000 msec.
The socket came from [host=10.56.13.202,port=1539,localport=80] See property
weblogic.login.readTimeoutMillis to increase of decrease timeout. See
property weblogic.login.logReadTimeoutsProp to turn off these log
messages.'"
The editor says it comes from WL configuration
Please Help !
Christophe--
Michael Young
Developer Relations Engineer
BEA Support

Connection rejected ..

When running the app against a load tool, wl 5.1 running sp9 almost stops
 handling requests after a say considerable size of requests and throws
 serious of the attached message.
 I guess wls is running out of sockets, but the app is perfect in normal
 conditions.
 When would this happen?
 <W> <ListenThread> Connection rejected: 'Login timed out after: '5000' ms on
 socket: 'Socket[addr=34.22.0.125/34.22.0.125,port=3345,localport=7001]''
 Thanks
 Madhu


Thanks Mike. I'm using Apache JMeter, test machines and server hooked to a
 single switch. Another issue that I'm seeing the o/p queue length on the NIC
 on the server is pretty high, so I guess that NIC takes all the request and
 it doesn't reach weblogic. Any suggestions?
 - Madhu
 "Mike Reiche" <[email protected]> wrote in message
 news:[email protected]...
 >
 > WLS prints out 'Login timed out' if something connects to it
 > but does not send any data for five seconds.
 > If you want to see this - then telnet <weblogic-host> 7001, and
 > wait for five seconds.
 >
 > Check what your load tool is doing. Is the machine where you are
 > running the load tool bogged down?
 >
 > Mike
 >
 > "Madhu" <[email protected]> wrote:
 > >When running the app against a load tool, wl 5.1 running sp9 almost stops
 > >handling requests after a say considerable size of requests and throws
 > >serious of the attached message.
 > >
 > >I guess wls is running out of sockets, but the app is perfect in normal
 > >conditions.
 > >
 > >When would this happen?
 > >
 > ><W> <ListenThread> Connection rejected: 'Login timed out after: '5000'
 > >ms on
 > >socket: 'Socket[addr=34.22.0.125/34.22.0.125,port=3345,localport=7001]''
 > >
 > >Thanks
 > >Madhu
 > >
 > >
 > >
 > >
 > >
 >

Re: Connection Rejected:Login Timed Out

This sounds like a slow client to me. Specifically the client isn't sending
enough data within the first 9 seconds for the server to determine which
protocol the client is using.
Srikant, [email protected], http://weblogic.bea.com/, etc.
Ajit wrote:
"Hi, I went through the various versions of Login Timed Out problems.This is my version. My Web server currently running on Weblogic Web Server 5.1.0 with service pack 9 is shutting down frequently.My server platform is SUN SOLARIS 2.6 5/98. The following messages reflect in the weblogic.log Thu Aug 02 08:49:52 EDT 2001:<W> <ListenThread> Connection rejected: 'Login timed out after 9000 msec. The socket came from [host=147.154.232.3,port=19431,localport=80] See property weblogic.login.readTimeoutMillis to increase of decrease timeout. See property weblogic.login.logReadTimeoutsProp to turn off these log messages.'Thu Aug 02 08:50:13 EDT 2001:<W> <ListenThread> Connection rejected: 'Login timed out after 9000 msec. The socket came from [host=147.154.232.5,port=10656,localport=80] See property weblogic.login.readTimeoutMillis to increase of decrease timeout. See property weblogic.login.logReadTimeoutsProp to turn off these log messages.'Thu Aug 02 09:23:18 EDT
2001:<!> <SSLListenThread> **** The WebLogic Server is no longer listening for connections.Thu Aug 02 09:23:18 EDT 2001:<!> <SSLListenThread> **** You should probably restart it.Thu Aug 02 09:23:18 EDT 2001: <WebLogicServer> Server shutdown by systemThu Aug 02 09:23:18 EDT 2001: <WebLogicServer> Server shutdown commencing NOWThu Aug 02 09:23:18 EDT 2001:<A> <ListenThread> ListenThread.run() failed:java.lang.ThreadDeathThu Aug 02 09:23:18 EDT 2001:<!> <ListenThread> **** The WebLogic Server is no longer listening for connections.Thu Aug 02 09:23:18 EDT 2001:<!> <ListenThread> **** You should probably restart it.Thu Aug 02 09:23:18 EDT 2001: <WebLogicServer> Server shutdown by systemThu Aug 02 09:23:19 EDT 2001: <HTTP> Destroying servlets in default servlet context.Thu Aug 02 09:23:19 EDT 2001: <ServletContext-General> proxy: destroyThu Aug 02 09:23:19 E

hi srikanth i am facing some problem in weblogic for a particular port.weblogic
is shutting down for that port .this port
is configured for SSL.
when i have reviewed the logs i could trace
following error.i dont know whether this error is linked to the shutting down of weblogic.
ERROR:on Apr 08 13:30:36 CEST 2002:<W> <SSLListenThread> Connection rejected: 'Login
timed out after: '25000' ms on socket: 'Socket[addr=192.193.118.137/192.193.118.
137,port=33280,localport=7003}''
Each and everytime restarting the weblogic
instance is not a proper solution so please
let me know what can i do for this weblogic
shutting down abnormally.
waiting for ur reply
Best Regards
Surender
Wipro Limited.

Error message: X11 connection rejected because of wrong authentication

Until recently I was able to ssh from the Mac in my office -- runing
MacOS 10.6.4, to a Sun Solaris server -- running Solaris 10 10/09
(update 8) and all available patches installed, and run X11 programs
displaying on my Mac.
I installed these patches recently:
142900-15 SunOS 5.10: kernel patch
124867-15 Sun Studio 12: Patch for C 5.9 compiler
122212-42 GNOME 2.6.0: GNOME Desktop Patch
138764-02 SunOS 5.10: acc driver patch
120199-16 SunOS 5.10: sysidtool Patch
119252-29 SunOS 5.10: System Administration Applications Patch
124630-44 SunOS 5.10: System Administration Applications, Network, and Core Libraries Patch
124628-10 SunOS 5.10: CD-ROM Install Boot Image Patch
118777-17 SunOS 5.10: Sun GigaSwift Ethernet 1.0 driver patch
121118-17 SunOS 5.10: Update Connection System Client 1.0.17
144759-02 SunOS 5.10: mount patch
145019-01 SunOS 5.10: ifconfig patch
119313-38 SunOS 5.10: WBEM Patch
124393-10 CDE 1.6: Dtlogin smf patch
119278-37 CDE 1.6: dtlogin patch
121734-13 SunOS 5.10: patch to support addition of new UTF-8 locales
119254-75 SunOS 5.10: Install and Patch Utilities Patch
118666-27 JavaSE 5.0: update 25 patch (equivalent to JDK 5.0u25)
118667-27 JavaSE 5.0: update 25 patch (equivalent to JDK 5.0u25), 64bit
121430-53 SunOS 5.8 5.9 5.10: Live Upgrade Patch
119246-38 SunOS 5.10: Manual Page updates for Solaris 10
121308-22 SunOS 5.10: Solaris Management Console Patch
119315-21 SunOS 5.10: Solaris Management Applications Patch
118712-24 SunOS 5.10: Sun XVR-100 Graphics Accelerator Patch
144325-02 SunOS 5.10: Resource Management User Interface Patch
145074-01 SunOS 5.10: Trusted JDS Help rebranding patch
124457-03 X11 6.6.2: xdm patch
and now when I try to run certain programs, namely Symantec NetBackup
Server (NBS) administrator interface, jnbSA, when I run the program I see:
X11 connection rejected because of wrong authentication.
and jnbSA fails. I removed these patches:
118666-27 JavaSE 5.0: update 25 patch (equivalent to JDK 5.0u25)
118667-27 JavaSE 5.0: update 25 patch (equivalent to JDK 5.0u25), 64bit
124457-03 X11 6.6.2: xdm patch
with no change. I have made NO updates to NBS, and what's
even more weird, regular X11 programs such as x{eyes,biff,emacs}
work fine.
I've tried tinkering with the contents of ~/sshconfig and /etc/ssh_config
to no avail.
Is anyone else seeing this problem?
Any suggestions?
Thanks!

I'm confused why you posted on the Tarantella/SGD Forum then?
Yes, you can use SGD to have your Mac client display back a Solaris/Linux/Windows/Mainframe, etc application remotely.
http://www.oracle.com/us/technologies/virtualization/oraclevm/061996.html

Connection rejected by server

Similar Messages

Maybe you are looking for