Re: Workspace Error?

Hi Kirk,

That is a good question that I don't have an answer for.  One would think 
that with a reasonable machine it should be done ending long before then. 
If it is still showing as being locked after that long a wait I'd maybe 
look at the .log file in the workspace for errors and look for the 
existence of the javaw process.  I am thinking here that maybe it hit some 
problem and ended without unlocking the workspace?  If your workspace is 
on a network drive then errors such as this can become more likely I 
think.  But then again, I am just going from what I have been told and my 
small personal experience with this stuff.

Mike

Mike Hockings, P.Eng.
WebSphere Development Tools for AS/400  -  CODE/Designer & WebFacing !
IBM Canada Ltd. Laboratory 
hockings@xxxxxxxxxx 




Kirk.Palmer@xxxxxxxxxxxxx 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
01/23/2007 05:27 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] Workspace Error?






How long should we wait?  I believe that it was 15-30 minutes between the 
time I shutdown WDSC and restarted getting the Workspace in use error.

Kirk




Mike Hockings <hockings@xxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
01/23/2007 04:19 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] Workspace Error?






FWIW

I would expect that a fast exit-restart of WDSC would give a workspace in 
use message.  Some time ago I was told by "persons in the know" that when 
you end WDSC the fact that the GUI has gone away does not mean that it is 
ended yet.  The javaw process will stick around for a bit and finish doing 


all it's state saving and stuff.  If you end it with the task manager it 
will just take that much longer to start the next time.  So my 
recommendation is just to be patient. This way everything will run like it 


should and you won't risk damaging your workspace by killing the javaw 
process.

Mike 


Mike Hockings, P.Eng.
WebSphere Development Tools for AS/400
IBM Canada Ltd. Laboratory 
hockings@xxxxxxxxxx 





Kirk.Palmer@xxxxxxxxxxxxx 
Sent by: wdsci-l-bounces+hockings=ca.ibm.com@xxxxxxxxxxxx
01/23/2007 02:42 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] Workspace Error?






I just encountered the same problem a few minutes ago.  I attempted to 
delete that .lock file from the .metadata directory like the message 
suggested.  Because the file was being used by another process, I was not 
able to delete it.  I then used the Task Manager to locate the javaw.exe 
process and ended it (since there were two instances of javaw.exe, I 
picked the one using more memory).  That allowed me to restart WDSC in the 



same workspace without problems.

HTH,
Kirk




<Rick.Chevalier@xxxxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
01/23/2007 01:34 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
<wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] Workspace Error?







James,

I believe there is a file called LOCK. In your workspace that determines
if it is in use or not.  Try removing that file and see if you can use
the workspace.  One of our developers here had a similar issue with a
shared workspace.  Never did get a definitive solution.

HTH,

Rick

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Ryberg, James
Sent: Tuesday, January 23, 2007 1:27 PM
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] Workspace Error?

Sometimes when we close WDSC and start it back up it says
that the defined workspace is in use.  Does memory not get
flushed out sometimes?

Thanks,

James L. Ryberg, Sr.
Associated Bank - Corp.
Programmer Analyst
Mail Stop: 7055
Work : (920) 405-2522
Fax   : (920) 405-2533
Email: James.Ryberg@xxxxxxxxxxxxxxxxxx


*************************** NOTICE ***************************

This e-mail and attachment(s) may contain information that is
privileged, confidential, and/or exempt from disclosure under
applicable law. If the reader of this message is not the
intended recipient, you are hereby notified that any
dissemination, distribution, or copy of this message is
strictly prohibited. If received in error, please notify the
sender immediately and delete/destroy the message and any
copies thereof. Although Associated Banc-Corp and/or its
affiliates (collectively
"Associated") attempt to prevent the passage of viruses via
e-mail and attachments thereto, Associated does not guarantee
that either are virus-free, and accepts no liability for any
damage sustained as a result of any such viruses.

Any federal tax advice contained in this communication
(including any attachments) is not intended or written to be
used or referred to in the promoting, marketing, or
recommending of any entity, investment plan or agreement, nor
is such advice intended or written to be used, and cannot be
used, by a taxpayer for the purpose of avoiding penalties
under the Internal Revenue Tax Code.

--
This is the Websphere Development Studio Client for iSeries 
(WDSCI-L) mailing list To post a message email:
WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change
list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.

Privileged and Confidential.  This e-mail, and any attachments there to, 
is intended only for use by the addressee(s) named herein and may contain 
privileged or confidential information.  If you have received this e-mail 
in error, please notify me immediately by a return e-mail and delete this 
e-mail.  You are hereby notified that any dissemination, distribution or 
copying of this e-mail and/or any attachments thereto, is strictly 
prohibited.