[
https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s...
]
Himanshu Gupta commented on AS7-1338:
-------------------------------------
Hi,
Can someone please summarize what is the final resolution for this bug?
As I understand from the bug, "JBAS011806: Channel end notification received,
closing channel Channel ID 72d0f3d7 (inbound) of Remoting connection 67ffa9c7 to
null" - this message in logs is fine and will come on Windows and currently no way to
suppress it for this OS.
We are testing with JBoss 7.1.1.Final and see this message at INFO level in JBoss
console. Also it seems that this statememnt is logged via System.err.println also from
code.
We just need to know what is the final stance on this one.
Thanks,
Himanshu
Remote JNDI support for AS7
---------------------------
Key: AS7-1338
URL:
https://issues.jboss.org/browse/AS7-1338
Project: Application Server 7
Issue Type: Task
Components: Naming
Reporter: Richard Opalka
Assignee: John Bailey
Priority: Critical
Labels: eap6_prd_req
Fix For: 7.1.0.Final
Add support for remote JNDI after all. It was agreed that:
* Remote JNDI would run over Remoting
* Remote JNDI for EJB is strictly a legacy access protocol, deprecated in favor of
"ejb:"
* The Remote JNDI service would proxy to a specific Context of the server JNDI tree -
maybe "java:jboss/shared", maybe something else
* Server-side services would opt-in to Remote JNDI; initially we'd only support:
** Remote EJB interfaces
** HornetQ connection factories
* In the future we may support:
** User bindings, so long as they're serializable
* In the future we will never support:
** Proxied DataSources
** Proxied JMS invocations
Initial project tree is at
https://github.com/dmlloyd/jboss-remote-jndi for now.
--
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