1 of 1 people found this helpful
M M wrote:
1. Time until user authentication times out (ie. inactivity, after which they must log in again)
Since console relies on session information you shall configure session timeout in gwt-console-server web.xml file.
M M wrote:
2. Timeout for remote data requests (like refreshing table lists, etc.)
I don't think this is configurable. Do you mean automatic refresh without user involvement?
For me point 2... is a problem too...
I have over 100.000 process instance running and every operation into console breaks by time-out...
I move from HSQLDB to Oracle but time is so high and error continues...
Thanks for the first one. I will look into it.
For the second, I mean the following scenario:
1. Log into console
2. Click on "Process Definitions"
3. Click on "Refresh" button.
4. After about 10 seconds of waiting, it returns an error like the following (and nothing is populated into the table):
This problem only happens intermittently - that is, some days it just keeps getting this error every time, no matter what (restart jboss, etc.). Most days, however, it works fine without any issue.
I would suspect some network issues. As far as I know there are no such time out defined in the console.
Well, somewhere, somehow, the timeout period for the request must be defined, because obviously something must know when to trigger the timeout. It must be defined either by a default value ssomewhere or a configuration option somewhere (be that in jbpm, tomcat, jboss, gwt, the browser, etc.)
Anyone have any ideas about how the time limit gets defined?
The timeout is 20 seconds and is hard-coded into the GWT code for the bpm console:
See line 124 - t.schedule(20000);