[jboss-jira] [JBoss JIRA] (AS7-4508) Auto reconnect for remote-naming

Mon May 14 01:54:17 EDT 2012

    [ https://issues.jboss.org/browse/AS7-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12692506#comment-12692506 ] 

jaikiran pai commented on AS7-4508:
-----------------------------------

I don't see HaRemoteNamingStore being (properly) cached and that's what I was going to fix. There's a bug in NamingStoreCache where the connection which gets passed to the CacheEntry for a HaRemoteNamingStore is null.

> 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