April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4463) Add VisualVm launch scripts to the AS7 distirubution

by John O'Hara (JIRA)

John O'Hara created AS7-4463: -------------------------------- Summary: Add VisualVm launch scripts to the AS7 distirubution Key: AS7-4463 URL: https://issues.jboss.org/browse/AS7-4463 Project: Application Server 7 Issue Type: Feature Request Components: Scripts Affects Versions: 7.1.1.Final Reporter: John O'Hara Assignee: Brian Stansberry Priority: Trivial -- 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

13 years, 6 months

2
2
0 / 0

[JBoss JIRA] (AS7-4237) Possible errrors

by Yamamoto Mie (JIRA)

Yamamoto Mie created AS7-4237: --------------------------------- Summary: Possible errrors Key: AS7-4237 URL: https://issues.jboss.org/browse/AS7-4237 Project: Application Server 7 Issue Type: Enhancement Components: Documentation Reporter: Yamamoto Mie Priority: Minor I have a few questions about AS7 and also found possible errors in the doc. Questions: - Null owned session update can you explain when is this message shown? - to multiple create* methods with different return types on home %s when is this message shown? to create* multiple methods?? or multiple create() methods? - EJB component for address %s is in Is this EJB component for address %s is in (state %s)? ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Possible errors - Class %s has more *that* one constructor annotated with @Inject -> more than? - Boolean to determine whether to create create the tables - Boolean to determine whether to create drop the tables - Timeout, in seconds, a deployment is allows to execute before being canceled. The default is 60 seconds. - Filed to lookup: %s - Specifies whether the ejb3 container need only (to?) provide the "LITE" profile of the specification. This value should only be false when using the "everything" distro. - Removes a specific (a) bean instance pool which has a strict upper limit for bean instances -No timed object invoke(d) for %s -- 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

13 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1133) MSC service in war file is loaded from WEB-INF/classes/META-INF/services instead of META-INF/services

by David Bosschaert (JIRA)

MSC service in war file is loaded from WEB-INF/classes/META-INF/services instead of META-INF/services ----------------------------------------------------------------------------------------------------- Key: AS7-1133 URL: https://issues.jboss.org/browse/AS7-1133 Project: Application Server 7 Issue Type: Bug Components: MSC, Web Affects Versions: 7.0.0.CR1 Reporter: David Bosschaert Priority: Minor When deploying a .war file that contains a META-INF/service/org.jboss.msc.service.ServiceActivator this file is only processed when it's in the WEB-INF/classes/META-INF/services location, where I think it should really be picked up fro /META-INF/services -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
1
0 / 0

[JBoss JIRA] (AS7-4632) Create ability to turn on logging levels per subsystem

by James Perkins (JIRA)

James Perkins created AS7-4632: ---------------------------------- Summary: Create ability to turn on logging levels per subsystem Key: AS7-4632 URL: https://issues.jboss.org/browse/AS7-4632 Project: Application Server 7 Issue Type: Feature Request Components: Logging Reporter: James Perkins Assignee: James Perkins Possibly edit the change-level operation to accept a subsystem name, e.g. jpa, and enable the specified level for all the JPA categories. {code} /:change-level(level=TRACE,subsystem=jpa) {code} Though at a root level, {{change-log-level}} might be more appropriate. -- 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

13 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8824) Cardinality constraints on children are not enforced after parsing

by Brian Stansberry (JIRA)

Cardinality constraints on children are not enforced after parsing ------------------------------------------------------------------ Key: JBAS-8824 URL: https://issues.jboss.org/browse/JBAS-8824 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Alpha1 Reporter: Brian Stansberry Priority: Critical Fix For: 7.0.0.Beta1 The parsers enforce cardinality constraints on child elements in the model, but they aren't enforced thereafter. So, for example, a second "profile" or "socket-binding-group" could be added to a standalone server via a management operation. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
5
0 / 0

[JBoss JIRA] (AS7-4626) Standard method of documenting whether expressions are supported in the jboss-as-config_x_x.xsd and in the subsystem xsds

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4626: ------------------------------------- Summary: Standard method of documenting whether expressions are supported in the jboss-as-config_x_x.xsd and in the subsystem xsds Key: AS7-4626 URL: https://issues.jboss.org/browse/AS7-4626 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Brian Stansberry Fix For: 7.2.0.Alpha1 Users should be able to read the xsd to tell if expressions are supported for a given attribute/element. Reading the management API metadata is too cumbersome and indirect. -- 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

