We are using ClearCase too. 1. Beanshell is as you say VERY flaky for accesss of code in ClearCase storage. I have managed at times to make it work for getting source code for classes under the cursor (C-cC-vC-y), but it takes time to get any response (emacs seems to hang in between). It can take between 5-10 retries before I get a reply from the Beanshell. I submitted a request to the list for help in managing to get some debugging trace information in the *bsh* buffer whenever I try to use the Beanshell functionality but received no answer yet :-( Without that I cannot say for sure if it is a network access issue, a ClearCase issue or a Beanshell issue.
When editing code on local drives (not NFS and not on ClearCase) the response time of the Beanshell is as reported in the JDEE documentation. 2. I have not experienced any issues with compilation. It works ok for me. 3. Clearcase is notoriously slow sometimes. Run a CCase Analysis Doctor (I am talking about windows here, I am not sure what happens in Unix, tho Unix CCase should have something similar) to see if there are any reported conflicts. > -----Original Message----- > From: Molitor, Stephen [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, April 24, 2002 9:28 PM > To: [EMAIL PROTECTED] > Subject: Things hang when using ClearCase > > > Has anyone noticed any general flakiness when using JDE and Emacs with > ClearCase? We just switched to ClearCase, using dynamic > views, on Windows > NT 4.0, with the ClearCase NFS client turned on. Since then, > lots of flaky > stuff has been happening. Most of these things happen even > with local Java > files not in ClearCase, but they seem to be related to the > NFS client, and > process IO. Specifically: > > 1. Starting the bean shell hangs -- even after waiting > several minutes for > it to start. > > 2. Compilation doesn't finish - the 'finished' message is not > displayed. > However, if I do CONTROL-ALT-DELETE to bring up the "Windows > NT Security" > box (used to bring up the task manager, etc., and it hides the desktop > temporarily) and then hit cancel, the 'finished' message > appears in the > compilcation buffer. > > 3. Things are slow in general, not just in Emacs. > > I could submit a bug report, but I suspect that this isn't > really JDE's > fault. Just wondering anyone has seen these kind of problems with > ClearCase, and has any workarounds. Any Emacs settings > related to process > IO and polling, timeouts, etc., that might help here? > > Thanks. > > Steve Molitor > [EMAIL PROTECTED] >
