+1... Pls don't comment tests out...
IMO Mtom tests are testing the limits of Axis2... They are proving that they are the most fragile, cause they deal with bytes & bits as well as they deal with large message sizes.
So when doing changes pls make sure to run the test with them...
(Without putting us in trouble ;-) )
~Thilina
On 8/15/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Folks,
With latest check-ins...all seems to be well. Please holler if you see
the tests break. Please don't comment the tests out or check in fixes
that may not hold up.
thanks,
dims
On 8/15/05, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
> Exits without even reaching the flush();
>
>
> On 8/15/05, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
> > Everything is working fine in the Server side up to
> SimpleHttpServerConnection.
> > When writing the body to the out stream the program exits.
> >
> > ~Thilina
> >
> >
> >
> > On 8/15/05, Thilina Gunarathne <[EMAIL PROTECTED] > wrote:
> > > Hi all,
> > > IMHO MTOM problem is something to deal in socket level.. The error
> occurs when we try to deffredly access the Mime part. That means when trying
> to access the stream sometime later. And at that point the stream is closed
> by server or client. (Still not clear who is doing it). This happens only
> when we are sending a moderate size MTOM message (>1kb).
> > >
> > > I feel this same eror will arise if we try sending a huge soap message
> and then try to acces the latter parts of the soap some time later...
> Anybody tried this????
> > >
> > > ~Thilina
> > >
> > > --
> > > "May the SourcE be with u"
> > > http://www.bloglines.com/blog/thilina
> >
> >
> >
> > --
> > "May the SourcE be with u"
> > http://www.bloglines.com/blog/thilina
>
>
>
> --
> "May the SourcE be with u"
> http://www.bloglines.com/blog/thilina
--
Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform
--
"May the SourcE be with u"
http://www.bloglines.com/blog/thilina
