[
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