Bug 1117364 – Setting "Socket Timeout" or "Stop Context Timeout" to 0 in mod_cluster configuration yields "Unknown error"

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1117364 - Setting "Socket Timeout" or "Stop Context Timeout" to 0 in mod_cluster configuration yields "Unknown error"

Summary:	Setting "Socket Timeout" or "Stop Context Timeout" to 0 in mod_cluster config...

Status:	VERIFIED

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	Web Console (Show other bugs)
Sub Component:
Version:	6.3.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity medium
Target Milestone:	DR9
Target Release:	EAP 6.4.0
Assigned To:	Heiko Braun
QA Contact:	Pavel Jelinek
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1161042
	Show dependency tree / graph

Reported:	2014-07-08 10:13 EDT by Martin Velas
Modified:	2017-10-09 20:21 EDT (History)
CC List:	10 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	HAL-449	Major	Resolved	Setting "Socket Timeout" or "Stop Context Timeout" to 0 in mod_cluster configuration yields "Unknown error"	2017-11-15 10:44 EST

Groups: None (edit)

Description Martin Velas 2014-07-08 10:13:08 EDT

Description of problem:
Setting "Socket Timeout" or "Stop Context Timeout" to 0 in mod_cluster configuration yields "Unknown error"

Version-Release number of selected component (if applicable):
6.3.0.ER9

How reproducible:
always

Steps to Reproduce:
1. start EAP server in standalone-full-ha
2. go to http://localhost:9990/console/App.html#modcluster
3. set "Socket Timeout" or "Stop Context Timeout" in "Networking" tab to 0

Actual results:
Unknown error message

Expected results:
Explanation/warning of invalid setting.

Comment 1 Martin Velas 2014-07-08 10:27:03 EDT

Also zero value should be valid for "Stop Context Timeout" ( => no timeout).

Comment 2 Michal Karm Babacek 2014-07-08 10:42:15 EDT

comment 1 is invalid, it's actually O.K. for Stop Context Timeout not to allow 0 as a value. Explanation: It would be meaningless, because if one doesn't want to wait, then one should use session-draining-strategy="NEVER" for that purpose.

It is my fault that Martin made comment 1, I supplied him with misleading information.

Comment 3 JBoss JIRA Server 2014-07-10 08:15:55 EDT

Harald Pehl <hpehl@redhat.com> updated the status of jira HAL-449 to Coding In Progress

Comment 4 JBoss JIRA Server 2014-07-11 04:51:12 EDT

Harald Pehl <hpehl@redhat.com> updated the status of jira HAL-449 to Resolved

Comment 5 Harald Pehl 2014-09-23 03:32:03 EDT

Fixed by HAL 2.4.0.Final BZ 1144083. Setting to MODIFIED

Comment 6 Jakub Cechacek 2014-09-29 05:47:20 EDT

Error message is not displayed anymore. However the configuration is not saved.

Comment 7 Jakub Cechacek 2014-09-29 05:47:30 EDT

Error message is not displayed anymore. However the configuration is not saved.

Comment 8 Heiko Braun 2014-10-08 02:46:09 EDT

Works for me Jakub, can you double check?

Comment 9 Jakub Cechacek 2014-10-09 04:20:30 EDT

1) I misunderstood the initial report (as I wasn't the reporter) and though that 0 is valid value -- it is not.

2) This makes me believe that the initial issue was in fact complaining about the "Unknown Error" title which is quite confusing but common in console (see BZ1027303). However the error description found in the body of dmr error was accurate [1]

3) Consequently this "fix" introduced a bug -- when setting invalid value in mod cluster configuration, there is no error displayed in console. 



[1] http://pastebin.test.redhat.com/238957

Comment 13 Michal Karm Babacek 2014-10-27 11:24:06 EDT

/me Fixed flags and the component for better tracking.

Comment 17 JBoss JIRA Server 2014-11-04 06:59:18 EST

Heiko Braun <ike.braun@googlemail.com> updated the status of jira HAL-449 to Reopened

Comment 18 JBoss JIRA Server 2014-11-05 04:00:53 EST

Heiko Braun <ike.braun@googlemail.com> updated the status of jira HAL-449 to Resolved

Comment 19 Jakub Cechacek 2014-11-13 07:23:40 EST

Verified 6.4.0.DR9

Note You need to log in before you can comment on or make changes to this bug.