[JBoss JIRA] (JBIDE-19217) org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19217?page=com.atlassian.jira.plugi... ]
Jiri Peterka updated JBIDE-19217:
---------------------------------
Priority: Critical (was: Major)
> org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-19217
> URL: https://issues.jboss.org/browse/JBIDE-19217
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.0.Alpha1
> Environment: JBDS Version: 9.0.0.Alpha1 nightly build
> Build id: Alpha1-v20150204-0904-B2748
> Build date: 20150204-0904
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.3.0.Alpha2
>
>
> While using Hibernate console in maven project
> {code}
> org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection
> at org.hibernate.exception.internal.SQLStateConversionDelegate.convert(SQLStateConversionDelegate.java:132)
> at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator$1$1.convert(BasicConnectionCreator.java:118)
> at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator.convertSqlException(BasicConnectionCreator.java:140)
> at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionCreator.makeConnection(DriverManagerConnectionCreator.java:54)
> at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator.createConnection(BasicConnectionCreator.java:75)
> at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionProviderImpl.configure(DriverManagerConnectionProviderImpl.java:106)
> at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:89)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:206)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:178)
> at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:260)
> at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:94)
> at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:89)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:206)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:178)
> at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:80)
> at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2442)
> at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2434)
> at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSettings(ConfigurationProxy.java:125)
> at org.hibernate.console.ConsoleConfiguration$6.execute(ConsoleConfiguration.java:438)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.console.ConsoleConfiguration.getSettings(ConsoleConfiguration.java:436)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:129)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:125)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:65)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:233)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.sql.SQLException: No suitable driver found for jdbc:h2:tcp://localhost/sakila
> at java.sql.DriverManager.getConnection(DriverManager.java:689)
> at java.sql.DriverManager.getConnection(DriverManager.java:208)
> at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionCreator.makeConnection(DriverManagerConnectionCreator.java:51)
> ... 26 more
> {code}
> Pom.xml
> {code}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>org.jboss.tools.hibernate.ui.bot.test</groupId>
> <artifactId>mvn-hibernate43</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> <dependencies>
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-core</artifactId>
> <version>4.3.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-entitymanager</artifactId>
> <version>4.3.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.hibernate.javax.persistence</groupId>
> <artifactId>hibernate-jpa-2.1-api</artifactId>
> <version>1.0.0.Final</version>
> </dependency>
> <dependency>
> <groupId>com.h2database</groupId>
> <artifactId>h2</artifactId>
> <version>1.3.161</version>
> </dependency>
> </dependencies>
> </project>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19217) org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19217?page=com.atlassian.jira.plugi... ]
Jiri Peterka commented on JBIDE-19217:
--------------------------------------
Still reproducible with JBDS 9.0.0.Alpha1-B11
> org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-19217
> URL: https://issues.jboss.org/browse/JBIDE-19217
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.0.Alpha1
> Environment: JBDS Version: 9.0.0.Alpha1 nightly build
> Build id: Alpha1-v20150204-0904-B2748
> Build date: 20150204-0904
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Fix For: 4.3.0.Alpha2
>
>
> While using Hibernate console in maven project
> {code}
> org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection
> at org.hibernate.exception.internal.SQLStateConversionDelegate.convert(SQLStateConversionDelegate.java:132)
> at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator$1$1.convert(BasicConnectionCreator.java:118)
> at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator.convertSqlException(BasicConnectionCreator.java:140)
> at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionCreator.makeConnection(DriverManagerConnectionCreator.java:54)
> at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator.createConnection(BasicConnectionCreator.java:75)
> at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionProviderImpl.configure(DriverManagerConnectionProviderImpl.java:106)
> at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:89)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:206)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:178)
> at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:260)
> at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:94)
> at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:89)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:206)
> at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:178)
> at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:80)
> at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2442)
> at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2434)
> at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSettings(ConfigurationProxy.java:125)
> at org.hibernate.console.ConsoleConfiguration$6.execute(ConsoleConfiguration.java:438)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.console.ConsoleConfiguration.getSettings(ConsoleConfiguration.java:436)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:129)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:125)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:65)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:233)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.sql.SQLException: No suitable driver found for jdbc:h2:tcp://localhost/sakila
> at java.sql.DriverManager.getConnection(DriverManager.java:689)
> at java.sql.DriverManager.getConnection(DriverManager.java:208)
> at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionCreator.makeConnection(DriverManagerConnectionCreator.java:51)
> ... 26 more
> {code}
> Pom.xml
> {code}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>org.jboss.tools.hibernate.ui.bot.test</groupId>
> <artifactId>mvn-hibernate43</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> <dependencies>
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-core</artifactId>
> <version>4.3.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-entitymanager</artifactId>
> <version>4.3.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.hibernate.javax.persistence</groupId>
> <artifactId>hibernate-jpa-2.1-api</artifactId>
> <version>1.0.0.Final</version>
> </dependency>
> <dependency>
> <groupId>com.h2database</groupId>
> <artifactId>h2</artifactId>
> <version>1.3.161</version>
> </dependency>
> </dependencies>
> </project>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18742) Only rely on rsync to publish new aggregate (remove other comparators)
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18742?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18742:
----------------------------------------
This bug is for aggregate sites. We don't need any check to rsync them. That's the whole cool thing about them.
> Only rely on rsync to publish new aggregate (remove other comparators)
> ----------------------------------------------------------------------
>
> Key: JBIDE-18742
> URL: https://issues.jboss.org/browse/JBIDE-18742
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.3.0.Alpha2
>
>
> Instead of the composite-install test to decide whether we aggregate or not, it would be simpler to build aggregation in any case and then use p2diff (or other smart mechanism) to decide whether we want to publish the new composite or not.
> It's more or less just a matter of scripting
> {code:none}
> p2diff file:${WORKSPACE}/results/${JOB_NAME}/all/repo/ http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/ | grep -e ^\< -e ^\> > p2diff_snapshot
> if [[ -s p2diff_snapshot ]]; then
> ./publish.sh
> fi
> {code}
> Another benefit is that it allows us to get rid of the composite (1 less couple of files to maintain)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19288) Module is not in Started state after deploy even though it is deployed correctly.
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19288?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19288:
-------------------------------------
Good catch. This is a bit of a regression from when we separated out the module state verifier for filesystem and mangement profiles.
* f9f4055 - (mine/JBIDE-18861_maint, JBIDE-18861_maint) JBIDE-18861 - ensure module start / stop uses filesystem and marker operations rather than management when in a filesystem profile (13 days ago, Rob Stryker)
So this affects current maintenance as well as of 2 weeks ago.
> Module is not in Started state after deploy even though it is deployed correctly.
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-19288
> URL: https://issues.jboss.org/browse/JBIDE-19288
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Reporter: Radim Hopp
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
>
>
> When deploying project to running server (I've tried it with Wildfly 8 and EAP 6.3), the project remains in state [Synchronized] instead of [Started, Synchronized] even though the project is correctly deployed and running.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19043) Error publishing jar inside utility project inside ear project
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19043?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19043:
-------------------------------------
> add embedded to utility deployment assembly (change to deploy-path="/jars/" in org.eclipse.wst.common.component, UI doesn't allow it)
The UI does allow it. You double-click on the deploy-path column and write jars/embedded.jar.
The resulting published archive looks as follows
{code}
[rob@localhost 1]$ du -a
4 ./WebApp1.war/WEB-INF/lib/Utility.jar
8 ./WebApp1.war/WEB-INF/lib
4 ./WebApp1.war/WEB-INF/classes/pak/TigerSarvlet.class
8 ./WebApp1.war/WEB-INF/classes/pak
12 ./WebApp1.war/WEB-INF/classes
24 ./WebApp1.war/WEB-INF
4 ./WebApp1.war/META-INF/MANIFEST.MF
8 ./WebApp1.war/META-INF
36 ./WebApp1.war
{code}
Exploding Utility jar, we see the following:
{code}
[rob@localhost 1]$ unzip -l ./WebApp1.war/WEB-INF/lib/Utility.jar
Archive: ./WebApp1.war/WEB-INF/lib/Utility.jar
Length Date Time Name
--------- ---------- ----- ----
612 02-19-2015 02:08 jars/Embedded.jar
39 02-19-2015 02:05 META-INF/MANIFEST.MF
261 02-19-2015 02:06 UtilityModel.class
0 02-19-2015 02:08 META-INF/
0 02-19-2015 02:08 jars/
--------- -------
912 5 files
{code}
Inside the embedded jar, we see:
{code}
[rob@localhost 1]$ unzip -l jars/Embedded.jar
Archive: jars/Embedded.jar
Length Date Time Name
--------- ---------- ----- ----
39 02-19-2015 02:05 META-INF/MANIFEST.MF
264 02-19-2015 02:06 EmbeddedModel.class
0 02-19-2015 02:08 META-INF/
--------- -------
303 3 files
{code}
So as far as I can tell, everything works as expected. I believe this use case has been supported for about a year, though I do recall it being a bug in the past.
> Error publishing jar inside utility project inside ear project
> --------------------------------------------------------------
>
> Key: JBIDE-19043
> URL: https://issues.jboss.org/browse/JBIDE-19043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.2.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.3.Beta1, 4.3.0.Beta1
>
>
> While verifying JBIDE-18862 I wanted to have some really big file to deploy so that I could see is an existing *.dodeploy marker is removed before the copying begins.
> So I created an ear project with a nested dynamic web project and utility project. Inside this utility project's src dir I copied JBDS installer jar. Then I tried to deploy the ear to a WildFly 8.2 server (both stopped and running).
> It seemed to work, the utility jar had 574 MB. But the tooling showed me this error:
> Publishing to wildfly has encountered a problem:
> {code}
> Error renaming /Volumes/Data/jbossqa/wildfly-8.2.0.Final/standalone/tmp/tmp582268190747176162.jar to /Volumes/Data/jbossqa/wildfly-8.2.0.Final/standalone/deployments/earproj.ear/lib/utilproj.jar/jboss-devstudio-8.0.2.GA-v20150114-2029-B382-installer-standalone.jar.
> This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
> You may adjust these settings in the server editor.
> {code}
> It's true that this was on a different FS, but both the tmp and deploy dirs were one FS, so that should be fine.
> And just to be sure, I tried the same on the same FS and the error was the same:
> {code}
> Error renaming /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/tmp/tmp7876542570838575938.jar to /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/deployments/earproj.ear/lib/utilproj.jar/jboss-devstudio-8.0.2.GA-v20150114-2029-B382-installer-standalone.jar.
> This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
> You may adjust these settings in the server editor.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months