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

violation of call-by-value if a outbound connection is configured

    Details

    • Steps to Reproduce:
      Hide

      Every invocation inside of the deployed application EAR/JAR using @Remote interface is affected if a jboss-ejb-client.xml is added to have a remote-outbound-connection for ejb invocation.
      It does not matter whether there is a running remote instance or the EJB is available remote!!

      Show
      Every invocation inside of the deployed application EAR/JAR using @Remote interface is affected if a jboss-ejb-client.xml is added to have a remote-outbound-connection for ejb invocation. It does not matter whether there is a running remote instance or the EJB is available remote!!

      Description

      If the server default configuration is used an EJB invocation via @Remote interface is, according to the specification, with call-by-value.

      But if the application is configured with jboss-ejb-client.xml to have a remote-outbound-connection the EJB invocation via @Remote is done as call-by-reference no matter whether the configuration is default or
      <in-vm-remote-interface-invocation pass-by-value="true"/>
      is used.

      This is a violation of the specification and can cause serious unexpected issues at runtime for the application if the parameters or return values are mutable

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  flavia.rainone Flavia Rainone
                  Reporter:
                  wdfink Wolf-Dieter Fink
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: