[jboss-jira] [JBoss JIRA] (AS7-4508) Auto reconnect for remote-naming
Sueleyman Vurucu (JIRA)
jira-events at lists.jboss.org
Wed May 16 05:44:18 EDT 2012
[ https://issues.jboss.org/browse/AS7-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693189#comment-12693189 ]
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>
...
> 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
> Fix For: 7.2.0.Alpha1
>
>
> 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
More information about the jboss-jira
mailing list