Enterprise Client Community

Hi,

is it possible to simplify the reconnect procedure? We use a lot of applications in kiosk mode (touchpanel). After a restart of the application server every client gets the reconnect dialog. If the operator uses the 'no' or 'cancel' option an error message is shown. Afterwards he has to use the restart button at bottom right. That leads to constant inquiries to the support team.
The best way would be to show a modal "server not available" dialog having only a "reconnect now" button. In addition, the client could also try to restart automatically.

Michael

Hi,

what we could do...: add a big(ger) reconnect button directly into the dialog in which the error details are displayed. In this case the user does not have to go to the bottom right... but directly can restart the client from the ocntent area.

Reagrds, Björn

Hi,

that would not really help us. This is in principle already possible, but the frequently changing operating staff is often overwhelmed with such unsual errors. What really would improve the situation for us is a automatic reconnect. Maybe configurabe via a start parameter of the client.

Michael

Hi,

with the last update we added certain improvements:

(1.) The client error screens now has a big button "Reload Page" - which should make it much easier for the user to react

(2.) The reconnection behaviour was updated - you now can define a quite big number of reconnection attempts as client parameter ("numberofreconnects"). The "pinging" for connections is not done in "immediate mode" (i.e. diectly after getting a connection error, then the next request is fired), but in some "relaxed mode":

For better explanation I just copy some lines of code:
Code:

                 if (m_transferXMLCallCounter > 15)
                 {
                     try { Thread.currentThread().sleep(5000); } catch (Exception exc) {}
                 }
                 else if (m_transferXMLCallCounter > 4)
                 {
                     try { Thread.currentThread().sleep(2000); } catch (Exception exc) {}
                 }
                 transferXML(clientId,browserDim,referenceComponent,originalURL);

So you can define a quite high number of reconnects without "destroying the network" and still have some constant pinging. When the server comes up again, then new sessions will be crated on server side (or...: old sessions will be re-invoked, if supporting fail-over).

Regards, Björn