[jbosstools-issues] [JBoss JIRA] (JBIDE-11107) ZipFileClosed exception while connecting multiple datbases via Hibernate configuration view

[Dmitry Geraskov (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitry Geraskov updated JBIDE-11107:
------------------------------------

    Fix Version/s: 4.0.x
                       (was: 4.0.0.Alpha1)

    
> ZipFileClosed exception while connecting multiple datbases via Hibernate configuration view
> -------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-11107
>                 URL: https://issues.jboss.org/browse/JBIDE-11107
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: hibernate
>    Affects Versions: 3.3.0.Beta1
>         Environment: JBT 3.3.0.Beta1 #93, L64
>            Reporter: Jiri Peterka
>            Assignee: Dmitry Geraskov
>             Fix For: 4.0.x
>
>         Attachments: hb-console.png
>
>
> Might be reproducible after several tries
> java.lang.IllegalStateException: zip file closed
> 	at java.util.zip.ZipFile.ensureOpen(ZipFile.java:415)
> 	at java.util.zip.ZipFile.getEntry(ZipFile.java:160)
> 	at java.util.jar.JarFile.getEntry(JarFile.java:208)
> 	at java.util.jar.JarFile.getJarEntry(JarFile.java:191)
> 	at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:757)
> 	at sun.misc.URLClassPath.getResource(URLClassPath.java:169)
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> 	at org.hibernate.console.ConsoleConfiguration$2$1.findClass(ConsoleConfiguration.java:199)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> 	at org.hibernate.console.ConsoleConfiguration$2$1.loadClass(ConsoleConfiguration.java:207)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> 	at org.hibernate.console.ConsoleConfiguration$2$1.loadClass(ConsoleConfiguration.java:215)
> 	at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
> 	at org.hsqldb.jdbcDriver.connect(Unknown Source)
> 	at org.hibernate.eclipse.libs.FakeDelegatingDriver.connect(FakeDelegatingDriver.java:40)
> 	at java.sql.DriverManager.getConnection(DriverManager.java:582)
> 	at java.sql.DriverManager.getConnection(DriverManager.java:154)
> 	at org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:133)
> 	at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.getConnection(AbstractMetaDataDialect.java:121)
> 	at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.getMetaData(AbstractMetaDataDialect.java:60)
> 	at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.caseForSearch(AbstractMetaDataDialect.java:163)
> 	at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:22)
> 	at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476)
> 	at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74)
> 	at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:126)
> 	at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> 	at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:107)
> 	at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:115)
> 	at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:65)
> 	at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
> 	at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira