1 2 Previous Next 18 Replies Latest reply on Jan 4, 2018 8:29 AM by Jaikiran Pai Go to original post
      • 15. Re: Problem with http invocation of ejb
        peter craddock Novice

        I can try the fix if you can confirm the project it went into that would be great.

         

        I got the impression it was a client side fix but just let me know and I'll confirm its all ok

        • 16. Re: Problem with http invocation of ejb
          Jaikiran Pai Master

          It's the same project as the previous bug fix - this one GitHub - wildfly/wildfly-http-client: The client libraries that support EJB, Naming and Transactions over HTTP . So the steps would be the same to build and update the jar. The additional thing you would need to do is, include that jar in your client classpath (and make it gets picked up).

          • 17. Re: Problem with http invocation of ejb
            peter craddock Novice

            I did a pull and a clean install on the source and this built 4 jars

             

            ./transaction/target/wildfly-http-transaction-client-1.0.9.Final-SNAPSHOT.jar

            ./naming/target/wildfly-http-naming-client-1.0.9.Final-SNAPSHOT.jar

            ./common/target/wildfly-http-client-common-1.0.9.Final-SNAPSHOT.jar

            ./ejb/target/wildfly-http-ejb-client-1.0.9.Final-SNAPSHOT.jar

             

            I copied all 4 to the client machine ready for testing.

             

            I recreated the error case were the connection was closed after 60 seconds then altered the client class path so the 4 jars above were loaded before the wildfly-client jar and re tested the application. I can confirm that the fix solved the issue and the next invocation to the server was OK even after the connection had been asked to close.

             

            The log from the client is here, it shows close being called and the next lookup being performed.

             

            13:11:36,781 DEBUG [HttpClientConnection] close called on connection to /10.2.33.6:8020

            13:11:43,419 DEBUG [HttpClientConnection] close called on connection to /10.2.33.6:8020

            13:11:43,419 DEBUG [HttpClientConnection] connection to /10.2.33.6:8020 closed

            13:11:43,431 DEBUG [HttpClientConnection] close called on connection to /10.2.33.6:8020

            13:11:43,431 DEBUG [HttpClientConnection] connection to /10.2.33.6:8020 closed

            13:11:53,859 DEBUG [HttpClientExchange] request terminated for request to /10.2.33.6:8020 /wildfly-services/naming/v1/lookup/cp%2Fcp-server%2FListSEJB%21com.cedar.cp.ejb.api.base.ListRemote

            13:11:53,862 DEBUG [HttpClientConnection] connection to /10.2.33.6:8020 is being upgraded

            13:11:53,892 DEBUG [HttpClientExchange] request terminated for request to /10.2.33.6:8020 /wildfly-services/ejb/v1/invoke/cp/cp-server/-/ListSEJB/-/com.cedar.cp.ejb.api.base.ListRemote/getAllRolesByPage/int/int/boolean

            13:11:53,903 DEBUG [HttpClientConnection] connection to /10.2.33.6:8020 is being upgraded

            13:12:43,866 DEBUG [HttpClientConnection] close called on connection to /10.2.33.6:8020

            13:12:43,867 DEBUG [HttpClientConnection] connection to /10.2.33.6:8020 closed

            13:12:43,927 DEBUG [HttpClientConnection] close called on connection to /10.2.33.6:8020

            13:12:43,927 DEBUG [HttpClientConnection] connection to /10.2.33.6:8020 closed

             

            I think the fix for the client was actually in the wildfly-http-client-common-1.0.9.Final-SNAPSHOT.jar will I have to create a new version of of the wildfly-client.jar or will I be able to get this from a build server or maven repository ?

            • 18. Re: Problem with http invocation of ejb
              Jaikiran Pai Master

              Thank you for verifying the fix.

               

              crazycradd  wrote:

               

              I think the fix for the client was actually in the wildfly-http-client-common-1.0.9.Final-SNAPSHOT.jar

              That's correct - the fix was in the "common" module of that project.

               

              crazycradd  wrote:

               

              will I have to create a new version of of the wildfly-client.jar or will I be able to get this from a build server or maven repository ?

              You can wait a few days for the WildFly repo to use a newer released version of this project. Once that's done, you can use the WildFly binary from the nightly build server as noted here WildFly nightly builds available

              1 2 Previous Next