Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 454592

Summary: zabbix - fix for jabber sender
Product: [Fedora] Fedora EPEL Reporter: albert <superber>
Component: zabbixAssignee: Dan Horák <dan>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: el4CC: dan, jeff
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-07-22 11:48:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description albert 2008-07-09 07:07:41 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; es-ES; rv:1.8.0.14eol) Gecko/20070505 Iceape/1.0.9 (Debian-1.0.13~pre080323b-0etch3)

Description of problem:
Some jabber servers close client connection by timeout (openfire for example). Zabbix does not reconnect with these servers. This bug persists in zabbix 1.4.5.
Patch is available at
http://www.zabbix.com/forum/showthread.php?t=7391&highlight=openfire

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


How reproducible:
Always


Steps to Reproduce:
1.Start openfire an zabbix server
2.Waith ten minutes
3.No more jabber notifications

Actual Results:


Expected Results:


Additional info:

Comment 1 Dan Horák 2008-07-09 07:43:07 UTC
The patch presented in the thread is a hack, not a solution. Opening and closing
the connection for each message is bad. I think a bug report at
http://support.zabbix.com (but it's not working now) would be required to
properly discuss the issue with upstream.