Forum Post: RE: Database and Apppserver port range set-up

  • Thread starter Thread starter rcluer
  • Start date Start date
Status
Not open for further replies.
R

rcluer

Guest
Nice answer Rob .. it's so often the 20:20 hindsight that proves the case. The -minport -maxport parameters to restrict port ranges used by Brokers were introduced way back in v8.2 to assist in tightening security with Firewalls etc. They're also there for the ubrokers. Like any of the startup parameters, it doesn't mean you have to use them and we put defaults in place when you don't. As Rob highlighted, having distinct port ranges helps the admin, if there's a problem making connections to a specific database, you immediately know which port range to target. If you take this one step further and define distinct sets for your secondary login brokers, even better. It also makes VST reporting easier, if you're using that .. it's up to you. Another consequence, is that there's nothing stopping a client from connecting DIRECTLY to the port a (spawned) remote server is listening on. (ie not the Login broker's port, the server's port in the minport maxport range). So on a badthings happen sort of day consider the following: Typically test databases are restored with the same name as production. Production database is started with -S 3000. Test database is started with -S 3010. Both use the default -minport 3000 -maxport 5000 range. Test database has since been shut down or dbdowned. The production database now has a remote server spawned listening on port 3010. If the test database were to be started at this juncture, it would fail with: The port 3010 is already in use. (12036) But it isn't. A developer/tester doesn't notice that the test database is down, or their session crashed and typically just re-runs their connection to 'do stuff' again: CONNECT -db dbname -S 3010 They are now connected to the production database. Now if that person runs (say) a performance benchmark on a massive delete code enhancement, it would impact the production database instead of the test database which would be a really bad thing .. avoided by having distinct minport maxport ranges ;) m2c

Continue reading...
 
Status
Not open for further replies.
Back
Top