Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1139202

Summary: [QE] (6.4.0) Long server shut-dow with unresponsive client with opened JNDI Context
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Miroslav Novak <mnovak>
Component: RemotingAssignee: Enrique Gonzalez Martinez <egonzale>
Status: CLOSED CURRENTRELEASE QA Contact: Jitka Kozana <jkudrnac>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.1CC: david.lloyd, egonzale, istudens, jkudrnac, kkhan
Target Milestone: DR9   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1139197 Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1139197, 1149618, 1149623    
Attachments:
Description Flags
JNDIContext.java none

Description Miroslav Novak 2014-09-08 11:36:15 UTC 
+++ This bug was initially created as a clone of Bug #1139197 +++

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.

--- Additional comment from Miroslav Novak on 2014-09-08 07:21:13 EDT ---
Comment 1 Miroslav Novak 2014-09-08 11:36:44 UTC 
Created attachment 935308 [details]
JNDIContext.java
Comment 2 Kabir Khan 2014-11-07 13:53:15 UTC 
Should be solved by remoting 3.3.4 upgrade
Comment 3 Ondřej Kalman 2014-11-14 15:19:19 UTC 
Verified with EAP 6.4.0.DR9