February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGTOOL-34) FQCN methods are not completely correct

by David Lloyd (Created) (JIRA)

FQCN methods are not completely correct --------------------------------------- Key: LOGTOOL-34 URL: https://issues.jboss.org/browse/LOGTOOL-34 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd The generated code looks like this: {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

14 years, 3 months

5
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1617) Create a MC bean handle in the likes of java.ejb.Handle

by Carlo de Wolf (JIRA)

Create a MC bean handle in the likes of java.ejb.Handle ------------------------------------------------------- Key: EJBTHREE-1617 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1617 Project: EJB 3.0 Issue Type: Feature Request Components: common Reporter: Carlo de Wolf Assignee: Ales Justin Priority: Critical Fix For: 1.0.0-CR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
2
0 / 0

[JBoss JIRA] (AS7-3710) Cannot see classes defined by OSGi bootdelegation

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-3710: ----------------------------------- Summary: Cannot see classes defined by OSGi bootdelegation Key: AS7-3710 URL: https://issues.jboss.org/browse/AS7-3710 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.1.Final I use a javaagent that does bytecode instrumentation. This injected code needs to be able to see its runtime dependency, which is available from the boot classloader. JBoss appears to ignore the "org.osgi.framework.bootdelegation" property -- 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, 3 months

3
7
0 / 0

[JBoss JIRA] (REMJMX-34) Clients hanging for 60s after closing connection to AS7

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-34: -------------------------------------- Summary: Clients hanging for 60s after closing connection to AS7 Key: REMJMX-34 URL: https://issues.jboss.org/browse/REMJMX-34 Project: Remoting JMX Issue Type: Bug Components: Connection Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 1.0.2.Final Non-daemon threads are keeping the process alive for one minute if the connection is closed - if the connection is not closed it is kept open for much longer. -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-153) EJB timer clustering and failover support

by Galder Zamarreno (JIRA)

EJB timer clustering and failover support ----------------------------------------- Key: JBCLUSTER-153 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-153 Project: JBoss Clustering Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Galder Zamarreno Assigned To: Brian Stansberry Support for clustered EJB timer service providing failover -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
7
0 / 0

[JBoss JIRA] Created: (AS7-1738) CLI usability: unclear that the CLI is managing a domain not a host

by Radoslav Husar (JIRA)

CLI usability: unclear that the CLI is managing a domain not a host ------------------------------------------------------------------- Key: AS7-1738 URL: https://issues.jboss.org/browse/AS7-1738 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.0.1.Final, 7.0.0.Final Reporter: Radoslav Husar Assignee: Alexey Loubyansky Looks to me that the CLI is behaving differently if you are running in a domain mode or in a stadnalone mode managing just a host. However it is not really clear from the CLI help messages. In the following log * the console does not say its running in the domain mode * claims that the --profile argument is optional even though its indeed required * does not say that it is not the master domain controller and refuses all changes anyway {code} [domain@rhusar:9999 /] add-jms-queue --help Synopsis: add-jms-queue [--profile=profile_name] --name=queue_name [--entries=entry(,entry)*] [--selector=selector_name] [--durable=(true|false)] Description: creates a JMS queue Arguments: profile - is allowed and required only in the domain mode, specifies the profile in which the JMS resource should be created. name - the name of the queue. entries - an optional comma-separated list of JNDI names the queue should be bound under. If not present, the name will be used as the JNDI name. selector - optional selector. durable - optional, specifies whether the queue should be durable or not (the default is true). [domain@rhusar:9999 /] add-jms-queue --profile=ha --name=rQ Operation add for address [ ("profile" => "ha"), ("subsystem" => "messaging"), ("jms-queue" => "rQ") ] can only handled by the master Domain Controller; this host is not the master Domain Controller [domain@rhusar:9999 /] add-jms-queue --name=rQ --profile argument value is missing. [domain@rhusar:9999 /] quit Closed connection to rhusar:9999 {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
8
0 / 0

[JBoss JIRA] (AS7-3963) Allow additional punctuation in user names added with add-user script

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3963: ------------------------------------- Summary: Allow additional punctuation in user names added with add-user script Key: AS7-3963 URL: https://issues.jboss.org/browse/AS7-3963 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.2.Final Would need to double check that user names with the additional punctuation don't cause additional problems either in the reading of properties files as properties file or within the mechanisms used which also use punctuation to split a single header e.g. HTTP Digest authentication. -- 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, 3 months

