This is completely naive and ignoring actual realities,
but it would seem to me that port assignment should be
completely configurable
So this should IMHO be a non-issue, but see first line.
- John
From: cosmos-dev-bounces@xxxxxxxxxxx
[mailto:cosmos-dev-bounces@xxxxxxxxxxx] On
Behalf Of Mohsin, Jimmy
Sent: Thursday, April 03, 2008
10:46 AM
To: Cosmos
Dev
Cc: Adivishnu,
Kishore
Subject: [cosmos-dev] Port
conflicts between COSMOS and other internalproducts
Team,
I am
running into a port conflict situation when I installed COSMOS i9 on an
internal staging server… Some comments / questions, please note that some
of these are not directly connected with COSMOS… but then I am never shy
of asking J
1.
I propose that we have a section
SOMEWHERE in our documentation that talks about the TOTALITY of the ports used
by COSMOS (including the pre-requisites et al). If such a page exists,
can someone please point me to it?
2.
What is our position on port
assignments? In case some port are “reserved” for COSMOS (I hope
such is not the case), what do we do if there is a conflict with a production
application which says, “Heck no, we will not reassign any of our
ports!!” ?
3.
If there are any port conflicts,
is there a recommended port mapper tool that we should suggest for our
adopters?
4.
Kish / Srini, has QA considered port conflict
/ assignment as part of their activities?
Thanks,
Jimmy Mohsin
Cell +1-609-635-1703