Bug 17431 – browseagelimit not sent in serverstatus

Bug 17431 - browseagelimit not sent in serverstatus

Summary:

browseagelimit not sent in serverstatus

Status:	NEW

Product:	Logitech Media Server
Classification:	Unclassified
Component:	CLI
Version:	7.6.0
Platform:	PC Other

Importance:	-- normal (vote)
Target Milestone:	---
Assigned To:	Unassigned bug - please assign me!

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-08-10 10:42 UTC by Joerg Schwieder
Modified:	2011-08-10 13:55 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

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

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

Description Joerg Schwieder 2011-08-10 10:42:37 UTC

In 7.6.1 the "browseagelimit" setting is no longer being sent in the server status when requested.

Comment 1 Michael Herger 2011-08-10 11:47:35 UTC

I grepped all of 7.5 and didn't find it being accessed anywhere but in the albums etc. queries. Are you sure this has ever been there?

Comment 2 Joerg Schwieder 2011-08-10 12:35:31 UTC

Definitely. I can see it being delivered with serverstatus in 7.5.5
I'm explicitly requesting it with the serverstatus subscription, maybe it's being piped through?

Comment 3 Michael Herger 2011-08-10 12:58:28 UTC

could you please post some log with network.cometd enabled?

Comment 4 Joerg Schwieder 2011-08-10 13:55:06 UTC

Hm.... Actually NOW I'm seeing it even in 7.6.1...
What I did is restart the server.

I DID try this at least a dozen times this afternoon and it wasn't there. No idea what triggered the change. Plus I have debug code in iPeng it only runs into when it'S not there.
Could it be that it doesn't show up unless it's not showing the default value (100)?
I did restart the server to update a few plugins in the meantime, could this somehow lock up?

Will keep an eye on it.
Sorry.