March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5293) Align domain.sh and standalone.sh logic about adding -server

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5293?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5293: ---------------------------------- Fix Version/s: Open To Community (was: 7.3.0.Alpha1) > Align domain.sh and standalone.sh logic about adding -server > ------------------------------------------------------------ > > Key: AS7-5293 > URL: https://issues.jboss.org/browse/AS7-5293 > Project: Application Server 7 > Issue Type: Sub-task > Components: Scripts > Reporter: Brian Stansberry > Fix For: Open To Community > > > The domain.sh script has a number of JVM vendor checks it uses to decide whether to add -server to the jvm launch command. In standalone.sh it's simpler; it simply checks for OSX. > I can't see any reason this logic should be significantly different between the two cases, either the JVM vendor checks are needed in both or they aren't needed in either. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-1371) Domain Management - Support for database connection pool in non AS process.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-1371?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-1371: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Domain Management - Support for database connection pool in non AS process. > --------------------------------------------------------------------------- > > Key: AS7-1371 > URL: https://issues.jboss.org/browse/AS7-1371 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Flemming Harms > Fix For: 8.0.0.Alpha1 > > > We need to support authentication for users stored in database, the domain management is in a non-AS process so we also need a pool of database connections. > These connections will be used to read only from the database, other than the isolation offered by the driver we should not require any advanced transaction support. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-4097) Using an extended persistence context in a stateless session bean should throw an exception

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4097?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4097: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Using an extended persistence context in a stateless session bean should throw an exception > ------------------------------------------------------------------------------------------- > > Key: AS7-4097 > URL: https://issues.jboss.org/browse/AS7-4097 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Karsten Wutzke > Fix For: 8.0.0.Alpha1 > > > Using an extended persistence context in a stateless session bean should not initiate. It should throw an exception to notify the user of incorrect use. > See JPA 2.0 spec, section 7.6.2: > "A container-managed extended persistence context can only be initiated within the scope of a stateful session bean." -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-5127) Performance bottleneck on Javassist

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5127?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5127: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Performance bottleneck on Javassist > ----------------------------------- > > Key: AS7-5127 > URL: https://issues.jboss.org/browse/AS7-5127 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 7.1.2.Final (EAP) > Environment: Sun/Oracle JDK 1.6_32, Linux 64b > Reporter: Alessandro Lazarotti > Assignee: Scott Marlow > Fix For: 8.0.0.Alpha1 > > > The method javassist.util.proxy.RuntimeSupport.find2methods has a synch block, called indirectly by ProxyFactory.createClass(). It is a strong bottleneck for frameworks as Hibernate which can use it several times in a large set of data. > Javassist 3.17.0-GA fixes it. AS7 should update its current javassist version. > More details in https://issues.jboss.org/browse/JASSIST-163 -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6181) Add @ValidIdRange annotation to message loggers and message bundles

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6181?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6181: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Add @ValidIdRange annotation to message loggers and message bundles > ------------------------------------------------------------------- > > Key: AS7-6181 > URL: https://issues.jboss.org/browse/AS7-6181 > Project: Application Server 7 > Issue Type: Enhancement > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.0.Alpha1 > > > A new release of the logging tooling will include a {{@ValidIdRange}} annotation. This will help document which id ranges allowed as well as provide compile time validation. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-947) Managed domain server :reload() operation

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-947?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry updated AS7-947: --------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Managed domain server :reload() operation > ----------------------------------------- > > Key: AS7-947 > URL: https://issues.jboss.org/browse/AS7-947 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha1 > > > Reloading yields an exception: > /host=local/server=server-one:reload > {noformat} > [Host Controller] 12:32:50,188 ERROR [org.jboss.as.host.controller] (pool-1-thread-24) Could not start server Server:server-one: java.lang.IllegalArgumentException: A node is already registered at '(server => server-one)' > [Host Controller] at org.jboss.as.controller.registry.NodeSubregistry.registerProxyController(NodeSubregistry.java:89) [jboss-as-controller-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] > {noformat} > A second operation request results in "broken pipe": > {noformat} > [Host Controller] 12:33:03,025 ERROR [org.jboss.as.protocol] (ModelControllerClient-thread - 1) Failed to close resource org.jboss.as.protocol.SimpleByteDataOutput@37c398e: java.net.SocketException: Broken pipe > {noformat} -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6521) Spurious server dirs created when directory-grouping="by-type" is set

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6521?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6521: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Spurious server dirs created when directory-grouping="by-type" is set > --------------------------------------------------------------------- > > Key: AS7-6521 > URL: https://issues.jboss.org/browse/AS7-6521 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: James Perkins > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > Add directory-grouping="by-type" to the <host><servers> element in the stock host.xml and run domain.sh. The following empty directories are created: > $JBOSS_HOME/domain/servers/server-one > $JBOSS_HOME/domain/servers/server-two > The content that would normally be in those dirs if directory-grouping="by-type" wasn't set appears to all be going where it should (e.g. under domain/data, domain/log etc) so the only issue here is the empty directories. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-4999) Alllow non persistent configuration(runtime) changes for server groups and domain using CLI

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4999?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4999: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Alllow non persistent configuration(runtime) changes for server groups and domain using CLI > ------------------------------------------------------------------------------------------- > > Key: AS7-4999 > URL: https://issues.jboss.org/browse/AS7-4999 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Shay Matasaro > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > Using the CLI , It is currently not possible to make runtime config changes to multiple servers , unless you are using a roll-out plan > One example is the ability to disable a mod-cluster context on multiple servers at once. > Since this operation does not affect the persistent server config it is currently not supported. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6601) Increment management model versions for security, messaging, infinispan subsystems

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6601?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6601: ---------------------------------- Fix Version/s: (was: 7.3.0.Alpha1) > Increment management model versions for security, messaging, infinispan subsystems > ---------------------------------------------------------------------------------- > > Key: AS7-6601 > URL: https://issues.jboss.org/browse/AS7-6601 > Project: Application Server 7 > Issue Type: Task > Components: Clustering, Domain Management, JMS, Security > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 8.0.0.Alpha1 > > > The AS7-6531 fixes have changed the management API for the 3 listed subsystems, and those changes are not expected to be reflected in the 7.2.0.Final tag. As a result, the management model versions need to be incremented. I anticipate using a micro version bump. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6379) Intermittent failures in RespawnTestCase

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6379?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6379: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) Assignee: Emanuel Muckenhuber > Intermittent failures in RespawnTestCase > ---------------------------------------- > > Key: AS7-6379 > URL: https://issues.jboss.org/browse/AS7-6379 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha1 > > > Problems like [1] still pop up fairly frequently. It seems the same 3 tests fail. > Failed tests: testReloadHcButNotServers(org.jboss.as.test.integration.respawn.RespawnTestCase) > testReloadHcButNotServersWithFailedServer(org.jboss.as.test.integration.respawn.RespawnTestCase) testHCReloadAbortPreservesServers(org.jboss.as.test.integration.respawn.RespawnTestCase) > [1] http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-ignore/... -- 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

13 years, 4 months

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 2013