[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cosmos-dev] Port conflicts between COSMOS and other internal products
|
The COSMOS Web Interface does not reserve any ports.
The data collection components uses some ports. Hubert would you list the
ports that we are currently using.
Thanks,
Sheldon
______________________________________
Sheldon Lee-Loy
"Mohsin, Jimmy"
<Jimmy.Mohsin@ca.
com> To
Sent by: "Cosmos Dev"
cosmos-dev-bounce <cosmos-dev@xxxxxxxxxxx>
s@xxxxxxxxxxx cc
"Adivishnu, Kishore"
<Kishore.Adivishnu@xxxxxx>
04/03/2008 10:45 Subject
AM [cosmos-dev] Port conflicts between
COSMOS and other internal products
Please respond to
Cosmos Dev
<cosmos-dev@eclip
se.org>
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
_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev