March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3860) HHH00389:Unsuccessful: drop sequence hibernate_sequence

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/AS7-3860?page=com.atlassian.jira.plugin.s... ] Burr Sutter commented on AS7-3860: ---------------------------------- H2 and we are configured for "create-drop" the last time I looked. > HHH00389:Unsuccessful: drop sequence hibernate_sequence > ------------------------------------------------------- > > Key: AS7-3860 > URL: https://issues.jboss.org/browse/AS7-3860 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Burr Sutter > Attachments: html5_deploy_server.log > > > Steps > - Using JBoss Tools nightly http://download.jboss.org/jbosstools/builds/nightly/trunk/latest/all/repo/ > - Pick HTML 5 from JBoss Central > - Add/Remove to deploy to JBoss Server > Sequence "HIBERNATE_SEQUENCE" not found; SQL statement: > drop sequence hibernate_sequence [90036-145] > Server.log section attached -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3860) HHH00389:Unsuccessful: drop sequence hibernate_sequence

by Robb Greathouse (JIRA)

[ https://issues.jboss.org/browse/AS7-3860?page=com.atlassian.jira.plugin.s... ] Robb Greathouse commented on AS7-3860: -------------------------------------- I am assuming that the underlying database is Hypersonic? If the persistence.xml or hibernate.cfg.xml file is configured for create-drop <property name="hbm2ddl.auto">create-drop</property> Then the entire database will be dropped and re-created. This will resolve the sequence problem. I understand that this is not as "clean" as just dropping a table would seem to be. However, just dropping a table is not a simple in a database as it is often portrayed. For example if the table that is dropped is a foreign key in other tables this can cause lots of problems with referential integrity all over the place. Different databases handle this in different ways. Some will block the dropping of the table and the sequence in order to prevent corruption. I don't know how Hypersonic works on this level. But from the error message I would guess that the deletion of the table is not complete. The sequence is either not being deleted or more likely is being left in an unusable state, so that a new sequence can not be created. Dropping and recreating tables is considered a bad practice during normal operations. What is the use case for doing this? Best practice would be to use a view rather than a table, if it is a temp table. If it is done during development, you probably want to do a complete database drop and recreate to avoid incomplete drops. Especially, if you are using a database that is not full enterprise as a complete clean-up may not be done. > HHH00389:Unsuccessful: drop sequence hibernate_sequence > ------------------------------------------------------- > > Key: AS7-3860 > URL: https://issues.jboss.org/browse/AS7-3860 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Burr Sutter > Attachments: html5_deploy_server.log > > > Steps > - Using JBoss Tools nightly http://download.jboss.org/jbosstools/builds/nightly/trunk/latest/all/repo/ > - Pick HTML 5 from JBoss Central > - Add/Remove to deploy to JBoss Server > Sequence "HIBERNATE_SEQUENCE" not found; SQL statement: > drop sequence hibernate_sequence [90036-145] > Server.log section attached -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4221) JCA subsystem with enabled archive validation and option 'fail-on-warn=true' produce no errors during deployment .rar archive with warnings in it.

by Vladimir Rastseluev (JIRA)

Vladimir Rastseluev created AS7-4221: ---------------------------------------- Summary: JCA subsystem with enabled archive validation and option 'fail-on-warn=true' produce no errors during deployment .rar archive with warnings in it. Key: AS7-4221 URL: https://issues.jboss.org/browse/AS7-4221 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.1.Final Reporter: Vladimir Rastseluev Assignee: Stefano Maestri Fix For: 7.1.2.Final Try to set JCA subsystem element like: <archive-validation "enabled"="true" "fail-on-warn"="true" "fail-on-error"="true" /> Then try to deploy .rar archive with ResourceAdapter implementation, which e.g. have some property of primitive type. Deployment doesn't fail. See also test case, reproducing this error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] (AS7-3860) HHH00389:Unsuccessful: drop sequence hibernate_sequence

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-3860?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-3860: ----------------------------------- Dropping a sequence object can be a critical operation. Especially if you soon recreate the same sequence object with a starting counter value of zero (since this could be used to generate unique key values for new database table rows). For this case, the error is that the hibernate_sequence doesn't exist (which is true). In this context, the error is a warning (so we can ignore it). If code changes are needed in Hibernate, a HHH jira would be needed. I'll close this jira in a few days unless there are AS7 changes needed. > HHH00389:Unsuccessful: drop sequence hibernate_sequence > ------------------------------------------------------- > > Key: AS7-3860 > URL: https://issues.jboss.org/browse/AS7-3860 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Burr Sutter > Attachments: html5_deploy_server.log > > > Steps > - Using JBoss Tools nightly http://download.jboss.org/jbosstools/builds/nightly/trunk/latest/all/repo/ > - Pick HTML 5 from JBoss Central > - Add/Remove to deploy to JBoss Server > Sequence "HIBERNATE_SEQUENCE" not found; SQL statement: > drop sequence hibernate_sequence [90036-145] > Server.log section attached -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4212) Arquillian service registered multiple time with the Environment

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-4212: ----------------------------------- Summary: Arquillian service registered multiple time with the Environment Key: AS7-4212 URL: https://issues.jboss.org/browse/AS7-4212 Project: Application Server 7 Issue Type: Bug Components: OSGi, Test Suite Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.2.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
4
0 / 0

[JBoss JIRA] (JBJCA-767) Archive validation should fail in all cases for WARN

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-767: ------------------------------------- Summary: Archive validation should fail in all cases for WARN Key: JBJCA-767 URL: https://issues.jboss.org/browse/JBJCA-767 Project: IronJacamar Issue Type: Bug Components: Deployer Affects Versions: 1.1.0.Alpha6, 1.0.9.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.10.Final, 1.1.0.Alpha7 Archive validation should fail if fail-on-warn is true for both WARNs and ERRORs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
2
0 / 0

[JBoss JIRA] (AS7-4220) CLONE - Typo in CLI for the read-resource-description for the deployment scanner subsystem

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/AS7-4220?page=com.atlassian.jira.plugin.s... ] Alexey Loubyansky moved JBPAPP-8488 to AS7-4220: ------------------------------------------------ Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-4220 (was: JBPAPP-8488) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.1.Final (was: EAP 6.0.0 ER 3_Beta1) Security: (was: JBoss Internal) Docs QE Status: (was: NEW) > CLONE - Typo in CLI for the read-resource-description for the deployment scanner subsystem > ------------------------------------------------------------------------------------------ > > Key: AS7-4220 > URL: https://issues.jboss.org/browse/AS7-4220 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.1.Final > Reporter: Dave Ryan > Assignee: Alexey Loubyansky > Priority: Minor > > Potential typo in a description for the auto-deploy-exploded attribute of the deployment scanner. Says "zipped" where it should say "exploded". I suspect the cause is just copying and pasting the auto-deploy-zipped text but missing the "exploded" change. > I've actually rewritten most of these descriptions in my documentation of the attributes for a reference topic. If you want to check those as potential updates, I can paste them in. I do imply assumed knowledge of boolean values to keep the sentences short. > For example, I rewrote the auto-deployed-exploded as: > "Allows the automatic deployment of exploded content without requiring a .dodeploy marker file. Recommended for only basic development scenarios to prevent exploded application deployment from occuring during changes by the developer or operating system." > Was: > "Controls whether zipped deployment content should be automatically deployed by the scanner without requiring the user to add a .dodeploy marker file. Setting this to 'true' is not recommended for anything but basic development scenarios, as there is no way to ensure that deployment will not occur in the middle of changes to the content." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4220) CLONE - Typo in CLI for the read-resource-description for the deployment scanner subsystem

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/AS7-4220?page=com.atlassian.jira.plugin.s... ] Alexey Loubyansky updated AS7-4220: ----------------------------------- Fix Version/s: 7.1.2.Final Component/s: Domain Management > CLONE - Typo in CLI for the read-resource-description for the deployment scanner subsystem > ------------------------------------------------------------------------------------------ > > Key: AS7-4220 > URL: https://issues.jboss.org/browse/AS7-4220 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.1.Final > Reporter: Dave Ryan > Assignee: Alexey Loubyansky > Priority: Minor > Fix For: 7.1.2.Final > > > Potential typo in a description for the auto-deploy-exploded attribute of the deployment scanner. Says "zipped" where it should say "exploded". I suspect the cause is just copying and pasting the auto-deploy-zipped text but missing the "exploded" change. > I've actually rewritten most of these descriptions in my documentation of the attributes for a reference topic. If you want to check those as potential updates, I can paste them in. I do imply assumed knowledge of boolean values to keep the sentences short. > For example, I rewrote the auto-deployed-exploded as: > "Allows the automatic deployment of exploded content without requiring a .dodeploy marker file. Recommended for only basic development scenarios to prevent exploded application deployment from occuring during changes by the developer or operating system." > Was: > "Controls whether zipped deployment content should be automatically deployed by the scanner without requiring the user to add a .dodeploy marker file. Setting this to 'true' is not recommended for anything but basic development scenarios, as there is no way to ensure that deployment will not occur in the middle of changes to the content." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3880) AS7-2824 fix removes ability to specify multiple paths in ARQ modulePath config

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-3880: ------------------------------------- Summary: AS7-2824 fix removes ability to specify multiple paths in ARQ modulePath config Key: AS7-3880 URL: https://issues.jboss.org/browse/AS7-3880 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.Final Reporter: Brian Stansberry Assignee: Thomas Diesler Fix For: 7.1.1.Final The AS7-2824 fix at https://github.com/jbossas/jboss-as/commit/cdb3b1d8f9453b1eb4ec617a83509b... adds a contract to ManagedDeployableContainer such that the ARQ config modulesPath must be a single file and must point to a directory with a sibling named "bundles". Neither seem like valid constraints for any Arquillian user who isn't interested in OSGi. See Galder's comment on AS7-2824 for how this breaks his usage. I think the issue here was identifying which of many dirs to use as jboss.modules.dir, which if not set to a valid location will result in failure to start the OSGi subsystem? Perhaps some logic to give preference to $JBOSS_HOME/modules if that is one of the items in the modulesPath list? Failing that, use the first item and document that? For the jboss.bundles.dir property, check for a sibling to jboss.modules.dir, if not found check for a sibling to any of the other items in the modulesPath list, if not found use $JBOSS_HOME/bundles? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
2
0 / 0

