powered by Jive Software

Connection closed before session established Socket

Hi there,

yes I know this was asked before, but all the existing threads didn’'t help me and were all a little bit different.

Symptoms:

Some clients can’'t log in. Other can.

Error.log:

2005.12.30 13:34:29 org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:158) Connection closed before session established

Socket[addr=/84.149.190.74,port=1368,localport=443]

2005.12.30 13:37:22 org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:158) Connection closed before session established

Socket[addr=/84.149.190.74,port=1371,localport=443]

2005.12.30 13:49:24 org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:158) Connection closed before session established

Socket[addr=/80.219.219.111,port=1040,localport=443]

2005.12.30 14:01:50 org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:158) Connection closed before session established

Socket[addr=/84.149.190.74,port=1548,localport=443]

2005.12.30 14:02:05 org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:158) Connection closed before session established

Socket[addr=/84.149.190.74,port=1549,localport=443]

2005.12.30 14:02:35 org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:158) Connection closed before session established

Socket[addr=/84.149.190.74,port=1551,localport=443]

2005.12.30 14:07:08 org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:158) Connection closed before session established

Socket[addr=/80.219.219.111,port=1151,localport=443]

debug.log:

2005.12.30 13:34:25 Connect Socket[addr=/84.149.190.74,port=1368,localport=443]

2005.12.30 13:37:16 Connect Socket[addr=/84.149.190.74,port=1371,localport=443]

2005.12.30 13:49:23 Connect Socket[addr=/80.219.219.111,port=1040,localport=443]

2005.12.30 14:01:50 Connect Socket[addr=/84.149.190.74,port=1548,localport=443]

2005.12.30 14:02:05 Connect Socket[addr=/84.149.190.74,port=1549,localport=443]

2005.12.30 14:02:34 Connect Socket[addr=/84.149.190.74,port=1551,localport=443]

2005.12.30 14:07:08 Connect Socket[addr=/80.219.219.111,port=1151,localport=443]

warn.log:

empty

details:

Even that clients that are logged in, are producing some of this errors. All connection were direct without proxys.

Constants:

I’‘m running Wildfire 2.4.0 on a SLES 9 SP 2 on a 32Bit VMware. Database is mysql. I’'ve installed the rpm from the download section. The listen port is 443 for compatibility with some proxy-settings. 2.3.0 worked with the same settings.

Can sombody please help me? But I don’'t think it is an configuration error.

Thx

Marc

Here is a paste from the admin interface:

Environment:

JVM Version and Vendor: 1.5.0_06 Sun Microsystems Inc. – Java HotSpot™ Server VM

Appserver: Jetty/5.1.x

OS / Hardware: Linux / i386

Locale / Timezone: en / Central European Time (1 GMT)

Java Memory: 7.95 MB of 63.31 MB (12.6%) used

Im getting the same errrors… ¿Anyone?

I was seeing the same error over and over this morning and couldn’'t connect to Wildfire with any chat client myself.

Note: I’'m running the Win32 version on Windows 2000 Server as a service

I restarted the service and everyone can connect again. I’‘m not sure if that helps at all for linux installs, but it’'s all I can tell you.

Hey guys,

We would need to collect some information in order to figure out what’'s going on. Before logging in from the client, can you open the XML traffic window and paste the sent and received XML when the login operation failed?

Thanks,

– Gato

Update: things are not well

It would seem that restarting the service on our Windows server only fixed things for some of our users. Less than half the users on our network can connect at this point. I haven’'t had a chance to dig much deeper, but will try to gather some info.

Update2: problem “magically” going away?

I’‘m seeing users connect that have not been able to connect all morning, but I haven’‘t made any further changes to the server. It would seem that whatever was preventing the connection is clearing up on its own. I don’‘t feel very confident about that, but as busy as today is I’'ll take anything I can get!

Message was edited by:

jcatlin

Hi,

thanks for your answers. I tried to log that XML-Traffic, but I faild. Perhaps I’'m just doing something wrong:

  • Open Spark

  • Login

  • “Help” -> “Show Traffic Window”

  • Logout to Login again

  • Traffic Window disapears

How do I open this “XML Traffic Window”??

Thx

Marc

Hi,

I was having some issues with broken pipes and some strange errors.

I´ve managed to track the errors to the configuration of mysql.

See my last reply in this post http://www.jivesoftware.org/community/thread.jspa?messageID=110817&#110817 .

Maybe it could help you…

Jcorreia