These were exactly the kind of symptoms that led to the creation of WSCOMMONS-489 (see the AXIS2 issues linked to WSCOMMONS-489).
Andreas On Tue, Mar 30, 2010 at 19:38, Uzzolino, Frank E <fuzzol...@uhc.com> wrote: > Heh, I guess it could be read both ways, so here's the scoop. > > We're having a problem that shows up only under load. Everything works > fine until we start putting a larger load through the client code. The > logs begin to show corruption errors where it almost appears that part > of one XML message is dropped into the middle of another. The XML can't > be parsed, and the app croaks. The second, more serious issue is that > once things start going bad, they go real bad, with the CPU pegging 100% > after just a few more minutes of testing. > > Here's the kicker -- this only happens on multi CPU boxes. If you run > the tests on a box with just one CPU (or change the process affinity to > one), everything works fine. > > Other postings I've researched point to the true problem lying in the > threadsafeness of sjsxp.jar, so we're going to be running another load > test tonight, but replace sjsxp.jsr with the Woodstox JARs. > > Other info: JDK 1.5; Tomcat 5.5; Windows 2003 Server; Client code was > generated with wsdl2java using xmlbeans. > > Thanks for all your replies. > > -Frank > > > -----Original Message----- > From: Hiranya Jayathilaka [mailto:hiranya...@gmail.com] > Sent: Tuesday, March 30, 2010 5:56 AM > To: commons-dev@ws.apache.org > Subject: Re: Stability of Axiom 1.2.9(trunk)? > > On Tue, Mar 30, 2010 at 1:40 PM, Andreas Veithen > <andreas.veit...@gmail.com>wrote: > >> Funny, one can read Frank's post in two different ways, with exact >> opposite meaning: >> >> - He is experiencing an issue with a released Axiom version and >> believes that it might be fixed in 1.2.9-SNAPSHOT (by WSCOMMONS-489), >> but he is wondering if it is a good idea to use a snapshot version. >> - He is experiencing an issue with 1.2.9-SNAPSHOT and believes that it > >> might be connected to the change in WSCOMMONS-489. He therefore has >> some doubts about the stability of the trunk. >> >> Reading his post again, I think "culprit" refers to "bug", not >> "WSCOMMONS-489", so it should be the first interpretation. >> > > Yes :) Going through that post again, I think it's the first > interpretation. > > Thanks, > Hiranya > > >> >> Andreas >> >> On Tue, Mar 30, 2010 at 07:57, Hiranya Jayathilaka >> <hiranya...@gmail.com> >> wrote: >> > The Apache Synapse trunk also depends on AXIOM trunk. We haven't >> > come across any major issues lately. Could you please explain the >> > error/issue you are experiencing with AXIOM trunk? >> > >> > Thanks, >> > Hiranya >> > >> > >> > On Mon, Mar 29, 2010 at 11:49 PM, Andreas Veithen >> > <andreas.veit...@gmail.com> wrote: >> >> I would say that the current version on the trunk is very stable. >> >> There have been some important changes since 1.2.8, but there have >> >> been no major changes during the last few months. The test suite in > >> >> Axiom is quite comprehensive, and in addition, we regularly run the >> >> Axis2 tests with 1.2.9-SNAPSHOT. I also know that IBM does some >> >> testing. On the other hand, there are some open issues that I would > >> >> like to fix before the 1.2.9 release and some of them may require >> >> larger changes. Thus, if you take a snapshot version now and >> >> continue to use that until the official 1.2.9 release, you should >> >> not encounter issues. >> >> >> >> Andreas >> >> >> >> On Mon, Mar 29, 2010 at 18:23, Uzzolino, Frank E >> >> <fuzzol...@uhc.com> >> wrote: >> >>> Hi everyone, >> >>> >> >>> We have a situation where a bug fixed in trunk (WSCOMMONS-489) may > >> >>> be the culprit for our problem. I'm wondering how stable trunk >> >>> (1.2.9?) is? >> >>> >> >>> Thanks, >> >>> >> >>> -Frank >> >>> >> >>> This e-mail, including attachments, may include confidential >> >>> and/or proprietary information, and may be used only by the person > >> >>> or entity to which it is addressed. If the reader of this e-mail >> >>> is not the >> intended >> >>> recipient or his or her authorized agent, the reader is hereby >> >>> notified that any dissemination, distribution or copying of this >> >>> e-mail is prohibited. If you have received this e-mail in error, >> >>> please notify >> the >> >>> sender by replying to this message and delete this e-mail > immediately. >> >>> >> >> >> > >> > >> > >> > -- >> > Hiranya Jayathilaka >> > Software Engineer; >> > WSO2 Inc.; http://wso2.org >> > E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 >> > Blog: http://techfeast-hiranya.blogspot.com >> > >> > > > > -- > Hiranya Jayathilaka > Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > This e-mail, including attachments, may include confidential and/or > proprietary information, and may be used only by the person or entity > to which it is addressed. If the reader of this e-mail is not the intended > recipient or his or her authorized agent, the reader is hereby notified > that any dissemination, distribution or copying of this e-mail is > prohibited. If you have received this e-mail in error, please notify the > sender by replying to this message and delete this e-mail immediately. > >
