[jboss-jira] [JBoss JIRA] (WFCORE-112) Long server shut-dow with unresponsive client with opened JNDI Context
Enrique González Martínez (JIRA)
issues at jboss.org
Wed Sep 17 09:23:02 EDT 2014
[ https://issues.jboss.org/browse/WFCORE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003464#comment-13003464 ]
Enrique González Martínez commented on WFCORE-112:
--------------------------------------------------
The problem is that the container is waiting the remoting component to shut down. This is not happening because the opened connection has been broken and it's not possible to close it normally. The OS closes the socket (triggered by a timeout - 15 min). After that, the EndpointService signals the server as complete and the server shuts down completely.
The test case attached uses the component only and it shows the same behavior.
> Long server shut-dow with unresponsive client with opened JNDI Context
> ----------------------------------------------------------------------
>
> Key: WFCORE-112
> URL: https://issues.jboss.org/browse/WFCORE-112
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Miroslav Novak
> Assignee: David Lloyd
> Attachments: JNDIContext.java, testcase.zip
>
>
> Description of problem:
> If client with opened JNDI context is disconnected from network, then clean shutdown (ctrl-c) of server takes 15 minutes.
> This scenario takes place, when network connections is lost between JMS clients with JNDI context and server.
> Version-Release number of selected component (if applicable):
> jboss-remoting-3.3.3.Final-redhat-1.jar
> How reproducible:
> always
> Steps to Reproduce:
> 1. Start EAP 6.3.1.CP.CR1 on first machine
> 2. Start client which creates JNDI context on second machine (use attached JNDIContext.java)
> 3. Disconnect network between client and server
> 4. Try to cleanly shutdown EAP 6.3.1.CP.CR1 server (by ctrl-c)
> Actual results:
> It takes 15 minutes for server to shutdown.
> Expected results:
> Server should shutdown almost immediately.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
More information about the jboss-jira
mailing list