Re: Fix for occasional Web service crashes, Re: [C++] Moving to Axis2C 0.93

2006-09-11 Thread Andrew Borley

On 9/9/06, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:


Andrew Borley wrote:

 Just got it working on Windows, compiles the runtime  samples and
 runs the
 calculator sample with no changes (on our side) required.
 I tried out the REST support too, but this seems to be a bit flakey -
the
 server seems to fall over occasionally. Not sure whether that's a
Tuscany
 issue or an Axis issue yet.

 Cheers
 Andy


Andy,

The fix committed under revision r441691 fixes the occasional server
crashes. This was not related to Web Services, it was a problem with
ComponentContextImpl::~ComponentContextImpl() aggressively deleting
proxies that it had served. Proxies need to live longer than the context
that served them as they can be passed around to other components for
example.

With my change, CPP proxies are now deleted when the CPPServiceProxy
object that created them gets deleted (and this will eventually happen
when the instance of the current Composite gets deleted, right now I
don't think that the destructors do all the necessary clean up, but this
is a more minor issue).

Let me know if you still see these occasional server crashes, this
change seemed to fix them in my environment at least. Thanks...



Hi Sebastien,

Those changes fixed my problem - no more server crashes!

Thanks
Andy


Fix for occasional Web service crashes, Re: [C++] Moving to Axis2C 0.93

2006-09-08 Thread Jean-Sebastien Delfino

Andrew Borley wrote:


Just got it working on Windows, compiles the runtime  samples and 
runs the

calculator sample with no changes (on our side) required.
I tried out the REST support too, but this seems to be a bit flakey - the
server seems to fall over occasionally. Not sure whether that's a Tuscany
issue or an Axis issue yet.

Cheers
Andy



Andy,

The fix committed under revision r441691 fixes the occasional server 
crashes. This was not related to Web Services, it was a problem with 
ComponentContextImpl::~ComponentContextImpl() aggressively deleting 
proxies that it had served. Proxies need to live longer than the context 
that served them as they can be passed around to other components for 
example.


With my change, CPP proxies are now deleted when the CPPServiceProxy 
object that created them gets deleted (and this will eventually happen 
when the instance of the current Composite gets deleted, right now I 
don't think that the destructors do all the necessary clean up, but this 
is a more minor issue).


Let me know if you still see these occasional server crashes, this 
change seemed to fix them in my environment at least. Thanks...


--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [C++] Moving to Axis2C 0.93

2006-09-07 Thread Andrew Borley

On 9/7/06, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:


Hi,

I tested our C++ Web Service support with Axis2C 0.93 on Linux and it
works with no code change. The only thing you need to do, after you
install Axis2C 0.93 and point your AXIS2C_HOME to it, is to turn the
MTOM (the SOAP Message Transmission Optimization Mechanism) support off
in axis2.xml.

In $AXIS2C_HOME/axis2.xml, change:
  parameter name=enableMTOM locked=falsetrue/parameter
to
  parameter name=enableMTOM locked=falsefalse/parameter

If you don't change that setting Axis2C will send your SOAP messages in
binary form in a Mime Multipart/Related XOP package and the external Web
Services that we're using in Bigbank and other samples do not like that
at all :)

I suggest that we switch to Axis2C 0.93 now since (1) 0.92 is not on the
download mirrors anymore and (2) 0.93 brings us support for REST / HTTP
GET. Could one of you running Visual Studio 6 or 7 please give it a try
on Windows? I can help test on Windows as well, but only once we get the
Visual Studio Express 2005 build working...



+1 for this from me.
I'll try getting it running on Windows VC7 today.

Andy


Re: [C++] Moving to Axis2C 0.93

2006-09-07 Thread Andrew Borley

On 9/7/06, Andrew Borley [EMAIL PROTECTED] wrote:




