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

Bug 1117364

Summary:	Setting "Socket Timeout" or "Stop Context Timeout" to 0 in mod_cluster configuration yields "Unknown error"
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Martin Velas <mvelas>
Component:	Web Console	Assignee:	Heiko Braun <hbraun>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Jelinek <pjelinek>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	bperkins, brian.stansberry, hbraun, hpehl, jkudrnac, kkhan, mbabacek, pjelinek, pslavice, rhusar
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:		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:	1161042

Description Martin Velas 2014-07-08 14:13:08 UTC

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 14:27:03 UTC

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

Comment 2 Michal Karm Babacek 2014-07-08 14:42:15 UTC

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 12:15:55 UTC

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

Comment 4 JBoss JIRA Server 2014-07-11 08:51:12 UTC

Harald Pehl <hpehl> updated the status of jira HAL-449 to Resolved

Comment 5 Harald Pehl 2014-09-23 07:32:03 UTC

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

Comment 6 Jakub Cechacek 2014-09-29 09:47:20 UTC

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

Comment 7 Jakub Cechacek 2014-09-29 09:47:30 UTC

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

Comment 8 Heiko Braun 2014-10-08 06:46:09 UTC

Works for me Jakub, can you double check?

Comment 9 Jakub Cechacek 2014-10-09 08:20:30 UTC

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 15:24:06 UTC

/me Fixed flags and the component for better tracking.

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

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

Comment 18 JBoss JIRA Server 2014-11-05 09:00:53 UTC

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

Comment 19 Jakub Cechacek 2014-11-13 12:23:40 UTC

Verified 6.4.0.DR9