RE: [WDSCI-L] Corrupted sessions?

["Bartell, Aaron L. (TC)" <ALBartell@xxxxxxxxxxxxxx>]

The way I "end" WDSc when this happens is look for javaw.exe in Task
Manager.  That is the RSE (in your verbiage).

Or you can just look for the application using the most memory;-)

I haven't had the multiple session problem you are saying and I have three
people in my department using it.  I am the only one that uses it constantly
so that may be why we haven't run into anything yet.  I wonder if this is
similar to the problems CODE had with multiple users??

Aaron Bartell



-----Original Message-----
From: Gregg Willow [mailto:gregg.willow@xxxxxxxxxxxxxx]
Sent: Friday, September 19, 2003 10:20 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] Corrupted sessions?


Two of us here at the office have been using RSE since coming back from
COMMON and have experienced session problems. For whatever reasons, we have
been able to confuse the software and the screen had dissappeared. When
attempting to restart WDSc a message appears indicating that another session
is already running in the associated workspace. If this was not the case
then deleting the .lock file would allow WDSc to restart. Bringing up Task
Manager I did not see the RSE application so it indicated to me that no
session was running. Attempting to delete the .lock file I get a message
saying that it is locked by another application. Help!

I am assuming these conditions have come across before this email. Is there
a new release that is addressing these issues? How can I restart RSE under
these conditions without having to bring down all my applications and
reboot?
Regards,

Gregg Willow