On 9/7/06, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:

 Hi,

 I tested our C++ Web Service support with Axis2C 0.93 on Linux and it
 works with no code change. The only thing you need to do, after you
 install Axis2C 0.93 and point your AXIS2C_HOME to it, is to turn the
 MTOM (the SOAP Message Transmission Optimization Mechanism) support off
 in axis2.xml.

 In $AXIS2C_HOME/axis2.xml, change:
   parameter name=enableMTOM locked=falsetrue/parameter
 to
   parameter name=enableMTOM locked=falsefalse/parameter

 If you don't change that setting Axis2C will send your SOAP messages in
 binary form in a Mime Multipart/Related XOP package and the external Web

 Services that we're using in Bigbank and other samples do not like that
 at all :)

 I suggest that we switch to Axis2C 0.93 now since (1) 0.92 is not on the
 download mirrors anymore and (2) 0.93 brings us support for REST / HTTP
 GET. Could one of you running Visual Studio 6 or 7 please give it a try
 on Windows? I can help test on Windows as well, but only once we get the
 Visual Studio Express 2005 build working...


+1 for this from me.
I'll try getting it running on Windows VC7 today.

Andy



Just got it working on Windows, compiles the runtime  samples and runs the
calculator sample with no changes (on our side) required.
I tried out the REST support too, but this seems to be a bit flakey - the
server seems to fall over occasionally. Not sure whether that's a Tuscany
issue or an Axis issue yet.

Cheers
Andy
Andy


Re: [C++] Moving to Axis2C 0.93

2006-09-07 Thread Jean-Sebastien Delfino

Andrew Borley wrote:

On 9/7/06, Andrew Borley [EMAIL PROTECTED] wrote:




On 9/7/06, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:

 Hi,

 I tested our C++ Web Service support with Axis2C 0.93 on Linux and it
 works with no code change. The only thing you need to do, after you
 install Axis2C 0.93 and point your AXIS2C_HOME to it, is to turn the
 MTOM (the SOAP Message Transmission Optimization Mechanism) support 
off

 in axis2.xml.

 In $AXIS2C_HOME/axis2.xml, change:
   parameter name=enableMTOM locked=falsetrue/parameter
 to
   parameter name=enableMTOM locked=falsefalse/parameter

 If you don't change that setting Axis2C will send your SOAP 
messages in
 binary form in a Mime Multipart/Related XOP package and the 
external Web


 Services that we're using in Bigbank and other samples do not like 
that

 at all :)

 I suggest that we switch to Axis2C 0.93 now since (1) 0.92 is not 
on the
 download mirrors anymore and (2) 0.93 brings us support for REST / 
HTTP
 GET. Could one of you running Visual Studio 6 or 7 please give it a 
try
 on Windows? I can help test on Windows as well, but only once we 
get the

 Visual Studio Express 2005 build working...


+1 for this from me.
I'll try getting it running on Windows VC7 today.

Andy



Just got it working on Windows, compiles the runtime  samples and 
runs the

calculator sample with no changes (on our side) required.
I tried out the REST support too, but this seems to be a bit flakey - the
server seems to fall over occasionally. Not sure whether that's a Tuscany
issue or an Axis issue yet.

Cheers
Andy
Andy



Andy,

I think this is a Tuscany issue, probably independent of REST. The 
server occasionally crashes for me with SOAP/HTTP as well. I'll try to 
dig into it and debug that issue later today.


Once Geoff gets SDO working on VC++2005, do you think you could try on 
that version as well? Thanks...


--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[C++] Moving to Axis2C 0.93

2006-09-06 Thread Jean-Sebastien Delfino

Hi,

I tested our C++ Web Service support with Axis2C 0.93 on Linux and it 
works with no code change. The only thing you need to do, after you 
install Axis2C 0.93 and point your AXIS2C_HOME to it, is to turn the 
MTOM (the SOAP Message Transmission Optimization Mechanism) support off 
in axis2.xml.


In $AXIS2C_HOME/axis2.xml, change:
 parameter name=enableMTOM locked=falsetrue/parameter
to
 parameter name=enableMTOM locked=falsefalse/parameter

If you don't change that setting Axis2C will send your SOAP messages in 
binary form in a Mime Multipart/Related XOP package and the external Web 
Services that we're using in Bigbank and other samples do not like that 
at all :)


I suggest that we switch to Axis2C 0.93 now since (1) 0.92 is not on the 
download mirrors anymore and (2) 0.93 brings us support for REST / HTTP 
GET. Could one of you running Visual Studio 6 or 7 please give it a try 
on Windows? I can help test on Windows as well, but only once we get the 
Visual Studio Express 2005 build working...


Thoughts?

--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]