March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6338) Remove -jaxpmodule from start scripts

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6338?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6338: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) I believe this is done. > Remove -jaxpmodule from start scripts > ------------------------------------- > > Key: AS7-6338 > URL: https://issues.jboss.org/browse/AS7-6338 > Project: Application Server 7 > Issue Type: Task > Components: Scripts > Reporter: David Lloyd > Assignee: Kabir Khan > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > JBoss Modules uses SPI to locate the JAXP providers, since 1.1. -- 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-4292) Invalid bundle deployment does not fail in domain

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4292?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4292: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Invalid bundle deployment does not fail in domain > ------------------------------------------------- > > Key: AS7-4292 > URL: https://issues.jboss.org/browse/AS7-4292 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, OSGi > Reporter: Thomas Diesler > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > Running org.jboss.as.test.integration.domain.suites.OSGiBundleLifecyleTestCase > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 35.653 sec <<< FAILURE! > on the server I see > {code} > 15:20:28,619 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit.bad-bundle.STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit.bad-bundle.STRUCTURE: Failed to process phase STRUCTURE of deployment "bad-bundle" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29] > Caused by: java.lang.NumberFormatException: For input string: "bogus" > at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) [rt.jar:1.6.0_29] > at java.lang.Integer.parseInt(Integer.java:449) [rt.jar:1.6.0_29] > at java.lang.Integer.parseInt(Integer.java:499) [rt.jar:1.6.0_29] > at org.osgi.framework.Version.<init>(Version.java:125) > at org.osgi.framework.Version.parseVersion(Version.java:218) > at org.jboss.osgi.spi.BundleInfo.validateBundleManifest(BundleInfo.java:204) > at org.jboss.osgi.spi.BundleInfo.isValidBundleManifest(BundleInfo.java:153) > at org.jboss.as.osgi.deployment.OSGiManifestStructureProcessor.deploy(OSGiManifestStructureProcessor.java:63) > {code} -- 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-4532) fix jvm management model for server and groups

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4532?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4532: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > fix jvm management model for server and groups > ---------------------------------------------- > > Key: AS7-4532 > URL: https://issues.jboss.org/browse/AS7-4532 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.0.0.Final, 7.1.0.Final > Reporter: Emanuel Muckenhuber > Assignee: Emanuel Muckenhuber > Labels: rhq > Fix For: 8.0.0.Alpha1 > > > We need to update the JVM child resource definition for server-groups and servers to only allow a single JVM configuration (i.e. configuration=JVM) resource. Currently only the first configured VM is used, where the name is the reference to the corresponding host level JVM. -- 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-6470) Improve reporting during deployment hang

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6470?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6470: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Improve reporting during deployment hang > ---------------------------------------- > > Key: AS7-6470 > URL: https://issues.jboss.org/browse/AS7-6470 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Environment: http://java.net/jira/browse/EJB_SPEC-60 > java version "1.7.0_09" > OpenJDK Runtime Environment (IcedTea7 2.3.3) (7u9-2.3.3-0ubuntu1~12.10.1) > OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode) > Ubuntu 12.10 > Reporter: Carlo de Wolf > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > Attachments: deployment-hang-20130205.txt, server.log > > > Management Thread waits indefinitely for, what seems to be, a finished operation. > {noformat} > "management-handler-thread - 2" prio=10 tid=0x00007fa1380d0000 nid=0x7683 in Object.wait() [0x00007fa136deb000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000e04ae778> (a org.jboss.as.controller.ContainerStateMonitor) > at java.lang.Object.wait(Object.java:503) > at org.jboss.as.controller.ContainerStateMonitor.awaitContainerStateChangeReport(ContainerStateMonitor.java:158) > - locked <0x00000000e04ae778> (a org.jboss.as.controller.ContainerStateMonitor) > at org.jboss.as.controller.ModelControllerImpl.awaitContainerStateChangeReport(ModelControllerImpl.java:464) > at org.jboss.as.controller.OperationContextImpl.awaitModelControllerContainerMonitor(OperationContextImpl.java:148) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:299) > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:142) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:112) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > {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-6655) binding subcontexts with <lookup> does not work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6655?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6655: ---------------------------------------------- James Livingston <jlivings(a)redhat.com> made a comment on [bug 918346|https://bugzilla.redhat.com/show_bug.cgi?id=918346] If you attempt to bind a subcontext via <lookup> in the naming subsystem it will fail when anything is looked up under it. To reproduce, add <lookup name="java:jboss/ds" lookup="java:jboss/datasources"/>, and then look up something under java:jboss/ds/ In ServiceBasedNamingStore.lookup() it needs to return a ResolveResult, but the (!(obj instanceof NamingContext)) check skips it. As a work-around, you can write an object factory which looks up the sub-context and then returns a wrapper around it, a Context implementation which simply delegates all methods to the original context. Since that wrapper is not a NamingContext instance, it works. > binding subcontexts with <lookup> does not work > ----------------------------------------------- > > Key: AS7-6655 > URL: https://issues.jboss.org/browse/AS7-6655 > Project: Application Server 7 > Issue Type: Bug > Components: Naming > Affects Versions: 7.1.3.Final (EAP) > Reporter: James Livingston > Assignee: Eduardo Martins > > If you attempt to bind a subcontext via <lookup> in the naming subsystem it will fail when anything is looked up under it. > To reproduce, add <lookup name="java:jboss/ds" lookup="java:jboss/datasources"/>, and then look up something under java:jboss/ds/ > In ServiceBasedNamingStore.lookup() it needs to return a ResolveResult, but the (!(obj instanceof NamingContext)) check skips it. > As a work-around, you can write an object factory which looks up the sub-context and then returns a wrapper around it, a Context implementation which simply delegates all methods to the original context. Since that wrapper is not a NamingContext instance, it works. -- 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-6655) binding subcontexts with <lookup> does not work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6655?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated AS7-6655: ----------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=918346 > binding subcontexts with <lookup> does not work > ----------------------------------------------- > > Key: AS7-6655 > URL: https://issues.jboss.org/browse/AS7-6655 > Project: Application Server 7 > Issue Type: Bug > Components: Naming > Affects Versions: 7.1.3.Final (EAP) > Reporter: James Livingston > Assignee: Eduardo Martins > > If you attempt to bind a subcontext via <lookup> in the naming subsystem it will fail when anything is looked up under it. > To reproduce, add <lookup name="java:jboss/ds" lookup="java:jboss/datasources"/>, and then look up something under java:jboss/ds/ > In ServiceBasedNamingStore.lookup() it needs to return a ResolveResult, but the (!(obj instanceof NamingContext)) check skips it. > As a work-around, you can write an object factory which looks up the sub-context and then returns a wrapper around it, a Context implementation which simply delegates all methods to the original context. Since that wrapper is not a NamingContext instance, it works. -- 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-2227) Port the legacy jmx-console to AS7

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-2227?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-2227: ---------------------------------- Fix Version/s: (was: 7.3.0.Alpha1) > Port the legacy jmx-console to AS7 > ---------------------------------- > > Key: AS7-2227 > URL: https://issues.jboss.org/browse/AS7-2227 > Project: Application Server 7 > Issue Type: Feature Request > Components: JMX > Reporter: Dimitris Andreadis > Assignee: Darran Lofthouse > Labels: JMX, as7, jmx-console > Attachments: jmx-console.war > > > I've seen a few people asking for a port of the old jmx-console to AS7, for monitoring purposes, until equivalent functionality is available through the new GWT-based console. > I've ported the old console in this branch: > https://github.com/dandreadis/jboss-as/commits/jmx-console > It only includes a new top-level directory 'jmx-console'. The directory is not build by default, and when you build it manually it does not alter the server configuration in any way, you need to manually copy the resulting target/jboss-as-jmx-console-VERSION.war to the server deployment directory (and rename it to jmx-console.war) > If there is interest, it could be included in the AS7 distro in some top level 'legacy' directory so it is not deployed by default? > The resulting .war is attached on this JIRA, in case someone wants to use it. It work just as well on AS 7.0.2 and the latest AS 7.1.x development branch. -- 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-6442) Make transformers testing of subsystems use the legacy maven dependencies recursively rather than running the old subsystem on the new controller

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6442?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6442: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Make transformers testing of subsystems use the legacy maven dependencies recursively rather than running the old subsystem on the new controller > ------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-6442 > URL: https://issues.jboss.org/browse/AS7-6442 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.Alpha1 > > > To do something like what we do in core-model-test, where instead of just getting the legacy subsystem, we make the scoped classloader used for the legacy controller bring in the full set of dependencies for the subsystem, including its real controller. That will definitely get rid of these issues, and all the deprecated methods left around, but will need all the classloader trickery/proxies etc. done to load up the proxy controller and to be able to read/write to it. I think I have pretty much all the code for that, but will need to double-check if you like the idea. It will mean a big reorg of code and will take at least a few days. It also means that the tests will need to download a lot more from maven, I'm not sure if lightning has some cached private repo or not. We could probably only recursively bring in the org.jboss.as dependencies recursively to make it a bit more efficient, i.e. loading JPA for 7.1.2 should not need all the hibernate jars for that version since we are only testing the model part. -- 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-6477) /host=* has something called "server" that is neither child nor attribute

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6477?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6477: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > /host=* has something called "server" that is neither child nor attribute > ------------------------------------------------------------------------- > > Key: AS7-6477 > URL: https://issues.jboss.org/browse/AS7-6477 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.2.0.Alpha1 > Reporter: Stan Silvert > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha1 > > > Start a domain with a host called "master". In CLI, do /host=master/:read-resource. In the result, you will see a resource called "server". > However, if you do /host=master/:read-children-types it will not show up as a child type. > If you do /host=master/:read-resource-description it will not show up as an attribute either. > So what is "server"? It's not a child and it's not an attribute. Is it something that should not show up in read-resource? -- 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-2618) Add quickstarts info to localhost:8080

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-2618?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-2618: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Add quickstarts info to localhost:8080 > -------------------------------------- > > Key: AS7-2618 > URL: https://issues.jboss.org/browse/AS7-2618 > Project: Application Server 7 > Issue Type: Task > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > Add another static page, quickstarts.html, that lists the quickstarts available and how to get them. Add a link from the main page. -- 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