I don't understand what you mean and I don't see anything in the
article you reference that relates to why we would change the port
from 1099. Could you explain?
AFAIK the only use we make of rmi is for jmx remoting for jsr88
deployment stuff. Is there some other use I'm not aware of?
I had raised this issue earlier:
http://www.nabble.com/Can-RMI-Naming-Port-be-1099--tf3454855s134.html#a9638251
I have not found a satisfactory explanation of this phenomenon...
Does anyone have any ideas?
Thanks
Anita
--- David Jencks [EMAIL PROTECTED] wrote:
I don't understand what you
--- Donald Woods [EMAIL PROTECTED] wrote:
And how does the portOffset relate to this? If you start with 1098,
isn't the next server instance going to use 1099 and the next one
1100?
If so, why not start with 1099 and let the next one use 1100 and
then
1101?
It's not clear to me
This change has completely broken the ability to run any of the TCK
interoperability tests.
Rick
Anita Kulshreshtha wrote:
--- Donald Woods [EMAIL PROTECTED] wrote:
And how does the portOffset relate to this? If you start with 1098,
isn't the next server instance going to use 1099 and
jaxws broke too
On 4/12/07, Rick McGuire [EMAIL PROTECTED] wrote:
This change has completely broken the ability to run any of the TCK
interoperability tests.
Rick
Anita Kulshreshtha wrote:
--- Donald Woods [EMAIL PROTECTED] wrote:
And how does the portOffset relate to this? If you start
On Apr 12, 2007, at 8:02 AM, Anita Kulshreshtha wrote:
I had raised this issue earlier:
http://www.nabble.com/Can-RMI-Naming-Port-be-1099--
tf3454855s134.html#a9638251
I have not found a satisfactory explanation of this phenomenon...
Does anyone have any ideas?
Hi Anita,
I think we
Kevan,
From our IRC conversation, it sounds like port 1099 needs to call to
LocateRegistry.createRegistry(port)
Assume the following server instances on the same box:
Server instance A with RMIRegistryService port set to 1079
Server instance B with RMIRegistryService port set to
--- Kevan Miller [EMAIL PROTECTED] wrote:
On Apr 12, 2007, at 8:02 AM, Anita Kulshreshtha wrote:
From our IRC conversation, it sounds like port 1099 needs to call to
LocateRegistry.createRegistry(port)
This is already being done in line 63. Should it be followed by
this?
Don't the following need to be updated too, given they are used
throughout the configs and assemblies?
assemblies\pom.xml 42 25:PlanNamingPort1099/PlanNamingPort
configs\pom.xml 63 25:PlanNamingPort1099/PlanNamingPort
Also, other references to 1099 in the source -
Why are we changing the port?
--jason
On Apr 11, 2007, at 7:33 PM, Donald Woods wrote:
Don't the following need to be updated too, given they are used
throughout the configs and assemblies?
assemblies\pom.xml 42 25:PlanNamingPort1099/
PlanNamingPort
configs\pom.xml 63 25:
In short, 1099 must be available to start other instances of
geronimo.
http://www.developer.com/java/ent/article.php/3455311
Thanks
Anita
--- Jason Dillon [EMAIL PROTECTED] wrote:
Why are we changing the port?
--jason
On Apr 11, 2007, at 7:33 PM, Donald Woods wrote:
Don't the
I don't get it... if we change the port to 1098... how then does some
other instance of Geronimo need 1099... and not 1098?
Is there anything specific on the document you linked to which
explains why we are changing the port? I quickly looked it over and
nothing stands out as
And how does the portOffset relate to this? If you start with 1098,
isn't the next server instance going to use 1099 and the next one 1100?
If so, why not start with 1099 and let the next one use 1100 and then
1101?
It's not clear to me either why the RMI port default needs to be
13 matches
Mail list logo
