search

tomasbilek / gwteventservice

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

random NoSessionAvailableException #44

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
From time to time, I get this exception: 
de.novanic.eventservice.service.exception.NoSessionAvailableException: There is 
no session available! Maybe no session was generated explicitly by the 
connection id generator
I am using glassfish and ListeEventListener V1.2
Changing the session-timeout in web-xml has no effect on this problem.
Thanks for your help

Original issue reported on code.google.com by paul75...@gmail.com on 18 Apr 2012 at 2:12

GoogleCodeExporter commented 8 years ago 
Hi,

I think this is still a configuration problem. GWTEventService re-schedules the 
connection regulary to avoid session timeouts, but it seems that the server has 
removed the session anyway. Could you please post your GWTEventService 
configuration/properties and the time which is configured for the 
session-timeout of your server configuration?

Original comment by sven.strohschein@googlemail.com on 16 Jul 2012 at 6:49

GoogleCodeExporter commented 8 years ago 
Since 1.2, I always have the same problem exactly. 
My environment is JBoss 6.1 on CentOS 6.3 64bits, Oracle jdk 6 x64
The session-timeout configuration of my app is:
<session-config>
  <session-timeout>60</session-timeout>
</session-config>

and the eventservice.properties
eventservice.time.waiting.max=20000
eventservice.time.waiting.min=0
eventservice.time.timeout=90000
eventservice.reconnect.attempt.count=10
#eventservice.connection.id.generator=de.novanic.eventservice.service.connection
.id.SessionConnectionIdGenerator
eventservice.connection.id.generator=de.novanic.eventservice.service.connection.
id.SessionExtendedConnectionIdGenerator
eventservice.connection.strategy.server.connector=de.novanic.eventservice.servic
e.connection.strategy.connector.longpolling.LongPollingServerConnector

Initially, I was using the SessionConnectionIdGenerator, then I changed it to 
SessionExtendedConnectionIdGenerator, however I get the very same exception 
message often.

Original comment by victor.h...@gmail.com on 18 Jul 2012 at 3:09