[hibernate-issues] [Hibernate-JIRA] Commented: (HBX-890) Invalid database connection properties causes Eclipse to crash

[Joseph Marques (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HBX-890?page=comments#action_26205 ] 

Joseph Marques commented on HBX-890:
------------------------------------

OK, I haven't used it myself ever, but java.util.concurrent.FutureTask looks promising.  Though, the cancel method claims that it can only attempt to cancel it, and that it may fail returning false.  Perhaps this would be one of those cases.

In any event, why doesn't the interrupt method on the thread work for you?  As long as you're making the connection to the database on an interruptable channel, the blocking connection should be forced closed and return with an appropriate exception.

> 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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira