This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 56852 - Cannot register two AS 8.1 instances that listen on the same port
Summary: Cannot register two AS 8.1 instances that listen on the same port
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: Nitya Doraisamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-23 12:00 UTC by Kirill Sorokin
Modified: 2005-07-19 09:44 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kirill Sorokin 2005-03-23 12:00:11 UTC
I have two lcoal instances of the AS 8.1 set up to listen on the same port. I
want to register them both in the IDE. Obviously the attempt to add the second
fails, as it has the same url as the first. However, having the possibility to
add these two instances might be quite useful for example to test different
server configurations etc.
Perharps some additional properties should be used to distinguish between server
instances instead just their urls.
Comment 1 Sherold Dev 2005-03-23 13:49:54 UTC
belongs to sunappserv
Comment 2 Lukas Jungmann 2005-03-23 14:19:05 UTC
I'm not sure if this is P2 bug, because you can simply create new domain with
different configuration then the default one(domain1) and this new domain can be
registered in IDE. See 'asadmin create-domain' command.

BTW: Having installed 2 AS of the same version is wasting of resources, IMO.
Comment 3 Kirill Sorokin 2005-03-23 14:35:06 UTC
Actually that's what I mean - I have two domains that are set up to listen on
the same port. For example I have a client application that is configured to
connect to this specified port. I want to deploy an application on both these
domains and check whether it works correctly (using the client). 
Thus I need to register them both in the IDE for deployment of the application,
but their url's are identical and so I cannot register both domains.

PS Why was the issue transferred to sunappserv? I used it only as an example,
this  should belong to the j2eeserver.
Comment 4 _ ludo 2005-03-23 15:01:23 UTC
P4 at best...or not an issue.
A workaround is to register the first one, work with it, then once you are done,
remove it from the registry (popup menu), then register the 2nd one, so that you
can work with it.
It's more or less equivalent to say that you would like to save/use 2 different
files with the same name on the same folder.

Also this test is done at the app serfver plugin level, so this issue (if there
is a reall issue) is not in j2eeserver at all.

Also what is the 'specific port' your mention? Is it the same for the 2 instances?
What do you expect when you try to start the 2 servers together?

Comment 5 Kirill Sorokin 2005-03-23 15:08:08 UTC
Yes, the port is the same for the two instances. I do not intend to start them
simultaneously.

The real issue here is that we can have two different appserver instances which
both are identified the same url. We cannot register them both.
Comment 6 _ ludo 2005-03-23 15:42:12 UTC
Our plugin could popup a big warnng, but still register the duplicated instance.
Would that work?

Nitya, what do you think?
Comment 7 Ivan Sidorkin 2005-03-24 10:10:47 UTC
If I can create two domains with same port I should have possibility to register
these two domains simultaneously.
Comment 8 Nitya Doraisamy 2005-04-02 00:15:50 UTC
Adding two 8.1 instances listening to same port results in both nodes being
active irrespective of whether the two instances are running. This is because
the deployment manager url is the same for both the instances and the connection
to the server is valid. This results in runtime tree that always displays the
state of the running instance for both the 8.1 nodes. I don't think this is a
good user interface design. Will not fix.