[JBoss JIRA] (AS7-6099) Include registered attributes with no model representation in read-resource results
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6099?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6099:
----------------------------------
Assignee: (was: Brian Stansberry)
> Include registered attributes with no model representation in read-resource results
> -----------------------------------------------------------------------------------
>
> Key: AS7-6099
> URL: https://issues.jboss.org/browse/AS7-6099
> Project: Application Server 7
> Issue Type: Enhancement
> Components: Domain Management
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Brian Stansberry
> Priority: Minor
>
> Following situation:
> 1) resource includes attribute xyz
> 2) No read-handler is registered for xyz (i.e. default read semantic Resource.getModel().get("xyz") is to be used)
> 3) Poorly coded "add" handler for the resource doesn't call model.get("xyz") for some reason.
> The effect of this is the read-resource result will not include "xyz" => undefined in the output. Nothing for xyz will appear at all, hiding the existence of the attribute from the caller.
> The read-resource handler can deal with a check in its loop through the AttributeAccess registration for the "no read-handler" case. (This check is already there; an 'else' clause is needed.) If no read-handler, see if there is an entry in the directAttributes map for the attribute; if not, add one with a value of new ModelNode().
--
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, 5 months
[JBoss JIRA] (AS7-6099) Include registered attributes with no model representation in read-resource results
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-6099:
-------------------------------------
Summary: Include registered attributes with no model representation in read-resource results
Key: AS7-6099
URL: https://issues.jboss.org/browse/AS7-6099
Project: Application Server 7
Issue Type: Enhancement
Components: Domain Management
Affects Versions: 7.1.3.Final (EAP)
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
Following situation:
1) resource includes attribute xyz
2) No read-handler is registered for xyz (i.e. default read semantic Resource.getModel().get("xyz") is to be used)
3) Poorly coded "add" handler for the resource doesn't call model.get("xyz") for some reason.
The effect of this is the read-resource result will not include "xyz" => undefined in the output. Nothing for xyz will appear at all, hiding the existence of the attribute from the caller.
The read-resource handler can deal with a check in its loop through the AttributeAccess registration for the "no read-handler" case. (This check is already there; an 'else' clause is needed.) If no read-handler, see if there is an entry in the directAttributes map for the attribute; if not, add one with a value of new ModelNode().
--
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, 5 months
[JBoss JIRA] (AS7-5798) Third level navigation back link
by Catherine Robson (JIRA)
[ https://issues.jboss.org/browse/AS7-5798?page=com.atlassian.jira.plugin.s... ]
Catherine Robson commented on AS7-5798:
---------------------------------------
Thanks Heiko, this looks better. I'll resolve.
> Third level navigation back link
> --------------------------------
>
> Key: AS7-5798
> URL: https://issues.jboss.org/browse/AS7-5798
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Console
> Reporter: Heiko Braun
> Assignee: Catherine Robson
> Labels: uxp
> Fix For: 7.2.0.CR1
>
> Attachments: Screen Shot 2012-12-06 at 10.10.07 AM.png, Screen Shot 2012-12-06 at 10.10.15 AM.png
>
>
> Third level navigation shows up under the tabbed second level nav- igation with a back link. The back link should be visually different than the tertiary navigation links to help distinguish the different types of action.
--
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, 5 months
[JBoss JIRA] (AS7-5798) Third level navigation back link
by Catherine Robson (JIRA)
[ https://issues.jboss.org/browse/AS7-5798?page=com.atlassian.jira.plugin.s... ]
Catherine Robson resolved AS7-5798.
-----------------------------------
Resolution: Done
> Third level navigation back link
> --------------------------------
>
> Key: AS7-5798
> URL: https://issues.jboss.org/browse/AS7-5798
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Console
> Reporter: Heiko Braun
> Assignee: Catherine Robson
> Labels: uxp
> Fix For: 7.2.0.CR1
>
> Attachments: Screen Shot 2012-12-06 at 10.10.07 AM.png, Screen Shot 2012-12-06 at 10.10.15 AM.png
>
>
> Third level navigation shows up under the tabbed second level nav- igation with a back link. The back link should be visually different than the tertiary navigation links to help distinguish the different types of action.
--
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, 5 months
[JBoss JIRA] (AS7-6060) naming's :jndi-view operation failing with standalone-full.xml configuration
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/AS7-6060?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil updated AS7-6060:
-----------------------------
Issue Type: Bug (was: Feature Request)
> naming's :jndi-view operation failing with standalone-full.xml configuration
> ----------------------------------------------------------------------------
>
> Key: AS7-6060
> URL: https://issues.jboss.org/browse/AS7-6060
> Project: Application Server 7
> Issue Type: Bug
> Components: Naming
> Reporter: Jeff Mesnil
> Assignee: Eduardo Martins
>
> I noticed this on AS7 master branch.
> If I run the server with the standalone.xml configuration, the /subsystem=naming:jndi-view runs fine.
> However with standalone-full.xml or standalone-full-ha.xml, the operation fails:
> {noformat}
> [standalone@localhost:9999 /] /subsystem=naming:jndi-view
> {
> "outcome" => "failed",
> "result" => {"java: contexts" => {"java:" => {
> "ConnectionFactory" => {
> "class-name" => "org.hornetq.jms.client.HornetQJMSConnectionFactory",
> "value" => "HornetQConnectionFactory [serverLocator=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=in-vm, factory=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory) ?server-id=0], discoveryGroupConfiguration=null], clientID=null, dupsOKBatchSize=1048576, transactionBatchSize=1048576, readOnly=false]"
> },
> "JmsXA" => {
> "class-name" => "java.lang.Object",
> "value" => "?"
> },
> "TransactionManager" => {
> "class-name" => "com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate",
> "value" => "com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate@36bbb8c4"
> },
> "ejb" => {
> "class-name" => "javax.naming.Context",
> "children" => {"mgmt" => {
> "class-name" => "javax.naming.Context",
> "children" => {"MEJB" => {"class-name" => "javax.management.j2ee.ManagementHome"}}
> }}
> }
> }}},
> "failure-description" => "JBAS014749: Operation handler failed: JBAS014487: Could not load view class for ejb EJB",
> "rolled-back" => true
> }
> {noformat}
> with the stack trace on the server-side:
> {noformat}
> 18:16:17,682 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("jndi-view") failed - address: ([("subsystem" => "naming")]): java.lang.RuntimeException: JBAS014487: Could not load view class for ejb EJB
> at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:90)
> at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getJndiViewInstanceValue(RemoteViewManagedReferenceFactory.java:79)
> at org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:144)
> at org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:138)
> at org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:138)
> at org.jboss.as.naming.management.JndiViewOperation.access$000(JndiViewOperation.java:48)
> at org.jboss.as.naming.management.JndiViewOperation$1.execute(JndiViewOperation.java:65)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:439) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:321) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:228) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:223) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:135) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:111) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09-icedtea]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09-icedtea]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
> Caused by: java.lang.ClassNotFoundException: javax.management.j2ee.ManagementHome from [Module "org.jboss.as.naming:main" from local module loader @5cbe930a (roots: /home/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules)]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.3.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.3.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.3.GA]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.3.GA]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.3.GA]
> at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_09-icedtea]
> at java.lang.Class.forName(Class.java:264) [rt.jar:1.7.0_09-icedtea]
> at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:87)
> ... 20 more
> {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, 5 months
[JBoss JIRA] (AS7-6098) Error using jndi view operation
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/AS7-6098?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar updated AS7-6098:
-----------------------------
Issue Type: Bug (was: Feature Request)
Component/s: Naming
> Error using jndi view operation
> -------------------------------
>
> Key: AS7-6098
> URL: https://issues.jboss.org/browse/AS7-6098
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, Naming
> Environment: domain mode
> Reporter: Heiko Braun
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 7.2.0.CR1
>
>
> {noformat}
> [Server:server-one] 14:42:04,306 ERROR [org.jboss.as.controller.management-operation] (host-controller-connection-threads - 1) JBAS014612: Operation ("jndi-view") failed - address: ([("subsystem" => "naming")]): java.lang.RuntimeException: JBAS014487: Could not load view class for ejb EJB
> [Server:server-one] at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:90)
> [Server:server-one] at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getJndiViewInstanceValue(RemoteViewManagedReferenceFactory.java:79)
> [Server:server-one] at org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:144)
> [Server:server-one] at org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:138)
> [Server:server-one] at org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:138)
> [Server:server-one] at org.jboss.as.naming.management.JndiViewOperation.access$000(JndiViewOperation.java:48)
> [Server:server-one] at org.jboss.as.naming.management.JndiViewOperation$1.execute(JndiViewOperation.java:65)
> [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:439) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:321) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:228) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:223) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:136) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:112) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler.doExecute(TransactionalProtocolOperationHandler.java:112) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$1.execute(TransactionalProtocolOperationHandler.java:95) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_37]
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_37]
> [Server:server-one] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37]
> [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
> [Server:server-one] Caused by: java.lang.ClassNotFoundException: javax.management.j2ee.ManagementHome from [Module "org.jboss.as.naming:main" from local module loader @353c375 (roots: /Users/hbraun/dev/prj/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules)]
> [Server:server-one] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at java.lang.Class.forName0(Native Method) [classes.jar:1.6.0_37]
> [Server:server-one] at java.lang.Class.forName(Class.java:247) [classes.jar:1.6.0_37]
> [Server:server-one] at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:87)
> [Server:server-one] ... 20 more
> {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, 5 months
[JBoss JIRA] (AS7-6098) Error using jndi view operation
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-6098?page=com.atlassian.jira.plugin.s... ]
Heiko Braun updated AS7-6098:
-----------------------------
Priority: Critical (was: Major)
> Error using jndi view operation
> -------------------------------
>
> Key: AS7-6098
> URL: https://issues.jboss.org/browse/AS7-6098
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Domain Management
> Environment: domain mode
> Reporter: Heiko Braun
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 7.2.0.CR1
>
>
> {noformat}
> [Server:server-one] 14:42:04,306 ERROR [org.jboss.as.controller.management-operation] (host-controller-connection-threads - 1) JBAS014612: Operation ("jndi-view") failed - address: ([("subsystem" => "naming")]): java.lang.RuntimeException: JBAS014487: Could not load view class for ejb EJB
> [Server:server-one] at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:90)
> [Server:server-one] at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getJndiViewInstanceValue(RemoteViewManagedReferenceFactory.java:79)
> [Server:server-one] at org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:144)
> [Server:server-one] at org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:138)
> [Server:server-one] at org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:138)
> [Server:server-one] at org.jboss.as.naming.management.JndiViewOperation.access$000(JndiViewOperation.java:48)
> [Server:server-one] at org.jboss.as.naming.management.JndiViewOperation$1.execute(JndiViewOperation.java:65)
> [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:439) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:321) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:228) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:223) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:136) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:112) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler.doExecute(TransactionalProtocolOperationHandler.java:112) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$1.execute(TransactionalProtocolOperationHandler.java:95) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_37]
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_37]
> [Server:server-one] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37]
> [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
> [Server:server-one] Caused by: java.lang.ClassNotFoundException: javax.management.j2ee.ManagementHome from [Module "org.jboss.as.naming:main" from local module loader @353c375 (roots: /Users/hbraun/dev/prj/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules)]
> [Server:server-one] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at java.lang.Class.forName0(Native Method) [classes.jar:1.6.0_37]
> [Server:server-one] at java.lang.Class.forName(Class.java:247) [classes.jar:1.6.0_37]
> [Server:server-one] at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:87)
> [Server:server-one] ... 20 more
> {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, 5 months