java.io.IOException

The taskhelper REST resource reported that task named 'EvictUnusedProxiedItemsTask' still running after '300' cycles! This may indicate a performance issue.

Samebug tips0

We couldn't find tips for this exception.

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

Solutions on the web3

  • via Unknown by Benjamin Hanzelmann,
  • via Unknown by Benjamin Hanzelmann,
  • via Unknown by Benjamin Hanzelmann,
  • Stack trace

    • java.io.IOException: The taskhelper REST resource reported that task named 'EvictUnusedProxiedItemsTask' still running after '300' cycles! This may indicate a performance issue. at org.sonatype.nexus.test.utils.TasksNexusRestClient.waitForTask(TasksNexusRestClient.java:252) at org.sonatype.nexus.test.utils.TasksNexusRestClient.runTask(TasksNexusRestClient.java:343) at org.sonatype.nexus.test.utils.TaskScheduleUtil.runTask(TaskScheduleUtil.java:202) at org.sonatype.nexus.integrationtests.nexus2692.AbstractEvictTaskIt.runTask(AbstractEvictTaskIt.java:207) at org.sonatype.nexus.integrationtests.nexus2692.Nexus2692EvictAllTaskIT.testEvictAllRepos(Nexus2692EvictAllTaskIT.java:29) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:70) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:158) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:98) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)

    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

    We couldn't find other users who have seen this exception.