Re: Address already in use: connect
Seems like a good idea to me!
Can you please raise a JIRA under the improvement tag?
Paul
On Nov 14, 2007 2:46 PM, Pär Malmqvist <[EMAIL PROTECTED]> wrote:
> Hello!
>
> The problem with "Address already in use: connect" exception for an
> Axis2 client when executing thousends of calls
> is solved by:
>
>
> Options options =
> stub._getServiceClient().getOptions(); options.setProperty(HTTPConstants.*
> REUSE_HTTP_CLIENT*, Boolean.*TRUE*);
>
> So it might be good to change the default value for HTTPConstants.*
> REUSE_HTTP_CLIENT*
> to TRUE for the client generated by the wsdl2java tool.
>
> What do you gurus think?
>
> /Pär
>
>
>
>
>
>
> > Subject: Re: Address already in use: connect
> > From: [EMAIL PROTECTED]
> > To: axis-user@ws.apache.org
> > Date: Wed, 10 Oct 2007 10:54:29 +0100
>
> >
> > Try to set some custom options [1], like caching/reusing the same http
> > client and throttling the max number of connections.
> >
> > Michele
> >
> > [1]
> >
> http://svn.apache.org/viewcvs.cgi//webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/async/AsyncService2Test.java
> >
> >
> > On Wed, 2007-10-10 at 11:13 +0200, Pär Malmqvist wrote:
> > > Hi!
> > >
> > > I have written a simple blocking client using Axis2 1.3 API's.
> > >
> > > When I do like this:
> > >
> > > for(int i = 0; i < 100; i++) {
> > > ...
> > > ServiceClient sender = new ServiceClient();
> > > sender.sendReceive(payload);
> > > ...
> > > }
> > >
> > > there is no problem. The client runs for many hours.
> > >
> > >
> > >
> > > When I do like this:
> > >
> > > ServiceClient sender = new ServiceClient();
> > >
> > > for(int i = 0; i < 100; i++) {
> > > ...
> > > sender.sendReceive(payload);
> > >
> > > sender.cleanup();
> > > sender.cleanupTransport();
> > >
> > > }
> > >
> > > I get exception AxisFault: Address already in use: connect
> > > after a couple of thousand calls.
> > >
> > > It seems to be something wrong in the ServiceClient class which
> > > shows up after a while.
> > > Any ideas?
> > >
> > > /Pär Malmqvist
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > __
> > > Explore the seven wonders of the world Learn more!
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
> --
> Get news, entertainment and everything you care about at Live.com. Check
> it out! <http://www.live.com/getstarted.aspx+>
>
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
RE: Address already in use: connect
Hi Michele!
I have also added:
options.setCallTransportCleanup(true);
to my generated client.
Do you know of any more cleanup calls I should do to use the wsdl2java
generated client in a correct way?
My main goal is to to get the wsdl2java client work fine.
/Pär
> From: [EMAIL PROTECTED]> Subject: Re: Address already in use: connect> Date:
> Wed, 14 Nov 2007 14:50:48 +> To: axis-user@ws.apache.org> > I think that
> this is not solution.> > The problem arises because your code doesn't cleanup
> the used > resources properly.> When you (re)use the same http client you
> can't see the problem only > because you're using only 1 object.> > Michele>
> > On 14 Nov 2007, at 14:46, Pär Malmqvist wrote:> > > Hello!> >> > The
> problem with "Address already in use: connect" exception for an > > Axis2
> client when executing thousends of calls> > is solved by:> >> > Options
> options = stub._getServiceClient().getOptions();> >> >
> options.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, Boolean.TRUE);> >> > So
> it might be good to change the default value for > >
> HTTPConstants.REUSE_HTTP_CLIENT> > to TRUE for the client generated by the
> wsdl2java tool.> >> > What do you gurus think?> >> > /Pär> >> >> >> >> >> >>
> > > Subject: Re: Address already in use: connect> > > From: [EMAIL
> PROTECTED]> > > To: axis-user@ws.apache.org> > > Date: Wed, 10 Oct 2007
> 10:54:29 +0100> > >> > > Try to set some custom options [1], like
> caching/reusing the same > > http> > > client and throttling the max number
> of connections.> > >> > > Michele> > >> > > [1]> > >
> http://svn.apache.org/viewcvs.cgi//webservices/axis2/trunk/java/ > >
> modules/integration/test/org/apache/axis2/async/AsyncService2Test.java> > >>
> > >> > > On Wed, 2007-10-10 at 11:13 +0200, Pär Malmqvist wrote:> > > > Hi!>
> > > >> > > > I have written a simple blocking client using Axis2 1.3 API's.>
> > > >> > > > When I do like this:> > > >> > > > for(int i = 0; i < 100;
> i++) {> > > > ...> > > > ServiceClient sender = new ServiceClient();> > > >
> sender.sendReceive(payload);> > > > ...> > > > }> > > >> > > > there is no
> problem. The client runs for many hours.> > > >> > > >> > > >> > > > When I
> do like this:> > > >> > > > ServiceClient sender = new ServiceClient();> > >
> >> > > > for(int i = 0; i < 100; i++) {> > > > ...> > > >
> sender.sendReceive(payload);> > > > > > > > sender.cleanup();> > > >
> sender.cleanupTransport();> > > >> > > > }> > > >> > > > I get exception
> AxisFault: Address already in use: connect> > > > after a couple of
> thousand calls.> > > >> > > > It seems to be something wrong in the
> ServiceClient class which> > > > shows up after a while.> > > > Any ideas?> >
> > >> > > > /Pär Malmqvist> > > >> > > >> > > >> > > >> > > >> > > >> > > >> >
> > >> > > >> > > > > >
> __> > > >
> Explore the seven wonders of the world Learn more!> > >> > >> > > > >
> -> > > To
> unsubscribe, e-mail: [EMAIL PROTECTED]> > > For additional commands, e-mail:
> [EMAIL PROTECTED]> > >> >> >> > Get news, entertainment and everything you
> care about at Live.com. > > Check it out!> > >
> -> To
> unsubscribe, e-mail: [EMAIL PROTECTED]> For additional commands, e-mail:
> [EMAIL PROTECTED]>
_
Connect to the next generation of MSN Messenger
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline
Re: Address already in use: connect
> Hello! > > The problem with "Address already in use: connect" exception for an > Axis2 client when executing thousends of calls > is solved by: > > > Options options = stub._getServiceClient().getOptions(); > > options.setProperty(HTTPConstants./REUSE_HTTP_CLIENT/, Boolean./TRUE/); > > So it might be good to change the default value for > HTTPConstants./REUSE_HTTP_CLIENT/ > to TRUE for the client generated by the wsdl2java tool. Try to do stub._getServiceClient().cleanupTransport(); Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Address already in use: connect
I think that this is not solution.
The problem arises because your code doesn't cleanup the used
resources properly.
When you (re)use the same http client you can't see the problem only
because you're using only 1 object.
Michele
On 14 Nov 2007, at 14:46, Pär Malmqvist wrote:
Hello!
The problem with "Address already in use: connect" exception for an
Axis2 client when executing thousends of calls
is solved by:
Options options = stub._getServiceClient().getOptions();
options.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, Boolean.TRUE);
So it might be good to change the default value for
HTTPConstants.REUSE_HTTP_CLIENT
to TRUE for the client generated by the wsdl2java tool.
What do you gurus think?
/Pär
> Subject: Re: Address already in use: connect
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
> Date: Wed, 10 Oct 2007 10:54:29 +0100
>
> Try to set some custom options [1], like caching/reusing the same
http
> client and throttling the max number of connections.
>
> Michele
>
> [1]
> http://svn.apache.org/viewcvs.cgi//webservices/axis2/trunk/java/
modules/integration/test/org/apache/axis2/async/AsyncService2Test.java
>
>
> On Wed, 2007-10-10 at 11:13 +0200, Pär Malmqvist wrote:
> > Hi!
> >
> > I have written a simple blocking client using Axis2 1.3 API's.
> >
> > When I do like this:
> >
> > for(int i = 0; i < 100; i++) {
> > ...
> > ServiceClient sender = new ServiceClient();
> > sender.sendReceive(payload);
> > ...
> > }
> >
> > there is no problem. The client runs for many hours.
> >
> >
> >
> > When I do like this:
> >
> > ServiceClient sender = new ServiceClient();
> >
> > for(int i = 0; i < 100; i++) {
> > ...
> > sender.sendReceive(payload);
> >
> > sender.cleanup();
> > sender.cleanupTransport();
> >
> > }
> >
> > I get exception AxisFault: Address already in use: connect
> > after a couple of thousand calls.
> >
> > It seems to be something wrong in the ServiceClient class which
> > shows up after a while.
> > Any ideas?
> >
> > /Pär Malmqvist
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
__
> > Explore the seven wonders of the world Learn more!
>
>
>
-
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
Get news, entertainment and everything you care about at Live.com.
Check it out!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Address already in use: connect
Hello!
The problem with "Address already in use: connect" exception for an Axis2
client when executing thousends of calls is solved by:
Options options = stub._getServiceClient().getOptions();
options.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, Boolean.TRUE);
So it might be good to change the default value for
HTTPConstants.REUSE_HTTP_CLIENT
to TRUE for the client generated by the wsdl2java tool.
What do you gurus think?
/Pär
> Subject: Re: Address already in use: connect> From: [EMAIL PROTECTED]> To:
> axis-user@ws.apache.org> Date: Wed, 10 Oct 2007 10:54:29 +0100> > Try to set
> some custom options [1], like caching/reusing the same http> client and
> throttling the max number of connections.> > Michele> > [1]>
> http://svn.apache.org/viewcvs.cgi//webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/async/AsyncService2Test.java>
> > > On Wed, 2007-10-10 at 11:13 +0200, Pär Malmqvist wrote:> > Hi!> > > > I
> have written a simple blocking client using Axis2 1.3 API's.> > > > When I do
> like this:> > > > for(int i = 0; i < 100; i++) {> > ...> > ServiceClient
> sender = new ServiceClient();> > sender.sendReceive(payload);> > ...> > }> >
> > > there is no problem. The client runs for many hours.> > > > > > > > When
> I do like this:> > > > ServiceClient sender = new ServiceClient();> > > >
> for(int i = 0; i < 100; i++) {> > ...> > sender.sendReceive(payload);> >
> > > sender.cleanup();> > sender.cleanupTransport();> > > > }> > > > I get
> exception AxisFault: Address already in use: connect> > after a couple of
> thousand calls.> > > > It seems to be something wrong in the ServiceClient
> class which> > shows up after a while.> > Any ideas?> > > > /Pär Malmqvist> >
> > > > > > > > > > > > > > > > > > >
> __> >
> Explore the seven wonders of the world Learn more!> > >
> -> To
> unsubscribe, e-mail: [EMAIL PROTECTED]> For additional commands, e-mail:
> [EMAIL PROTECTED]>
_
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx
RE: WSDL2Java, Address already in use: connect
On Sat, 2007-10-13 at 11:00 +0200, Pär Malmqvist wrote: > I guess the solution you gave me works for both cases, but in this > case I would like to get a generated client that works fine with not > much work. > Not that I am that lazy but I think of the people that dont have that > much knowledge about Axis2 and we want everybody to use Axis2 in a > simple way! The simple way allows you to achieve simple goals (i.e. single invocation). If you want something more complicated you'll need more advanced settings. Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: WSDL2Java, Address already in use: connect
Hi Michele! Yes I know about your other reply, it was my question that one too... :) Thanks! I guess the solution you gave me works for both cases, but in this case I would like to get a generated client that works fine with not much work. Not that I am that lazy but I think of the people that dont have that much knowledge about Axis2 and we want everybody to use Axis2 in a simple way! So it would be nice to here the opinion from anyone working with the WSDL2Java tool. Regards Pär Malmqvist > Subject: Re: WSDL2Java, Address already in use: connect> From: [EMAIL > PROTECTED]> To: axis-user@ws.apache.org> Date: Fri, 12 Oct 2007 16:11:33 > +0100> > A question like yours - with related reply - was sent to this > mailing> list 2 days ago.> > Michele> > On Fri, 2007-10-12 at 16:05 +0200, > Pär Malmqvist wrote:> > Hi!> > > > I am using Axis2 1.3 and have generated a > client of type xmlbeans with> > WSDL2Java.> > > > I am using the constructor: > stub = new MyServiceStub(endPoint);> > Then I create my request and execute > the service and it works fine.> > > > But when I have done a couple of > thousands requests I get the> > exception:> > Address already in use: > connect.> > > > Is there something wrong in the generated client or am I > using it> > wrong?> > > > /Pär Malmqvist> > > > > > > > > > > > > __> > > Invite your mail contacts to join your friends list with Windows Live> > > Spaces. It's easy! Try it!> > > > -> To > unsubscribe, e-mail: [EMAIL PROTECTED]> For additional commands, e-mail: > [EMAIL PROTECTED]> _ Discover the new Windows Vista http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE
Re: WSDL2Java, Address already in use: connect
A question like yours - with related reply - was sent to this mailing list 2 days ago. Michele On Fri, 2007-10-12 at 16:05 +0200, Pär Malmqvist wrote: > Hi! > > I am using Axis2 1.3 and have generated a client of type xmlbeans with > WSDL2Java. > > I am using the constructor: stub = new MyServiceStub(endPoint); > Then I create my request and execute the service and it works fine. > > But when I have done a couple of thousands requests I get the > exception: > Address already in use: connect. > > Is there something wrong in the generated client or am I using it > wrong? > > /Pär Malmqvist > > > > > > __ > Invite your mail contacts to join your friends list with Windows Live > Spaces. It's easy! Try it! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WSDL2Java, Address already in use: connect
Hi! I am using Axis2 1.3 and have generated a client of type xmlbeans with WSDL2Java. I am using the constructor: stub = new MyServiceStub(endPoint); Then I create my request and execute the service and it works fine. But when I have done a couple of thousands requests I get the exception: Address already in use: connect. Is there something wrong in the generated client or am I using it wrong? /Pär Malmqvist _ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us
Re: Address already in use: connect
Try to set some custom options [1], like caching/reusing the same http
client and throttling the max number of connections.
Michele
[1]
http://svn.apache.org/viewcvs.cgi//webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/async/AsyncService2Test.java
On Wed, 2007-10-10 at 11:13 +0200, Pär Malmqvist wrote:
> Hi!
>
> I have written a simple blocking client using Axis2 1.3 API's.
>
> When I do like this:
>
> for(int i = 0; i < 100; i++) {
> ...
> ServiceClient sender = new ServiceClient();
> sender.sendReceive(payload);
> ...
> }
>
> there is no problem. The client runs for many hours.
>
>
>
> When I do like this:
>
> ServiceClient sender = new ServiceClient();
>
> for(int i = 0; i < 100; i++) {
> ...
> sender.sendReceive(payload);
>
> sender.cleanup();
> sender.cleanupTransport();
>
> }
>
> I get exception AxisFault: Address already in use: connect
> after a couple of thousand calls.
>
> It seems to be something wrong in the ServiceClient class which
> shows up after a while.
> Any ideas?
>
> /Pär Malmqvist
>
>
>
>
>
>
>
>
>
> __
> Explore the seven wonders of the world Learn more!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Address already in use: connect
Hi!
I have written a simple blocking client using Axis2 1.3 API's.
When I do like this:
for(int i = 0; i < 100; i++) {
...
ServiceClient sender = new ServiceClient();
sender.sendReceive(payload);
...
}
there is no problem. The client runs for many hours.
When I do like this:
ServiceClient sender = new ServiceClient();
for(int i = 0; i < 100; i++) {
...
sender.sendReceive(payload);
sender.cleanup();
sender.cleanupTransport();
}
I get exception AxisFault: Address already in use: connect
after a couple of thousand calls.
It seems to be something wrong in the ServiceClient class which shows up after
a while.
Any ideas?
/Pär Malmqvist
_
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE
AW: AW: Axis 1.3 Address already in use: connect-> java.net.BindException
Hi, i see it right that this is a clientside issue, or? The client must do the change on his regestry, not the server, because he did't bind? Thanks. Dirk > -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 8. November 2005 17:34 > An: axis-user@ws.apache.org > Betreff: Re: AW: Axis 1.3 Address already in use: connect-> > java.net.BindException > > Dirk wrote: > > So the best is to wait between the requests? > > We made the registry changes as outlined in the original document; > decreased the amount of time spent in TIME_WAIT state, and increased the > number of TCP/IP dynamic ports available--it enabled us to more than > double > the number of virtual users during performance testing without > encountering > these errors. > > If you can't (or don't want to) modify your Windows registry, then you'll > need to keep those simultaneous requests at a lower level, or accept that > some of them will fail... or, as you said, modify your code in some way so > that you don't overload the available ports. > > Meghan > > _ > Meghan Pietila > Java Middleware Architect > Sales & Service Management Program > US Bank > > > -- > > Electronic Privacy Notice. This e-mail, and any attachments, contains > information that is, or may be, covered by electronic communications > privacy laws, and is also confidential and proprietary in nature. If you > are not the intended recipient, please be advised that you are legally > prohibited from retaining, using, copying, distributing, or otherwise > disclosing this information in any manner. Instead, please reply to the > sender that you have received this communication in error, and then > immediately delete it. Thank you in advance for your cooperation. > == >
Re: AW: Axis 1.3 Address already in use: connect-> java.net.BindException
Dirk wrote: > So the best is to wait between the requests? We made the registry changes as outlined in the original document; decreased the amount of time spent in TIME_WAIT state, and increased the number of TCP/IP dynamic ports available--it enabled us to more than double the number of virtual users during performance testing without encountering these errors. If you can't (or don't want to) modify your Windows registry, then you'll need to keep those simultaneous requests at a lower level, or accept that some of them will fail... or, as you said, modify your code in some way so that you don't overload the available ports. Meghan _ Meghan Pietila Java Middleware Architect Sales & Service Management Program US Bank -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. ==
AW: Axis 1.3 Address already in use: connect-> java.net.BindException
Whow, thanks for this.
So the best is to wait between the requests?
Thanks.
Dirk
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 8. November 2005 16:29
> An: axis-user@ws.apache.org
> Betreff: Re: Axis 1.3 Address already in use: connect->
> java.net.BindException
>
> Funny that you ask that, we just spent a few weeks debugging the same
> error
> in our performance testing (we deploy to servers running Windows for this
> application).
>
> After much Google searching by all of us, our very astute WebSphere
> support
> guy found this article (sorry, I don't know where he found it, so can't
> give it proper attribution):
>
> (See attached file: WindowsPortConfig.doc)
>
> Basically, it was a Windows operating system default setting limitation.
> He also commented that he had searched the Microsoft Web site, and had
> some
> indications that the default value for MaxUserPort is set to 5000.
>
> Hope this is helpful,
>
> Meghan
>
> _
> Meghan Pietila
> Java Middleware Architect
> Sales & Service Management Program
> US Bank
>
>
>
>
> "Bromberg, Dirk -
> encoway" To: axis-
> [EMAIL PROTECTED]
> <[EMAIL PROTECTED]cc:
> .de> Subject: Axis 1.3 Address
> already in use: connect-> java.net.BindException
>
> 11/08/2005 07:10
> AM
> Please respond to
> axis-user
>
>
>
>
>
>
> Hello,
>
> I've setup a webservice using tomcat and axis 1.3 via ant.
>
> It is a simple object with a method. When I call it thousand times (e.g.
> in a loop) than sometimes I get this exception:
>
> ------------
> AxisFault
> faultCode:
> {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> faultSubcode:
> faultString: java.net.BindException: Address already in use: connect
> faultActor:
> faultNode:
> faultDetail:
>
> {http://xml.apache.org/axis/}stackTrace:java.net.BindException:
> Address already in use: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> ---
>
>
> after it the service works like before...
>
>
> Must I close something or synchronize the service method?
>
>
> Thanks
>
> Dirk
>
>
>
>
> --
>
> Electronic Privacy Notice. This e-mail, and any attachments, contains
> information that is, or may be, covered by electronic communications
> privacy laws, and is also confidential and proprietary in nature. If you
> are not the intended recipient, please be advised that you are legally
> prohibited from retaining, using, copying, distributing, or otherwise
> disclosing this information in any manner. Instead, please reply to the
> sender that you have received this communication in error, and then
> immediately delete it. Thank you in advance for your cooperation.
> ==
>
Re: Axis 1.3 Address already in use: connect-> java.net.BindException
Funny that you ask that, we just spent a few weeks debugging the same error
in our performance testing (we deploy to servers running Windows for this
application).
After much Google searching by all of us, our very astute WebSphere support
guy found this article (sorry, I don't know where he found it, so can't
give it proper attribution):
(See attached file: WindowsPortConfig.doc)
Basically, it was a Windows operating system default setting limitation.
He also commented that he had searched the Microsoft Web site, and had some
indications that the default value for MaxUserPort is set to 5000.
Hope this is helpful,
Meghan
_
Meghan Pietila
Java Middleware Architect
Sales & Service Management Program
US Bank
"Bromberg, Dirk -
encoway" To:
axis-user@ws.apache.org
<[EMAIL PROTECTED]cc:
.de> Subject: Axis 1.3 Address
already in use: connect-> java.net.BindException
11/08/2005 07:10
AM
Please respond to
axis-user
Hello,
I've setup a webservice using tomcat and axis 1.3 via ant.
It is a simple object with a method. When I call it thousand times (e.g.
in a loop) than sometimes I get this exception:
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.BindException: Address already in use: connect
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.BindException:
Address already in use: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
---
after it the service works like before...
Must I close something or synchronize the service method?
Thanks
Dirk
--
Electronic Privacy Notice. This e-mail, and any attachments, contains
information that is, or may be, covered by electronic communications privacy
laws, and is also confidential and proprietary in nature. If you are not the
intended recipient, please be advised that you are legally prohibited from
retaining, using, copying, distributing, or otherwise disclosing this
information in any manner. Instead, please reply to the sender that you have
received this communication in error, and then immediately delete it. Thank you
in advance for your cooperation.
==
WindowsPortConfig.doc
Description: MS-Word document
Axis 1.3 Address already in use: connect-> java.net.BindException
Hello,
I've setup a webservice using tomcat and axis 1.3 via ant.
It is a simple object with a method. When I call it thousand times (e.g.
in a loop) than sometimes I get this exception:
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.BindException: Address already in use: connect
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.BindException:
Address already in use: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
---
after it the service works like before...
Must I close something or synchronize the service method?
Thanks
Dirk
