All,
For a particular scenario, our module core dumps in some axis library
functions consistently but with different back traces. I'm attaching the
dumps.log file that has as many as 4 different back-traces produced for
the same scenario.
Also, please find attached the log that has axis
Hi raghav,
Axis2/C 1.3 was recently released. There are lots of new features and
bug fixes in that release. Please try that.
http://ws.apache.org/axis2/c/download.cgi
-Thanks,
Manjula.
On Wed, 2008-03-05 at 17:34 +0530, Raghavendra SM wrote:
All,
For a particular scenario, our module core
Thanks Manjula,
But thats not a viable option for us. We would still want to continue
using axis2C-1.0 for some more time.
Are these dumps well known? And have they been specifically fixed in
axis2c-1.3?
Regards,
~raghav
-Original Message-
From: Manjula Peiris [mailto:[EMAIL
Hi Raghavendra,
Raghavendra SM [EMAIL PROTECTED] writes:
Thanks Manjula,
But thats not a viable option for us. We would still want to continue
using axis2C-1.0 for some more time.
Are these dumps well known? And have they been specifically fixed in
axis2c-1.3?
Hmm..For me it seems
Raghavendra SM wrote:
Thanks Manjula,
But thats not a viable option for us. We would still want to continue
using axis2C-1.0 for some more time.
Are these dumps well known?
No.
Are you using the same service client instance from multiple threads?
Samisa...
Raghavendra SM wrote:
Thanks Manjula,
But thats not a viable option for us. We would still want to continue
using axis2C-1.0 for some more time.
Well, the community in general is unable to support this scenario.
Almost all of the devs are working with the latest release. And over
time,
On Wed, 2008-03-05 at 18:09 +0530, Raghavendra SM wrote:
Thanks Manjula,
But thats not a viable option for us. We would still want to continue
using axis2C-1.0 for some more time.
IMHO, changing from Axis2/C 1.0 to 1.3 is not a big issue. Because the
client API and the service API did not
Manjula Peiris wrote:
On Wed, 2008-03-05 at 18:09 +0530, Raghavendra SM wrote:
Thanks Manjula,
But thats not a viable option for us. We would still want to continue
using axis2C-1.0 for some more time.
IMHO, changing from Axis2/C 1.0 to 1.3 is not a big issue. Because the
client API
Hi Senaka,
I am working with Subra on resolving this issue, and I am having no luck
in getting Axis2/C 1.3.0 to work with the libraries he already discussed
about in previous threads. Even removing the -static-libgcc flag
during compilation of our libraries does not resolve the issue.
Ed
Hello folks,
I am running in to another problem and was wondering if I could get some
help from you guys.
Another developer in my team had to add the following lines to httpd config
file. These lines are in a separate .conf file which is placed in the
/etc/httpd/conf.d/ directory and gets
10 matches
Mail list logo