You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Wayne Johnson (JIRA)" <ax...@ws.apache.org> on 2007/05/16 20:47:16 UTC
[jira] Created: (AXISCPP-1031) SSL_write called with
m_sslHandle=null when socket closed
SSL_write called with m_sslHandle=null when socket closed
---------------------------------------------------------
Key: AXISCPP-1031
URL: https://issues.apache.org/jira/browse/AXISCPP-1031
Project: Axis-C++
Issue Type: Bug
Components: Transport (axis3)
Affects Versions: 1.6 Final
Environment: Testing with Axis[J] on a jetty server. Server has maxIdleTime=60000 (for testing, but any time could be used). WIndowsXP.
Reporter: Wayne Johnson
Fix For: 1.6 Final
When Jetty closes the socket due to maxIdleTime, the next write (from httptransport.cpp, ~line 264) detects the closure and calls HTTPSSLChannel::OpenSSL_Close(), which sets m_sslHandle = NULL. httptransport.cpp, ~line 265 then calls the m_pActiveChannel->writeBytes() again to send the remainder of the packet (without checking if the first write succeded). The null handle causes a crash.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Issue Comment Edited: (AXISCPP-1031) SSL_write called with
m_sslHandle=null when socket closed
Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXISCPP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509936 ]
nadir amra edited comment on AXISCPP-1031 at 7/3/07 9:51 AM:
-------------------------------------------------------------
Wayne, thanks for the info. I put the code into SVN now with your updates included.
I will wait until end of July to whenever you tell to me if sooner to close issue out, unless you feel you need more time.
was:
Wayne, thanks for the info. I put the code into SVN now with your updates included.
I will wait until end of June to whenever you tell to me if sooner to close issue out, unless you feel you need more time.
> SSL_write called with m_sslHandle=null when socket closed
> ---------------------------------------------------------
>
> Key: AXISCPP-1031
> URL: https://issues.apache.org/jira/browse/AXISCPP-1031
> Project: Axis-C++
> Issue Type: Bug
> Components: Transport (axis3)
> Affects Versions: 1.6 Final
> Environment: Testing with Axis[J] on a jetty server. Server has maxIdleTime=60000 (for testing, but any time could be used). WIndowsXP.
> Reporter: Wayne Johnson
> Fix For: 1.6 Final
>
> Attachments: HTTPSSLChannel.cpp, HTTPSSLChannel.cpp, HTTPSSLChannel.hpp
>
>
> When Jetty closes the socket due to maxIdleTime, the next write (from httptransport.cpp, ~line 264) detects the closure and calls HTTPSSLChannel::OpenSSL_Close(), which sets m_sslHandle = NULL. httptransport.cpp, ~line 265 then calls the m_pActiveChannel->writeBytes() again to send the remainder of the packet (without checking if the first write succeded). The null handle causes a crash.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXISCPP-1031) SSL_write called with
m_sslHandle=null when socket closed
Posted by "Wayne Johnson (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXISCPP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507893 ]
Wayne Johnson commented on AXISCPP-1031:
----------------------------------------
Sorry for the delay. It seems we've changed our code to bypass this issue at this time...
I have been testing with your modified SSL code (sans this bug) and it seems to be working well. The only issue seems to be that the "PRNG not seeded" error does not come out, but that now appears to be a bug/feature in OpenSSL. I did come up with some issues in the error reporting code that you had after I desk checked it. I'll upload my suggested corrections.
If you don't mind, I'll leave this bug open for a little longer and see if I can hit the original issue again.
Thanks for your work on this.
> SSL_write called with m_sslHandle=null when socket closed
> ---------------------------------------------------------
>
> Key: AXISCPP-1031
> URL: https://issues.apache.org/jira/browse/AXISCPP-1031
> Project: Axis-C++
> Issue Type: Bug
> Components: Transport (axis3)
> Affects Versions: 1.6 Final
> Environment: Testing with Axis[J] on a jetty server. Server has maxIdleTime=60000 (for testing, but any time could be used). WIndowsXP.
> Reporter: Wayne Johnson
> Fix For: 1.6 Final
>
> Attachments: HTTPSSLChannel.cpp, HTTPSSLChannel.hpp
>
>
> When Jetty closes the socket due to maxIdleTime, the next write (from httptransport.cpp, ~line 264) detects the closure and calls HTTPSSLChannel::OpenSSL_Close(), which sets m_sslHandle = NULL. httptransport.cpp, ~line 265 then calls the m_pActiveChannel->writeBytes() again to send the remainder of the packet (without checking if the first write succeded). The null handle causes a crash.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Updated: (AXISCPP-1031) SSL_write called with
m_sslHandle=null when socket closed
Posted by "Wayne Johnson (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXISCPP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wayne Johnson updated AXISCPP-1031:
-----------------------------------
Attachment: HTTPSSLChannel.cpp
HTTPSSLChannel.cpp with suggested changes to handle proper errors from SSL_Connect, and to add the full SSL error stack to error message.
> SSL_write called with m_sslHandle=null when socket closed
> ---------------------------------------------------------
>
> Key: AXISCPP-1031
> URL: https://issues.apache.org/jira/browse/AXISCPP-1031
> Project: Axis-C++
> Issue Type: Bug
> Components: Transport (axis3)
> Affects Versions: 1.6 Final
> Environment: Testing with Axis[J] on a jetty server. Server has maxIdleTime=60000 (for testing, but any time could be used). WIndowsXP.
> Reporter: Wayne Johnson
> Fix For: 1.6 Final
>
> Attachments: HTTPSSLChannel.cpp, HTTPSSLChannel.cpp, HTTPSSLChannel.hpp
>
>
> When Jetty closes the socket due to maxIdleTime, the next write (from httptransport.cpp, ~line 264) detects the closure and calls HTTPSSLChannel::OpenSSL_Close(), which sets m_sslHandle = NULL. httptransport.cpp, ~line 265 then calls the m_pActiveChannel->writeBytes() again to send the remainder of the packet (without checking if the first write succeded). The null handle causes a crash.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Closed: (AXISCPP-1031) SSL_write called with
m_sslHandle=null when socket closed
Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXISCPP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nadir amra closed AXISCPP-1031.
-------------------------------
> SSL_write called with m_sslHandle=null when socket closed
> ---------------------------------------------------------
>
> Key: AXISCPP-1031
> URL: https://issues.apache.org/jira/browse/AXISCPP-1031
> Project: Axis-C++
> Issue Type: Bug
> Components: Transport (axis3)
> Affects Versions: 1.6 Final
> Environment: Testing with Axis[J] on a jetty server. Server has maxIdleTime=60000 (for testing, but any time could be used). WIndowsXP.
> Reporter: Wayne Johnson
> Fix For: 1.6 Final
>
> Attachments: HTTPSSLChannel.cpp, HTTPSSLChannel.cpp, HTTPSSLChannel.hpp
>
>
> When Jetty closes the socket due to maxIdleTime, the next write (from httptransport.cpp, ~line 264) detects the closure and calls HTTPSSLChannel::OpenSSL_Close(), which sets m_sslHandle = NULL. httptransport.cpp, ~line 265 then calls the m_pActiveChannel->writeBytes() again to send the remainder of the packet (without checking if the first write succeded). The null handle causes a crash.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXISCPP-1031) SSL_write called with
m_sslHandle=null when socket closed
Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXISCPP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498097 ]
nadir amra commented on AXISCPP-1031:
-------------------------------------
Wayne,
Have you had time to test the patch?
> SSL_write called with m_sslHandle=null when socket closed
> ---------------------------------------------------------
>
> Key: AXISCPP-1031
> URL: https://issues.apache.org/jira/browse/AXISCPP-1031
> Project: Axis-C++
> Issue Type: Bug
> Components: Transport (axis3)
> Affects Versions: 1.6 Final
> Environment: Testing with Axis[J] on a jetty server. Server has maxIdleTime=60000 (for testing, but any time could be used). WIndowsXP.
> Reporter: Wayne Johnson
> Fix For: 1.6 Final
>
> Attachments: HTTPSSLChannel.cpp, HTTPSSLChannel.hpp
>
>
> When Jetty closes the socket due to maxIdleTime, the next write (from httptransport.cpp, ~line 264) detects the closure and calls HTTPSSLChannel::OpenSSL_Close(), which sets m_sslHandle = NULL. httptransport.cpp, ~line 265 then calls the m_pActiveChannel->writeBytes() again to send the remainder of the packet (without checking if the first write succeded). The null handle causes a crash.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Updated: (AXISCPP-1031) SSL_write called with
m_sslHandle=null when socket closed
Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXISCPP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nadir amra updated AXISCPP-1031:
--------------------------------
Attachment: HTTPSSLChannel.hpp
HTTPSSLChannel.cpp
Wayne, try these out. I have not compiled the code so you might get some stupid compile errors, if so, let me know. I tried to ensure correctness.
Please ensure that everything works, and then the error condition that you were encountering (i.e. timeout).
Thanks
> SSL_write called with m_sslHandle=null when socket closed
> ---------------------------------------------------------
>
> Key: AXISCPP-1031
> URL: https://issues.apache.org/jira/browse/AXISCPP-1031
> Project: Axis-C++
> Issue Type: Bug
> Components: Transport (axis3)
> Affects Versions: 1.6 Final
> Environment: Testing with Axis[J] on a jetty server. Server has maxIdleTime=60000 (for testing, but any time could be used). WIndowsXP.
> Reporter: Wayne Johnson
> Fix For: 1.6 Final
>
> Attachments: HTTPSSLChannel.cpp, HTTPSSLChannel.hpp
>
>
> When Jetty closes the socket due to maxIdleTime, the next write (from httptransport.cpp, ~line 264) detects the closure and calls HTTPSSLChannel::OpenSSL_Close(), which sets m_sslHandle = NULL. httptransport.cpp, ~line 265 then calls the m_pActiveChannel->writeBytes() again to send the remainder of the packet (without checking if the first write succeded). The null handle causes a crash.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXISCPP-1031) SSL_write called with
m_sslHandle=null when socket closed
Posted by "Wayne Johnson (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXISCPP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496749 ]
Wayne Johnson commented on AXISCPP-1031:
----------------------------------------
Send me a patch and I'd be glad to test it. I realize my patch may not be the best solution. It was intended to be quick and dirty.
Thanks.
> SSL_write called with m_sslHandle=null when socket closed
> ---------------------------------------------------------
>
> Key: AXISCPP-1031
> URL: https://issues.apache.org/jira/browse/AXISCPP-1031
> Project: Axis-C++
> Issue Type: Bug
> Components: Transport (axis3)
> Affects Versions: 1.6 Final
> Environment: Testing with Axis[J] on a jetty server. Server has maxIdleTime=60000 (for testing, but any time could be used). WIndowsXP.
> Reporter: Wayne Johnson
> Fix For: 1.6 Final
>
>
> When Jetty closes the socket due to maxIdleTime, the next write (from httptransport.cpp, ~line 264) detects the closure and calls HTTPSSLChannel::OpenSSL_Close(), which sets m_sslHandle = NULL. httptransport.cpp, ~line 265 then calls the m_pActiveChannel->writeBytes() again to send the remainder of the packet (without checking if the first write succeded). The null handle causes a crash.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXISCPP-1031) SSL_write called with
m_sslHandle=null when socket closed
Posted by "Wayne Johnson (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXISCPP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496595 ]
Wayne Johnson commented on AXISCPP-1031:
----------------------------------------
Patch: (Permission is given to include this in the product)
Index: transport/axis3/HTTPSSLChannel/HTTPSSLChannel.cpp
===================================================================
--- transport/axis3/HTTPSSLChannel/HTTPSSLChannel.cpp (revision 516429)
+++ transport/axis3/HTTPSSLChannel/HTTPSSLChannel.cpp (working copy)
@@ -710,8 +710,13 @@
int HTTPSSLChannel::
WriteToSocket( const char * psTxBuffer, int iSize)
{
- int nByteSent;
+ int nByteSent=-1;
+ if (!m_sslHandle)
+ {
+ return -1;
+ }
+
nByteSent = SSL_write( m_sslHandle, (char *) psTxBuffer, iSize);
if(nByteSent < 0)
This could also be fixed by having httptransport.cpp check the return codes from it's calls to writeBytes.
> SSL_write called with m_sslHandle=null when socket closed
> ---------------------------------------------------------
>
> Key: AXISCPP-1031
> URL: https://issues.apache.org/jira/browse/AXISCPP-1031
> Project: Axis-C++
> Issue Type: Bug
> Components: Transport (axis3)
> Affects Versions: 1.6 Final
> Environment: Testing with Axis[J] on a jetty server. Server has maxIdleTime=60000 (for testing, but any time could be used). WIndowsXP.
> Reporter: Wayne Johnson
> Fix For: 1.6 Final
>
>
> When Jetty closes the socket due to maxIdleTime, the next write (from httptransport.cpp, ~line 264) detects the closure and calls HTTPSSLChannel::OpenSSL_Close(), which sets m_sslHandle = NULL. httptransport.cpp, ~line 265 then calls the m_pActiveChannel->writeBytes() again to send the remainder of the packet (without checking if the first write succeded). The null handle causes a crash.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXISCPP-1031) SSL_write called with
m_sslHandle=null when socket closed
Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXISCPP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509936 ]
nadir amra commented on AXISCPP-1031:
-------------------------------------
Wayne, thanks for the info. I put the code into SVN now with your updates included.
I will wait until end of June to whenever you tell to me if sooner to close issue out, unless you feel you need more time.
> SSL_write called with m_sslHandle=null when socket closed
> ---------------------------------------------------------
>
> Key: AXISCPP-1031
> URL: https://issues.apache.org/jira/browse/AXISCPP-1031
> Project: Axis-C++
> Issue Type: Bug
> Components: Transport (axis3)
> Affects Versions: 1.6 Final
> Environment: Testing with Axis[J] on a jetty server. Server has maxIdleTime=60000 (for testing, but any time could be used). WIndowsXP.
> Reporter: Wayne Johnson
> Fix For: 1.6 Final
>
> Attachments: HTTPSSLChannel.cpp, HTTPSSLChannel.cpp, HTTPSSLChannel.hpp
>
>
> When Jetty closes the socket due to maxIdleTime, the next write (from httptransport.cpp, ~line 264) detects the closure and calls HTTPSSLChannel::OpenSSL_Close(), which sets m_sslHandle = NULL. httptransport.cpp, ~line 265 then calls the m_pActiveChannel->writeBytes() again to send the remainder of the packet (without checking if the first write succeded). The null handle causes a crash.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXISCPP-1031) SSL_write called with
m_sslHandle=null when socket closed
Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXISCPP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496748 ]
nadir amra commented on AXISCPP-1031:
-------------------------------------
Wayne,
The code should be throwing an exception on the initial error. It does not. I can make the code changes so that the SSL transport throws an exception (not sure why it does not), but can you test given that I do not have the resources or expertise in open SSL?
Otherwise, I can make your change but I do not think it is the right thing to do....it seems to hide the fact that there was an error.
> SSL_write called with m_sslHandle=null when socket closed
> ---------------------------------------------------------
>
> Key: AXISCPP-1031
> URL: https://issues.apache.org/jira/browse/AXISCPP-1031
> Project: Axis-C++
> Issue Type: Bug
> Components: Transport (axis3)
> Affects Versions: 1.6 Final
> Environment: Testing with Axis[J] on a jetty server. Server has maxIdleTime=60000 (for testing, but any time could be used). WIndowsXP.
> Reporter: Wayne Johnson
> Fix For: 1.6 Final
>
>
> When Jetty closes the socket due to maxIdleTime, the next write (from httptransport.cpp, ~line 264) detects the closure and calls HTTPSSLChannel::OpenSSL_Close(), which sets m_sslHandle = NULL. httptransport.cpp, ~line 265 then calls the m_pActiveChannel->writeBytes() again to send the remainder of the packet (without checking if the first write succeded). The null handle causes a crash.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Resolved: (AXISCPP-1031) SSL_write called with
m_sslHandle=null when socket closed
Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXISCPP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nadir amra resolved AXISCPP-1031.
---------------------------------
Resolution: Fixed
Marking as resolved. Let it stay there for a while.
> SSL_write called with m_sslHandle=null when socket closed
> ---------------------------------------------------------
>
> Key: AXISCPP-1031
> URL: https://issues.apache.org/jira/browse/AXISCPP-1031
> Project: Axis-C++
> Issue Type: Bug
> Components: Transport (axis3)
> Affects Versions: 1.6 Final
> Environment: Testing with Axis[J] on a jetty server. Server has maxIdleTime=60000 (for testing, but any time could be used). WIndowsXP.
> Reporter: Wayne Johnson
> Fix For: 1.6 Final
>
> Attachments: HTTPSSLChannel.cpp, HTTPSSLChannel.cpp, HTTPSSLChannel.hpp
>
>
> When Jetty closes the socket due to maxIdleTime, the next write (from httptransport.cpp, ~line 264) detects the closure and calls HTTPSSLChannel::OpenSSL_Close(), which sets m_sslHandle = NULL. httptransport.cpp, ~line 265 then calls the m_pActiveChannel->writeBytes() again to send the remainder of the packet (without checking if the first write succeded). The null handle causes a crash.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXISCPP-1031) SSL_write called with
m_sslHandle=null when socket closed
Posted by "Wayne Johnson (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXISCPP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498247 ]
Wayne Johnson commented on AXISCPP-1031:
----------------------------------------
I just updated to the latest SVN revisions and had some local patches conflicting, add that to a project wide conversion to VS 2005 and things are a mess here. It will be a day or two till I get that environment set up again.
I'll let you know.
Thanks.
> SSL_write called with m_sslHandle=null when socket closed
> ---------------------------------------------------------
>
> Key: AXISCPP-1031
> URL: https://issues.apache.org/jira/browse/AXISCPP-1031
> Project: Axis-C++
> Issue Type: Bug
> Components: Transport (axis3)
> Affects Versions: 1.6 Final
> Environment: Testing with Axis[J] on a jetty server. Server has maxIdleTime=60000 (for testing, but any time could be used). WIndowsXP.
> Reporter: Wayne Johnson
> Fix For: 1.6 Final
>
> Attachments: HTTPSSLChannel.cpp, HTTPSSLChannel.hpp
>
>
> When Jetty closes the socket due to maxIdleTime, the next write (from httptransport.cpp, ~line 264) detects the closure and calls HTTPSSLChannel::OpenSSL_Close(), which sets m_sslHandle = NULL. httptransport.cpp, ~line 265 then calls the m_pActiveChannel->writeBytes() again to send the remainder of the packet (without checking if the first write succeded). The null handle causes a crash.
--
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org