Hello,
I have created an extension that selects a list of items from a database (1049 items) to be stored in an array on the server. This is only requested once when the server is started. We use this list to speed things up.
Now the problem is that the following error appears:
[Warning] > Found User queues full: messages were dropped
The strange part is, none of the items are missing. So what was dropped? I'm guessing the user is the server, and the server is not sending any messages.
rsnail
[Warning] > Found User queues full: messages were dropped
This error is outputted by the server when the User message queue is full, and there's no more space to add other messages in it.Now the problem is that the following error appears:
[Warning] > Found User queues full: messages were dropped
For each user the server allocates a queue where messages are temporarily stored while waiting that the client receives them (when the connection of the client is very slow the queue can fill up quickly)
The size of the queue depends on the <MaxWriterQueue> param in the config.xml and it's set by default to 50 (50 messages for each user queue.)
It doesn't seem that what you're doing on the server side (loading data from the DB) is related with that message... maybe it's just a coincidence? Does it happen all the times? Did you test it on a live server? Maybe in that moment the traffic was high?
Are you sending this data to the clients? Or do you just keep it on the server side?This is only requested once when the server is started.
The trace command sends it's text message to the AdminTool, so that you can debug the extension remotely. You can turn this behaviour on/off by changing the value of the <ExtensionRemoteDebug> tag in the config.I commented my trace commands and the error has dissappeared. I'm guessing the trace is send a message.
However this has very little to no impact on the server unless you're tracing hundreds of lines of text
Yes, it happens everytime I have the trace uncommented. It does not happen when I have the trace commented. No, I did not test it on a live server. I had 2 clients connected, the AdminTool and my Client.Does it happen all the times? Did you test it on a live server? Maybe in that moment the traffic was high?
Server only.Are you sending this data to the clients? Or do you just keep it on the server side?
I'm guessing this caused the message. I was tracing more than 2000 lines of text in 1 for loop to the AdminTool.However this has very little to no impact on the server unless you're tracing hundreds of lines of text
BTW. Your product is working great so far, and I hope to start testing the new 1.4.0 Beta this coming week.
rsnail
eh eh ... that's the problem.I'm guessing this caused the message. I was tracing more than 2000 lines of text in 1 for loop to the AdminTool.
Your foor loop is definately faster than the time taken by the server to send the messages back to the admin tool.
Once the queue is filled with messages (default limit is 50) the server will start dropping messages until some space is available again.
Simple solution: instead of tracing many small messages, try concatenating them into a larger text message. The server won't complain and you won't see the error message anymore
Hope it helps