[
http://jira.jboss.com/jira/browse/JBAS-3724?page=comments#action_12358725 ]
Grant Quimby commented on JBAS-3724:
------------------------------------
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.
NotFoundInDispatcherException from InvokerLocator when accessing
remote calls when on a non default port
--------------------------------------------------------------------------------------------------------
Key: JBAS-3724
URL:
http://jira.jboss.com/jira/browse/JBAS-3724
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployment services, EJB3, Remoting
Affects Versions: JBossAS-4.0.4.GA
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.
Reporter: Grant Quimby
Assigned To: Dimitris Andreadis
Priority: Blocker
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira