java.util.NoSuchElementException

property swift.endpoint not present in properties: [jclouds.user-threads, jclouds.identity, jclouds.max-session-failures, jclouds.max-connection-reuse, jclouds.scheduler-threads, jclouds.credential, jclouds.build-version, jclouds.iso3166-codes, jclouds.blobstore.metaprefix, jclouds.so-timeout, jclouds.max-connections-per-host, jclouds.max-connections-per-context, jclouds.strip-expect-header, jclouds.regions, jclouds.io-worker-threads, jclouds.api, jclouds.api-version, jclouds.payloads.pretty-print, jclouds.connection-timeout, jclouds.provider, jclouds.session-interval]

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 web733

  • via Stack Overflow by donof43
    , 1 year ago
    , jclouds.blobstore.metaprefix, jclouds.so-timeout, jclouds.max-connections-per-host, jclouds.max-connections-per-context, jclouds.strip-expect-header, jclouds.regions, jclouds.io-worker-threads, jclouds.api, jclouds.api-version, jclouds.payloads.pretty-print, jclouds.connection-timeout, jclouds.provider, jclouds.session-interval]
  • Timeout waiting for idle object
  • Timeout waiting for idle object
  • Stack trace

    • java.util.NoSuchElementException: property swift.endpoint not present in properties: [jclouds.user-threads, jclouds.identity, jclouds.max-session-failures, jclouds.max-connection-reuse, jclouds.scheduler-threads, jclouds.credential, jclouds.build-version, jclouds.iso3166-codes, jclouds.blobstore.metaprefix, jclouds.so-timeout, jclouds.max-connections-per-host, jclouds.max-connections-per-context, jclouds.strip-expect-header, jclouds.regions, jclouds.io-worker-threads, jclouds.api, jclouds.api-version, jclouds.payloads.pretty-print, jclouds.connection-timeout, jclouds.provider, jclouds.session-interval] at org.jclouds.ContextBuilder.searchPropertiesForProviderScopedProperty(ContextBuilder.java:293) at org.jclouds.ContextBuilder.resolveProperties(ContextBuilder.java:412) at org.jclouds.ContextBuilder.buildInjector(ContextBuilder.java:316) at org.jclouds.ContextBuilder.buildView(ContextBuilder.java:618) at org.jclouds.ContextBuilder.buildView(ContextBuilder.java:598) at jenkins.plugins.jclouds.blobstore.BlobStoreProfile.ctx(BlobStoreProfile.java:79) at jenkins.plugins.jclouds.blobstore.BlobStoreProfile.upload(BlobStoreProfile.java:105) at jenkins.plugins.jclouds.blobstore.BlobStorePublisher.perform(BlobStorePublisher.java:159) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)

    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.