How to prevent “net::ERR_SPDY_PROTOCOL_ERROR 200” when connecting an Event Source to a Java Function that...





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I am using an EventSource in Javascript to connect to a Java Spring Boot endpoint.



This works fine when I connect the app to my localhost java server but while connecting to my dev server I keep getting a net::ERR_SPDY_PROTOCOL_ERROR 200 every 33 seconds or so.



I have the latest version of Chrome(v71).



What am I doing wrong?



This is the function in my Java Spring Boot Server:



@CrossOrigin
@RequestMapping(path = {"/sse"})
public SseEmitter handleSse(@RequestParam String callId) {
SseEmitter emitter = new SseEmitter(7200000L);
this.emitters.put(callId, emitter);
emitter.onCompletion(() -> this.emitters.remove(callId));
emitter.onTimeout(() -> this.emitters.remove(callId));
return emitter;
}









share|improve this question































    0















    I am using an EventSource in Javascript to connect to a Java Spring Boot endpoint.



    This works fine when I connect the app to my localhost java server but while connecting to my dev server I keep getting a net::ERR_SPDY_PROTOCOL_ERROR 200 every 33 seconds or so.



    I have the latest version of Chrome(v71).



    What am I doing wrong?



    This is the function in my Java Spring Boot Server:



    @CrossOrigin
    @RequestMapping(path = {"/sse"})
    public SseEmitter handleSse(@RequestParam String callId) {
    SseEmitter emitter = new SseEmitter(7200000L);
    this.emitters.put(callId, emitter);
    emitter.onCompletion(() -> this.emitters.remove(callId));
    emitter.onTimeout(() -> this.emitters.remove(callId));
    return emitter;
    }









    share|improve this question



























      0












      0








      0








      I am using an EventSource in Javascript to connect to a Java Spring Boot endpoint.



      This works fine when I connect the app to my localhost java server but while connecting to my dev server I keep getting a net::ERR_SPDY_PROTOCOL_ERROR 200 every 33 seconds or so.



      I have the latest version of Chrome(v71).



      What am I doing wrong?



      This is the function in my Java Spring Boot Server:



      @CrossOrigin
      @RequestMapping(path = {"/sse"})
      public SseEmitter handleSse(@RequestParam String callId) {
      SseEmitter emitter = new SseEmitter(7200000L);
      this.emitters.put(callId, emitter);
      emitter.onCompletion(() -> this.emitters.remove(callId));
      emitter.onTimeout(() -> this.emitters.remove(callId));
      return emitter;
      }









      share|improve this question
















      I am using an EventSource in Javascript to connect to a Java Spring Boot endpoint.



      This works fine when I connect the app to my localhost java server but while connecting to my dev server I keep getting a net::ERR_SPDY_PROTOCOL_ERROR 200 every 33 seconds or so.



      I have the latest version of Chrome(v71).



      What am I doing wrong?



      This is the function in my Java Spring Boot Server:



      @CrossOrigin
      @RequestMapping(path = {"/sse"})
      public SseEmitter handleSse(@RequestParam String callId) {
      SseEmitter emitter = new SseEmitter(7200000L);
      this.emitters.put(callId, emitter);
      emitter.onCompletion(() -> this.emitters.remove(callId));
      emitter.onTimeout(() -> this.emitters.remove(callId));
      return emitter;
      }






      java server-sent-events






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 3 at 11:12









      Peter Cordes

      135k19204345




      135k19204345










      asked Jan 3 at 10:58









      Sajjan Kumar JainSajjan Kumar Jain

      11




      11
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Turns out the issue was with the server request timing out. Our servers had a limit of 30 seconds for a response to be sent to a request. But an event source request needs to stay alive for longer.



          Changing the server timeout limit fixed the issue.






          share|improve this answer
























            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%2f54020969%2fhow-to-prevent-neterr-spdy-protocol-error-200-when-connecting-an-event-sourc%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Turns out the issue was with the server request timing out. Our servers had a limit of 30 seconds for a response to be sent to a request. But an event source request needs to stay alive for longer.



            Changing the server timeout limit fixed the issue.






            share|improve this answer




























              0














              Turns out the issue was with the server request timing out. Our servers had a limit of 30 seconds for a response to be sent to a request. But an event source request needs to stay alive for longer.



              Changing the server timeout limit fixed the issue.






              share|improve this answer


























                0












                0








                0







                Turns out the issue was with the server request timing out. Our servers had a limit of 30 seconds for a response to be sent to a request. But an event source request needs to stay alive for longer.



                Changing the server timeout limit fixed the issue.






                share|improve this answer













                Turns out the issue was with the server request timing out. Our servers had a limit of 30 seconds for a response to be sent to a request. But an event source request needs to stay alive for longer.



                Changing the server timeout limit fixed the issue.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 20 at 11:43









                Sajjan Kumar JainSajjan Kumar Jain

                11




                11
































                    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%2f54020969%2fhow-to-prevent-neterr-spdy-protocol-error-200-when-connecting-an-event-sourc%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

                    MongoDB - Not Authorized To Execute Command

                    in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith

                    Npm cannot find a required file even through it is in the searched directory