You are viewing a plain text version of this content. The canonical link for it is here.
Posted to axis1-java-user@axis.apache.org by se...@wipro.com on 2012/02/03 10:10:10 UTC
Regarding CLOSE_WAIT issue in Axis 1.x
Hello Team,
In our project we have Axis1.2 been integrated with Tomcat5 and used for
the past few years.
We face CLOSE_WAIT(as in JIRA AXIS2-2883
<https://issues.apache.org/jira/browse/AXIS2-2883> ) issue and from the
release notes of Axis2 1.5.1, it is inferred that the issue is resolved
in this release.
So, we are thought of migrating from axis1.2 to axis2 1.5.1, only to
solve this CLOSE_WAIT issue in particular.
But I learnt that Axis1 to Axis2 is a major design change and could
involve more complexities.
Is there is any patch/workaround to solve this issue on top Axis1.2
itself?
Please support regarding this.
With Best Regards,
Senthil Kumar Sekar
Please do not print this email unless it is absolutely necessary.
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
www.wipro.com
Re: Regarding CLOSE_WAIT issue in Axis 1.x
Posted by Andreas Veithen <an...@gmail.com>.
On Mon, Feb 6, 2012 at 08:04, <se...@wipro.com> wrote:
> Hello Andreas,
>
> Thanks for the reply.
>
> I didn't try with Axis1.4, as the below issues are still open.
> https://issues.apache.org/jira/browse/SOAP-170 or
> https://issues.apache.org/jira/browse/AXIS-2430
What makes you sure that the issue you are encountering is identical
to one of these two bug reports?
> The patch in issue SOAP-170 is at client side. I need solution at Axis side?
>
> Is there any other option ?
>
>
> With Regards,
> Senthil Kumar Sekar
>
>
> -----Original Message-----
> From: Andreas Veithen [mailto:andreas.veithen@gmail.com]
> Sent: Saturday, February 04, 2012 3:17 AM
> To: axis1-java-user@axis.apache.org
> Subject: Re: Regarding CLOSE_WAIT issue in Axis 1.x
>
> It may be simpler to upgrade to Axis 1.4. Did you test with that version?
>
> Also, is the issue with Axis 1.x described somewhere? E.g. does it
> match https://issues.apache.org/jira/browse/SOAP-170 or
> https://issues.apache.org/jira/browse/AXIS-2430?
>
> Andreas
>
> On Fri, Feb 3, 2012 at 10:10, <se...@wipro.com> wrote:
>> Hello Team,
>>
>>
>>
>> In our project we have Axis1.2 been integrated with Tomcat5 and used for
>> the past few years.
>>
>>
>>
>> We face CLOSE_WAIT(as in JIRA AXIS2-2883
>> <https://issues.apache.org/jira/browse/AXIS2-2883> ) issue and from the
>> release notes of Axis2 1.5.1, it is inferred that the issue is resolved
>> in this release.
>>
>>
>>
>> So, we are thought of migrating from axis1.2 to axis2 1.5.1, only to
>> solve this CLOSE_WAIT issue in particular.
>>
>>
>>
>> But I learnt that Axis1 to Axis2 is a major design change and could
>> involve more complexities.
>>
>>
>>
>> Is there is any patch/workaround to solve this issue on top Axis1.2
>> itself?
>>
>>
>>
>> Please support regarding this.
>>
>>
>>
>> With Best Regards,
>>
>> Senthil Kumar Sekar
>>
>>
>>
>>
>> Please do not print this email unless it is absolutely necessary.
>>
>> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
>>
>> WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
>>
>> www.wipro.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis1-java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: axis1-java-user-help@axis.apache.org
>
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
>
> www.wipro.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis1-java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: axis1-java-user-help@axis.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis1-java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: axis1-java-user-help@axis.apache.org
RE: Regarding CLOSE_WAIT issue in Axis 1.x
Posted by se...@wipro.com.
Hello Andreas,
Thanks for the reply.
I didn't try with Axis1.4, as the below issues are still open.
https://issues.apache.org/jira/browse/SOAP-170 or
https://issues.apache.org/jira/browse/AXIS-2430
The patch in issue SOAP-170 is at client side. I need solution at Axis side?
Is there any other option ?
With Regards,
Senthil Kumar Sekar
-----Original Message-----
From: Andreas Veithen [mailto:andreas.veithen@gmail.com]
Sent: Saturday, February 04, 2012 3:17 AM
To: axis1-java-user@axis.apache.org
Subject: Re: Regarding CLOSE_WAIT issue in Axis 1.x
It may be simpler to upgrade to Axis 1.4. Did you test with that version?
Also, is the issue with Axis 1.x described somewhere? E.g. does it
match https://issues.apache.org/jira/browse/SOAP-170 or
https://issues.apache.org/jira/browse/AXIS-2430?
Andreas
On Fri, Feb 3, 2012 at 10:10, <se...@wipro.com> wrote:
> Hello Team,
>
>
>
> In our project we have Axis1.2 been integrated with Tomcat5 and used for
> the past few years.
>
>
>
> We face CLOSE_WAIT(as in JIRA AXIS2-2883
> <https://issues.apache.org/jira/browse/AXIS2-2883> ) issue and from the
> release notes of Axis2 1.5.1, it is inferred that the issue is resolved
> in this release.
>
>
>
> So, we are thought of migrating from axis1.2 to axis2 1.5.1, only to
> solve this CLOSE_WAIT issue in particular.
>
>
>
> But I learnt that Axis1 to Axis2 is a major design change and could
> involve more complexities.
>
>
>
> Is there is any patch/workaround to solve this issue on top Axis1.2
> itself?
>
>
>
> Please support regarding this.
>
>
>
> With Best Regards,
>
> Senthil Kumar Sekar
>
>
>
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
>
> www.wipro.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis1-java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: axis1-java-user-help@axis.apache.org
Please do not print this email unless it is absolutely necessary.
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
www.wipro.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis1-java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: axis1-java-user-help@axis.apache.org
Re: Regarding CLOSE_WAIT issue in Axis 1.x
Posted by Andreas Veithen <an...@gmail.com>.
It may be simpler to upgrade to Axis 1.4. Did you test with that version?
Also, is the issue with Axis 1.x described somewhere? E.g. does it
match https://issues.apache.org/jira/browse/SOAP-170 or
https://issues.apache.org/jira/browse/AXIS-2430?
Andreas
On Fri, Feb 3, 2012 at 10:10, <se...@wipro.com> wrote:
> Hello Team,
>
>
>
> In our project we have Axis1.2 been integrated with Tomcat5 and used for
> the past few years.
>
>
>
> We face CLOSE_WAIT(as in JIRA AXIS2-2883
> <https://issues.apache.org/jira/browse/AXIS2-2883> ) issue and from the
> release notes of Axis2 1.5.1, it is inferred that the issue is resolved
> in this release.
>
>
>
> So, we are thought of migrating from axis1.2 to axis2 1.5.1, only to
> solve this CLOSE_WAIT issue in particular.
>
>
>
> But I learnt that Axis1 to Axis2 is a major design change and could
> involve more complexities.
>
>
>
> Is there is any patch/workaround to solve this issue on top Axis1.2
> itself?
>
>
>
> Please support regarding this.
>
>
>
> With Best Regards,
>
> Senthil Kumar Sekar
>
>
>
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
>
> www.wipro.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis1-java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: axis1-java-user-help@axis.apache.org