Return-path: Envelope-to: israel@ssf.com.mx Delivery-date: Mon, 01 Jun 2015 17:40:08 -0500 Received: from cocos2.grupoinda.net ([192.99.20.154]:58123) by vishnu.hosting-mexico.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.85) (envelope-from ) id 1YzYNL-001CWk-QF for israel@ssf.com.mx; Mon, 01 Jun 2015 17:40:08 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sicom.ws; s=default; h=Content-Type:Content-Transfer-Encoding:MIME-Version:Message-ID:Subject:From:To:Date; bh=bbfBcjXF5+vUSMZH4kxGRcMvn6LyeP4E8Ur3LfVcCSg=; b=oXku5+ErGuU/aCiBoSj4NJUMGJU8s3NS3YDPh6TCFVS28fhTJIbLSZe9jQG823UZkTDTxOcrJU0xSMkLlqMj+s15lmZ4Xdi9Rw/OIeiiHVW/K9vAVDTznAvVZrbkd5fHv8Mf+s/LKC4xRXK5lXhHaM4RoW3mhbXxT6RlvgEgwqE=; Received: from [177.240.169.60] (port=4417 helo=www.sicom.mx) by cocos2.grupoinda.net with esmtpa (Exim 4.85) (envelope-from ) id 1YzYNO-0005WL-KV for israel@ssf.com.mx; Mon, 01 Jun 2015 17:40:10 -0500 Date: Mon, 1 Jun 2015 14:54:25 +0000 To: israel@ssf.com.mx From: SICOM Bug Tracker Subject: =?utf-8?Q?[G4S=5FModuloCpu_0001415]:_Sortear_la_falta_de_memoria_din?= =?utf-8?Q?=C3=A1mica_al_esperar_notificaci=C3=B3n_emergente?= Message-ID: <0dad3ff46487a5a6bccc1e4a407cd7c9@www.sicom.mx> X-Priority: 3 X-Mailer: PHPMailer 5.1 (phpmailer.sourceforge.net) keywords: [G4S_ModuloCpu] Mejora en implementacion MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cocos2.grupoinda.net X-AntiAbuse: Original Domain - ssf.com.mx X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - sicom.ws X-Get-Message-Sender-Via: cocos2.grupoinda.net: authenticated_id: mantis@sicom.ws X-Spam-Status: No, score=1.0 X-Spam-Score: 10 X-Spam-Bar: + X-Ham-Report: Spam detection software, running on the system "vishnu.hosting-mexico.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see root\@localhost for details. Content preview: The following issue has been SUBMITTED. ====================================================================== http://www.sicom.mx/mantis/view.php?id=1415 ====================================================================== Reported By: agarcia Assigned To: ====================================================================== Project: G4S_ModuloCpu Issue ID: 1415 Category: Mejora en implementacion Reproducibility: N/A Severity: minor Priority: normal Status: new ====================================================================== Date Submitted: 2015-03-23 16:06 GMT Last Modified: 2015-03-23 16:06 GMT ====================================================================== Summary: Sortear la falta de memoria dinámica al esperar notificación emergente Description: Al enviar datos por GPRS (configuración, código de enlace y asignación de identificador) el sistema espera un mensaje y lo almacena como notificación emergente en memoria dinámica para mostrarlo en pantalla. Actualmente se usa la bandera de 'Nueva Notificación' para reconocer que llegó una respuesta. Esto puede ocasionar que, si no se dispone de memoria dinámica para almacenar el mensaje, el sistema 'crea' que no responde el servidor cuando sí lo esté haciendo. [...] Content analysis details: (1.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: sicom.mx] 1.1 DATE_IN_PAST_06_12 Date: is 6 to 12 hours before Received: date -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Spam-Flag: NO The following issue has been SUBMITTED. ====================================================================== http://www.sicom.mx/mantis/view.php?id=1415 ====================================================================== Reported By: agarcia Assigned To: ====================================================================== Project: G4S_ModuloCpu Issue ID: 1415 Category: Mejora en implementacion Reproducibility: N/A Severity: minor Priority: normal Status: new ====================================================================== Date Submitted: 2015-03-23 16:06 GMT Last Modified: 2015-03-23 16:06 GMT ====================================================================== Summary: Sortear la falta de memoria dinámica al esperar notificación emergente Description: Al enviar datos por GPRS (configuración, código de enlace y asignación de identificador) el sistema espera un mensaje y lo almacena como notificación emergente en memoria dinámica para mostrarlo en pantalla. Actualmente se usa la bandera de 'Nueva Notificación' para reconocer que llegó una respuesta. Esto puede ocasionar que, si no se dispone de memoria dinámica para almacenar el mensaje, el sistema 'crea' que no responde el servidor cuando sí lo esté haciendo. Habrá que crear una manera para que la respuesta sea procesada aun cuando no hay memoria dinámica para almacenar el mensaje. ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 2015-03-23 16:06 agarcia New Issue ======================================================================