Hi, just since the new look and feel we have had some users (including me) report that the system keeps booting them out and saying they need to re-login, and then occasionally it says email error/user not recognised, and then they have to start a new browser and start again. It is doing this quite frequently -perhaps every 15-30mins?
The nature of shark spotting is that you have multiple windows open and multiple tabs within those windows so it is important we are not timed out for each window. If the system is detecting no activity in one of 50 tabs and kicking the user out on that basis then it will be problematic, since we wont be necessarily touching every tab/every window every few minutes to keep them active.
Could you please check if you can keep sessions open for longer to avoid this issue?
I’m still waiting to hear back about extending the timeout session from 30 mins to longer. Half of our team is traveling right now so these fixes will be happening asynchronously.
Here’s what I know:
- As long as you’re actively working in Sharkbook, the session timeout warning shouldn’t pop up in any open tabs
- When a timeout warning does appear, it will display in multiple tabs, but you only need to acknowledge it in one of them to extend the session.
Session timeouts have been extended to 1 hour.
Hi Anastasia - something is still not quite right. It keeps kicking us out - not even an hour later - just a few minutes later each time (and several times an hour it won’t let me back in as it says that my password/username not recognised - then later it accepts me and lets me back in). Another common bug that keeps appearing is “HTTP Status 500” - sometimes my computer warns me that the site is unsecure too?
Type Exception Report
Message An exception occurred processing [iaResults.jsp] at line [42]
Description The server encountered an unexpected condition that prevented it from fulfilling the request.
Exception
org.apache.jasper.JasperException: An exception occurred processing [iaResults.jsp] at line [42] 39: Shepherd myShepherd = new Shepherd(request); 40: myShepherd.setAction(“iaResults.jsp: matchResults nameKey getter”); 41: myShepherd.beginDBTransaction(); 42: User user = myShepherd.getUser(request); 43: String currentUsername = “”; 44: if (user!=null){ 45: currentUsername = user.getUsername();
I’ve not experienced this while working in Sharkbook this week. What you’re describing sounds like the server going offline and coming back on again. I’m waiting to hear back from the team on this.
It looks like this is related to a redirect configuration issue getting bounced between sharkbook.ai and www.sharkbook.ai. We aim to have this fixed by the end of the business day.
This behavior has been fixed.