On Friday, March 12, 1999 3:47 PM, Greg Ritter [SMTP:[EMAIL PROTECTED]] wrote:
> [EMAIL PROTECTED] wrote:
> > [snip]
> > The protocol [Oracle] uses is such that when you
> > wish to make a database connection, you connect to a given port and
then
> > oracle dynamcally creates a new port for you to connect to. A firewall
that
> > allowed you to connect to random ports would not be much of a firewall.
> >
>
> Are you sure that it actually uses a random port? I've always used
> Oracle thin jdbc urls like "jdbc:oracle:thin:@machine:1521:orcl", which
> indicates it should connect to port 1521 on machine, and ask the
> listener for SID orcl. Are you saying that this port is only used for
> setup, and then communication is done on some other random port?
>
> I've never had a problem with connecting across the firewall from a
> servlet here at work to Oracle instances on my home machine, assuming
> that port 1521 was kept open. I assumed that the actual communication
> was done over this port.
>
Oracle connections are normal TCP/IP connections. A listener process
listens on a well known port, defined in the Oracle configuration. When a
connection is accepted it is inherited by a child process which manages
that connection. An Oracle option known (and misnamed) as Multi-Threaded
Server (MTS) pre-starts a fixed number of child processes which act as a
pool and are assigned to a connection on a transaction by transaction
basis. The latter allow large number of connected users without
overwhelming the server with processes.
Regards,
Bob
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://www.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