13 years, 6 months

1
1
0 / 0

[JBoss JIRA] (AS7-4627) Remove ServerEnvironment.getModulesDir()

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4627: ------------------------------------- Summary: Remove ServerEnvironment.getModulesDir() Key: AS7-4627 URL: https://issues.jboss.org/browse/AS7-4627 Project: Application Server 7 Issue Type: Task Components: Server Reporter: Brian Stansberry Fix For: 7.2.0.Alpha1 This method was deprecated in 7.1.0 and the OSGi subsystem is removing the only known use of it in 7.1.2. Remove the method in 7.2. -- 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

13 years, 6 months

1
2
0 / 0

[JBoss JIRA] (AS7-4383) Mode to disable writing deployment outcome files to deployment scanner dir

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4383: ------------------------------------- Summary: Mode to disable writing deployment outcome files to deployment scanner dir Key: AS7-4383 URL: https://issues.jboss.org/browse/AS7-4383 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 Investigate adding a config option that disables writing the .isdeploying, .deployed, .isundeploying, .undeployed files to the deployment scanner dir. Idea is to make it possible to have multiple scanners on different nodes sharing the deployment directory, without having the markers from one interfere with another. This may not be practical at all in reality; needs investigation. Marker files created by the user to control deployment should still be supported. The .failed and .pending files are a bit of a gray area that need investigation. -- 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

13 years, 6 months

4
5
0 / 0

[JBoss JIRA] (AS7-4428) Arquillian: IllegalStateException: standard-sockets -> http -> bound-port is undefined

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-4428: --------------------------------- Summary: Arquillian: IllegalStateException: standard-sockets -> http -> bound-port is undefined Key: AS7-4428 URL: https://issues.jboss.org/browse/AS7-4428 Project: Application Server 7 Issue Type: Bug Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka This happens sometimes in QA lab, probably due to slowness. See https://hudson.qa.jboss.com/hudson/job/AS7-TS-valid-mvn-all-ipv6/56/testR... {code} java.lang.RuntimeException: java.lang.IllegalStateException: standard-sockets -> http -> bound-port is undefined at org.jboss.as.arquillian.container.ManagementClient.getBinding(ManagementClient.java:222) at org.jboss.as.arquillian.container.ManagementClient.getWebUri(ManagementClient.java:111) at org.jboss.as.arquillian.container.ManagementClient.getDeploymentMetaData(ManagementClient.java:117) at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:150) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:156) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:123) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:266) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:122) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:90) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:79) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:258) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:234) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:78) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) at org.junit.runners.ParentRunner.run(ParentRunner.java:300) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) Caused by: java.lang.IllegalStateException: standard-sockets -> http -> bound-port is undefined at org.jboss.as.arquillian.container.ManagementClient.defined(ManagementClient.java:193) at org.jboss.as.arquillian.container.ManagementClient.getBinding(ManagementClient.java:218) ... 96 more {code} -- 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

13 years, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (JGRP-1317) STABLE: compress STABLE messages

by Bela Ban (JIRA)

STABLE: compress STABLE messages -------------------------------- Key: JGRP-1317 URL: https://issues.jboss.org/browse/JGRP-1317 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.12.2, 3.1 For large clusters, stable messages are quite large, and should be compressed. E.g.: - Don't send the entire view (with all members), but only the ViewId, then the indices of a digest array would point to the rank of a member within the referred-to ViewId - A digest has 3 longs (low, highest_received and highest_delivered). Do we need all 3 every time ? - Compress the 3 longs into 1 long and 2 shorts: the latter 2 are offsets from the first seqno - Use a bit set (consisting of a variable number of ints) to set the 3 variables - If we have a digest (0), 0, 0: send a special marker - Canonicalize digests: if everyone has (14) 20, 22, then we could write it once, give it an ID of (say) 1 and then only refer to 1 again if we encounter the same digest. Actually, as a matter of fact, most of the digests would be the same, so this optimization could have a big effect ! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
7
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 April 2012