February 2012 - jboss-jira - Jboss List Archives

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

by Jay Balunas (JIRA)

[ https://issues.jboss.org/browse/AS7-3860?page=com.atlassian.jira.plugin.s... ] Jay Balunas reassigned AS7-3860: -------------------------------- Assignee: (was: Jay Balunas) > 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, 4 months

1
0
0 / 0

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

by Jay Balunas (JIRA)

[ https://issues.jboss.org/browse/AS7-3860?page=com.atlassian.jira.plugin.s... ] Jay Balunas moved AEROGEAR-35 to AS7-3860: ------------------------------------------ Project: Application Server 7 (was: AeroGear) Key: AS7-3860 (was: AEROGEAR-35) Component/s: JPA / Hibernate (was: examples) (was: as-*) Security: (was: Public) Fix Version/s: (was: 1.0.0.M2) > 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 > Assignee: Jay Balunas > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-3847) Non-standard format of IPv6 address(-es) in LOG files

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-3847?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-3847: ---------------------------------- Priority: Major (was: Critical) The issue here is java.net.Inet6Address.getHostAddress() does not follow the RFC 5952 standard; specifically http://tools.ietf.org/html/rfc5952#section-4.2. A separate JBWEB JIRA needs to be filed for org.apache.coyote.http11.Http11Protocol as that code is not part of the AS7 code base. > Non-standard format of IPv6 address(-es) in LOG files > ----------------------------------------------------- > > Key: AS7-3847 > URL: https://issues.jboss.org/browse/AS7-3847 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.0.Final > Reporter: Pavel Janousek > > There are several places where some IPv6 address related info is logged. The format of a such info is formally correct, but used format is against [RFC-5952|http://tools.ietf.org/html/rfc5952] - this RFC has status of +Proposed standard+ and I don't know any software product which doesn't follow it (at least by-default). > I think in enterprise product we should not violate this RFC. > I'm mentioning about LOG messages like: > {code} > 15:14:15,985 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /0:0:0:0:0:0:0:1%1:9999 > > 15:14:15,990 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on localhost6.localdomain6/0:0:0:0:0:0:0:1%1:4447 > {code} > In both lines IPv6 address should be stretched to "::1" string. > More "funny" and obfuscated version of the same LOG content is LOG line like this: > {code} > 15:14:14,363 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A1%251-8080 > {code} > But both version of the issue is almost unreadable by human. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-3845) generateStandaloneJdrReport test case fails on Windows

by Shelly McGowan (JIRA)

Shelly McGowan created AS7-3845: ----------------------------------- Summary: generateStandaloneJdrReport test case fails on Windows Key: AS7-3845 URL: https://issues.jboss.org/browse/AS7-3845 Project: Application Server 7 Issue Type: Bug Components: Test Suite Reporter: Shelly McGowan Assignee: Mike Clark Fix For: 7.1.1.Final org.jboss.as.test.integration.jdr.mgmt.JdrReportManagmentTestCase.generateStandaloneJdrReport java.lang.AssertionError: JDR report missing, not located at {code} 07:26:52,175 INFO [org.jboss.as.jdr] (management-handler-threads - 15) JBAS013300: Starting creation of a JBoss Diagnostic Report (JDR). 07:27:00,718 WARN [org.jboss.as.jdr] (MainThread) JBAS013303: JDR python interpreter encountered an exception.: Traceback (most recent call last): File "<string>", line 1, in <module> File "W:\workspace\JBoss-AS-7.1.x-testSuite-windows\testsuite\integration\basic\..\..\..\build\target\jboss-as-7.1.1.Final-SNAPSHOT\modules\org\jboss\as\jdr\main\jboss-as-sos-7.1.1.Final-SNAPSHOT.jar\sos\sosreport.py", line 220, in __init__ File "W:\workspace\JBoss-AS-7.1.x-testSuite-windows\testsuite\integration\basic\..\..\..\build\target\jboss-as-7.1.1.Final-SNAPSHOT\modules\org\jboss\as\jdr\main\jboss-as-sos-7.1.1.Final-SNAPSHOT.jar\sos\policies\__init__.py", line 148, in is_root AttributeError: 'module' object has no attribute 'getuid' at org.python.core.PyException.fillInStackTrace(PyException.java:70) [jython-standalone-2.5.2.jar:] {code} See: http://hudson.jboss.org/hudson/view/All/job/JBoss-AS-7.1.x-testSuite-wind... -- 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, 4 months

3
3
0 / 0

[JBoss JIRA] (AS7-2785) Do not call @PostConstruct multiple times on @Startup @Singleton bean.

by Dan Spasojevic (Created) (JIRA)

Do not call @PostConstruct multiple times on @Startup @Singleton bean. ---------------------------------------------------------------------- Key: AS7-2785 URL: https://issues.jboss.org/browse/AS7-2785 Project: Application Server 7 Issue Type: Feature Request Components: EJB Affects Versions: 7.1.0.Beta1, 7.0.2.Final Reporter: Dan Spasojevic Assignee: Carlo de Wolf Attachments: test.zip Given an @Startup @Singleton bean with a @PostConstruct method called Controller; when the Controller's dependencies are satisfied then its @PostConstruct method is called. Given another @Startup @Singleton bean with a @PostConstruct method called Client that has an @EJB injection of the Controller; when the Client's dependencies are satisfied then the @PostConstruct method of both the Controller and Client are called. This is true for each Client instance. So if there are N Client instances, there will be N+1 invocations of Controller's @PostConstruct. -- 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, 4 months

8
8
0 / 0

[JBoss JIRA] (JBMESSAGING-1915) TopicPublisher aceepts invalid delivery modes.

by Doug Grove (JIRA)

Doug Grove created JBMESSAGING-1915: --------------------------------------- Summary: TopicPublisher aceepts invalid delivery modes. Key: JBMESSAGING-1915 URL: https://issues.jboss.org/browse/JBMESSAGING-1915 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Environment: JBoss 4.3.0.GA_CP08 Reporter: Doug Grove Priority: Minor Valid delivery modes are specified on the abstract interface javax.jmx.DeliveryMode. For JBoss, these have values of NON_PERSISTENT = 1 and PERSISTENT = 2. If an invalid value, -1 for example, is passed to TopicPublisher.publish(), no exception is thrown and the call can block for a substantial period. -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] (AS7-3590) Deprecate OperationContext.getRootResource(); provide variant to get a read only view of an addressed branch of the Resource tree

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-3590: ------------------------------------- Summary: Deprecate OperationContext.getRootResource(); provide variant to get a read only view of an addressed branch of the Resource tree Key: AS7-3590 URL: https://issues.jboss.org/browse/AS7-3590 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Critical Fix For: 7.1.1.Final OperationContext.getRootResource() is very expensive as it clones the entire model in order to provide a defensive copy that callers can't use to mutate parent resources. In almost all cases the caller then navigates to a lower level of the tree to read. The OperationContext should provide a method to do this for them, restricting the cost of defending against writes to the portion of the tree the caller actually cares about. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] (AS7-3678) Can not determine the local host in a multi host domain under /host

by Heiko Rupp (JIRA)

Heiko Rupp created AS7-3678: ------------------------------- Summary: Can not determine the local host in a multi host domain under /host Key: AS7-3678 URL: https://issues.jboss.org/browse/AS7-3678 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Rupp Assignee: Brian Stansberry Fix For: 7.1.1.Final [21:28:49] <+pilhuhn> bstansberry (probably stupid) question: how do I see in the management api which host under /host is the local one? I have no example handy, but remember that in a multi-host domain all hosts are listed in /host [21:29:17] ChanServ sets mode +v stuartdouglas [21:30:42] <+bstansberry> pilhuhn: not stupid. can you file a JIRA for 7.1.1? -- 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, 4 months

3
9
0 / 0

[JBoss JIRA] (AS7-2272) run.sh and run.bat for compatibility

by Rich Sharples (Created) (JIRA)

run.sh and run.bat for compatibility ------------------------------------ Key: AS7-2272 URL: https://issues.jboss.org/browse/AS7-2272 Project: Application Server 7 Issue Type: Feature Request Components: Scripts Affects Versions: 7.1.0.Alpha1 Environment: all Reporter: Rich Sharples Assignee: Brian Stansberry Fix For: 7.1.0.Beta1 Many seasoned JBoss users expect to be able to run bin/run.sh (bin\run.bat). Now deprecated these scripts inform the user what to use instead : eg. run.sh is no longer supported. The scripts standalone.sh (standalone.bat on Windows) should be used to start a single instance. and domain.sh (domain.bat on Windows) should be used to start in domain mode. See the documentation for further information. -- 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, 4 months

5
4
0 / 0

[JBoss JIRA] (AS7-3675) Expose HostControllerEnvironment via management API

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-3675: ------------------------------------- Summary: Expose HostControllerEnvironment via management API Key: AS7-3675 URL: https://issues.jboss.org/browse/AS7-3675 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.1.Final Add a resource at /host=*/core-service=host-controller-enviroment. Analogous to the one on servers at /core-service=server-environment. -- 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, 4 months

2
1
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 February 2012