Application Server 3  4  5 and 6
  1. Application Server 3 4 5 and 6
  2. JBAS-3724

NotFoundInDispatcherException from InvokerLocator when accessing remote calls when on a non default port

    Details

    • Type: Bug Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker Blocker
    • Resolution: Out of Date Out of Date
    • Affects Version/s: JBossAS-4.0.4.GA
    • Fix Version/s: No Release
    • Component/s: Deployers, EJB, Remoting
    • Labels:
      None
    • Environment:
      One JBoss 4.0.4.GA install with two instances, one on the default ports and one on ports with an increase of 1000 on all port numbers.
    • Affects:
      Compatibility/Configuration
    • Estimated Difficulty:
      Low
    • Similar Issues:
      Show 10 results 

      Description

      When trying to access a remote application that is running in a server instance that does not have the default InvokerLocator port (3873) the remote caller recieves a NotFoundInDispatcherException when trying to call a method in the EJB3 Stateless Session Bean as the EJB3 Session Bean's InvokerLocator is at port 4873 and not port 3873 where the Remote Proxy looks.

      Similar issue for Service Beans at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=89537

      This is okay presently but in approximately two weeks we need to be running four instances with Session beans in two of them, which is currently not possible in a production version.

        Gliffy Diagrams

          Activity

          Hide
          Marady Prak added a comment -

          Check your network setting. In order to get two instances to work on the same NIC you have to configure multiple IP address on the NIC and point each of the instance to bind to the specific address/name (look at startup parameters on how to do this).

          Show
          Marady Prak added a comment - Check your network setting. In order to get two instances to work on the same NIC you have to configure multiple IP address on the NIC and point each of the instance to bind to the specific address/name (look at startup parameters on how to do this).
          Hide
          Grant Quimby added a comment -

          Network settings are fine. Using bindings to separate the instances. And running referring to only internal references works okay.

          Its only when referencing across instances that problems occur. And then only when using the non-standard ports (Unable to use standard JBoss ports as they are already in use).

          Instance 1
          HTTP : 8880
          Invoker : 4873

          Instance 2
          HTTP : 9880
          Invoker : 5873

          When doing a remote lookup from instance 1 to instance 2 or vica versa the Invoker says it can't find the reference. A debug check shows it looking for the reference at port 3873.

          Hope that clarifies things.

          Show
          Grant Quimby added a comment - Network settings are fine. Using bindings to separate the instances. And running referring to only internal references works okay. Its only when referencing across instances that problems occur. And then only when using the non-standard ports (Unable to use standard JBoss ports as they are already in use). Instance 1 HTTP : 8880 Invoker : 4873 Instance 2 HTTP : 9880 Invoker : 5873 When doing a remote lookup from instance 1 to instance 2 or vica versa the Invoker says it can't find the reference. A debug check shows it looking for the reference at port 3873. Hope that clarifies things.
          Hide
          Jason Greene added a comment -

          Now that work is well underway with AS7, all previous community releases are end-of-lifed. So, all issues not directly assigned to an AS7 release are being closed.

          JBoss EAP is our supported enterprise version of AS, and you can file your issues against any release during its very long support window via CSP/RHN.

          If you believe your issue is still relevant to AS7 then please verify it and reopen.

          Show
          Jason Greene added a comment - Now that work is well underway with AS7, all previous community releases are end-of-lifed. So, all issues not directly assigned to an AS7 release are being closed. JBoss EAP is our supported enterprise version of AS, and you can file your issues against any release during its very long support window via CSP/RHN. If you believe your issue is still relevant to AS7 then please verify it and reopen.

            People

            • Assignee:
              Dimitris Andreadis
              Reporter:
              Grant Quimby
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development