Details
-
Suggestion
-
Resolution: Tracked Elsewhere
-
None
-
None
Description
When JIRA connects to an external system to import from, if the connection fails it logs:
2007-02-16 08:22:22,572 ERROR [web.action.util.DatabaseConnectionBean] Error occurred while connecting to the database.
java.sql.SQLException: Network error IOException: Connection timed out: connect
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:372)
at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:178)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:193)
at com.atlassian.jira.web.action.util.DatabaseConnectionBean.getConnection(DatabaseConnectionBean.java:112)
at com.atlassian.jira.web.action.util.DatabaseConnectionBean.isValid(DatabaseConnectionBean.java:127)
at com.atlassian.jira.web.action.util.DatabaseConnectionBean.validateConnection(DatabaseConnectionBean.java:307)
at com.atlassian.jira.web.action.util.fogbugz.ConfigureFogBugzMapping.doStart(ConfigureFogBugzMapping.java:36)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
It would be helpful to print the connection details (JDBC URL, user address) in a debug statement just before the connect, so we've got a better chance of debugging the problem.
