Opened 11 years ago

Closed 10 years ago

Last modified 9 years ago

#295 closed defect (wontfix)

Timeout while using the Flex client

Reported by: twagoo Owned by: Twan Goosen
Priority: major Milestone:
Component: ComponentRegistry Version:
Keywords: Cc:


From a user reports it seems that, while logged in through the Flex web frontend, his session for the component registry times out. This should be prevented by the frequent 'ping' that the client sends to the server. Possibly this does not function while editing or when the application is not focused (e.g. screen saver).

An alternative explanation is that the SP or IdP triggers a timeout of the session after a fixed login time, but that's not very likely. Need to investigate.

Copy of the e-mail communication:

On 3/27/13 12:23 , Onno Crasborn wrote:

I get an error message when browsing the component registry saying "Internal Server error cannot process the data, try reloading the application."

What I did was create a new profile based on an existing one, same for a component, and then leave for coffee. When I get back i'm logged out, and upon logging in again I can't find my new profile nor new component -- I reckon I didn't yet save them. So far so good, but then when I try to do it again, the error appears.

Just tested by logging in from another browser + another computer; same message.

I could not find anything in the logs but my guess is that your session
had timed out. This should not happen, so you can consider this a bug in
the application. Refreshing the *entire* web page should update the
state of the web interface and give you the opportunity to log back in.

Change History (4)

comment:1 Changed 11 years ago by twagoo

Milestone: ComponentRegistry-1.14ComponentRegistry-1.15

comment:2 Changed 10 years ago by Twan Goosen

Owner: changed from twagoo to Twan Goosen
Status: newassigned

comment:3 Changed 10 years ago by Twan Goosen

Resolution: wontfix
Status: assignedclosed

Have not heard any similar reports since this ticket was created. Most likely cause is the application going into sleep mode, which cannot be prevented anyway.

comment:4 Changed 9 years ago by Twan Goosen

Milestone: ComponentRegistry-1.16

wontfixes and worksforme taken off of 1.16 milestone

Note: See TracTickets for help on using tickets.