[
https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s...
]
Ed Keen commented on AS7-1338:
------------------------------
I have followed these instructions and have successfully sent a remote message. However,
after each message, I see the following logs on the server. Is there something else I
need to do?
ERROR [org.jboss.remoting.remote] JBREM000200: Remote connection failed:
java.io.IOException: An existing connection was forcibly closed by the remote host
INFO [org.jboss.as.naming] JBAS011806: Channel end notification received, closing channel
Channel ID 58ff39c8 (inbound) of Remoting connection 01889fce to null
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