Bug 1139202 - [QE] (6.4.0) Long server shut-dow with unresponsive client with opened JNDI Context
Summary: [QE] (6.4.0) Long server shut-dow with unresponsive client with opened JNDI C...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Remoting
Version: 6.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: DR9
: EAP 6.4.0
Assignee: Enrique Gonzalez Martinez
QA Contact: Jitka Kozana
URL:
Whiteboard:
Depends On:
Blocks: 1139197 1149618 1149623
TreeView+ depends on / blocked
 
Reported: 2014-09-08 11:36 UTC by Miroslav Novak
Modified: 2019-08-19 12:42 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1139197
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)
JNDIContext.java (1.84 KB, text/plain)
2014-09-08 11:36 UTC, Miroslav Novak 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker REM3-194 0 Major Resolved Long server shut-dow with unresponsive client with opened JNDI Context 2017-06-08 10:15:13 UTC

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
Note You need to log in before you can comment on or make changes to this bug.