|
Not sure, whether this applies to all cases, but from my experience, whenever I ran into the "another session running" situation, I had closed WDSc without stopping the WAS test server. So I try to remember stopping the server BEFORE closing the workbench. As said, not sure if it always helps. But another tip: Asking myself if it is save to kill the javaw.exe, in Windows Task manager, I first sort by task name (click the table header) and if there is only one javaw running, it is most likely the one to blame - if there are many, booting the PC might be the better solution. Wilfried Blankertz
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.