Closed GoogleCodeExporter closed 9 years ago
GoogleCodeExporter
commented
9 years ago That is very odd indeed. Can't say we've seen that before, but perhaps there's
something about the newest Vaadin 7.2.3. This occurs every time you try to
login now?Original comment by yoz...@gmail.com on 1 Jul 2014 at 10:49
GoogleCodeExporter
commented
9 years ago We are able to login to the support account without incidence. It's not clear
what is wrong. We'd installed a patch release to try to catch the exception we
see, but it's odd in that it's just trying to restore the previous tabs. The
only thing we noted is that you logged in and never logged off, which is when
the previous tabs are saved, and instead was forced logged off due to session
timeout.
2014-07-01 11:09:16 PDT EsfVaadinUI closed on session expiration for SNIP
2014-07-01 09:38:56 PDT User SNIP logged in from IP address SNIP with browser
type: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/35.0.1916.153 Safari/537.36
We'll see if we can reproduce that scenario and bug.Original comment by yoz...@gmail.com on 1 Jul 2014 at 11:10
GoogleCodeExporter
commented
9 years ago I just logged in now fine. It seems to have cleared up. I was away from my
computer after working for a while. When I came back there was a box that said
that it had timed out and to click to be able to log in. I'm sorry, I forgot
that happened and should have stated it earlier. It seems to fall in line with
what the logs show.Original comment by christ...@abinti.com on 1 Jul 2014 at 11:16
GoogleCodeExporter
commented
9 years ago That's good news. We'll keep the ticket open a bit more as we just created a
user account, logged in, opened various tabs, and then closed the browser
without logging off. But it is odd because the first login also has no previous
tabs.
If that doesn't do it, we'll redo the scenario you explained above in case
there's a difference in the Vaadin processing when the application is open and
it times out.Original comment by yoz...@gmail.com on 1 Jul 2014 at 11:27
GoogleCodeExporter
commented
9 years ago Closing the browser didn't cause the problem, but it also did show the session
ended log entry. Trying again by doing an initial login, opening various tabs,
and then leaving it open but unused until the session expires.Original comment by yoz...@gmail.com on 2 Jul 2014 at 3:55
GoogleCodeExporter
commented
9 years ago I'll try that now and follow up after it expires.Original comment by christ...@abinti.com on 2 Jul 2014 at 4:20
GoogleCodeExporter
commented
9 years ago We're not able to reproduce this, so we're going to close it as we at least
fixed the code that infringed and caused the exception that blocked your login.
It will be in the standard July release.Original comment by yoz...@gmail.com on 2 Jul 2014 at 6:45
GoogleCodeExporter
commented
9 years ago I logged in, opened several tabs and left a document that I was creating open,
and left it for the session to expire. I did this twice, each time I was able
to click on the session expired banner, as I did yesterday. However, this time
when logging in after an expired session I did not receive an error.Original comment by christ...@abinti.com on 2 Jul 2014 at 6:48
GoogleCodeExporter
commented
9 years ago Thank you - I appreciate your help.Original comment by christ...@abinti.com on 2 Jul 2014 at 6:53
Original issue reported on code.google.com by
christ...@abinti.comon 1 Jul 2014 at 6:31