So, the best solution yet is using Core Server API. But we can't run application on different machine in this case (in my case probably this is ok). I can't understand how interface could affect to performance. Probably they even use the same code when they run same things and at least they use the same Core Server API. Time for parsing messages is not critical when you run big query. I guess Heinrich ran small queries, that why gap was so big. But, I can only guessing here. Anyway, thanks for help and information. I'm going to use XML-RPC, till find some better solution (SOAP, RMI maybe, maybe even EJB)))
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Heinrich G?tzger Sent: Friday, July 12, 2002 3:54 PM To: xindice-users@xml.apache.org Subject: RE: Problem with resource freeing. salue, just a short intermediate: Think about the performance. XML-RPC brings a tenth of CORBA in throughput. I did some tests with Xindice and some with eXist some month ago and as far as this is comparable at all, there is a huge gap in msg/sec during storing. I didn't check for retrieval since I always know the id of the document in my case. So even if I bother with the CORBA due to a ORB conflict I wouldn't give it away like nothing without thinking it over again. regards Heinrich On Fri, 12 Jul 2002, Kanarinka wrote: >Hi Jenya - > >The Xindice XML-RPC interface is designed so that XML-RPC will replace >CORBA as the multi-language access mechanism. Here's a good link to the >purpose behind the XML-RPC interface: >http://xindice-xmlrpc.sourceforge.net/ > >To download the XML_RPC interface go here: >http://sourceforge.net/projects/xindice-xmlrpc/ > >The problems that we were encountering seemed similar to what Edward >Nesterov was describing in the initial post that I replied to. We found >that Xindice would run smoothly for the first few hundred transactions >(about 5 minutes based on what our application does) but that the >resources used by the Xindice transactions were not getting freed. >Basically what would end up happening is that our application and the >tomcat server would appear to hang in odd, random places and the CPU >would max out and the JVM would end up hung/crashed. > >Switching to the XML-RPC interface solved this problem. It looks like >the developers all want to cut CORBA anyways as the default >implementation and there's some further discussion of the problem, for >example, here: > >http://marc.theaimsgroup.com/?l=xindice-dev&m=102643473900429&w=2 > >I highly recommend using the XML-RPC interface right from the beginning. >It wasn't too painful to port our application over to it, but it did >take a few days work. > >Hope that helps, >catherine > >-----Original Message----- >From: Jenya Strokin [mailto:[EMAIL PROTECTED] >Sent: Friday, July 12, 2002 1:53 PM >To: xindice-users@xml.apache.org >Subject: RE: Problem with resource freeing. > > >May I ask instead of what you start using XML-RPC interface? >Because I'm going to use Xindice with Tomcat, I probably should use this >interface too. >I've tested Xindice using APIService, is it bring the problem? >Could you give more details of this case? I'm new in Xindice and any >information is helpful. >Thanks, >Jenya > >-----Original Message----- >From: Kanarinka [mailto:[EMAIL PROTECTED] >Sent: Friday, July 12, 2002 12:45 PM >To: xindice-users@xml.apache.org >Subject: RE: Problem with resource freeing. > >Hello all, > >For the record I want to state that switching to the XML-RPC interface >has solved the resource freeing and memory issues that we were >experiencing with Xindice under Win2K. > >Hope that helps someone in the future... > >Cheers, >Catherine > >-----Original Message----- >From: Edward Nesterov [mailto:[EMAIL PROTECTED] >Sent: Monday, July 08, 2002 10:55 AM >To: xindice-users@xml.apache.org >Subject: Re: Problem with resource freeing. > > >Hi, > >1) We spent a lot of time for writing the custom mapper RDBMS<->XML as >all open source XMLDB which are on the market did not match our >criteria. > >2) No we did not try Xindice's XML_RPC interface. > >Ed. > >Kanarinka wrote: > >>Hi Edward, >> >>I'm sorry to hear that. Could I bother you with two quick questions? >> >>1) What did you switch to instead of Xindice? >> >>2) Did you try Xindice's XML-RPC Interface? According to Walt Meyer >this >>seemed to solve some memory and resource issues on Windows -- >>http://www.thatwaltguy.com/xinstaller/ >> >>Thanks for your help, >>Catherine >> >>-----Original Message----- >>From: Edward Nesterov [mailto:[EMAIL PROTECTED] >>Sent: Wednesday, July 03, 2002 5:38 PM >>To: xindice >>Subject: Re: Problem with resource freeing. >> >> >>Hi, >> >>We abandoned xindice until this problem is fixed. >>Sorry. >> >>Ed. >> >>Catherine D'Ignazio wrote: >> >>>Hello - >>> >>>Has there been any exploration of the issue below? We are running our >>>application and Xindice under Tomcat 4.0 and this problem seems to be >>>happening. >>> >>>The application and xindice handle requests fine for about the first 5 >>>minutes that the app server is up and running but after that the >>>application hangs. It hangs in different places every time, so there >is >>>no consistency to it. >>> >>>We are running on Win2K, jdk 1.3.1_01, Tomcat 4.0 and Win2K, jdk >>>1.3.1_03, Tomcat 4.0 >>> >>>Does anybody have more information/workarounds/etc about this? >>> >>>We would really appreciate it since we are about to deploy a distance >>>learning application using Xindice. >>> >>>Thanks >>>Catherine D'Ignazio >>> >>> >>>PREVIOUS MESSAGE: >>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>List: xindice-users >>>Subject: Problem with resource freeing. >>>From: Edward Nesterov <[EMAIL PROTECTED]> >>>Date: 2002-05-08 17:33:25 >>>[Download message RAW] >>> >>>Hi, >>>I am working with latest release of Xindice on Linux >RH6.2/JDK1.3.1_03. >>> >>>The following problem constantly occurs: >>> -Closing of Collection does not free resources (socket >>>connections are >>>established, thread(process) is alive(running)) though isOpen() >returns >>> >> >>>false. >>> -Resources became freed only on client application exit, which >>>makes >>>impossible to use Xindice together with servlet engines, or other kind > >>>of application servers. >>> >>>I observed the same behavior on W2K/JDK1.3.1. >>>Is it bug or feature? >>>Are there any places to change the behavior of Xindice? >>> >>>Thanks. >>> >>>Ed. >>> >>> >>> >> >> >> > >------------------------------------------- >Introducing NetZero Long Distance >Unlimited Long Distance only $29.95/ month! >Sign Up Today! www.netzerolongdistance.com > -- http://www.xmlBlaster.org ------------------------------------------- Introducing NetZero Long Distance Unlimited Long Distance only $29.95/ month! Sign Up Today! www.netzerolongdistance.com