[JBoss JIRA] (AS7-4219) Invalid descriptor doesn't rejected - requirement of <servlet-name> uniqueness by specs.

by Pavel Janousek (JIRA)

[ https://issues.jboss.org/browse/AS7-4219?page=com.atlassian.jira.plugin.s... ] Pavel Janousek commented on AS7-4219: ------------------------------------- PR-1837 demonstrates a problem. > Invalid descriptor doesn't rejected - requirement of <servlet-name> uniqueness by specs. > ---------------------------------------------------------------------------------------- > > Key: AS7-4219 > URL: https://issues.jboss.org/browse/AS7-4219 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.1.2.Final > Reporter: Pavel Janousek > Assignee: Remy Maucherat > Priority: Blocker > > Invalid web.xml deployment descriptor like this: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" metadata-complete="false"> > <servlet> > <servlet-name>ConflictServlet</servlet-name> > <servlet-class>org.jboss.as.test.integration.web.servlet.deployment.DummyServlet</servlet-class> > </servlet> > <servlet> > <servlet-name>ConflictServlet</servlet-name> > <servlet-class>org.jboss.as.test.integration.web.servlet.deployment.DummyServlet</servlet-class> > </servlet> > </web-app> > {code} > isn't rejected during deploying a such WAR application. > Uniqueness of <servlet-name> is requirement of Servlet deployment descriptor. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2012