>>
>>
>>> Lasso 9.2.3 64bit CentOS 6.
>>>
>>> Hi All,
>>>
>>> After thinking that my CPU at 100% was caused by external sessions, it now looks like it wasn't, sorry :-) ..
>>>
>>> The issue is intermittently showing up on our production server, but not on our development machines.
>>>
>>> Two questions:
>>>
>>> 1) This is a quad core server, and when lasso is at 100% CPU, it is using 100% of one core.. the other 3 cores are mostly idle. Lasso is completely unresponsive to access via HTTP. The question is, how do I get lasso to spawn more threads for each core? (is this even possible?)
>>>
>>> 2) Im thinking the issue could be caused by an infinite loop in our code, or something silly like that. It 8.5.6 you could set a recursion limit or a thread time limit.. how do you do this in 9?
>>>
>>> This is starting to stress me a little.. :-)
>>>
>>> Daniel Parker

OK.. The issue was that I was using a variable as the -Host in an Email_Send tag.. This variable was null (unintentionally).. Lasso will then consume 100% CPU which is caused by a stuck message in the SQLite smtp_queue DB. Upon restart lasso will be at 100% CPU within 1 minute.

The Fix is to delete the contents of this table.

Our particular table contents looked like this:

..dump smtp_queue
PRAGMA foreign_keys=OFF;
BEGIN TRANSACTION;
CREATE TABLE smtp_queue (id INTEGER, id_site INTEGER, id_route INTEGER, id_cache INTEGER, mime_text TEXT, mime_recipients TEXT, mime_from TEXT, smtp_host TEXT, smtp_port INTEGER DEFAULT 25, smtp_timeout INTEGER DEFAULT 15, smtp_username TEXT, smtp_password TEXT, smtp_ssl TEXT, queue_date TEXT, queue_status TEXT, queue_error TEXT, queue_number INTEGER DEFAULT 0, queue_priority INTEGER DEFAULT 0, queue_retries INTEGER DEFAULT 0, merge_array TEXT, merge_tokens TEXT, create_date TEXT, PRIMARY KEY (id) );
INSERT INTO "smtp_queue" VALUES(1,'63a28bf1-d7f6-4d90-b63d-d8833eecaca2',NULL,NULL,X'4D494D452D56657273696F6E3A20312E300D0A582D4D61696C65723A204C6173736F2050726F66657373696F6E616C20392E320D0A4D6573736167652D49443A203C35373964613364622D636661612D346362372D626363642D633663333633343461303938403132372E302E302E313E0D0A446174653A205765642C2031352041756720323031322031323A30333A3137202B313230300D0A546F3A206C6F6773406265657263656C6C61722E636F2E6E7A0D0A46726F6D3A2062756773406265657263656C6C61722E636F6D0D0A5375626A6563743A204E657720427567205265706F727465640D0A436F6E74656E742D547970653A20746578742F706C61696E3B20636861727365743D7574662D380D0A436F6E74656E742D5472616E736665722D456E636F64696E673A2071756F7465642D7072696E7461626C650D0A0D0A200D0A','logs@example.com','bugs@example.com','','','','','','','2012-08-15 12:03:17','queued','',0,3,0,X'6E756C6C',X'6E756C6C','2012-08-15 12:03:17');
COMMIT;

I feel that this was my own stupid fault, but maybe Lasso should't completely kill itself in this situation.

Im posting this to the list as I hope it helps someone else in the future.

Daniel Parker

#############################################################
This message is sent to you because you are subscribed to
the mailing list Lasso
Lasso@lists.lassosoft.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>