[
https://issues.jboss.org/browse/AS7-4508?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-4508:
-----------------------------------
Yeah, I noticed that part while looking at the code although I didn't mention that as
a workaround to the user since it really looked like something that happens to work but
probably wasn't intended that way (should we be ignoring duplicate URLs in that comma
separated list?). The other thing that I'm working as part of this change is to
cleanup HaRemotingNamingStore a bit to make sure that it uses the NamingStoreCache so that
appropriate cleanup of channel and connection takes place whenever necessary.
Auto reconnect for remote-naming
--------------------------------
Key: AS7-4508
URL:
https://issues.jboss.org/browse/AS7-4508
Project: Application Server 7
Issue Type: Feature Request
Components: Naming, Remoting
Affects Versions: 7.1.1.Final
Reporter: Yves Peter
Assignee: jaikiran pai
After restarting a JBoss 7 Server all remote jndi clients should automatically and
transparently reconnect to the the server. For some clients this means that they also have
to be restarted before they work again.
At the moment, trying to look something up after a server restart throws this error:
Caused by: org.jboss.remoting3.NotOpenException: Writes closed
at
org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:107)
at
org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:296)
at org.jboss.naming.remote.protocol.v1.WriteUtil.write(WriteUtil.java:59)
at org.jboss.naming.remote.protocol.v1.Protocol$1.execute(Protocol.java:76)
... 16 more
See forum threat for details.
--
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