Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 98397 invoked from network); 13 Oct 2005 12:28:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Oct 2005 12:28:50 -0000 Received: (qmail 22348 invoked by uid 500); 13 Oct 2005 12:28:50 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 22327 invoked by uid 500); 13 Oct 2005 12:28:49 -0000 Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C User List" Reply-To: "Apache AXIS C User List" Delivered-To: mailing list axis-c-user@ws.apache.org Received: (qmail 22316 invoked by uid 99); 13 Oct 2005 12:28:49 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Oct 2005 05:28:49 -0700 Received-SPF: pass (asf.osuosl.org: domain of HAWKINSJ@uk.ibm.com designates 195.212.29.136 as permitted sender) Received: from [195.212.29.136] (HELO mtagate3.uk.ibm.com) (195.212.29.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Oct 2005 05:28:51 -0700 Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate3.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j9DCSooj083770 for ; Thu, 13 Oct 2005 13:28:50 +0100 Received: from d06av02.portsmouth.uk.ibm.com (d06av02.portsmouth.uk.ibm.com [9.149.37.228]) by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j9DCSNqB186726 for ; Thu, 13 Oct 2005 13:28:23 +0100 Received: from d06av02.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av02.portsmouth.uk.ibm.com (8.12.11/8.13.3) with ESMTP id j9DCSNwg004639 for ; Thu, 13 Oct 2005 13:28:23 +0100 Received: from d06ml068.portsmouth.uk.ibm.com (d06ml068.portsmouth.uk.ibm.com [9.149.38.194]) by d06av02.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j9DCSNNd004636 for ; Thu, 13 Oct 2005 13:28:23 +0100 In-Reply-To: <00cd01c5cfe5$66d12490$421610ac@Avebury> To: "Apache AXIS C User List" MIME-Version: 1.0 Subject: Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails? X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 From: John Hawkins X-MIMETrack: S/MIME Sign by Notes Client on John Hawkins/UK/IBM(Release 6.0.2CF1|June 9, 2003) at 13/10/2005 13:17:10, Serialize by Notes Client on John Hawkins/UK/IBM(Release 6.0.2CF1|June 9, 2003) at 13/10/2005 13:17:10, Serialize complete at 13/10/2005 13:17:10, S/MIME Sign failed at 13/10/2005 13:17:10: The cryptographic key was not found, Serialize by Router on D06ML068/06/M/IBM(Release 6.53HF247 | January 6, 2005) at 13/10/2005 13:28:23, Serialize complete at 13/10/2005 13:28:23 Message-ID: Date: Thu, 13 Oct 2005 13:28:23 +0100 Content-Type: multipart/alternative; boundary="=_alternative 00437DAB80257099_=" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multipart message in MIME format. --=_alternative 00437DAB80257099_= Content-Type: text/plain; charset="US-ASCII" I think the XMLParser library is a red herring. The work is done in the engine. Do you recompile the engine too ? We do try out multithreaded clients but we would not have noticed whether the dll was loaded more than once. Tomaz Rotovnik 13/10/2005 12:01 Please respond to "Apache AXIS C User List" To Apache AXIS C User List cc Subject Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails? Hi Thank you for the response. I just want to say that using different libraries (AxisXMLParser.dll - original, my release and my debug , xerces-c_X_X) causes different behavior in loading HTTPChannel.dll library. I'm using only 1.5 version of AXIS. Only when I generated AxisXMLParser.dll library by myself (compiled with VC++ 6.0) and using xerces-c_2_7.dll library I get correct behavior ( HTTPChannel.dll library is loaded only once). In other cases (using original AxisXMLParser.dll which loads xerces-c_2_2) HTTPChannel.dll library is loaded for each axis instance. Does anyone checked loading HTTPChannel.dll when using multithreaded client side of axis? Best regards Tomaz ----- Original Message ----- From: John Hawkins To: Apache AXIS C User List Sent: Thursday, October 13, 2005 12:40 PM Subject: Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails? Hmm, not quite clear on what you're saying here but if it helps I don't think we fixed the transport reload issue until post 1.5 "Tomaz Rotovnik" 12/10/2005 18:38 Please respond to "Apache AXIS C User List" To "Apache AXIS C User List" cc Subject Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails? Hi I tested again and I think I found the problem. First I used my compiled version of AxisClient.dll with AxisXMLParser.dll allready provided in axis version 1.5 + xerces-c_2_2_0. Each time I performed transaction, the HTTPChannel.dll librariy was loaded again and again. Then I used my compilation of debug AxisXMLParser.dll with xerces-c_2_7. Debug HTTPChannel.dll library was loaded only at the begining (when Axis::initialize(false) was called). If I use debug version of AxisClient.dll and release version of AxisXMLParser.dll the release HTTPChannel.dll librariy is loaded at each call again and again. It is very strange and also not logical for me. ----- Original Message ----- From: John Hawkins To: Apache AXIS C User List Sent: Wednesday, October 12, 2005 11:28 AM Subject: Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails? Hmm, I thought we'd got rid of this - there is certainly a JIRA that was trying to address all these sorts of issues.http://issues.apache.org/jira/browse/AXISCPP-657 Hmm, looks like it never had any specific issues addressed in it ! Maybe you can use this JIRA to fix it ? cheers, John. --=_alternative 00437DAB80257099_= Content-Type: text/html; charset="US-ASCII"
I think the XMLParser library is a red herring. The work is done in the engine. Do you recompile the engine too ?

