[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-890?page=co...
]
Joseph Marques commented on HBX-890:
------------------------------------
Is it possible just to fork some kind of worker thread that has timeouts, have the
connection attempt performed there instead, and forcefully kill the work upon timeout
assuming the worst case of the driver causing it to hang forever?
Invalid database connection properties causes Eclipse to crash
--------------------------------------------------------------
Key: HBX-890
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HBX-890
Project: Hibernate Tools
Type: Bug
Versions: 3.2beta8
Reporter: Joseph Marques
In this case the hibernate.connection.url was the issue. I had been using
"jdbc:postgresql://localhost:<port>/<db>", but that caused Eclipse
to crash because that just hangs.
The proper syntax, for the way I've exposed my postgres installation, is one of the
following:
1) jdbc:postgresql://<hostname>:<port>/<db>
2) jdbc:postgresql://<ip_address>:<port>/<db>
If there was an explicit timeout for the connection attempt, and then a graceful handling
of that timeout, Eclipse wouldn't have to die.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira