]
Heiko Braun commented on AS7-6060:
----------------------------------
yes, works.
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
Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
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: