search

hoangduit / openmeetings

Automatically exported from code.google.com/p/openmeetings
0 stars 0 forks source link

TCP session timeout when connecting to openmeeting server through a stateful firewall #452

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Which version of OpenMeetings are you running?
0.5.1
What's your operating system on client and server side?
Client = Windows XP SP2, Server = Ubuntu
Is it a problem related to the client/usability or server-side?
Client TCP session timeout

Our openmeetings server is sitting behind a stateful firewall (Juniper SSG
140). The TCP idle session timeout on the firewall is 30 mins. What appears
to be happening is when you join a meeting and sit idle for over 30 mins,
things start breaking in openmeetings. I'm guessing this is being caused by
the firewall dropping the idle session but the client and server still
thinking the TCP session is still alive. 
For example, after sitting idle in a meeting for over 30 mins, when I try
to upload a file I just receive a "HTTP 500" error box. Also, no files will
show under the Files tab even though there have been files uploaded. At
that point you have to completely log out of openmeetings, close and
re-launch the browser and log back into the meeting.
Does Openmeetings implement some sort of TCP keepalive to keep the TCP
session active if you are sitting idle (not clicking on stuff or presenting
something in openmeetings)?

Original issue reported on code.google.com by mr.k...@gmail.com on 14 May 2008 at 10:24

GoogleCodeExporter commented 9 years ago 
are you sure that you are not just *logged-out*.
If you don*t do *anything* for more then 15-20 minutes, your SID will be 
deleted,
that means that every request returns NULL.

Original comment by seba.wag...@gmail.com on 15 May 2008 at 7:05

GoogleCodeExporter commented 9 years ago 
It doesn't appear that I get logged out. I can still see people's active 
webcams and
I can see stuff being presented on the white board. I guess my question would 
be why
would the server delete your sid after 15-20 mins of inactivity? Many of the 
meetings
we've tested using openmeetings last 2+ hours.

Original comment by mr.k...@gmail.com on 15 May 2008 at 8:02

GoogleCodeExporter commented 9 years ago 
You should review this Issue with the latest Versions again. I think its 
outdated.

Original comment by seba.wag...@gmail.com on 9 Jan 2010 at 3:14