2
2
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, 3 months

3
2
0 / 0

[JBoss JIRA] (AS7-3901) jsr88 enterprise deployment URI processing does not take IP stack preference into account

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created AS7-3901: ---------------------------------------- Summary: jsr88 enterprise deployment URI processing does not take IP stack preference into account Key: AS7-3901 URL: https://issues.jboss.org/browse/AS7-3901 Project: Application Server 7 Issue Type: Bug Components: EE Affects Versions: 7.1.0.Final Reporter: Richard Achmatowicz Assignee: David Lloyd The test case org.jboss.as.test.smoke.jsr88.EnterpriseDeploymentTestCase testDistributeWebApp is failing with the following exception when the testsuite is started with IPv6 addresses as follows: {noformat} ./integration-tests.sh clean install -Dnode0=::1 -Dnode1=::1 -DudpGroup=ff0e::1 -Dipv6 {noformat} The exception is: {noformat} <failure message="expected:<Completed> but was:<Failed>" type="java.lang.AssertionError">java.lang.AssertionError: expected:<Completed> but was:<Failed> at org.junit.Assert.fail(Assert.java:93) at org.junit.Assert.failNotEquals(Assert.java:647) at org.junit.Assert.assertEquals(Assert.java:128) at org.junit.Assert.assertEquals(Assert.java:147) at org.jboss.as.test.smoke.jsr88.EnterpriseDeploymentTestCase.testDistributeWebApp(EnterpriseDeploymentTestCase.java:102) 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.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.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.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) 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.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) 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.createTestContext(TestContextHandler.java:89) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) 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.createClassContext(TestContextHandler.java:75) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) 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.GeneratedMethodAccessor1.invoke(Unknown Source) 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.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) 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$5.evaluate(Arquillian.java:240) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) 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.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) 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:164) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) </failure> <system-out> 10:39:34,387 INFO [org.jboss.as.ee.deployment.spi] (Thread-31) JBAS016100: Begin deploy: [target=http://org.jboss.as.ee.deployment/jsr88?targetType=as7,parent=null,type=war,id=file:/tmp/deployment-web.war] Distribute failed on target: org.jboss.as.ee.deployment.spi.DeploymentManagerTarget@5b39626c: java.lang.RuntimeException: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeAsync(AbstractModelControllerClient.java:114) at org.jboss.as.controller.client.helpers.standalone.impl.ModelControllerClientServerDeploymentManager.executeOperation(ModelControllerClientServerDeploymentManager.java:47) at org.jboss.as.controller.client.helpers.standalone.impl.AbstractServerDeploymentManager.execute(AbstractServerDeploymentManager.java:79) at org.jboss.as.ee.deployment.spi.DeploymentManagerTarget.executeDeploymentPlan(DeploymentManagerTarget.java:203) at org.jboss.as.ee.deployment.spi.DeploymentManagerTarget.deploy(DeploymentManagerTarget.java:126) at org.jboss.as.ee.deployment.spi.DeploymentWorker.run(DeploymentWorker.java:64) Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:168) at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:166) at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:138) at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:62) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:106) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:89) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:253) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:152) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeAsync(AbstractModelControllerClient.java:112) ... 5 more </system-out> {noformat} -- 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, 3 months

2
6
0 / 0

[JBoss JIRA] (AS7-2245) Help text needed for topics

by Kevin Barfield (Created) (JIRA)

Help text needed for topics --------------------------- Key: AS7-2245 URL: https://issues.jboss.org/browse/AS7-2245 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Kevin Barfield Assignee: Heiko Braun There needs to be help text for each topic in the console - this help text should explain what the topic is, why it is important to the user, and maybe a link to the relevant docs section. This needs to be understandable by average people For example: Datasource Configurations Datasources are used to connect JBoss EAP to databases. This page allows admins to view existing datasources Admins can also create, modify, and delete datasources. Please see the datasource section of the documentation for more details about datasources <link>. -- 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, 3 months

3
3
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