[JBoss JIRA] (WFLY-9739) JPA / Hibernate: There is already an object named 'x' in the database
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-9739?page=com.atlassian.jira.plugin.... ]
Scott Marlow commented on WFLY-9739:
------------------------------------
Hi, does the database contain a table called "ANIMAL"? Or perhaps "animal"? I'm not sure if there is a bug or not in Hibernate but it sounds like Hibernate may be getting a list of tables from JDBC DatabaseMetaData that contains "Animal" with a different case than expected.
We will soon reject this issue, since there is no bug to fix in the WildFly project (as far as I can tell). If there is a Hibernate bug, that can be reported via [https://hibernate.atlassian.net/browse/HHH].
If you want to let us know the exact case of the ANIMAL table name, that could be helpful.
> JPA / Hibernate: There is already an object named 'x' in the database
> ---------------------------------------------------------------------
>
> Key: WFLY-9739
> URL: https://issues.jboss.org/browse/WFLY-9739
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 11.0.0.Final
> Environment: Windows 10 64 bits / Windows Server 2012 R2 64 bits
> Java version: 1.8.0_151
> SQL Server 2014
> Reporter: Eric SantAnna
> Assignee: Scott Marlow
> Attachments: sqljdbc4.jar, wildfly11-migration.zip
>
>
> I'm getting an Exception as a warning in the server.log when a database object already exists an my persistence.xml has the property "hibernate.hbm2ddl.auto" set to "update".
> This doesn't happen in my tests with 10.1.0.Final.
> Appearently, despite these Exceptions, all my applications are running ok.
> I saw this behaviour while I was migrating my application from JBoss 7.1.1.Final to Wildfly. I'm deciding between Wildfly 10.1 and 11.
> This behaviour isn't good cause, I'm flooding the logs and it doesn't seem reliable for my manager.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9739) JPA / Hibernate: There is already an object named 'x' in the database
by Eric SantAnna (JIRA)
Eric SantAnna created WFLY-9739:
-----------------------------------
Summary: JPA / Hibernate: There is already an object named 'x' in the database
Key: WFLY-9739
URL: https://issues.jboss.org/browse/WFLY-9739
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 11.0.0.Final
Environment: Windows 10 64 bits / Windows Server 2012 R2 64 bits
Java version: 1.8.0_151
SQL Server 2014
Reporter: Eric SantAnna
Assignee: Scott Marlow
Attachments: sqljdbc4.jar, wildfly11-migration.zip
I'm getting an Exception as a warning in the server.log when a database object already exists an my persistence.xml has the property "hibernate.hbm2ddl.auto" set to "update".
This doesn't happen in my tests with 10.1.0.Final.
Appearently, despite these Exceptions, all my applications are running ok.
I saw this behaviour while I was migrating my application from JBoss 7.1.1.Final to Wildfly. I'm deciding between Wildfly 10.1 and 11.
This behaviour isn't good cause, I'm flooding the logs and it doesn't seem reliable for my manager.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-783) Error migrating repository from 5.x to 6.2
by Jan Schatteman (JIRA)
[ https://issues.jboss.org/browse/DROOLS-783?page=com.atlassian.jira.plugin... ]
Jan Schatteman reassigned DROOLS-783:
-------------------------------------
Assignee: Edson Tirelli (was: Jan Schatteman)
> Error migrating repository from 5.x to 6.2
> ------------------------------------------
>
> Key: DROOLS-783
> URL: https://issues.jboss.org/browse/DROOLS-783
> Project: Drools
> Issue Type: Bug
> Components: tools
> Affects Versions: 6.2.0.Final
> Environment: Linux 3.8.13-55.1.5.el6uek.x86_64 #2 SMP Wed Jan 28 17:03:28 PST 2015 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Pierangelo Repetti
> Assignee: Edson Tirelli
> Attachments: guvnor-jcr2vfs-migration.git.zip, repository_export.zip, rules.zip, runMigration.log, stderr.out
>
>
> The migration of a rules repository from Guvnor 5.x to KIE WB shows the following error
> java.io.FileNotFoundException: File modules.xml not found
> during the JCR import phase.
> Detail:
> Jcr import started. Reading from import directory ({/home/ecs/brain/migration/drools-wb-jcr2vfs-distribution-6.2.0.Final/bin/tmp-jcr2vfs}).
> Category import started
> Category import ended
> Module import started
> java.io.FileNotFoundException: File modules.xml not found
> at org.drools.workbench.jcr2vfsmigration.common.FileManager.getFile(FileManager.java:163)
> at org.drools.workbench.jcr2vfsmigration.common.FileManager.getModulesExportFile(FileManager.java:54)
> at org.drools.workbench.jcr2vfsmigration.common.FileManager$Proxy$_$$_WeldClientProxy.getModulesExportFile(FileManager$Proxy$_$$_WeldClientProxy.java)
> at org.drools.workbench.jcr2vfsmigration.vfsImport.ModuleAssetImporter.importAll(ModuleAssetImporter.java:114)
> at org.drools.workbench.jcr2vfsmigration.vfsImport.ModuleAssetImporter$Proxy$_$$_WeldClientProxy.importAll(ModuleAssetImporter$Proxy$_$$_WeldClientProxy.java)
> at org.drools.workbench.jcr2vfsmigration.VfsImporter.importAll(VfsImporter.java:80)
> at org.drools.workbench.jcr2vfsmigration.VfsImporter$Proxy$_$$_WeldClientProxy.importAll(VfsImporter$Proxy$_$$_WeldClientProxy.java)
> at org.drools.workbench.jcr2vfsmigration.VfsImporterLauncher.launchImport(VfsImporterLauncher.java:57)
> at org.drools.workbench.jcr2vfsmigration.VfsImporterLauncher.run(VfsImporterLauncher.java:49)
> at org.drools.workbench.jcr2vfsmigration.VfsImporterLauncher.main(VfsImporterLauncher.java:34)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-783) Error migrating repository from 5.x to 6.2
by Sayed Abdul (JIRA)
[ https://issues.jboss.org/browse/DROOLS-783?page=com.atlassian.jira.plugin... ]
Sayed Abdul edited comment on DROOLS-783 at 1/26/18 3:38 PM:
-------------------------------------------------------------
Hi Team,
Please help to migrate drools 5.0.0 to any latest Guvnor compatible with jboss eap 6.4.
1.I am considering 6.5.0 as the drools version.please suggest if it's fine.
2.Also let me please know if the migration tool supports this migration.
- ----------------------------
i am getting below error with the sample repo attached in this ticket.
repository.xml doeesn't exist, so i renamed the file and getting below errors:
1)01:52:06.624 [main] WARN o.a.j.c.c.ConfigurationErrorHandler - Warning parsing the configuration at line 1 using system id file:/C:/../drools-wb-jcr2vfs-distribution-6.5.0.Final/drools-wb-jcr2vfs-distribution-6.5.0.Final/migration/repository_export/repository.xml: org.xml.sax.SAXParseException; systemId: file:/C:/../..../drools-wb-jcr2vfs-distribution-6.5.0.Final/drools-wb-jcr2vfs-distribution-6.5.0.Final/migration/repository_export/repository.xml; lineNumber: 1; columnNumber: 470; Document root element "sv:node", must match DOCTYPE root "null".
01:52:06.624 [main] WARN o.a.j.c.c.ConfigurationErrorHandler - Warning parsing the configuration at line 1 using system id file:/C:/Users/../drools-wb-jcr2vfs-distribution-6.5.0.Final/drools-wb-jcr2vfs-distribution-6.5.0.Final/migration/repository_export/repository.xml: org.xml.sax.SAXParseException; systemId: file:/C:/../../drools-wb-jcr2vfs-distribution-6.5.0.Final/drools-wb-jcr2vfs-distribution-6.5.0.Final/migration/repository_export/repository.xml; lineNumber: 1; columnNumber: 470; Document is invalid: no grammar found.
.
org.jboss.weld.exceptions.WeldException: WELD-000049 Unable to invoke [method] @PostConstruct public org.drools.guvnor.server.repository.RepositoryStartupService.create() on org.drools.guvnor.server.repository.ProductionRepositoryStartupService@13c3543
at org.jboss.weld.bean.AbstractClassBean.defaultPostConstruct(AbstractClassBean.java:400)
at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget.postConstruct(ManagedBean.java:174)
at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:294)
at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:107)
at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:90)
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
at org.drools.guvnor.server.repository.ProductionRepositoryStartupService$Proxy$_$$_WeldClientProxy.newSession(ProductionRepositoryStartupService$Proxy$_$$_WeldClientProxy.java)
2)Caused by: org.drools.repository.RulesRepositoryException: javax.jcr.RepositoryException: Invalid repository configuration file:
3)INFO VFS import started. Reading from import directory C:\..\.\drools-wb-jcr2vfs-distribution-6.5.0.Final\drools-wb-jcr2vfs-distribution-6.5.0.Final\bin\tmp-jcr2vfs.
INFO Module import started
java.io.FileNotFoundException: File modules.xml not found
at org.drools.workbench.jcr2vfsmigration.common.FileManager.getFile(FileManager.java:167)
at org.drools.workbench.jcr2vfsmigration.common.FileManager.getModulesExportFile(FileManager.java:58)
at org.drools.workbench.jcr2vfsmigration.common.FileManager$Proxy$_$$_WeldClientProxy.getModulesExportFile(FileManager$Proxy$_$$_WeldClientProxy.java)
at org.drools.workbench.jcr2vfsmigration.vfsImport.ModuleAssetImporter.importAll(ModuleAssetImporter.java:123)
at org.drools.workbench.jcr2vfsmigration.vfsImport.ModuleAssetImporter$Proxy$_$$_WeldClientProxy.importAll(ModuleAssetImporter$Proxy$_$$_WeldClientProxy.java)
at org.drools.workbench.jcr2vfsmigration.VfsImporter.importAll(VfsImporter.java:65)
at org.drools.workbench.jcr2vfsmigration.VfsImporter$Proxy$_$$_WeldClientProxy.importAll(VfsImporter$Proxy$_$$_WeldClientProxy.java)
at org.drools.workbench.jcr2vfsmigration.VfsImporterLauncher.launchImport(VfsImporterLauncher.java:56)
at org.drools.workbench.jcr2vfsmigration.VfsImporterLauncher.run(VfsImporterLauncher.java:48)
at org.drools.workbench.jcr2vfsmigration.VfsImporterLauncher.main(VfsImporterLauncher.java:33)
INFO Module import ended
Thanks
was (Author: sayed):
Hi Team,
I have a similar assignment to migrate drools 5.0.0 to any latest Guvnor compatible with jboss eap 6.4.
1.I am considering 6.5.0 as the drools version.please suggest if it's fine.
2.Also let me please know if the migration tool supports this migration.
Best regards
> Error migrating repository from 5.x to 6.2
> ------------------------------------------
>
> Key: DROOLS-783
> URL: https://issues.jboss.org/browse/DROOLS-783
> Project: Drools
> Issue Type: Bug
> Components: tools
> Affects Versions: 6.2.0.Final
> Environment: Linux 3.8.13-55.1.5.el6uek.x86_64 #2 SMP Wed Jan 28 17:03:28 PST 2015 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Pierangelo Repetti
> Assignee: Jan Schatteman
> Attachments: guvnor-jcr2vfs-migration.git.zip, repository_export.zip, rules.zip, runMigration.log, stderr.out
>
>
> The migration of a rules repository from Guvnor 5.x to KIE WB shows the following error
> java.io.FileNotFoundException: File modules.xml not found
> during the JCR import phase.
> Detail:
> Jcr import started. Reading from import directory ({/home/ecs/brain/migration/drools-wb-jcr2vfs-distribution-6.2.0.Final/bin/tmp-jcr2vfs}).
> Category import started
> Category import ended
> Module import started
> java.io.FileNotFoundException: File modules.xml not found
> at org.drools.workbench.jcr2vfsmigration.common.FileManager.getFile(FileManager.java:163)
> at org.drools.workbench.jcr2vfsmigration.common.FileManager.getModulesExportFile(FileManager.java:54)
> at org.drools.workbench.jcr2vfsmigration.common.FileManager$Proxy$_$$_WeldClientProxy.getModulesExportFile(FileManager$Proxy$_$$_WeldClientProxy.java)
> at org.drools.workbench.jcr2vfsmigration.vfsImport.ModuleAssetImporter.importAll(ModuleAssetImporter.java:114)
> at org.drools.workbench.jcr2vfsmigration.vfsImport.ModuleAssetImporter$Proxy$_$$_WeldClientProxy.importAll(ModuleAssetImporter$Proxy$_$$_WeldClientProxy.java)
> at org.drools.workbench.jcr2vfsmigration.VfsImporter.importAll(VfsImporter.java:80)
> at org.drools.workbench.jcr2vfsmigration.VfsImporter$Proxy$_$$_WeldClientProxy.importAll(VfsImporter$Proxy$_$$_WeldClientProxy.java)
> at org.drools.workbench.jcr2vfsmigration.VfsImporterLauncher.launchImport(VfsImporterLauncher.java:57)
> at org.drools.workbench.jcr2vfsmigration.VfsImporterLauncher.run(VfsImporterLauncher.java:49)
> at org.drools.workbench.jcr2vfsmigration.VfsImporterLauncher.main(VfsImporterLauncher.java:34)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFCORE-3549) Drop back to a final version of jboss-logmanager 2.0.9.Final
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3549?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-3549:
----------------------------------
Summary: Drop back to a final version of jboss-logmanager 2.0.9.Final (was: Drop back to a final version of jboss-logmanager)
> Drop back to a final version of jboss-logmanager 2.0.9.Final
> ------------------------------------------------------------
>
> Key: WFCORE-3549
> URL: https://issues.jboss.org/browse/WFCORE-3549
> Project: WildFly Core
> Issue Type: Component Upgrade
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Blocker
>
> Components in WildFly should generally always be final. There was an upgrade to {{org.jboss.logmanager:jboss-logmanager}} to allow for a {{json-formatter}} PR to be done. This should be done in a topic branch and the log manager upgrade should not be merged in until the log manager itself is final.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-783) Error migrating repository from 5.x to 6.2
by Sayed Abdul (JIRA)
[ https://issues.jboss.org/browse/DROOLS-783?page=com.atlassian.jira.plugin... ]
Sayed Abdul commented on DROOLS-783:
------------------------------------
Hi Team,
I have a similar assignment to migrate drools 5.0.0 to any latest Guvnor compatible with jboss eap 6.4.
1.I am considering 6.5.0 as the drools version.please suggest if it's fine.
2.Also let me please know if the migration tool supports this migration.
Best regards
> Error migrating repository from 5.x to 6.2
> ------------------------------------------
>
> Key: DROOLS-783
> URL: https://issues.jboss.org/browse/DROOLS-783
> Project: Drools
> Issue Type: Bug
> Components: tools
> Affects Versions: 6.2.0.Final
> Environment: Linux 3.8.13-55.1.5.el6uek.x86_64 #2 SMP Wed Jan 28 17:03:28 PST 2015 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Pierangelo Repetti
> Assignee: Jan Schatteman
> Attachments: guvnor-jcr2vfs-migration.git.zip, repository_export.zip, rules.zip, runMigration.log, stderr.out
>
>
> The migration of a rules repository from Guvnor 5.x to KIE WB shows the following error
> java.io.FileNotFoundException: File modules.xml not found
> during the JCR import phase.
> Detail:
> Jcr import started. Reading from import directory ({/home/ecs/brain/migration/drools-wb-jcr2vfs-distribution-6.2.0.Final/bin/tmp-jcr2vfs}).
> Category import started
> Category import ended
> Module import started
> java.io.FileNotFoundException: File modules.xml not found
> at org.drools.workbench.jcr2vfsmigration.common.FileManager.getFile(FileManager.java:163)
> at org.drools.workbench.jcr2vfsmigration.common.FileManager.getModulesExportFile(FileManager.java:54)
> at org.drools.workbench.jcr2vfsmigration.common.FileManager$Proxy$_$$_WeldClientProxy.getModulesExportFile(FileManager$Proxy$_$$_WeldClientProxy.java)
> at org.drools.workbench.jcr2vfsmigration.vfsImport.ModuleAssetImporter.importAll(ModuleAssetImporter.java:114)
> at org.drools.workbench.jcr2vfsmigration.vfsImport.ModuleAssetImporter$Proxy$_$$_WeldClientProxy.importAll(ModuleAssetImporter$Proxy$_$$_WeldClientProxy.java)
> at org.drools.workbench.jcr2vfsmigration.VfsImporter.importAll(VfsImporter.java:80)
> at org.drools.workbench.jcr2vfsmigration.VfsImporter$Proxy$_$$_WeldClientProxy.importAll(VfsImporter$Proxy$_$$_WeldClientProxy.java)
> at org.drools.workbench.jcr2vfsmigration.VfsImporterLauncher.launchImport(VfsImporterLauncher.java:57)
> at org.drools.workbench.jcr2vfsmigration.VfsImporterLauncher.run(VfsImporterLauncher.java:49)
> at org.drools.workbench.jcr2vfsmigration.VfsImporterLauncher.main(VfsImporterLauncher.java:34)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFCORE-3554) Append the content to the file with name tmp|file results to 'tmp\|file' being created
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3554?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-3554:
-------------------------------------
Description:
*Description of problem:*
Append the content to the file with name tmp|file results to 'tmp\|file' being created.
*Actual results:*
{code}
[standalone@embedded /] version >> tmp\|file
The file created is named 'tmp\|file'
{code}
*Expected results:*
{code}
The file created is named 'tmp|file'
{code}
was:
*Description of problem:*
Append the content to the file with name tmp|file results to 'tmp\|file' being created.
*Actual results:*
[standalone@embedded /] version >> tmp\|file
The file created is named 'tmp\|file'
*Expected results:*
The file created is named 'tmp|file'
> Append the content to the file with name tmp|file results to 'tmp\|file' being created
> --------------------------------------------------------------------------------------
>
> Key: WFCORE-3554
> URL: https://issues.jboss.org/browse/WFCORE-3554
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Katerina Novotna
> Assignee: Jean-Francois Denise
>
> *Description of problem:*
> Append the content to the file with name tmp|file results to 'tmp\|file' being created.
> *Actual results:*
> {code}
> [standalone@embedded /] version >> tmp\|file
> The file created is named 'tmp\|file'
> {code}
> *Expected results:*
> {code}
> The file created is named 'tmp|file'
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFCORE-3559) FilePermissionTestCase permission checking issue
by Jean-Francois Denise (JIRA)
Jean-Francois Denise created WFCORE-3559:
--------------------------------------------
Summary: FilePermissionTestCase permission checking issue
Key: WFCORE-3559
URL: https://issues.jboss.org/browse/WFCORE-3559
Project: WildFly Core
Issue Type: Bug
Components: CLI, Test Suite
Reporter: Jean-Francois Denise
Assignee: Katerina Novotna
On my mac laptop the test is failing with:
testFileDefaultPermissions(org.jboss.as.test.integration.management.cli.FilePermissionTestCase) Time elapsed: 1.273 sec <<< FAILURE!
java.lang.AssertionError: The test file has unexpected permissions: rw-r--r--
Expected: is "rw-rw-r--"
but: was "rw-r--r--"
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.jboss.as.test.integration.management.cli.FilePermissionTestCase.testFileDefaultPermissions(FilePermissionTestCase.java:102)
My mask could make the files to be created with these permissions, do we really want to check that?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months