Hide Forgot
Description of problem: jBPM Console does not render in Firefox Version-Release number of selected component (if applicable): dev6 jbpm console from Firefox 8.0.1 on Mac 10.6.x How reproducible: Very Steps to Reproduce: 1.login in to jbpm console with admin / admin from Firefox 8.0.1 Actual results: half inch of white at the top the screen and the rest of the screen was pale blue Expected results: jBPM Console page with Tasks, Processes, etc. Additional info: Verified this worked fine with Safari and Chrome.
I've not been able to confirm this issue, it seems to work fine on various versions of Firefox, including Firefox 8.0.1 on Windows XP. I don't have a Mac to test this on unfortunately? Can anyone verify whether they can reproduce this on a Mac?
Works fine on latest Firefox 9.0.1: http://i.imgur.com/aTl7B.png on Mac. I am not able to download specifically version 8 from the update manager because 9.0.1 is the latest.
I upgraded to Firefox 9.0.1 and cleared my browser cache and I can now login and access jBPM Console okay. This issue can be closed.
I'd like to add, that with ER1 (and using Firefox 8.0), this issue seemed non existent. Up till now, when I got the pale-blue-with-white-strip page again. It took many tries though, much more than before. Also, working with the jBPM Console by myself, it always worked better than when I used Selenium WebDriver (automation) - that way was (and still is it seems) more prone to this issue.
Using ER2, Firefox 8.0, Selenium WebDriver, issue still present, happening more and more often. It's seriously blocking any test I might want to do. Please look at it.
Do you think this might be an issue that only shows on Mac? Or have you been able to reproduce this on other OSs? Are you aware of other users being able to reproduce this? Unfortunately, no-one from the team has been able to reproduce this locally yet. When you say that it only happens occasionally, how should we try to trigger it? Just hitting (hard) refresh on login screen? Or are there better ways to make it fail?
I'm using Fedora 15. And I've found a way around the issue just now. And a way to reproduce it as a consequence. After filling in username and password, you need to click really fast, without a delay, on the submit button. This produces the blank page. The workaround for the bug is then, obviously, waiting a bit before submitting the login information. Could you still look at the issue? We might have some really fast customers. ;)
Ok, that should give us some more info on trying to reproduce this. I'll let you know how it goes.
(We have a workaround, so no longer a TestBlocker.)
Created attachment 576482 [details] Console with no panels after logon Here is a screen shot that illustrates the issue I was able to reproduce. It only happens when server was restarted but the browser with jbpm-console logon form was not reloaded by user tried to logon directly by filling in the form and submit.
It seems like the nature of GWT application is that it is initialized when user accesses the main url that triggers entry point of the module, this is where everything is initialized and in quite few places it is initialized asynchronously which could lead to some components of the application being not yet ready when user logs into the system (as described in bz slight delay solves the issue). Same goes for the case with log off, user logs off and the page is reloaded meaning it is initialized but when server stops gwt/errai looses connection to it and the framework seems to be not ready any more. After several hours of browsing through the code and debugging I managed to get some relevant messages from errai, this is what is printed out when trying to login after restart without reloading: No subscribers for: AuthorizationListener<br/>Additional details:<br/> Attempt to send message to subject for which there are no subscribers This AuthorizationListener is responsible for triggering workspace construction but as there are no subscribers it just does nothing.
Given that we've only been able to reproduce this issue when restarting the server but not reloading the login page, how much time should we spend on trying to solve this issue as: - restarting the application server should not be a common use case - the user would probably hit refresh in this case, which would solve the issue
On 2.1 I said: "I upgraded to Firefox 9.0.1 and cleared my browser cache and I can now login and access jBPM Console okay. This issue can be closed." I have never seen a problem with it since.