[slscripters] New Inventory Send Rate Throttle?

[Fred Allandale]

I sell a mailing list kiosk that sends items such as newsletters and gifts to a list of subscribers.  This product has been fielded for several years, but this week a new problem was brought to my attention by two different long time users.  They got the following message when sending inventory items (using llGiveInventory) to a list of subscribers.  “"Second Life: Objects you own in <region name> have sent out excessive inventory and their offers have been temporarily deactivated. The last inventory offer sent was from <object name>.”  Neither had ever seen this message before and they have been using this system for over two years.  Is anyone aware of some new limits on inventory item send rates that has been changed in the past couple of weeks?  I am aware of the limit on llInstantMessage of 5000 per hour, but I am not aware of any similar limits on llGiveInventory, nor have I been able to locate any reference to send rate limits in the LSL Portal or JIRA.  I use multiple scripts to send items to the list of subscribers as rapidly as possible (a maximum rate of about 10 per second) and have never had it throttled before.  I’ve got about 1500 of these systems fielded so I am concerned that some recent SL change has broken them.

[Nexii Malthus]

This is quite concerning considering I'm trying to start up my own products as well that may at uncommon times have to chew through sending mass product updates. At least I can very easily handle telling customers to simple shift-drag their servers to scale up their system to the load balancing mechanisms, but others may not be so fortunate.

It might be best if we bring this up on Monday at the simulator scripting user group --  https://wiki.secondlife.com/wiki/Simulator_User_Group

- Nexii Malthus

On Thu, Jan 26, 2012 at 4:11 AM, Fred Allandale <Fred_Al...@msn.com> wrote:

I sell a mailing list kiosk that sends items such as newsletters and gifts to a list of subscribers.  This product has been fielded for several years, but this week a new problem was brought to my attention by two different long time users.  They got the following message when sending inventory items (using llGiveInventory) to a list of subscribers.  “"Second Life: Objects you own in <region name> have sent out excessive inventory and their offers have been temporarily deactivated. The last inventory offer sent was from <object name>.”  Neither had ever seen this message before and they have been using this system for over two years.  Is anyone aware of some new limits on inventory item send rates that has been changed in the past couple of weeks?  I am aware of the limit on llInstantMessage of 5000 per hour, but I am not aware of any similar limits on llGiveInventory, nor have I been able to locate any reference to send rate limits in the LSL Portal or JIRA.  I use multiple scripts to send items to the list of subscribers as rapidly as possible (a maximum rate of about 10 per second) and have never had it throttled before.  I’ve got about 1500 of these systems fielded so I am concerned that some recent SL change has broken them.

_______________________________________________
Click here to unsubscribe or manage your list subscription:
https://lists.secondlife.com/cgi-bin/mailman/listinfo/secondlifescripters

[Fred Allandale]

Thanks Nexii.  I won’t be able to attend the user group but would be happy if you bring it up.  At this point, I’m not sure if it is unique to just a couple of my customers, or if there was some recent server change that is going to eventually affect more customers. I’ve only gotten two reports of this problem, but it started for both of them right after the last server update.  I’m not sure which server version they are running but I will try to find out. I can/will, of course, throttle my inventory send rate if necessary, but without knowing the rules, I don’t know how far to throttle it and I don’t want to slow down the sending any more than I have to.

 

-Fred

[Stickman]

> It might be best if we bring this up on Monday at the simulator scripting
> user group --  https://wiki.secondlife.com/wiki/Simulator_User_Group

Kelly shows up to the Friday server office hours at 4pm in Denby.
Sooner than Monday.

Can also try IMing him directly, Kelly Linden. But sending an email
would probably be best. ke...@lindenlab.com

He does watch this mailing list, though. So he probably just hasn't
had time to reply yet.

Stickman

[Kadah]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I was planning to bring this up at Friday's meeting if I'm able to attend.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPIaTFAAoJEIdLfPRu7qE2GD4IALonooIW46aBEDu9FYw/aFm4
bdwSH5QxZ1IoiYoecJOHAZiKwAyJA/5nWqFl4DsHZ5mh3i/nZM2ghhLdAjavei0J
9L6MVQTa8opX+QzDQV+Ggz49rtrEo51tiGG6d5ouewwTzn0KcNTaCdSvbpvrvVE4
TCBMJbuPjk/UkQDM4ZrZqNv3qiQQNjzM8Iv+TNFipknGrV+fB3Sx29X9IE8KT3VG
kDAHi1zIRt8My3Vs7mu6vFXpPm02js9lfIwzM0tdGRnp12ZoM8oP/YuHDACbtYyI
4fjlBdn58LuP6vH7f+99eSgGtXGqaahwMXapieipTBr0clt2XFSI1/t/98au1/w=
=9Ufv
-----END PGP SIGNATURE-----

[Fred Allandale]

FWIW, both reports of this problem were from Second Life RC Magnum
12.01.24.248357. One of the customers tried it from a different sim (don't
know which sim version) and had no problems.

-Fred Allandale

[Stickman]

On Thu, Jan 26, 2012 at 11:55 AM, Fred Allandale <Fred_Al...@msn.com> wrote:
> FWIW, both reports of this problem were from Second Life RC Magnum
> 12.01.24.248357.  One of the customers tried it from a different sim (don't
> know which sim version) and had no problems.

Fred,

For what it's worth, that's worth a lot.

http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_Magnum/12#12.01.24.248357

Nothing visible on the surface. Could try digging deeper into the
listed Jiras and see if they explain something more.

It's probably one of those invisible security fixes. They don't tell
you about them before they're live. And they don't tell you about them
afterwards, either. But if you point out that it breaks existing
content, they'll change the fix not to if they can.

Stickman

[Kadah]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I brought this up at the Beta server UG and Oskar isn't aware of any
changes to llGiveInventory but asked for a jira to be filed on it.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPIeBjAAoJEIdLfPRu7qE2X9YIAKjhUTAxWmk0Bak5hunvjVcf
Jv2geMAA/09UlQHiC6Yy9njqVW2MR9J5rrZIdvLBbPMsMdM+doztY4HFMFkUVPrd
XcTgiw9/rBfuDpoeD9yRgBeWIrlt98lTi8jFIBdBFU/YkXrQ//iFtGt0jQgxeLZd
Sy5A3W1iPf9KphxV3Lu7Gm4ft3X7HEa/75v5ln8PQU+plEU4xtahx/nNLZZK9MIa
VqoSRC0xw+7MJ6Qa77oa3syLQcuEPEy9Zn58Hz1v5Rqn8+grE6iJFlNc3Oxiv+WD
8pN4ofgZQ5pWj3TWr/0VrlJOqek/tgQscity4hN7VPXw34TzwCMsUkYLmDltt6k=
=PBFD
-----END PGP SIGNATURE-----

[Jack Abraham]

Is it possible this is a manifestation of the grey goo fence? The cube farmers griefing the public sandboxes have largely given up on self-replicating objects; this may be why.

http://lslwiki.net/lslwiki/wakka.php?wakka=GreyGooFence

--
Jack Abraham A: Because it messes up the order in which people normally read text.
jack.abraham Q: Why is top-posting such a bad thing?
@me.com A: Top-posting.
Q: What is the most annoying thing in e-mail?

[Fred Allandale]

I opened a new JIRA bug report: https://jira.secondlife.com/browse/SVC-7631

-----Original Message-----
From: Kadah [mailto:kadah...@gmail.com]
Sent: Thursday, January 26, 2012 4:23 PM
To: Fred Allandale
Cc: secondlif...@lists.secondlife.com
Subject: Re: [slscripters] New Inventory Send Rate Throttle?