Return-Path: X-Original-To: apmail-axis-c-user-archive@www.apache.org Delivered-To: apmail-axis-c-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 548B59518 for ; Fri, 30 Dec 2011 10:30:34 +0000 (UTC) Received: (qmail 5261 invoked by uid 500); 30 Dec 2011 10:30:33 -0000 Delivered-To: apmail-axis-c-user-archive@axis.apache.org Received: (qmail 4951 invoked by uid 500); 30 Dec 2011 10:30:24 -0000 Mailing-List: contact c-user-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache AXIS C User List" Delivered-To: mailing list c-user@axis.apache.org Received: (qmail 4937 invoked by uid 99); 30 Dec 2011 10:30:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Dec 2011 10:30:22 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [85.158.139.83] (HELO mail182.messagelabs.com) (85.158.139.83) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Dec 2011 10:30:15 +0000 X-Env-Sender: Pankaj.Kharwal@kf.se X-Msg-Ref: server-11.tower-182.messagelabs.com!1325240992!9038251!1 X-Originating-IP: [213.115.12.30] X-StarScan-Version: 6.4.3; banners=kf.se,-,- X-VirusChecked: Checked Received: (qmail 14184 invoked from network); 30 Dec 2011 10:29:52 -0000 Received: from smtp.kf.se (HELO smtp.kf.se) (213.115.12.30) by server-11.tower-182.messagelabs.com with AES128-SHA encrypted SMTP; 30 Dec 2011 10:29:52 -0000 Received: from STO-MBX-06.kf.local ([::1]) by STO-CASHUB-02.kf.local ([10.130.1.152]) with mapi; Fri, 30 Dec 2011 11:29:52 +0100 From: Pankaj Kharwal To: "c-user@axis.apache.org" Date: Fri, 30 Dec 2011 11:29:49 +0100 Subject: Do not want some application code to be executed for each request Thread-Topic: Do not want some application code to be executed for each request Thread-Index: AczG3fWkdHP8liocTl6G5mUn6iYsCQ== Message-ID: Accept-Language: en-US, sv-SE Content-Language: sv-SE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, sv-SE Content-Type: multipart/alternative; boundary="_000_B40A0E70620A7A4AA3822397B7677B1F05468589E6STOMBX06kfloc_" MIME-Version: 1.0 --_000_B40A0E70620A7A4AA3822397B7677B1F05468589E6STOMBX06kfloc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear all, I have an application written in C/C++ (runs as a webservice) which was pr= eviously running on some other platform. Now, the application has been por= ted to Linux and now we are using AXIS2C 1.6.0. So far, I have been succes= sful in running the application on AXIS2C with minor glitches. However, the application has some constructors which query tables (heavy S= ELECTS) and based on the data read from the tables, the application proces= ses the request. The problem is that when I fire a request, AXIS2C execute= s these constructors for each request. This is not desirable because I do = not want these heavy SELECTs to be executed each time the request comes to= AXIS since it takes upto 3 seconds for the constructors to execute the SQ= L SELECTs. Is there any way to call these constructors only at the start of AXIS engi= ne and save this as a context to be used by the upcoming requests? Thanks and Regards, Pankaj Kharwal Stockholm, Sweden ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________ --_000_B40A0E70620A7A4AA3822397B7677B1F05468589E6STOMBX06kfloc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear all,

 

I have an application written in C/C++ (runs as a webservice) which was previously running on some other platform. Now, the application has been ported to Linux and now we are using AXIS2C 1.6.0. So= far, I have been successful in running the application on AXIS2C with minor glitches.

 

However, the application has some constructors which = query tables (heavy SELECTS) and based on the data read from the tables, the application processes the request. The problem is that when I fire a reque= st, AXIS2C executes these constructors for each request. This is not desirable= because I do not want these heavy SELECTs to be executed each time the req= uest comes to AXIS since it takes upto 3 seconds for the constructors to execut= e the SQL SELECTs.

 

Is there any way to call these constructors only at t= he start of AXIS engine and save this as a context to be used by the upcoming= requests?

 

 

Thanks and Regards,

Pankaj Kharwal

Stockholm, Sweden


______________________________________________________________________
= This email has been scanned by the Symantec Email Security.cloud service.<= BR> For more information please visit http://www.symanteccloud.com
______________________________________________________________________
= --_000_B40A0E70620A7A4AA3822397B7677B1F05468589E6STOMBX06kfloc_--