Re: RPC-faults by ressource-problem?

[Alexander Schatten <al...@gmx.net>]

I can hardly give more details; I receive a fault string that the service is
not available.

the complete application works fine, when running "standalone"; but these
problems start when :

(1) SOAP is running in Enhydra App-Server
(2) the client app is running in JBuilder

as soon as I start the client from command-line no problems occur.

alex

Sanjiva Weerawarana wrote:

> I personally haven't noticed any instability. Can you please
> post some details about what exactly happens (including specific
> exceptions etc.).
>
> Bye,
>
> Sanjiva.
>
> ----- Original Message -----
> From: "Alexander Schatten" <al...@gmx.net>
> To: <so...@xml.apache.org>
> Sent: Monday, June 25, 2001 9:17 AM
> Subject: RPC-faults by ressource-problem?
>
> > I have installed Apache SOAP running on Enhydra Appserver on my
> > notebook.
> >
> > when I develop SOAP RPC applications, I use JBuilder Enterprise parallel
> > to Enhydra and SOAP and Interclient/Interbase.
> >
> > All RPCs work basically, but SOAP is extremely instable under these
> > conditions. Usually a few 3-5 RPC calls work, than RPC "crashes" by
> > sending RPC-fault strings (service not available...).
> >
> > Can it be, that SOAP gets unstable when ressources are too small
> > (memory,...)?
> >
> >
> > thank you
> >
> >
> > Alex