2:37 p.m.
Console: naming shows nothing if there is an exception getting jndi-view
------------------------------------------------------------------------
Key: AS7-2354
URL: https://issues.jboss.org/browse/AS7-2354
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.Alpha1
Environment: RHEL 6.0 VM
Reporter: Naveen Malik
Assignee: Heiko Braun
I have an EJB3 service converted from EAP 5.1. When I attempt to see the jndi view via
cli or web console it fails. But in the cli the tree is still returned in the failed
output. So the data is still available, but the uncaught exception is causing the console
to display nothing.
./jboss-admin.sh --connect --controller=`hostname`:9999
--command="/subsystem=naming/:jndi-view"
--
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
2:39 p.m.
[
https://issues.jboss.org/browse/AS7-2354?page=com.atlassian.jira.plugin.s...
]
Naveen Malik commented on AS7-2354:
-----------------------------------
19:23:11,842 ERROR [org.jboss.as.controller] (pool-1-thread-23) Operation
("jndi-view") failed - address: ([("subsystem" =>
"naming")]): java.lang.RuntimeException: Could not load view class for ejb
MyEjbBean
at
org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:64)
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:113)
[jboss-as-naming-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.naming.ServiceBasedNamingStore.list(ServiceBasedNamingStore.java:140)
[jboss-as-naming-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.list(NamingContext.java:260)
[jboss-as-naming-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.naming.NamingContext.list(NamingContext.java:276)
[jboss-as-naming-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:113)
[jboss-as-naming-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:122)
[jboss-as-naming-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:122)
[jboss-as-naming-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.naming.management.JndiViewOperation.access$000(JndiViewOperation.java:45)
[jboss-as-naming-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.naming.management.JndiViewOperation$1.execute(JndiViewOperation.java:78)
[jboss-as-naming-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.as.controller.OperationContextImpl.executeStep(OperationContextImpl.java:388)
[jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.as.controller.OperationContextImpl.doCompleteStep(OperationContextImpl.java:287)
[jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.as.controller.OperationContextImpl.completeStep(OperationContextImpl.java:221)
[jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.naming.management.JndiViewOperation.execute(JndiViewOperation.java:109)
[jboss-as-naming-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.as.controller.OperationContextImpl.executeStep(OperationContextImpl.java:388)
[jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.as.controller.OperationContextImpl.doCompleteStep(OperationContextImpl.java:287)
[jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.as.controller.OperationContextImpl.completeStep(OperationContextImpl.java:221)
[jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:371)
[jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.as.controller.OperationContextImpl.executeStep(OperationContextImpl.java:388)
[jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.as.controller.OperationContextImpl.doCompleteStep(OperationContextImpl.java:287)
[jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.as.controller.OperationContextImpl.completeStep(OperationContextImpl.java:221)
[jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:108)
[jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doProcessRequest(ModelControllerClientOperationHandler.java:156)
[jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.processRequest(ModelControllerClientOperationHandler.java:109)
[jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.as.protocol.mgmt.ManagementChannel$RequestReceiver.processRequest(ManagementChannel.java:286)
at
org.jboss.as.protocol.mgmt.ManagementChannel$RequestReceiver.access$500(ManagementChannel.java:260)
at org.jboss.as.protocol.mgmt.ManagementChannel.doHandle(ManagementChannel.java:161)
at org.jboss.as.protocol.ProtocolChannel.handleMessage(ProtocolChannel.java:158)
at
org.jboss.remoting3.remote.RemoteConnectionChannel$4.run(RemoteConnectionChannel.java:224)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[:1.6.0_17]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[:1.6.0_17]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_17]
Caused by: java.lang.ClassNotFoundException: my.ejb.MyEjbRemote from [Module
"org.jboss.as.naming:main" from local module loader @244aeb52 (roots:
/var/lib/jbossas/modules)]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191)
[jboss-modules.jar:1.0.3.GA]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:361)
[jboss-modules.jar:1.0.3.GA]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:333)
[jboss-modules.jar:1.0.3.GA]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:310)
[jboss-modules.jar:1.0.3.GA]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:103)
[jboss-modules.jar:1.0.3.GA]
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:332) [:1.6.0_17]
at java.lang.Class.forName0(Native Method) [:1.6.0_17]
at java.lang.Class.forName(Class.java:264) [:1.6.0_17]
at
org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:62)
... 31 more
Console: naming shows nothing if there is an exception getting
jndi-view
------------------------------------------------------------------------
Key: AS7-2354
URL: https://issues.jboss.org/browse/AS7-2354
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.Alpha1
Environment: RHEL 6.0 VM
Reporter: Naveen Malik
Assignee: Heiko Braun
Labels: eap6-ux
I have an EJB3 service converted from EAP 5.1. When I attempt to see the jndi view via
cli or web console it fails. But in the cli the tree is still returned in the failed
output. So the data is still available, but the uncaught exception is causing the console
to display nothing.
./jboss-admin.sh --connect --controller=`hostname`:9999
--command="/subsystem=naming/:jndi-view"
--
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
2:41 p.m.
[
https://issues.jboss.org/browse/AS7-2354?page=com.atlassian.jira.plugin.s...
]
Naveen Malik updated AS7-2354:
------------------------------
Attachment: empty-jndi-bindings.png
Screen shot in the UI when the exception occurs.
Console: naming shows nothing if there is an exception getting
jndi-view
------------------------------------------------------------------------
Key: AS7-2354
URL: https://issues.jboss.org/browse/AS7-2354
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.Alpha1
Environment: RHEL 6.0 VM
Reporter: Naveen Malik
Assignee: Heiko Braun
Labels: eap6-ux
Attachments: empty-jndi-bindings.png
I have an EJB3 service converted from EAP 5.1. When I attempt to see the jndi view via
cli or web console it fails. But in the cli the tree is still returned in the failed
output. So the data is still available, but the uncaught exception is causing the console
to display nothing.
./jboss-admin.sh --connect --controller=`hostname`:9999
--command="/subsystem=naming/:jndi-view"
--
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
5:21 a.m.
[
https://issues.jboss.org/browse/AS7-2354?page=com.atlassian.jira.plugin.s...
]
Heiko Braun updated AS7-2354:
-----------------------------
Fix Version/s: No Release
Console: naming shows nothing if there is an exception getting
jndi-view
------------------------------------------------------------------------
Key: AS7-2354
URL: https://issues.jboss.org/browse/AS7-2354
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.Alpha1
Environment: RHEL 6.0 VM
Reporter: Naveen Malik
Assignee: Heiko Braun
Labels: eap6-ux
Fix For: No Release
Attachments: empty-jndi-bindings.png
I have an EJB3 service converted from EAP 5.1. When I attempt to see the jndi view via
cli or web console it fails. But in the cli the tree is still returned in the failed
output. So the data is still available, but the uncaught exception is causing the console
to display nothing.
./jboss-admin.sh --connect --controller=`hostname`:9999
--command="/subsystem=naming/:jndi-view"
--
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
5:23 a.m.
[
https://issues.jboss.org/browse/AS7-2354?page=com.atlassian.jira.plugin.s...
]
Heiko Braun updated AS7-2354:
-----------------------------
Fix Version/s: (was: No Release)
Console: naming shows nothing if there is an exception getting
jndi-view
------------------------------------------------------------------------
Key: AS7-2354
URL: https://issues.jboss.org/browse/AS7-2354
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.Alpha1
Environment: RHEL 6.0 VM
Reporter: Naveen Malik
Assignee: Heiko Braun
Labels: eap6-ux
Attachments: empty-jndi-bindings.png
I have an EJB3 service converted from EAP 5.1. When I attempt to see the jndi view via
cli or web console it fails. But in the cli the tree is still returned in the failed
output. So the data is still available, but the uncaught exception is causing the console
to display nothing.
./jboss-admin.sh --connect --controller=`hostname`:9999
--command="/subsystem=naming/:jndi-view"
--
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
5:35 a.m.
[
https://issues.jboss.org/browse/AS7-2354?page=com.atlassian.jira.plugin.s...
]
Heiko Braun commented on AS7-2354:
----------------------------------
Can you attach the deployment that creates the error?
Console: naming shows nothing if there is an exception getting
jndi-view
------------------------------------------------------------------------
Key: AS7-2354
URL: https://issues.jboss.org/browse/AS7-2354
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.Alpha1
Environment: RHEL 6.0 VM
Reporter: Naveen Malik
Assignee: Heiko Braun
Labels: eap6-ux
Attachments: empty-jndi-bindings.png
I have an EJB3 service converted from EAP 5.1. When I attempt to see the jndi view via
cli or web console it fails. But in the cli the tree is still returned in the failed
output. So the data is still available, but the uncaught exception is causing the console
to display nothing.
./jboss-admin.sh --connect --controller=`hostname`:9999
--command="/subsystem=naming/:jndi-view"
--
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
12:28 p.m.
[
https://issues.jboss.org/browse/AS7-2354?page=com.atlassian.jira.plugin.s...
]
Naveen Malik commented on AS7-2354:
-----------------------------------
I don't have that deployment available anymore. It's not likely I'll have
time to reproduce it for a while, but I'll post the deployment if I have the time.
Console: naming shows nothing if there is an exception getting
jndi-view
------------------------------------------------------------------------
Key: AS7-2354
URL: https://issues.jboss.org/browse/AS7-2354
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.Alpha1
Environment: RHEL 6.0 VM
Reporter: Naveen Malik
Assignee: Heiko Braun
Labels: eap6-ux
Attachments: empty-jndi-bindings.png
I have an EJB3 service converted from EAP 5.1. When I attempt to see the jndi view via
cli or web console it fails. But in the cli the tree is still returned in the failed
output. So the data is still available, but the uncaught exception is causing the console
to display nothing.
./jboss-admin.sh --connect --controller=`hostname`:9999
--command="/subsystem=naming/:jndi-view"
--
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
2:58 p.m.
[
https://issues.jboss.org/browse/AS7-2354?page=com.atlassian.jira.plugin.s...
]
Stian Thorgersen commented on AS7-2354:
---------------------------------------
This seems to be related to my issue: http://community.jboss.org/thread/176868
Console: naming shows nothing if there is an exception getting
jndi-view
------------------------------------------------------------------------
Key: AS7-2354
URL: https://issues.jboss.org/browse/AS7-2354
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.Alpha1
Environment: RHEL 6.0 VM
Reporter: Naveen Malik
Assignee: Heiko Braun
Labels: eap6-ux
Attachments: empty-jndi-bindings.png
I have an EJB3 service converted from EAP 5.1. When I attempt to see the jndi view via
cli or web console it fails. But in the cli the tree is still returned in the failed
output. So the data is still available, but the uncaught exception is causing the console
to display nothing.
./jboss-admin.sh --connect --controller=`hostname`:9999
--command="/subsystem=naming/:jndi-view"
--
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
3 p.m.
[
https://issues.jboss.org/browse/AS7-2354?page=com.atlassian.jira.plugin.s...
]
Stian Thorgersen edited comment on AS7-2354 at 1/3/12 3:58 PM:
---------------------------------------------------------------
This seems to be related to my issue: http://community.jboss.org/thread/176868. However, I
got output for other deployments, just not the deployment with a remote bean in it.
was (Author: stianst):
This seems to be related to my issue: http://community.jboss.org/thread/176868
Console: naming shows nothing if there is an exception getting
jndi-view
------------------------------------------------------------------------
Key: AS7-2354
URL: https://issues.jboss.org/browse/AS7-2354
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.Alpha1
Environment: RHEL 6.0 VM
Reporter: Naveen Malik
Assignee: Heiko Braun
Labels: eap6-ux
Attachments: empty-jndi-bindings.png
I have an EJB3 service converted from EAP 5.1. When I attempt to see the jndi view via
cli or web console it fails. But in the cli the tree is still returned in the failed
output. So the data is still available, but the uncaught exception is causing the console
to display nothing.
./jboss-admin.sh --connect --controller=`hostname`:9999
--command="/subsystem=naming/:jndi-view"
--
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
7:29 a.m.
[
https://issues.jboss.org/browse/AS7-2354?page=com.atlassian.jira.plugin.s...
]
Heiko Braun resolved AS7-2354.
------------------------------
Resolution: Out of Date
Console: naming shows nothing if there is an exception getting
jndi-view
------------------------------------------------------------------------
Key: AS7-2354
URL: https://issues.jboss.org/browse/AS7-2354
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.Alpha1
Environment: RHEL 6.0 VM
Reporter: Naveen Malik
Assignee: Heiko Braun
Labels: eap6-ux
Attachments: empty-jndi-bindings.png
I have an EJB3 service converted from EAP 5.1. When I attempt to see the jndi view via
cli or web console it fails. But in the cli the tree is still returned in the failed
output. So the data is still available, but the uncaught exception is causing the console
to display nothing.
./jboss-admin.sh --connect --controller=`hostname`:9999
--command="/subsystem=naming/:jndi-view"
--
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
4632
days inactive
4826
days old
9 comments
8 participants
participants (8)
-
Heiko Braun (Commented) (JIRA) -
Heiko Braun (JIRA)
-
Heiko Braun (Updated) (JIRA)
-
Naveen Malik (Commented) (JIRA)
-
Naveen Malik (Created) (JIRA)
-
Naveen Malik (Updated) (JIRA)
-
Stian Thorgersen (Commented) (JIRA)
-
Stian Thorgersen (Issue Comment Edited) (JIRA)