Created attachment 773773 [details] Screen shot of dialog with exception. Description of problem: To recreate: - Search for a CSP map topic ID, for example: 11864. - It brings you here: http://skynet.usersys.redhat.com:8080/pressgang-ccms-ui/#SearchResultsAndTopicView;query;topicIds=11864 - Leave the page open and go do something else for a while (read mail, get coffee). I'm not sure how long, but 10 minutes is probably safe. :-) - Come back to the page and click on "DocBuilder" in the left menu. - You get a dialog box with above message. This is probably a timeout issue. Screen shot attached. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This is only an issue with Google Chrome. I am on Version 28.0.1500.71. I can not reproduce it in Firefox. Not sure it's worth your time to look into this or fix it.
I see something similar in Chrome going from 1 topic directly to the next within a minute or 2 using the Search.
I saw this going to the search screen. Thu Jul 25 08:40:48 GMT+1000 2013 org.jboss.pressgang.ccms.ui.client.local.App SEVERE: (TypeError) : Object SearchTagsFieldsAndFiltersView has no method 'EW' 0.js:838 Thu Jul 25 08:40:48 GMT+1000 2013 org.jboss.pressgang.ccms.ui.client.local.App SEVERE: Unknown.cX(StackTraceCreator.java:174) Unknown.kNb(StackTraceCreator.java:508) Unknown.GV(Exceptions.java:29) Unknown.mic(HistoryImpl.java:40) Unknown.anonymous(HistoryImplTimer.java:45) Unknown.MNb(Impl.java:189) Unknown.UNb(Impl.java:243) Unknown.anonymous(Impl.java:70) Unknown.anonymous(HistoryImplTimer.java:50)
HI Matt, just to let you know, Alex Dellapenta has seen the same problem. And yes, it always happens going to a search of one type or another.
*** Bug 990809 has been marked as a duplicate of this bug. ***
This may have been because there were two HTML5 message listeners (the rendered view and the revisions view), and they were picking up each others messages. I've uploaded build 201308161246 to the dev server, and will see if this has fixed the issue.
Thanks Matt. I'll let you know if I see it again.
Just saw the exception again this morning, so this has not fixed the issue.
I meant to tell you I didn't see it all day on Friday, so I thought it might be fixed. Sorry.
Exceptions.java is present in every stack trace I have seen, and it is part of the com.google.inject.internal package. After some double checking I found there were two instances where com.google.inject.Inject was used instead of javax.inject.Inject, which I have fixed up. I'll upload a new version to the dev server and see if this fixes the issue.
Nope, that didn't fix it.
Marking this as CLOSED as I can no longer replicate it. Feel free to re-open it if it occurs again.
Hi Lee, that's fine by me. I only saw it for a short time. I'm sure it was fixed.