OMW - not responding when opened the second time on a development client
Has anyone experienced this problem when using OMW on a development/fat client? ... The issue occurs on all dev clients since upgrading to TR9.2.1.
Windows Development client
Windows 2012 R2
TR 9.2.1
Steps to reproduce:
1. log into DV fat client
2. Fast Path to OMW
3. Click Find
4. Close OMW app
5. Fast Path to OMW ... again
6. the client becomes unresponsive ... activeConsole.exe is not responding
7. the only way to recover is to 'kill' the process and log back in again
The jde.log is clean (no errors logged).
Thanks.