SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-15-2008, 11:57 PM
| ||||
| ||||
 Postgres JDBC Connections claim port 1099 We are having an issue where we have one Java VM that starts up and creates say 10 JDBC connections to a local PostgreSQL instance, version 8.0. As these connections are created, they are made to the default PostgreSQL port 5432. On XP based machines this winds up spawning several instances of Postgres.exe and each one of these instances takes up a port that seem to start in the range of 1048 or so. We are finding that if we then start another Java VM that is running JBoss it will attempt to claim port 1099 for its default naming services but one of the Postgres.exe instances has already claimed it which then stops JBoss from loading. Does anyone know if there is a way to control the port range that each Postgres.exe will use so that we can ensure that these connections do not wind up taking a port that another application will use? Without that option, it seems that you would be forced to start services in a very specific order to avoid the contention. Thanks, Jack      |
Linear Mode
