Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-3309

Remote client couldn't connect EJB remote interface if the ejb3.deployer InvokerLocator port is set to non-default value. (other than 3873)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • No Release
    • JBossAS-4.0.4RC1, JBossAS-4.0.4.CR2, JBossAS-4.0.4.GA
    • EJB, Remoting
    • None

    • Tested on Windows 2003 server, Windows XP, Linux RHEL 4. HW platform - PC X86 (32 bit)

    • Workaround Exists
    • Hide

      To be able to connect EJB remote interface we must have in each bean written following annotaqation: @RemoteBinding(clientBindUrl="socket://10.0.100.255:3973/", jndiBinding="LookupTestRemote") (example) / then it works. But it isn't systematic solution - it's problematic to make different deployments.

      Show
      To be able to connect EJB remote interface we must have in each bean written following annotaqation: @RemoteBinding(clientBindUrl="socket://10.0.100.255:3973/", jndiBinding="LookupTestRemote") (example) / then it works. But it isn't systematic solution - it's problematic to make different deployments.

      When they are more than one instances of jboss as running on one machine, you have to change ports to non-default values because of avoiding port colission. (The problem is with the InvokerLocator port to EJB3.0 Connector: DefaultEjb3Connector)

              patriot1burke@gmail.com Bill Burke (Inactive)
              ipetros_jira Petr Zeman (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: