[
https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s...
]
Ed Keen commented on AS7-1338:
------------------------------
@Jason, yes I have a java test class that drops one message on a queue and then
terminates. So you are correct that I am creating a new process/VM for each message. I
modified my test to send 3 messages instead of one. The test basically sends a text
message and the listener logs what was received. So now sending it 3 times within the
same JVM, my log file looks like this. You can see that the 3 messages are received, but
at the end, I get 3 error messages now instead of one:
{code}
13:13:46,051 INFO [stdout] Received message: hello world
13:13:46,114 INFO [stdout] Received message: hello again
13:13:46,176 INFO [stdout] Received message: hello again2
13:13:46,614 ERROR [org.jboss.remoting.remote] JBREM000200: Remote connection failed:
java.io.IOException: An existing connection was forcibly closed by the remote host
13:13:46,614 ERROR [org.jboss.remoting.remote] JBREM000200: Remote connection failed:
java.io.IOException: An existing connection was forcibly closed by the remote host
13:13:46,614 ERROR [org.jboss.remoting.remote] JBREM000200: Remote connection failed:
java.io.IOException: An existing connection was forcibly closed by the remote host
13:13:46,614 INFO [org.jboss.as.naming] JBAS011806: Channel end notification received,
closing channel Channel ID 5ac36493 (inbound) of Remoting connection 01feee93 to null
13:13:46,629 INFO [org.jboss.as.naming] JBAS011806: Channel end notification received,
closing channel Channel ID 18098326 (inbound) of Remoting connection 009bdb78 to null
13:13:46,629 INFO [org.jboss.as.naming] JBAS011806: Channel end notification received,
closing channel Channel ID 6ab1a53c (inbound) of Remoting connection 0065c572 to null
{code}
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