Uploaded image for project: 'Bitbucket Server'
  1. Bitbucket Server
  2. BSERV-11330

After upgrading to Bitbucket 5.13+, the following warning is reported in the logs

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Highest
    • Resolution: Fixed
    • 5.13.0, 5.14.0, 5.13.1, 5.13.3, 5.14.1
    • 5.13.4, 5.14.2, 5.15.1, 5.16.0
    • None

    Description

      Summary

      After upgrading to 5.13.+, the application logs contain the there was problem terminating git-upload-pack message.

      Apart from this warning message in the logs, there is no other symptom and no impact.

      Steps to Reproduce

      It can be reproduced intermittently by performing multiple concurrent git fetches of the same repository at the same time over the ssh protocol and when it's either a cache:miss or a cache:bypass (ref advertisement cache is not enabled).

      Expected Results

      No warning message should appear in the application logs.

      Actual Results

      The below exception is thrown in the atlassian-bitbucket.log file:

      WARN [ssh-scm-request-handler] <user> <session> <ip> SSH - git-upload-pack '<repository>' c.a.s.i.s.g.p.s.CachingSshUploadPack <project>/<repository>[<repository_id>]: there was problem terminating git-upload-pack
      java.io.IOException: Stream closed
      	at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170)
      	at java.io.BufferedInputStream.read(BufferedInputStream.java:336)
      	at java.io.FilterInputStream.read(FilterInputStream.java:133)
      	at com.atlassian.utils.process.WatchdogAwareInputStream.read(WatchdogAwareInputStream.java:44)
      	at java.io.FilterInputStream.read(FilterInputStream.java:107)
      	at com.atlassian.utils.process.WatchdogAwareInputStream.read(WatchdogAwareInputStream.java:37)
      	at com.atlassian.stash.internal.scm.git.protocol.InteractiveHostingCommand.copyAll(InteractiveHostingCommand.java:158)
      	at com.atlassian.stash.internal.scm.git.protocol.InteractiveHostingCommand.access$700(InteractiveHostingCommand.java:31)
      	at com.atlassian.stash.internal.scm.git.protocol.InteractiveHostingCommand$CopyRemainingHandler.processStdOut(InteractiveHostingCommand.java:440)
      	at com.atlassian.stash.internal.scm.git.protocol.InteractiveHostingCommand$DispatchingOutputHandler.process(InteractiveHostingCommand.java:313)
      	at com.atlassian.bitbucket.scm.SummarizingProcessHandler$DelegatingInputStreamHandler.process(SummarizingProcessHandler.java:184)
      	at com.atlassian.bitbucket.scm.SummarizingProcessHandler$DelegatingInputStreamHandler.process(SummarizingProcessHandler.java:166)
      	at com.atlassian.bitbucket.scm.SummarizingProcessHandler.processOutput(SummarizingProcessHandler.java:90)
      	at com.atlassian.utils.process.ExternalProcessImpl$StdoutHandler.handle(ExternalProcessImpl.java:794)
      	at com.atlassian.utils.process.ExternalProcessImpl$HandlerLatchedRunnable.doTask(ExternalProcessImpl.java:731)
      	at com.atlassian.utils.process.LatchedRunnable.run(LatchedRunnable.java:158)
      	at com.atlassian.utils.process.ExternalProcessImpl$AsynchronousHandlerLatchedRunnable.run(ExternalProcessImpl.java:700)
      	at com.atlassian.stash.internal.concurrent.DefaultTransferableStateManager$StateTransferringRunnable.run(DefaultTransferableStateManager.java:166)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      	at java.lang.Thread.run(Thread.java:748)
      	... 1 frame trimmed
      

      Workaround

      Not available.

      Attachments

        Issue Links

          Activity

            People

              csubraveti Chandravadan
              ccurti Caterina Curti (Kate)
              Votes:
              2 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: