java.lang.Exception

History command failed when trying to get the latest transaction of type add

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web4107

  • via Jenkins JIRA by Daisuke TASAKI, 1 year ago
    History command failed when trying to get the latest transaction of type add
  • via Jenkins JIRA by Daisuke TASAKI, 1 year ago
    History command failed when trying to get the latest transaction of type add
  • via wso2.org by Unknown author, 1 year ago
    Failed to get existing details of the tenant:wso2.com
  • Stack trace

    • java.lang.Exception: History command failed when trying to get the latest transaction of type add at hudson.plugins.accurev.AccurevSCM.getLatestTransaction(AccurevSCM.java:1179) at hudson.plugins.accurev.AccurevSCM.checkStreamForChanges(AccurevSCM.java:1101) at hudson.plugins.accurev.AccurevSCM.pollChanges(AccurevSCM.java:810) at hudson.scm.SCM.poll(SCM.java:375) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1588) at hudson.model.AbstractProject._poll(AbstractProject.java:1558) at hudson.model.AbstractProject.poll(AbstractProject.java:1490) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.