Getting webService must not be null error

Issue #61 open
Peter Burrows created an issue

The majority of our build are failing with the following error:

Errors getting changes for --** (com.atlassian.bamboo.repository.RepositoryException : java.lang.RuntimeException: com.atlassian.bamboo.repository.RepositoryException: java.lang.NullPointerException: webService must not be null)

The logs give no real indication of what is causing it, can you shed any light on this?

Comments (9)

  1. Peter Burrows reporter

    Is this what you are looking for:

    com.atlassian.bamboo.repository.RepositoryException: java.lang.RuntimeException: com.atlassian.bamboo.repository.RepositoryException: java.lang.NullPointerException: webService must not be null
        at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectChangesSinceLastBuildInternal(DefaultChangeDetectionManager.java:398)
        at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectChangesSinceRevisions(DefaultChangeDetectionManager.java:286)
        at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectChangesSinceRevisions(DefaultChangeDetectionManager.java:185)
        at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectAllChangesSinceLastBuild(DefaultChangeDetectionManager.java:142)
        at com.atlassian.bamboo.v2.trigger.ManualBuildDetectionAction.performDelayedChangeDetection(ManualBuildDetectionAction.java:173)
        at com.atlassian.bamboo.chains.ChainExecutionManagerImpl$2.getChainState(ChainExecutionManagerImpl.java:209)
        at com.atlassian.bamboo.chains.ChainExecutionManagerImpl.tryStartChainState(ChainExecutionManagerImpl.java:262)
        at com.atlassian.bamboo.chains.ChainExecutionManagerImpl.delayedStart(ChainExecutionManagerImpl.java:198)
        at sun.reflect.GeneratedMethodAccessor1639.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:304)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
        at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
        at com.sun.proxy.$Proxy100.delayedStart(Unknown Source)
        at com.atlassian.bamboo.plan.PlanExecutionManagerImpl$1$1$1$1.run(PlanExecutionManagerImpl.java:405)
        at com.atlassian.bamboo.util.CacheAwareness.whileReadingThroughCaches(CacheAwareness.java:85)
        at com.atlassian.bamboo.util.CacheAwareness.whileReadingThroughCaches(CacheAwareness.java:102)
        at com.atlassian.bamboo.plan.PlanExecutionManagerImpl$1$1$1.call(PlanExecutionManagerImpl.java:400)
        at com.atlassian.bamboo.plan.PlanExecutionManagerImpl$1$1$1.call(PlanExecutionManagerImpl.java:394)
        at com.atlassian.util.concurrent.ManagedLocks$ManagedLockImpl.withLock(ManagedLocks.java:312)
        at com.atlassian.bamboo.plan.PlanExecutionLockServiceImpl.lock(PlanExecutionLockServiceImpl.java:85)
        at com.atlassian.bamboo.plan.PlanExecutionManagerImpl.doWithProcessLock(PlanExecutionManagerImpl.java:761)
        at com.atlassian.bamboo.plan.PlanExecutionManagerImpl.access$200(PlanExecutionManagerImpl.java:126)
        at com.atlassian.bamboo.plan.PlanExecutionManagerImpl$1$1.run(PlanExecutionManagerImpl.java:388)
        at com.atlassian.bamboo.utils.BambooRunnables$1.run(BambooRunnables.java:49)
        at com.atlassian.bamboo.security.ImpersonationHelper.runWith(ImpersonationHelper.java:31)
        at com.atlassian.bamboo.security.ImpersonationHelper.runWithSystemAuthority(ImpersonationHelper.java:20)
        at com.atlassian.bamboo.security.ImpersonationHelper$1.run(ImpersonationHelper.java:52)
        at java.lang.Thread.run(Unknown Source)
    Caused by: java.lang.RuntimeException: com.atlassian.bamboo.repository.RepositoryException: java.lang.NullPointerException: webService must not be null
        at com.atlassian.bamboo.executor.RetryingTaskExecutor.rerun(RetryingTaskExecutor.java:132)
        at com.atlassian.bamboo.executor.RetryingTaskExecutor.runTask(RetryingTaskExecutor.java:88)
        at com.atlassian.bamboo.executor.RetryingTaskExecutor.retry(RetryingTaskExecutor.java:191)
        at com.atlassian.bamboo.executor.RetryingTaskExecutor.retry(RetryingTaskExecutor.java:176)
        at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectionChangesWithRetry(DefaultChangeDetectionManager.java:501)
        at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectChangesSinceLastBuildInternal(DefaultChangeDetectionManager.java:358)
        ... 32 more
    Caused by: com.atlassian.bamboo.repository.RepositoryException: java.lang.NullPointerException: webService must not be null
        at com.stellarity.bamboo.repository.TfsRepository.collectChanges(TfsRepository.java:330)
        at com.stellarity.bamboo.repository.TfsRepository.collectChangesSinceLastBuild(TfsRepository.java:217)
        at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager$2.call(DefaultChangeDetectionManager.java:506)
        at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager$2.call(DefaultChangeDetectionManager.java:502)
        at com.atlassian.bamboo.executor.RetryingTaskExecutor.rerun(RetryingTaskExecutor.java:108)
        ... 37 more
    Caused by: java.lang.NullPointerException: webService must not be null
        at com.microsoft.tfs.util.Check.throwForNull(Check.java:135)
        at com.microsoft.tfs.util.Check.notNull(Check.java:28)
        at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.<init>(VersionControlClient.java:438)
        at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.<init>(VersionControlClient.java:520)
        at com.microsoft.tfs.core.config.client.DefaultClientFactory$7.newClient(DefaultClientFactory.java:238)
        at com.microsoft.tfs.core.config.client.DefaultClientFactory.newClient(DefaultClientFactory.java:91)
        at com.microsoft.tfs.core.TFSConnection.getClient(TFSConnection.java:1470)
        at com.microsoft.tfs.core.TFSTeamProjectCollection.getVersionControlClient(TFSTeamProjectCollection.java:359)
        at com.stellarity.bamboo.repository.TfsRepository.collectChanges(TfsRepository.java:252)
        ... 41 more
    

    if not let me know where to find it...

    Thanks Pete

  2. Peter Burrows reporter

    Hi Sergey,

    Thanks that has fixed the problem.

    Just for anyone else who may come across this ticket from search or such like, the exact steps were as follows: 1. Ensure no builds running 2. Stop Apache Tomcat Bamboo windows service 3. Delete contents of %localappdata%\Microsoft\Team Foundation\4.0\Cache - Ensure empty Cache folder is present afterwards or Bamboo won't restart 4. Restart Apache Tomcat Bamboo

    Thanks Pete

  3. Sergey Podobry

    I'm glad it helped. Meanwhile I'll try to figure out what happened under the hood and how to avoid it in future.

  4. MickS

    Hi, Running Bamboo 5.9.4 and stumbled upon this error. We run on a Linux host with Windows buildagents. The path equivalent of the solution on a Linux host is the following:

    ~/.microsoft/Team Foundation/4.0/Cache
    

    I deleted both Tee-* folders in a running instance from the Cache folder and the problem was resolved. The folders were automatically recreated.

  5. Sergey Podobry

    Hi Mick van der Most van Spijk,

    Thanks for sharing!

    Do you know how to reproduce this issue? I'd like to add automatic cache cleanup in case of errors but I need a way to test it.

  6. Brian Andersen

    Had this issue today with Bamboo version 5.14.3.1 build 51416. Was able to resolve by following Mick's advice and deleting ~/.microsoft/Team Foundation/4.0/Cache/TEE-* directories.

  7. Log in to comment