Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-10137

EJB lookup over HTTP fails if object is used in the signiture

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 11.0.0.Final
    • Fix Version/s: None
    • Component/s: EJB, Remoting
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      invoke method with object in the signature using HTTP connection
      Context.PROVIDER_URL, http://localhost:8080/wildfly-services

      use TCP and method will work
      Context.PROVIDER_URL, remote+http://localhost:8080/wildfly-services

      Show
      invoke method with object in the signature using HTTP connection Context.PROVIDER_URL, http://localhost:8080/wildfly-services use TCP and method will work Context.PROVIDER_URL, remote+ http://localhost:8080/wildfly-services

      Description

      I have a swing client that makes calls to the EJB tier via RMI the majority of the calls work fine using the workaround from WFLY-9636.

      The following calls was failing when connected over HTTP but was fine when using the original TCP connection

      public EntityList getAllWorkingSetsForCube( ModelRef modelRef, FinanceCubeRef financeCubeRef, int userId, Integer[] allowedStates )

      I worked round this and found that creating a method without the Integer[] as part of the signature works.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                parsharma Parul Sharma
                Reporter:
                crazycradd peter craddock
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: