Bug 454592 - zabbix - fix for jabber sender
Summary: zabbix - fix for jabber sender
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: zabbix
Version: el4
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Dan Horák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-09 07:07 UTC by albert
Modified: 2008-07-22 11:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-22 11:48:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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.


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