We do try out multithreaded clients but we would not have noticed whether the dll was loaded more than once.






Tomaz Rotovnik <tomaz.rotovnik@uni-mb.si>

13/10/2005 12:01
Please respond to
"Apache AXIS C User List"
To
Apache AXIS C User List <axis-c-user@ws.apache.org>
cc
Subject
Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?





Hi
 
Thank you for the response. I just want to say that using different libraries (AxisXMLParser.dll  - original, my release and my debug ,  xerces-c_X_X) causes different behavior in loading HTTPChannel.dll library. I'm using only 1.5 version of AXIS.
 
Only when I generated AxisXMLParser.dll library by myself  (compiled with VC++ 6.0) and using xerces-c_2_7.dll library I get correct behavior (HTTPChannel.dll library is loaded only once). In other cases (using original AxisXMLParser.dll which loads xerces-c_2_2) HTTPChannel.dll library is loaded for each axis instance.
 
Does anyone checked loading HTTPChannel.dll when using multithreaded client side of axis?
 
Best regards
 
Tomaz
 
 
 
----- Original Message -----
From: John Hawkins
To: Apache AXIS C User List
Sent: Thursday, October 13, 2005 12:40 PM
Subject: Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?


Hmm, not quite clear on what you're saying here but if it helps I don't think we fixed the transport reload issue until post 1.5




"Tomaz Rotovnik" <tomaz.rotovnik@uni-mb.si>

12/10/2005 18:38
Please respond to
"Apache AXIS C User List"
To
"Apache AXIS C User List" <axis-c-user@ws.apache.org>
cc
Subject
Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?







Hi
 
I tested again and I think I found the problem. First I used my compiled version of AxisClient.dll with AxisXMLParser.dll allready provided in axis version 1.5 + xerces-c_2_2_0. Each time I performed transaction, the HTTPChannel.dll librariy was loaded again and again.
 
Then I used my compilation of debug AxisXMLParser.dll with xerces-c_2_7. Debug HTTPChannel.dll library was loaded only at the begining (when Axis::initialize(false) was called).
 
If I use debug version of AxisClient.dll and release version of AxisXMLParser.dll the release HTTPChannel.dll librariy is loaded at each call again and again.
 
It is very strange and also not logical for me.
 
 
 
----- Original Message -----
From: John Hawkins
To: Apache AXIS C User List
Sent: Wednesday, October 12, 2005 11:28 AM
Subject: Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?


Hmm, I thought we'd got rid of this - there is certainly a JIRA that was trying to address all these sorts of issues.http://issues.apache.org/jira/browse/AXISCPP-657
Hmm, looks like it never had any specific issues addressed in it ! Maybe you can use this JIRA to fix it ?

cheers,
John.

--=_alternative 00437DAB80257099_=--