java.lang.NullPointerException

This exception has no message.

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 web123786

  • via Terracotta by unnutz, 11 months ago
    This exception has no message.
  • This exception has no message.
  • This exception has no message.
  • Stack trace

    • java.lang.NullPointerException at org.cloudfoundry.client.lib.archive.AbstractApplicationArchiveEntry.deduceMissingData(AbstractApplicationArchiveEntry.java:105) at org.cloudfoundry.client.lib.archive.AbstractApplicationArchiveEntry.getSha1Digest(AbstractApplicationArchiveEntry.java:74) at org.cloudfoundry.ide.eclipse.internal.server.core.ModuleResourceApplicationArchive$ModuleFileEntryAdapter.computeNewDeployedResourceEntry(ModuleResourceApplicationArchive.java:311) at org.cloudfoundry.ide.eclipse.internal.server.core.ModuleResourceApplicationArchive$ModuleFileEntryAdapter.getDeployedResourcesEntry(ModuleResourceApplicationArchive.java:299) at org.cloudfoundry.ide.eclipse.internal.server.core.ModuleResourceApplicationArchive$ModuleFileEntryAdapter.getSize(ModuleResourceApplicationArchive.java:289) at org.cloudfoundry.client.lib.CloudResources.<init>(CloudResources.java:88) at org.cloudfoundry.client.lib.CloudFoundryClient.getKnownRemoteResources(CloudFoundryClient.java:384) at org.cloudfoundry.client.lib.CloudFoundryClient.uploadApplication(CloudFoundryClient.java:375) at org.cloudfoundry.ide.eclipse.internal.server.core.CloudFoundryServerBehaviour.doDeployApplication(CloudFoundryServerBehaviour.java:255) at org.cloudfoundry.ide.eclipse.internal.server.core.CloudFoundryServerBehaviour.access$2(CloudFoundryServerBehaviour.java:220) at org.cloudfoundry.ide.eclipse.internal.server.core.CloudFoundryServerBehaviour$StartOrDeployAction$1.doRun(CloudFoundryServerBehaviour.java:1348) at org.cloudfoundry.ide.eclipse.internal.server.core.CloudFoundryServerBehaviour$StartOrDeployAction$1.doRun(CloudFoundryServerBehaviour.java:1) at org.cloudfoundry.ide.eclipse.internal.server.core.CloudFoundryServerBehaviour$Request.run(CloudFoundryServerBehaviour.java:1170) at org.cloudfoundry.ide.eclipse.internal.server.core.CloudFoundryServerBehaviour$StartOrDeployAction.performDeployment(CloudFoundryServerBehaviour.java:1371) at org.cloudfoundry.ide.eclipse.internal.server.core.CloudFoundryServerBehaviour$DeployAction.deployModule(CloudFoundryServerBehaviour.java:1236) at org.cloudfoundry.ide.eclipse.internal.server.core.CloudFoundryServerBehaviour.doDeployOrStartModule(CloudFoundryServerBehaviour.java:601) at org.cloudfoundry.ide.eclipse.internal.server.core.CloudFoundryServerBehaviour.updateRestartModuleRunMode(CloudFoundryServerBehaviour.java:712) at org.cloudfoundry.ide.eclipse.internal.server.ui.actions.StartStopApplicationAction.performAction(StartStopApplicationAction.java:84) at org.cloudfoundry.ide.eclipse.internal.server.ui.actions.CloudFoundryEditorAction$1.run(CloudFoundryEditorAction.java:91) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

    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.