Menu

#394 An internal error occurred during: "Refreshing ClearCase Resource States"

2.x
closed-invalid
None
2
2015-10-13
2015-09-21
No

Hi, After long long (years) time of beautiful and seamless working, the plugin cedently have stopped to work.
Our IT recently made upgrade for ClearCase to version 8.0.0.15, but I am not sure that this is the case for error. It looks like the problem in some caching - part of projects that had been opened early still working.
Here is the error:

java.lang.IllegalArgumentException: Argument not valid: Could not get status information from view
at net.sourceforge.clearcase.ClearCase.error(ClearCase.java:706)
at net.sourceforge.clearcase.ClearCase.error(ClearCase.java:597)
at net.sourceforge.clearcase.ClearCaseCLIImpl.parserOutputLSView(ClearCaseCLIImpl.java:1603)
at net.sourceforge.clearcase.ClearCaseCLIImpl.getViewType(ClearCaseCLIImpl.java:1010)
at net.sourceforge.eclipseccase.ClearCaseProvider.isSnapshotView(ClearCaseProvider.java:675)
at net.sourceforge.eclipseccase.StateCache.doUpdate(StateCache.java:271)
at net.sourceforge.eclipseccase.StateCache.doUpdate(StateCache.java:158)
at net.sourceforge.eclipseccase.StateCache.doUpdate(StateCache.java:146)
at net.sourceforge.eclipseccase.StateCacheJob.execute(StateCacheJob.java:121)
at net.sourceforge.eclipseccase.StateCacheJobQueue.executePendingJobs(StateCacheJobQueue.java:179)
at net.sourceforge.eclipseccase.StateCacheJobQueue.run(StateCacheJobQueue.java:103)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Related

Bugs: #394

Discussion

  • Mikael Petterson

    Hi,

    I wonder if this has something to do with the new auto connect function.
    Could you more describe what happens when you start eclipse and show with some picture what is going on... since I have no access to clearcase .

    br.

    //mike

     
  • Michael Neifeld

    Michael Neifeld - 2015-10-08

    Hi Mike,
    How are you?
    I am sorry for delay - it was a lot of holidays here.
    I don't know what to describe - I was tried my regular work like switching workspaces, adding a project to the workspace or adding new project/files to ClearCase.
    I suspect that it can be the result of one of the latest ClearCase uprgades, but I am not sure.
    I've attached some pictures for you, I hope it will help.

    Regards,
    Michael.

     
  • Mikael Petterson

    Hey Michael!
    Nice to hear from you again. I am doing fine. Since my company have stopped using cc I had a hard time to do testing. But now it seems that I can soon have access to a cc server.
    No problem with delay. I hope you had a great time with family and friends.

    I checked the code and I wonder if it is possible to run the following command:

    cleartool lsview -pro -ful <viewname>

    and provide the output here.

    Talk to you soon :-)

    br,

    //mike

     
    • Michael Neifeld

      Michael Neifeld - 2015-10-13

      Hi Mike,

      I've attached that you've asked for.

      But I am pretty sure now, that the problem is a result of some paranoid
      security program, that interfere in normal ClearCase work.
      I had a stormy debate at few last days and finally it seems that ClearCase
      finally starts work normally.
      I am still checking it, but so far all works.

      Regards,
      Michael.

      On Tue, Oct 13, 2015 at 2:18 PM, Mikael Petterson eraonel@users.sf.net
      wrote:

      Hey Michael!
      Nice to hear from you again. I am doing fine. Since my company have
      stopped using cc I had a hard time to do testing. But now it seems that I
      can soon have access to a cc server.
      No problem with delay. I hope you had a great time with family and friends.

      I checked the code and I wonder if it is possible to run the following
      command:

      cleartool lsview -pro -ful <viewname>

      and provide the output here.

      Talk to you soon :-)

      br,

      //mike

      Status: open
      Group: 2.x
      Created: Mon Sep 21, 2015 11:25 AM UTC by Michael Neifeld
      Last Updated: Thu Oct 08, 2015 06:12 AM UTC
      Owner: nobody

      Hi, After long long (years) time of beautiful and seamless working, the
      plugin cedently have stopped to work.
      Our IT recently made upgrade for ClearCase to version 8.0.0.15, but I am
      not sure that this is the case for error. It looks like the problem in some
      caching - part of projects that had been opened early still working.
      Here is the error:

      java.lang.IllegalArgumentException: Argument not valid: Could not get
      status information from view
      at net.sourceforge.clearcase.ClearCase.error(ClearCase.java:706)
      at net.sourceforge.clearcase.ClearCase.error(ClearCase.java:597)
      at
      net.sourceforge.clearcase.ClearCaseCLIImpl.parserOutputLSView(ClearCaseCLIImpl.java:1603)
      at
      net.sourceforge.clearcase.ClearCaseCLIImpl.getViewType(ClearCaseCLIImpl.java:1010)
      at
      net.sourceforge.eclipseccase.ClearCaseProvider.isSnapshotView(ClearCaseProvider.java:675)
      at net.sourceforge.eclipseccase.StateCache.doUpdate(StateCache.java:271)
      at net.sourceforge.eclipseccase.StateCache.doUpdate(StateCache.java:158)
      at net.sourceforge.eclipseccase.StateCache.doUpdate(StateCache.java:146)
      at
      net.sourceforge.eclipseccase.StateCacheJob.execute(StateCacheJob.java:121)
      at
      net.sourceforge.eclipseccase.StateCacheJobQueue.executePendingJobs(StateCacheJobQueue.java:179)
      at
      net.sourceforge.eclipseccase.StateCacheJobQueue.run(StateCacheJobQueue.java:103)
      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)


      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/eclipse-ccase/bugs/394/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Bugs: #394

  • Mikael Petterson

    Ok. Good news. I will cancel the bug report and if you have the same problem again just file a new bug report.

    //mike

     
  • Mikael Petterson

    • status: open --> closed-invalid
    • assigned_to: Mikael Petterson
     

Log in to post a comment.