Your browser was unable to load all of the resources. They may have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.

QB Upgrade 6->7 : jdbc SQL Server connection problem using official ms driver #8

PtvTEp ·

Hi, can anyone help me:
during QB upgrade from 6.0.27 to 7.0.31 there occurs a "connection refused" exception while
QuickBuild connects to SQL Server using the MS official
JDBC driver instead of jTDS for compatiblity reason.
Orignially we have
_hibernate.dialect=org.hibernate.dialect.SQLServerDialect
hibernate.connection.driver_class=net.sourceforge.jtds.jdbc.Driver
hibernate.connection.url=jdbc:jtds:sqlserver://ska-wn-tvsi:1433/quickbuild_TestEnv;instance=PTV_VISION
hibernate.connection.username=blah
hibernate.connection.password=blah
_
QB Upgrade says it uses
hibernate.connection.url=jdbc:sqlserver://ska-wn-tvsi:1433;databaseName=quickbuild_TestEnv;instance=PTV_VISION
and throws an exception during "INFO com.pmease.quickbuild.bootstrap.Upgrade - Migrating exported data..."

2018-02-16 12:16:32,928 [pool-1-thread-1] INFO com.pmease.quickbuild.bootstrap.Upgrade - >>> 2018-02-16 12:16:32,928 INFO - QuickBuild server stopped.
2018-02-16 12:16:32,928 [pool-1-thread-2] ERROR com.pmease.quickbuild.bootstrap.Upgrade - >>> Exception in thread "main" java.lang.ExceptionInInitializerError
2018-02-16 12:16:32,928 [pool-1-thread-2] ERROR com.pmease.quickbuild.bootstrap.Upgrade - >>> at com.pmease.quickbuild.Quickbuild.importData(Quickbuild.java:938)
2018-02-16 12:16:32,928 [pool-1-thread-2] ERROR com.pmease.quickbuild.bootstrap.Upgrade - >>> at com.pmease.quickbuild.bootstrap.Bootstrap$6.execute(Bootstrap.java:203)
2018-02-16 12:16:32,928 [pool-1-thread-2] ERROR com.pmease.quickbuild.bootstrap.Upgrade - >>> at com.pmease.quickbuild.Quickbuild$3.run(Quickbuild.java:656)
2018-02-16 12:16:32,928 [pool-1-thread-2] ERROR com.pmease.quickbuild.bootstrap.Upgrade - >>> at java.lang.Thread.run(Unknown Source)
2018-02-16 12:16:32,928 [pool-1-thread-2] ERROR com.pmease.quickbuild.bootstrap.Upgrade - >>> Caused by: com.google.inject.ProvisionException: Guice provision errors:
2018-02-16 12:16:32,928 [pool-1-thread-2] ERROR com.pmease.quickbuild.bootstrap.Upgrade - >>>
2018-02-16 12:16:32,928 [pool-1-thread-2] ERROR com.pmease.quickbuild.bootstrap.Upgrade - >>> 1) Error in custom provider, java.lang.RuntimeException: com.microsoft.sqlserver.jdbc.SQLServerException:
Fehler beim Herstellen der TCP/IP-Verbindung mit dem Host 'ska-wn-tvsi', Port 1433. Fehler: 'Connection refused: connect...
2018-02-16 12:16:32,928 [pool-1-thread-2] ERROR com.pmease.quickbuild.bootstrap.Upgrade - >>> while locating com.pmease.quickbuild.persistence.SessionFactoryProvider
2018-02-16 12:16:32,928 [pool-1-thread-2] ERROR com.pmease.quickbuild.bootstrap.Upgrade - >>> at com.pmease.quickbuild.QuickbuildModule.configure(QuickbuildModule.java:36)
2018-02-16 12:16:32,928 [pool-1-thread-2] ERROR com.pmease.quickbuild.bootstrap.Upgrade - >>> while locating org.hibernate.SessionFactory
2018-02-16 12:16:32,928 [pool-1-thread-2] ERROR com.pmease.quickbuild.bootstrap.Upgrade - >>> for field at com.pmease.quickbuild.entitymanager.impl.DefaultDataManager.sessionFactory(DefaultDataManager.java:115)
2018-02-16 12:16:32,928 [pool-1-thread-2] ERROR com.pmease.quickbuild.bootstrap.Upgrade - >>> at com.pmease.quickbuild.entitymanager.impl.DefaultDataManager.class(DefaultDataManager.java:115)
2018-02-16 12:16:32,928 [pool-1-thread-2] ERROR com.pmease.quickbuild.bootstrap.Upgrade - >>> while locating com.pmease.quickbuild.entitymanager.impl.DefaultDataManager
2018-02-16 12:16:32,928 [pool-1-thread-2] ERROR com.pmease.quickbuild.bootstrap.Upgrade - >>> while locating com.pmease.quickbuild.entitymanager.DataManager
2018-02-16 12:16:32,944 [pool-1-thread-2] ERROR com.pmease.quickbuild.bootstrap.Upgrade - >>>
2018-02-16 12:16:32,944 [pool-1-thread-2] ERROR com.pmease.quickbuild.bootstrap.Upgrade - >>> 1 error

  • replies 1
  • views 471
  • stars 0
PtvTEp ·

I have found a solution to this simple connection problem:
i use a Port in the jdbc connection now, for which the sql server instance is configured.
(see "SQL Server Configuration Manager" Network Configuration... TCP/IP port number for SQL Server 2012 instance is the value of the TCP Dynamic Ports item under IPAll.).
I still do not know, why the jTDS driver with port 1433 in its connection string was able to connect and the MS official was not...