Uploaded image for project: '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
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: 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

      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

          Attachments

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: