[asterisk-bugs] [JIRA] (ASTERISK-25665) Duplicate logging in queue log for EXITEMPTY events

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-25665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=228875#comment-228875 ] 

Asterisk Team commented on ASTERISK-25665:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> Duplicate logging in queue log for EXITEMPTY events
> ---------------------------------------------------
>
>                 Key: ASTERISK-25665
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25665
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 1.8.32.3
>            Reporter: Ove Aursand
>            Severity: Minor
>
> How to reproduce:
> Create a queue without members and place a call in the queue. The queue needs "leavewhenempty" set to yes.
> Generates something like this in the log:
> 1452163740|1452163738.3|que0120550|NONE|ENTERQUEUE||+4721074800|1
> 1452163740|1452163738.3|que0120550|NONE|EXITEMPTY|1|1|0
> 1452163740|1452163738.3|que0120550|NONE|EXITEMPTY|1|1|0
> ast_log for EXITEMPTY is called in queue_exec and also wait_our_turn. To me it looks like it's the same issue in the source code for 13.6.0 as well, but I haven't tested on that version.
> Removing the ast_log line in wait_our_turn fixed the issue for me.



--
This message was sent by Atlassian JIRA
(v6.2#6252)