Re: axis2/c in c++ application
Hi Vivian, Vivian Zhou [EMAIL PROTECTED] writes: Hi All, I have a c++ application that needs to call some web services. Basically I will need to make soap/http calls, I am also looking for easy/clear APIs to make these calls. It seems to me that AXIS2/c is a good fix to me. Can you confirm with that? Are there any C++ samples using AXIS2/c APIs available? I saw bunch of c samples in the downloaded package. Yes It is possible to write C++ applications using Axis2/C. There is C++ wrapper available also [1]. Appreciate your interest in Axis2/C. thanks, Dinesh 1. http://wso2.org/projects/wsf/cpp -- http://nethu.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2/c in c++ application
Hi Vivian, If you are really keen on seeing some C++ samples written for Axis2/C, please try the C++ wrapper to Axis2/C, [1], which has almost all the Axis2/C samples written in a C++ fashion. [1] http://wso2.org/projects/wsf/cpp Regards, Senaka Hi Vivian, Vivian Zhou [EMAIL PROTECTED] writes: Hi All, I have a c++ application that needs to call some web services. Basically I will need to make soap/http calls, I am also looking for easy/clear APIs to make these calls. It seems to me that AXIS2/c is a good fix to me. Can you confirm with that? Are there any C++ samples using AXIS2/c APIs available? I saw bunch of c samples in the downloaded package. Yes It is possible to write C++ applications using Axis2/C. There is C++ wrapper available also [1]. Appreciate your interest in Axis2/C. thanks, Dinesh 1. http://wso2.org/projects/wsf/cpp -- http://nethu.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2C] IIS module - cannot find the log file
Hi Dave, I just tried, yes, it is a bug. I do not know what has caused it, as it doesn't seem to look like a side-effect of a fix. I will fix this today evening. Regards, Senaka Hi Dave, I will take a look and correct this ASAP. Should be a result of a recent fix. Thanks for letting us know. Regards, Senaka Hi All, I've been using the IIS module and getting a log file, but today I can no longer find the log file. I have everything set up as it should be with axis2c_home, log_file and log_level defined in the registry. My web service runs fine, but no log file. Yesterday I noticed my log file was missing the last 2 characters which was strange as the path was long, but only 130 characters. So instead of axis2iis.log I was getting axis2iis.l. And now today no log file at all. Does anyone know of a problem with the IIS module with respect to this or do you have any steps you recommend to figure out what it happening. I have not had much luck in the past with debugging IIS so I'm hoping not to have to do that. Thanks, -Dave. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2C-974) Buffer overflow in HTTP Authentication client (with solution)
Buffer overflow in HTTP Authentication client (with solution) - Key: AXIS2C-974 URL: https://issues.apache.org/jira/browse/AXIS2C-974 Project: Axis2-C Issue Type: Bug Components: transport/http Affects Versions: 1.2.0, Current (Nightly), 1.3.0 Environment: Axis + Visual C++ 6 Reporter: Stefano Pettini Priority: Critical Fix For: 1.2.0, 1.3.0 Bug is present in 1.3.0-RC1 announced by Dinesh on 7/2/2008 too. In file /src/core/transport/http/sender/http_sender.c, functions axis2_http_sender_configure_http_basic_auth and axis2_http_sender_configure_proxy_basic_auth use sprintf without allocating enough bytes to hold the null string terminator. Line 1295, int plen = axutil_strlen (uname) + axutil_strlen (passwd) + 1 is not correct, should be +2. Line 1302, elen = axutil_base64_encode_len (plen) is not correct, a +1 should be added. Similar fixes should be applied to lines 1423 and 1430. Please note that memory allocation for auth_str (using elen + 6) is risky for the future. If Basic is substituted with Digest the +6 becomes incorrect, causing another buffer overflow. Thank you, Stefano. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2C-974) Buffer overflow in HTTP Authentication client (with solution)
[ https://issues.apache.org/jira/browse/AXIS2C-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefano Pettini updated AXIS2C-974: --- Remaining Estimate: (was: 0.25h) Original Estimate: (was: 0.25h) Buffer overflow in HTTP Authentication client (with solution) - Key: AXIS2C-974 URL: https://issues.apache.org/jira/browse/AXIS2C-974 Project: Axis2-C Issue Type: Bug Components: transport/http Affects Versions: 1.2.0, Current (Nightly), 1.3.0 Environment: Axis + Visual C++ 6 Reporter: Stefano Pettini Priority: Critical Fix For: 1.2.0, 1.3.0 Bug is present in 1.3.0-RC1 announced by Dinesh on 7/2/2008 too. In file /src/core/transport/http/sender/http_sender.c, functions axis2_http_sender_configure_http_basic_auth and axis2_http_sender_configure_proxy_basic_auth use sprintf without allocating enough bytes to hold the null string terminator. Line 1295, int plen = axutil_strlen (uname) + axutil_strlen (passwd) + 1 is not correct, should be +2. Line 1302, elen = axutil_base64_encode_len (plen) is not correct, a +1 should be added. Similar fixes should be applied to lines 1423 and 1430. Please note that memory allocation for auth_str (using elen + 6) is risky for the future. If Basic is substituted with Digest the +6 becomes incorrect, causing another buffer overflow. Thank you, Stefano. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2C-975) iis_iaspi_plugin_51 can't handle long log_file names
iis_iaspi_plugin_51 can't handle long log_file names Key: AXIS2C-975 URL: https://issues.apache.org/jira/browse/AXIS2C-975 Project: Axis2-C Issue Type: Bug Components: transport/http Environment: MS Windows XP, MS IIS 5.1 Reporter: Senaka Fernando Assignee: Senaka Fernando Fix For: 1.3.0 iis_iaspi_plugin_51 can't handle long log_file names. I tried with a name with 110+ characters. My log file is created, but, not where I expect it to be. I lies somewhere in the path ending with some 100 characters and some junk text. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2C-975) iis_iaspi_plugin_51 can't handle long log_file names
[ https://issues.apache.org/jira/browse/AXIS2C-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566990#action_12566990 ] Senaka Fernando commented on AXIS2C-975: Hi Dave, I figured out the problem. It is burried deep inside our code, where we actually create the log. We copy the log_name to a temporary buffer which is simply, 100 characters long. I think this has nothing to do with IIS or Windows. I will fix this once I finish with some Windows Issues. Regards, Senaka iis_iaspi_plugin_51 can't handle long log_file names Key: AXIS2C-975 URL: https://issues.apache.org/jira/browse/AXIS2C-975 Project: Axis2-C Issue Type: Bug Components: transport/http Environment: MS Windows XP, MS IIS 5.1 Reporter: Senaka Fernando Assignee: Senaka Fernando Fix For: 1.3.0 Original Estimate: 36h Remaining Estimate: 36h iis_iaspi_plugin_51 can't handle long log_file names. I tried with a name with 110+ characters. My log file is created, but, not where I expect it to be. I lies somewhere in the path ending with some 100 characters and some junk text. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-974) Buffer overflow in HTTP Authentication client (with solution)
[ https://issues.apache.org/jira/browse/AXIS2C-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2C-974. Resolution: Fixed Assignee: Senaka Fernando Hi Stefano, I solved your problem one. Problem two is not an issue. Please refer rfc2617, at [1] for a better explanation. Try, axutil_base64_encode (encoded, Aladdin:open sesame, strlen(Aladdin) + strlen(open sesame) + 1); and then, encoded = [QWxhZGRpbjpvcGVuIHNlc2FtZQ==] But, axutil_base64_encode (encoded, Aladdin:open sesame, strlen(Aladdin) + strlen(open sesame) + 2); and then, encoded = [QWxhZGRpbjpvcGVuIHNlc2FtZQA=] Problem three is already addressed. We do have a separate Digest Auth Implementation. Read through http_sender.c. [1] http://www.rfc.net/rfc2617.html#p5 Many thanks for your concern. Regards, Senaka Buffer overflow in HTTP Authentication client (with solution) - Key: AXIS2C-974 URL: https://issues.apache.org/jira/browse/AXIS2C-974 Project: Axis2-C Issue Type: Bug Components: transport/http Affects Versions: 1.2.0, Current (Nightly), 1.3.0 Environment: Axis + Visual C++ 6 Reporter: Stefano Pettini Assignee: Senaka Fernando Priority: Critical Fix For: 1.2.0, 1.3.0 Bug is present in 1.3.0-RC1 announced by Dinesh on 7/2/2008 too. In file /src/core/transport/http/sender/http_sender.c, functions axis2_http_sender_configure_http_basic_auth and axis2_http_sender_configure_proxy_basic_auth use sprintf without allocating enough bytes to hold the null string terminator. Line 1295, int plen = axutil_strlen (uname) + axutil_strlen (passwd) + 1 is not correct, should be +2. Line 1302, elen = axutil_base64_encode_len (plen) is not correct, a +1 should be added. Similar fixes should be applied to lines 1423 and 1430. Please note that memory allocation for auth_str (using elen + 6) is risky for the future. If Basic is substituted with Digest the +6 becomes incorrect, causing another buffer overflow. Thank you, Stefano. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2C-976) base64 encode length returns size of encoded string + 1.
base64 encode length returns size of encoded string + 1. Key: AXIS2C-976 URL: https://issues.apache.org/jira/browse/AXIS2C-976 Project: Axis2-C Issue Type: Bug Affects Versions: 1.3.0 Reporter: Senaka Fernando base64 encode length returns size of encoded string + 1, which is incorrect. This is because we assume that someone expects the length + 1 to accommodate '\0' that we add. But, if we gave the same string to a strlen() it returns size of encoded string. This would confuse a potential user. axutil_base64_encode (encoded, senaka, 6) = 9, and strlen(encoded) = 8. Also, axutil_base64_encode_len(6) = 9. Therefore, I think it is better to stick to the strlen() way, especially because popular libraries and resources adopt that strategy. Refer [1] for more information. [1] http://www.obviex.com/Articles/CiphertextSize.aspx Regards, Senaka -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2C-902) echo_blocking_dual occasionally segfaulted the simple axis server.
[ https://issues.apache.org/jira/browse/AXIS2C-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567155#action_12567155 ] Senaka Fernando commented on AXIS2C-902: Hi Dinesh, This seems to be fixed. However, I will leave this open until we do the release, just to be sure. Regards, Senaka echo_blocking_dual occasionally segfaulted the simple axis server. -- Key: AXIS2C-902 URL: https://issues.apache.org/jira/browse/AXIS2C-902 Project: Axis2-C Issue Type: Bug Components: samples Affects Versions: Current (Nightly) Environment: Ubuntu 7.10 (Gutsy Gibbon), CURL + libxml2, TCPMon Reporter: Senaka Fernando Fix For: 1.3.0 I have been running echo_blocking_dual in a loop and found out that occasionally the simple axis http server segfaults. My system memory consumption is 575MB/1011MB and swap is 1.5GB/3.8GB. Also note that this problem occurred on Ubuntu 7.10 system, with CURL transport. And, I ran with the TCPMon utility actively monitoring the payloads. This is the tail of my axis2.log [Thu Jan 17 00:27:36 2008] [debug] http_transport_sender.c(228) ctx_epr:http://localhost:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__ [Thu Jan 17 00:27:36 2008] [debug] http_transport_sender.c(711) OP name axutil_qname_get_localpart = http://www.w3.org/2004/08/wsdl/in-out [Thu Jan 17 00:27:36 2008] [error] libxml2_reader_wrapper.c(945) Extra content at the end of the document -- SEVERITY_ERROR [Thu Jan 17 00:27:36 2008] [error] libxml2_reader_wrapper.c(456) error occured in reading xml stream [Thu Jan 17 00:27:36 2008] [critical] soap_builder.c(803) SOAP message does not have a SOAP envelope element [Thu Jan 17 00:27:36 2008] [debug] engine.c(302) Axis2 engine receive completed! Please note that even though the server segfaulted, I got a response HTTP/1.1 202 Accepted for the last request, the one which made the server segfault. All further requests failed as the server is not operational. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-975) iis_iaspi_plugin_51 can't handle long log_file names
[ https://issues.apache.org/jira/browse/AXIS2C-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2C-975. Resolution: Fixed Fixed Issue iis_iaspi_plugin_51 can't handle long log_file names Key: AXIS2C-975 URL: https://issues.apache.org/jira/browse/AXIS2C-975 Project: Axis2-C Issue Type: Bug Components: transport/http Environment: MS Windows XP, MS IIS 5.1 Reporter: Senaka Fernando Assignee: Senaka Fernando Fix For: 1.3.0 Original Estimate: 36h Remaining Estimate: 36h iis_iaspi_plugin_51 can't handle long log_file names. I tried with a name with 110+ characters. My log file is created, but, not where I expect it to be. I lies somewhere in the path ending with some 100 characters and some junk text. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2/c in c++ application
Hi Arseny, I am NOT looking for tools to generate c-style stubs because my C++ application needs to be able to access unlimitted number of web service providers. What I need is the capability (a web service client engine with some simple and clean APIs) that allows my C++ code to make a web service call and get reply using HTTP/SOAP protocol. In this case, my C++ code is basically a webs ervice client. By browsing the AXIS2/c stuff and mail archives, seems that it can satisfy my requirements. I would like fellow developers to confirm that before I make a decision to use it. Thanks! Vivi - Original Message From: Arseny [EMAIL PROTECTED] To: Apache AXIS C User List [EMAIL PROTECTED] Sent: Friday, February 8, 2008 12:07:23 AM Subject: Re: axis2/c in c++ application AXIS2/C (in fact WSDL2C) generates C-style stubs, so I prefer the first revision of Axis with its C++ stubs. Vivian Zhou wrote: Hi All, I have a c++ application that needs to call some web services. Basically I will need to make soap/http calls, I am also looking for easy/clear APIs to make these calls. It seems to me that AXIS2/c is a good fix to me. Can you confirm with that? Are there any C++ samples using AXIS2/c APIs available? I saw bunch of c samples in the downloaded package. Thanks in avance. Vivi Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://us.rd.yahoo.com/evt=51734/*http://tools.search.yahoo.com/newsearch/category.php?category=shopping - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
[jira] Issue Comment Edited: (AXIS2C-975) iis_iaspi_plugin_51 can't handle long log_file names
[ https://issues.apache.org/jira/browse/AXIS2C-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567203#action_12567203 ] hoodoo99 edited comment on AXIS2C-975 at 2/8/08 1:08 PM: --- Thanks, Senaka. I figured out the other problem I was having with IIS. I had used backslash characters for the log_file and axis2c_home paths. The manual is currently not correct as it shows backslash characters for these paths. When I changed the paths to use forward slashes everything worked and I got the log file where I specified. I didn't enter an issue for that as I wanted to check with you that the logic is correct since I think I was using backslash characters previously and it was working (I can't be 100% sure though as I didn't save any of the old registry settings). The manual shows: Add a string value with the name AXIS2C_HOME and a value of c:\axis2c Add a string value with the name log_file and a value of c:\axis2c\logs\axis2.log Note that the code looks for axis2c_home in the registry. Are registry key names case sensitive? If so, then that part is also not correct in the manual. Thanks, -Dave. was (Author: hoodoo99): Thanks, Senaka. I figured out the other problem I was having with IIS. I had used backslash characters for the log_file and axis2c_home paths. The manual is currently not correct as it shows backslash characters for these paths. I didn't enter an issue for that as I wanted to check with you that the logic is correct since I think I was using backslash characters previously and it was working (I can't be 100% sure though as I didn't save any of the old registry settings). The manual shows: Add a string value with the name AXIS2C_HOME and a value of c:\axis2c Add a string value with the name log_file and a value of c:\axis2c\logs\axis2.log Note that the code looks for axis2c_home in the registry. Are registry key names case sensitive? If so, then that part is also not correct in the manual. Thanks, -Dave. iis_iaspi_plugin_51 can't handle long log_file names Key: AXIS2C-975 URL: https://issues.apache.org/jira/browse/AXIS2C-975 Project: Axis2-C Issue Type: Bug Components: transport/http Environment: MS Windows XP, MS IIS 5.1 Reporter: Senaka Fernando Assignee: Senaka Fernando Fix For: 1.3.0 Original Estimate: 36h Time Spent: 5h Remaining Estimate: 31h iis_iaspi_plugin_51 can't handle long log_file names. I tried with a name with 110+ characters. My log file is created, but, not where I expect it to be. I lies somewhere in the path ending with some 100 characters and some junk text. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2C-975) iis_iaspi_plugin_51 can't handle long log_file names
[ https://issues.apache.org/jira/browse/AXIS2C-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567203#action_12567203 ] Dave Meier commented on AXIS2C-975: --- Thanks, Senaka. I figured out the other problem I was having with IIS. I had used backslash characters for the log_file and axis2c_home paths. The manual is currently not correct as it shows backslash characters for these paths. I didn't enter an issue for that as I wanted to check with you that the logic is correct since I think I was using backslash characters previously and it was working (I can't be 100% sure though as I didn't save any of the old registry settings). The manual shows: Add a string value with the name AXIS2C_HOME and a value of c:\axis2c Add a string value with the name log_file and a value of c:\axis2c\logs\axis2.log Note that the code looks for axis2c_home in the registry. Are registry key names case sensitive? If so, then that part is also not correct in the manual. Thanks, -Dave. iis_iaspi_plugin_51 can't handle long log_file names Key: AXIS2C-975 URL: https://issues.apache.org/jira/browse/AXIS2C-975 Project: Axis2-C Issue Type: Bug Components: transport/http Environment: MS Windows XP, MS IIS 5.1 Reporter: Senaka Fernando Assignee: Senaka Fernando Fix For: 1.3.0 Original Estimate: 36h Time Spent: 5h Remaining Estimate: 31h iis_iaspi_plugin_51 can't handle long log_file names. I tried with a name with 110+ characters. My log file is created, but, not where I expect it to be. I lies somewhere in the path ending with some 100 characters and some junk text. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2C-884) Seg fault in libxml when svc client torn down in a multithreaded client
[
https://issues.apache.org/jira/browse/AXIS2C-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567024#action_12567024
]
Bill Mitchell commented on AXIS2C-884:
--
You're very welcome.
By the way, to implement a call to initialize libxml in my main thread, I did
not have to include all the libxml includes which caused some conflicts with
other xml related includes I had. Instead I excerpted just the fragment of the
header file for initialization and encapsulated it under an ifdef in my app:
// If libxml2 is used, instead of guththila, then we need to explicitly
initialize outside of Axis2c
#if AXIS_LIBXML_INIT_IN_MAIN_THREAD
// Define libxml entry points directly, to avoid conflicts with Xerces
#ifdef __cplusplus
extern C {
#endif
#include libxml/xmlexports.h
XMLPUBFUN void XMLCALL
xmlInitParser(void);
XMLPUBFUN void XMLCALL
xmlCleanupParser(void);
#ifdef __cplusplus
}
#endif
#endif
Then I added a call to xmlInitParser() in my main thread, again under ifdef,
and worked around the problem. I may have had another issue to make sure that
libxml2 and its friends are built with the VS debug C runtime included in the
manifest, but I had already solved that issue in order to debug libxml2.
The other, simpler workaround is to rebuild Axis to use the guththila parser.
I only went back to libxml2 as I was encountering guththila problems that I
thought would take some time to resolve. All the ones I encountered in my app
have been fixed in 1.3 and it works fine for me. There are a couple of other
minor ones that are preventing the guththila parser becoming the default parser
today. I think the general direction is to move to guththila as soon as
practicable. For your app, like mine, it may be there already.
Seg fault in libxml when svc client torn down in a multithreaded client
---
Key: AXIS2C-884
URL: https://issues.apache.org/jira/browse/AXIS2C-884
Project: Axis2-C
Issue Type: Bug
Components: core/deployment
Affects Versions: Current (Nightly)
Environment: Windows XP, Visual Studio 2005, libxml 2.6.25 and libxml
2.6.30, libcurl
Reporter: Bill Mitchell
Attachments: axis2.trace, desc_builder_diff.txt
In a multithreaded application, if the stub/svc client is freed in a thread
different from that used when the svc client was built, libxml crashes. The
trace below shows the information available from a release build with debug
information embedded.
I have verified this is not an effect of combining debug and release C
runtimes, or different versions of the C runtime. Rebuilding all the libxml
related dlls with the same runtime as is used for Axis and the client app
does not solve the problem.
Interestingly, rebuilding libxml with threads disabled does make the crash go
away. But the default build of libxml commonly available has native threads
enabled, and building without thread support may make the library not thread
safe.
By adding debug trace statements in the axis2.trace file, I have verified
that the xml_reader being torn down when the crash happens is the one used to
read the axis2.xml file when the configuration was first read. (axis2.trace
file attached.)
Looking at the code in libxml, it appears that libxml decides to close the
reader using an internal close routine intended for closing compressed
channels through zlib. Apparently the C runtime library returns a -1 EOF
status when closing a file opened for read. The close routine, gzio.c in
zlib, treats this as an error, and when libxml attempts to report the error
and determines that it is in a different thread, things really go downhill
fast. I have not isolated why the EnterCriticalSection call crashes in the
system, but it does.
One way to avoid the problem would be to guarantee that the stub/svc client
is freed in the same thread as created it. In my multithreaded client
application, though, I work hard to share the stub across threads
deliberately to reduce the number of distinct service clients and the
associated demand on the server.
Windows call traceback at time of crash:
ntdll.dll!7c918fea()
[Frames below may be incorrect and/or missing, no symbols loaded for
ntdll.dll]
msvcr80.dll!78134d09()
ntdll.dll!7c910e91()
ntdll.dll!7c9106eb()
msvcr80.dll!78134d83()
ntdll.dll!7c90104b()
libxml2.dll!xmlGetGlobalState() Line 570 C
libxml2.dll!__xmlLastError() Line 709 + 0x5 bytes C
libxml2.dll!__xmlRaiseError(void (void *, _xmlError *)*
schannel=0x, void (void *, const char *, no type)*
channel=0x, void * data=0x, void *
[jira] Resolved: (AXIS2C-710) pkg-config not detected properly during configure
[ https://issues.apache.org/jira/browse/AXIS2C-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera resolved AXIS2C-710. --- Resolution: Fixed pkg-config not detected properly during configure - Key: AXIS2C-710 URL: https://issues.apache.org/jira/browse/AXIS2C-710 Project: Axis2-C Issue Type: Bug Components: build system (Unix/Linux) Affects Versions: 1.1.0 Environment: Red Hat Enterprise Linux 4 with pkgconfig-0.15 RPM installed Reporter: Stefano Pettini Assignee: Sanjaya Ratnaweera Fix For: 1.3.0 I cannot compile Axis2/C on RHEL4 because: checking for LIBXML2... configure: error: The pkg-config script could not be found or is too old. Make sure it is in your PATH or set the PKG_CONFIG environment variable to the full path to pkg-config. I don't see the need of version 0.20 or higher, since the installed version, 0.15, is able to retrieve LIBS and CFLAGS of libxml-2.0 without any problem. By the way: Alternatively, you may set the environment variables LIBXML2_CFLAGS and LIBXML2_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. This doesn't work too, since I manually set those variables, here they are, just copied from set output: LIBXML2_CFLAGS=-I/usr/include/libxml2 LIBXML2_LIBS='-lxml2 -lpthread -lz -lm' But configure still try to use the pkg-config utility it doesn't like. Upgrading the RPM is not an option, this would require an upgraded C library too. I solved modifying the configure script of axiom, lowering the required pkg-config version from 0.20 to 0.15 and works perfectly. I think this fix should be included in next releases. Thank you! Stefano -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2C-573) Fix warnings on windows
[ https://issues.apache.org/jira/browse/AXIS2C-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567252#action_12567252 ] Bill Mitchell commented on AXIS2C-573: -- I glad to see you are picking these up, Senaka. After changing the Windows makefile to /W3 to enable warnings, I was beginning to get irritated by these, too. Obviously a lot are just AXIS2_PARAM_CHECK calls that return the wrong type, e.g., AXIS2_FAILURE, in a method that is supposed to return a pointer. When I saw the signed/unsigned warnings, though, these set off bells and whistles for me. I've not looked at these in particular, but in other projects on which I have worked, the signed/unsigned warnings are usually real coding errors as the C promotion rules for signed/unsigned do not yield the comparison that a human reader expects. Thanks. Fix warnings on windows Key: AXIS2C-573 URL: https://issues.apache.org/jira/browse/AXIS2C-573 Project: Axis2-C Issue Type: Bug Components: build system (Windows) Environment: Windows Reporter: Nandika Jayawardana Assignee: Senaka Fernando Fix For: 1.3.0 When building axis2c source on windows, there are large number of warnings. These warnings should be fixed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[AXIS2C] Questions about using REST
Hi Senaka, Samisa and Others,
I am now starting to implement REST style calls and have a couple
questions:
1. It seems that a GET REST call only works if a query string with at
least one value is specified in the URI. For example I want to do
wsclient.exe -get
http://localhost:9090/axis2/services/aewebservices70/GetItem/111; to get
item 111 but that won't work. I have to do wsclient.exe -get
http://localhost:9090/axis2/services/aewebservices70/GetItem/111?foo=bar
and then the request does get dispatched to my code. Is there a way
around this?
2. I don't know how to get at the values in the URL, like the 111
value above which I have mapped like parameter
name=RESTLocationGetItem/{itemid}/parameter. Do I look up
itemid somewhere in the message context? I haven't done much with the
context so any code samples would be awesome. If I want to get query
string values how do I do that?
Thank you for your help!
-Dave.
**
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. Any
unauthorized review, use, disclosure or distribution is prohibited. If you are
not the intended recipient, please contact the sender by reply e-mail and
destroy all copies of the original message.
**
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]Axis2/C 1.3.0 RC1
Hi, I tested both binary and source distributions in Linux with the following scenarios 1. Sandesha2 with simple axis server and apache2 server both for libxml2 and Guththila parser 2. Savan with simple axis2 server/apache2 server both for libxml2 and Guththila parser. 3. All Axis2/C samples. Following problem encountered 1. echo_rest sample fails with Received OM : ExceptionOperation Not Found, Endpoint referance address is /axis2/services/echo/echoString and wsa actions is (null)/Exception thanks Damitha Dinesh Premalal wrote: Hi Devs, I uploaded Axis2/C 1.3.0 RC1 here [1]. Please test and send your feedback. thanks, Dinesh 1.http://people.apache.org/~dinesh/release/1.3.0-RC1/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]Axis2/C 1.3.0 RC1
Hi Damitha, Damitha Kumarage [EMAIL PROTECTED] writes: 1. echo_rest sample fails with Received OM : ExceptionOperation Not Found, Endpoint referance address is /axis2/services/echo/echoString and wsa actions is (null)/Exception I think you need to enable echo service for REST request. In service.xml file there is commented settings, you can enable echo service for REST requests by simply uncommenting them. Please refer axis2c_manual that ships with Axis2/C 1.3.0 RC1. Looking forward to hear from others too ;) thanks, Dinesh -- http://nethu.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
