Button won't postback after long-lasting asyncs












0















I faced with a weird situation. Let's first take a look at a simple example in ASP.NET Web Forms:



<asp:UpdatePanel ID="UpdatePanel1" runat="server">
<ContentTemplate>
<asp:Button ID="testButton" runat="server" Text="Run" OnClick="testButton_Click" />
</ContentTemplate>
</asp:UpdatePanel>
<asp:UpdateProgress ID="UpdateProgress1" runat="server">
<ProgressTemplate>
Loading...
</ProgressTemplate>
</asp:UpdateProgress>
<asp:UpdatePanel ID="UpdatePanel2" runat="server">
<ContentTemplate>
<asp:Label ID="Label1" runat="server"></asp:Label>
</ContentTemplate>
<Triggers>
<asp:AsyncPostBackTrigger ControlID="testButton" EventName="Click" />
</Triggers>




public partial class About : Page
{
protected void Page_Load(object sender, EventArgs e)
{

}

protected async void testButton_Click(object sender, EventArgs e)
{
Task<string> List = new Task<string>
{
RunLong1(),
RunLong2()
};

string responses = await Task.WhenAll(List);

Label1.Text = responses[0] + " " + responses[1];
}

private async Task<string> RunLong1()
{
await Task.Run(() =>
{
System.Threading.Thread.Sleep(100000);
});
return "finished the async task 1";
}

private async Task<string> RunLong2()
{
await Task.Run(() =>
{
System.Threading.Thread.Sleep(60000);
});
return "finished the async task 1";
}

}


So, I have a button inside an update panel linked to an UpdateProgress panel. When the button is clicked, the UpdateProgress panel is triggered and the word "loading" appears. In addition, the same button is the trigger to another update panel where it posts back a result. When I click the button, two async methods start running in parallel mode. After they finish their tasks, a message is displayed.



Here it is the weird thing. If the running time of one of the async methods is more than 100,000 msec, then the button won't post back. The word "loading" stays there forever! If the duration of the async method is less than 100,000 msec, then when I click the button, it runs both RunLong1 & RunLong2 async methods and when all finish, the label1 inside the updatePanel2 displays a text and the word "loading" disappears.



Why does this happen? Why won't the button post back if one of the async methods lasts more than 100 sec?










