[ https://issues.jboss.org/browse/AS7-4508?page=com.atlassian.jira.plugin.s... ] Yves Peter updated AS7-4508: ---------------------------- Description: 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. was: After restarting a JBoss 7 Server all remote jndi clients should automatically and transparently reconnect to the the server. At the moment, trying to look something up after a 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. Forum Reference: https://community.jboss.org/message/729775#729775 (was: https://community.jboss.org/message/729775#729775) -- 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

[ https://issues.jboss.org/browse/AS7-4508?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-4508: ----------------------------------- I see that there are more than a couple of users who have been asking for this feature. I'll assign this to myself and start work on this. This is something similar to what we did with EJB client reconnect feature. -- 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

[ 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. -- 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

[ https://issues.jboss.org/browse/AS7-4508?page=com.atlassian.jira.plugin.s... ] Stuart Douglas commented on AS7-4508: ------------------------------------- I don't think the HaRemoteNamingStore should use the naming store cache, as the HaRemoteNamingStore are themselves cached, so an extra level of caching would just add more complexity with no benefit IMHO. -- 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

[ https://issues.jboss.org/browse/AS7-4508?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-4508: ----------------------------------- Pull request sent to upstream remote-naming project https://github.com/jbossas/jboss-remote-naming/pull/8 -- 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

[ https://issues.jboss.org/browse/AS7-4508?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-4508: ----------------------------------- Whenever a new release of remote-naming project is done and integrated into AS7 upstream this should be available. In the meantime, if you want to test it out then you can use this 1.0.4.Final-SNAPSHOT version of jboss-remote-naming jar https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... in your client classpath. -- 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

[ https://issues.jboss.org/browse/AS7-4508?page=com.atlassian.jira.plugin.s... ] Sueleyman Vurucu commented on AS7-4508: --------------------------------------- Hi jaikiran, thanks for work. Modifying the client pom like shown below works too. I assume that will be inculde in the 7.1.3.Final EAP Tag. Will be this build publish in http://www.jboss.org/jbossas/downloads/ ?? Beacause 7.1.2.Final doesn't. ... <dependency> <groupId>org.jboss.as</groupId> <artifactId>jboss-as-ejb-client-bom</artifactId> <type>pom</type> <exclusions> <groupId>org.jboss</groupId> <artifactId>jboss-remote-naming</artifactId> </exclusions> </dependency> <dependency> <groupId>org.jboss</groupId> <artifactId>jboss-remote-naming</artifactId> <version>1.0.4.Final-SNAPSHOT</version> </dependency> ... -- 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

[ https://issues.jboss.org/browse/AS7-4508?page=com.atlassian.jira.plugin.s... ] Stuart Douglas updated AS7-4508: -------------------------------- Fix Version/s: 7.1.3.Final (EAP) Git Pull Request: https://github.com/jbossas/jboss-remote-naming/pull/8 (was: https://github.com/jbossas/jboss-remote-naming/pull/8) Forum Reference: https://community.jboss.org/message/729775#729775 (was: https://community.jboss.org/message/729775#729775) -- 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