Open rbeckman-nextgen opened 4 years ago
rbeckman-nextgen
commented
4 years ago This also happens with the Administrator in OSX. Eventually, "Operation timed out" and "host is down" errors appear.
Imported Comment. Original Details: Author: jacobb Created: 2013-10-18T13:46:30.000-0700
rbeckman-nextgen
commented
4 years ago This happens every time connection to the server is interrupted. Very annoying because the client cannot be killed unless all Java processes are killed (usually I have more than one instances of client running so this kills all instances).
Imported Comment. Original Details: Author: aitougan Created: 2014-04-07T10:14:25.000-0700
rbeckman-nextgen
commented
4 years ago alertException performs some checks to determine if the connection has timed out and whether the Administrator should log off immediately. However it appears that some of the ClientExceptions we receive when a server is no longer available are shown via alertError, which does not perform such checks. Therefore we should either perform the same types of handling in alertError or be more strict about which method is used.
Imported Comment. Original Details: Author: wayneh Created: 2015-01-27T12:37:09.000-0800
rbeckman-nextgen
commented
4 years ago This issue should be mitigated now in 3.5, since idle connections are being closed after 5 minutes.
Imported Comment. Original Details: Author: narupley Created: 2017-05-10T16:31:09.000-0700
If the server/virtual machine hosting the Mirth Connect Server powers off before closing the Mirth Connect Administrator, the Mirth Connect Administrator will then lock up. The only way to close the Mirth Connect administrator at this point is to force close it with Task Manger (when using Windows).
Imported Issue. Original Details: Jira Issue Key: MIRTH-2393 Reporter: mbs Created: 2013-03-12T14:27:53.000-0700