4:08 a.m.
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
4:15 a.m.
New subject: [Hibernate-JIRA] Commented: (HBX-890) Invalid database connection properties causes Eclipse to crash
[
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
4:19 a.m.
New subject: [Hibernate-JIRA] Commented: (HBX-890) Invalid database connection properties causes Eclipse to crash
[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-890?page=co...
]
Joseph Marques commented on HBX-890:
------------------------------------
I was opening an instance of the HQL editor, and I was prompted "would you like to
open a session factory?" - I said yes, and then Eclipse hung.......
I suppose this would have happened had I tried to create a session factory directly,
before opening an HQL editor.
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
4:28 a.m.
New subject: [Hibernate-JIRA] Commented: (HBX-890) Invalid database connection properties causes Eclipse to crash
[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-890?page=co...
]
Christian Bauer commented on HBX-890:
-------------------------------------
I've seen this come up a few times now. In a regular application, developers should
use JDBC to check the connection before building a SessionFactory. Since this is double
work, and might be required anyway for this case, we might want to introduce a
Configuration.testConnection() method.
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
4:43 a.m.
New subject: [Hibernate-JIRA] Commented: (HBX-890) Invalid database connection properties causes Eclipse to crash
[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-890?page=co...
]
Max Rydahl Andersen commented on HBX-890:
-----------------------------------------
Christian: The problem is that the some jdbc drivers actually hangs forever...can't
kill it, can't actually test it reliably...
Joseph: If you had opened the sf directly it should just run in the background.
Note, in current cvs I've forced hibernate to not contact the db when a SF is created
making this less of a problem (of course until you try and execute a query - the query
thread doing that will possibly hang)
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
4:47 a.m.
New subject: [Hibernate-JIRA] Commented: (HBX-890) Invalid database connection properties causes Eclipse to crash
[
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
4:49 a.m.
New subject: [Hibernate-JIRA] Commented: (HBX-890) Invalid database connection properties causes Eclipse to crash
[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-890?page=co...
]
Max Rydahl Andersen commented on HBX-890:
-----------------------------------------
note: a .testConnection(long timeout) is still relevant it might just need to spawn a
thread to reliably return for some driver/db combo's.
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
5:15 a.m.
New subject: [Hibernate-JIRA] Commented: (HBX-890) Invalid database connection properties causes Eclipse to crash
[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-890?page=co...
]
Max Rydahl Andersen commented on HBX-890:
-----------------------------------------
you can't forcefull kill a thread in java
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
12:26 p.m.
New subject: [Hibernate-JIRA] Commented: (HBX-890) Invalid database connection properties causes Eclipse to crash
[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-890?page=co...
]
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
12:41 a.m.
New subject: [Hibernate-JIRA] Commented: (HBX-890) Invalid database connection properties causes Eclipse to crash
[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-890?page=co...
]
Max Rydahl Andersen commented on HBX-890:
-----------------------------------------
FutureTask is jdk 1.5 (No go for now)
Thread.interrupt: requires that the driver is written to be "interruptable" and
follow http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Thread.html#interrupt() which I
hardly think many are.
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
12:41 a.m.
New subject: [Hibernate-JIRA] Commented: (HBX-890) Invalid database connection properties causes Eclipse to crash
[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-890?page=co...
]
Max Rydahl Andersen commented on HBX-890:
-----------------------------------------
feel free to supply a unittested .testConnection() method though.
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
6346
days inactive
6347
days old
hibernate-issues@lists.jboss.org
10 comments
3 participants
participants (3)
-
Christian Bauer (JIRA) -
Joseph Marques (JIRA)
-
Max Rydahl Andersen (JIRA)