[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-890?page=co...
]
Max Rydahl Andersen commented on HBX-890:
-----------------------------------------
hang where and when ?
The problem is that there is no standard/comon way of telling jdbc drivers to gracefully
timeout; so the only thing we can do is to spawn another thread that then might be
waiting/running for a long time.
To do that I need to know where and when you bumped into the issue (since we already spawn
most things asynchronous)
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