share|improve this question



























    0















    I faced with a weird situation. Let's first take a look at a simple example in ASP.NET Web Forms:



    <asp:UpdatePanel ID="UpdatePanel1" runat="server">
    <ContentTemplate>
    <asp:Button ID="testButton" runat="server" Text="Run" OnClick="testButton_Click" />
    </ContentTemplate>
    </asp:UpdatePanel>
    <asp:UpdateProgress ID="UpdateProgress1" runat="server">
    <ProgressTemplate>
    Loading...
    </ProgressTemplate>
    </asp:UpdateProgress>
    <asp:UpdatePanel ID="UpdatePanel2" runat="server">
    <ContentTemplate>
    <asp:Label ID="Label1" runat="server"></asp:Label>
    </ContentTemplate>
    <Triggers>
    <asp:AsyncPostBackTrigger ControlID="testButton" EventName="Click" />
    </Triggers>




    public partial class About : Page
    {
    protected void Page_Load(object sender, EventArgs e)
    {

    }

    protected async void testButton_Click(object sender, EventArgs e)
    {
    Task<string> List = new Task<string>
    {
    RunLong1(),
    RunLong2()
    };

    string responses = await Task.WhenAll(List);

    Label1.Text = responses[0] + " " + responses[1];
    }

    private async Task<string> RunLong1()
    {
    await Task.Run(() =>
    {
    System.Threading.Thread.Sleep(100000);
    });
    return "finished the async task 1";
    }

    private async Task<string> RunLong2()
    {
    await Task.Run(() =>
    {
    System.Threading.Thread.Sleep(60000);
    });
    return "finished the async task 1";
    }

    }


    So, I have a button inside an update panel linked to an UpdateProgress panel. When the button is clicked, the UpdateProgress panel is triggered and the word "loading" appears. In addition, the same button is the trigger to another update panel where it posts back a result. When I click the button, two async methods start running in parallel mode. After they finish their tasks, a message is displayed.



    Here it is the weird thing. If the running time of one of the async methods is more than 100,000 msec, then the button won't post back. The word "loading" stays there forever! If the duration of the async method is less than 100,000 msec, then when I click the button, it runs both RunLong1 & RunLong2 async methods and when all finish, the label1 inside the updatePanel2 displays a text and the word "loading" disappears.



    Why does this happen? Why won't the button post back if one of the async methods lasts more than 100 sec?










    share|improve this question

























      0












      0








      0








      I faced with a weird situation. Let's first take a look at a simple example in ASP.NET Web Forms:



      <asp:UpdatePanel ID="UpdatePanel1" runat="server">
      <ContentTemplate>
      <asp:Button ID="testButton" runat="server" Text="Run" OnClick="testButton_Click" />
      </ContentTemplate>
      </asp:UpdatePanel>
      <asp:UpdateProgress ID="UpdateProgress1" runat="server">
      <ProgressTemplate>
      Loading...
      </ProgressTemplate>
      </asp:UpdateProgress>
      <asp:UpdatePanel ID="UpdatePanel2" runat="server">
      <ContentTemplate>
      <asp:Label ID="Label1" runat="server"></asp:Label>
      </ContentTemplate>
      <Triggers>
      <asp:AsyncPostBackTrigger ControlID="testButton" EventName="Click" />
      </Triggers>




      public partial class About : Page
      {
      protected void Page_Load(object sender, EventArgs e)
      {

      }

      protected async void testButton_Click(object sender, EventArgs e)
      {
      Task<string> List = new Task<string>
      {
      RunLong1(),
      RunLong2()
      };

      string responses = await Task.WhenAll(List);

      Label1.Text = responses[0] + " " + responses[1];
      }

      private async Task<string> RunLong1()
      {
      await Task.Run(() =>
      {
      System.Threading.Thread.Sleep(100000);
      });
      return "finished the async task 1";
      }

      private async Task<string> RunLong2()
      {
      await Task.Run(() =>
      {
      System.Threading.Thread.Sleep(60000);
      });
      return "finished the async task 1";
      }

      }


      So, I have a button inside an update panel linked to an UpdateProgress panel. When the button is clicked, the UpdateProgress panel is triggered and the word "loading" appears. In addition, the same button is the trigger to another update panel where it posts back a result. When I click the button, two async methods start running in parallel mode. After they finish their tasks, a message is displayed.



      Here it is the weird thing. If the running time of one of the async methods is more than 100,000 msec, then the button won't post back. The word "loading" stays there forever! If the duration of the async method is less than 100,000 msec, then when I click the button, it runs both RunLong1 & RunLong2 async methods and when all finish, the label1 inside the updatePanel2 displays a text and the word "loading" disappears.



      Why does this happen? Why won't the button post back if one of the async methods lasts more than 100 sec?










      share|improve this question














      I faced with a weird situation. Let's first take a look at a simple example in ASP.NET Web Forms:



      <asp:UpdatePanel ID="UpdatePanel1" runat="server">
      <ContentTemplate>
      <asp:Button ID="testButton" runat="server" Text="Run" OnClick="testButton_Click" />
      </ContentTemplate>
      </asp:UpdatePanel>
      <asp:UpdateProgress ID="UpdateProgress1" runat="server">
      <ProgressTemplate>
      Loading...
      </ProgressTemplate>
      </asp:UpdateProgress>
      <asp:UpdatePanel ID="UpdatePanel2" runat="server">
      <ContentTemplate>
      <asp:Label ID="Label1" runat="server"></asp:Label>
      </ContentTemplate>
      <Triggers>
      <asp:AsyncPostBackTrigger ControlID="testButton" EventName="Click" />
      </Triggers>




      public partial class About : Page
      {
      protected void Page_Load(object sender, EventArgs e)
      {

      }

      protected async void testButton_Click(object sender, EventArgs e)
      {
      Task<string> List = new Task<string>
      {
      RunLong1(),
      RunLong2()
      };

      string responses = await Task.WhenAll(List);

      Label1.Text = responses[0] + " " + responses[1];
      }

      private async Task<string> RunLong1()
      {
      await Task.Run(() =>
      {
      System.Threading.Thread.Sleep(100000);
      });
      return "finished the async task 1";
      }

      private async Task<string> RunLong2()
      {
      await Task.Run(() =>
      {
      System.Threading.Thread.Sleep(60000);
      });
      return "finished the async task 1";
      }

      }


      So, I have a button inside an update panel linked to an UpdateProgress panel. When the button is clicked, the UpdateProgress panel is triggered and the word "loading" appears. In addition, the same button is the trigger to another update panel where it posts back a result. When I click the button, two async methods start running in parallel mode. After they finish their tasks, a message is displayed.



      Here it is the weird thing. If the running time of one of the async methods is more than 100,000 msec, then the button won't post back. The word "loading" stays there forever! If the duration of the async method is less than 100,000 msec, then when I click the button, it runs both RunLong1 & RunLong2 async methods and when all finish, the label1 inside the updatePanel2 displays a text and the word "loading" disappears.



      Why does this happen? Why won't the button post back if one of the async methods lasts more than 100 sec?







      asynchronous button postback






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 24 '18 at 0:15









      Nassos KranidiotisNassos Kranidiotis

      11




      11
























          0






          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53454125%2fbutton-wont-postback-after-long-lasting-asyncs%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53454125%2fbutton-wont-postback-after-long-lasting-asyncs%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          404 Error Contact Form 7 ajax form submitting

          How to know if a Active Directory user can login interactively

          Refactoring coordinates for Minecraft Pi buildings written in Python