You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Michele Mazzucco <Mi...@ncl.ac.uk> on 2006/08/17 16:32:04 UTC
[Axis2] multiple ServiceClients problem
Hi all,
I have to spare some threads, and each of them creates a new
ServiceClient object in order to send messages. Now the problem is that
they fail, since they try to use the same port (I guess). Is there any
possibility to specify which port should they use?
Thanks,
Michele
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] multiple ServiceClients problem
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Hi Bin,
no, I think my problem is different:
org.apache.axis2.transport.http.SimpleHTTPServer.start
(SimpleHTTPServer.java:184) ERROR [pool-1-thread-1] -
java.net.BindException: Address already in use
[java] ERROR Sender:run Failed send #0
[java] ncl.qosp.test.functional.client.Sender.run(Sender.java:
141) ERROR [pool-1-thread-1] - Failed send #0
[java] ERROR Sender:logException ERROR!:
[java] ncl.qosp.test.functional.client.Sender.logException
(Sender.java:171) ERROR [pool-1-thread-1] - ERROR!:
[java] ERROR Sender:logException org.apache.axis2.AxisFault:
Address already in use; nested exception is:
[java] java.net.BindException: Address already in use
[java] at
org.apache.axis2.transport.http.SimpleHTTPServer.start
(SimpleHTTPServer.java:185)
[java] at
org.apache.axis2.engine.ListenerManager.addListener
(ListenerManager.java:178)
[java] at
org.apache.axis2.description.ClientUtils.inferInTransport
(ClientUtils.java:102)
[java] at
org.apache.axis2.description.OutInAxisOperationClient.execute
(OutInAxisOperation.java:248)
[java] at
org.apache.axis2.client.ServiceClient.sendReceiveNonBlocking
(ServiceClient.java:582)
[java] at
org.apache.axis2.client.ServiceClient.sendReceiveNonBlocking
(ServiceClient.java:555)
[java] at ncl.qosp.test.functional.client.Sender.run
(Sender.java:134)
[java] at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:650)
[java] at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:675)
[java] at java.lang.Thread.run(Thread.java:613)
[java] Caused by: java.net.BindException: Address already in use
[java] at java.net.PlainSocketImpl.socketBind(Native Method)
[java] at java.net.PlainSocketImpl.bind
(PlainSocketImpl.java:359)
[java] at java.net.ServerSocket.bind(ServerSocket.java:319)
[java] at java.net.ServerSocket.<init>(ServerSocket.java:185)
[java] at java.net.ServerSocket.<init>(ServerSocket.java:97)
[java] at
org.apache.axis2.transport.http.server.DefaultConnectionListener.<init>(
DefaultConnectionListener.java:64)
[java] at
org.apache.axis2.transport.http.server.HttpFactory.newRequestConnectionL
istener(HttpFactory.java:199)
[java] at
org.apache.axis2.transport.http.server.SimpleHttpServer.init
(SimpleHttpServer.java:80)
[java] at
org.apache.axis2.transport.http.SimpleHTTPServer.start
(SimpleHTTPServer.java:181)
[java] ... 9 more
Regards,
Michele
On 17 Aug 2006, at 18:10, Bin Zhou wrote:
> Michele Mazzucco <Michele.Mazzucco <at> ncl.ac.uk> writes:
>
>>
>> Hi all,
>>
>> I have to spare some threads, and each of them creates a new
>> ServiceClient object in order to send messages. Now the problem is
>> that
>> they fail, since they try to use the same port (I guess). Is there
>> any
>> possibility to specify which port should they use?
>>
>> Thanks,
>> Michele
>>
>
>
>
> Hi Michele,
>
> I met the same problem too. I also try to use another thread to create
> ServiceClient for sending message. The exceptions seems like the
> following
> (sorry for the long list).
>
> Is that similar to yours?
>
> wishes,
> Bin
>
> -------------------------------------------------------
> org.apache.axis2.AxisFault: null; nested exception is:
> java.lang.NullPointerException
> at org.apache.axis2.description.OutInAxisOperationClient.execute
> (OutInAxisOperation.java:287)
> at org.apache.axis2.client.ServiceClient.sendReceive
> (ServiceClient.java:457)
> at org.apache.axis2.client.ServiceClient.sendReceive
> (ServiceClient.java:399)
> at aop.core.Agent.processMails(Agent.java:140)
> at aop.core.Agent.run(Agent.java:116)
> Caused by: java.lang.Exception: org.apache.axis2.AxisFault: null;
> nested
> exception is:
> java.lang.NullPointerException
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:318)
> at
> org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLo
> gic
> (RawXMLINOutMessageReceiver.java:126)
> at
> org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive
> (AbstractInOutSyncMessageReceiver.java:37)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequ
> est
> (HTTPTransportUtils.java:284)
> at org.apache.axis2.transport.http.AxisServlet.doPost
> (AxisServlet.java:136)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
> (ApplicationFilterChain.java:237)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter
> (ApplicationFilterChain.java:157)
> at org.apache.catalina.core.StandardWrapperValve.invoke
> (StandardWrapperValve.java:214)
> at org.apache.catalina.core.StandardValveContext.invokeNext
> (StandardValveContext.java:104)
> at org.apache.catalina.core.StandardPipeline.invoke
> (StandardPipeline.java:520)
> at org.apache.catalina.core.StandardContextValve.invokeInternal
> (StandardContextValve.java:198)
> at org.apache.catalina.core.StandardContextValve.invoke
> (StandardContextValve.java:152)
> at org.apache.catalina.core.StandardValveContext.invokeNext
> (StandardValveContext.java:104)
> at org.apache.catalina.core.StandardPipeline.invoke
> (StandardPipeline.java:520)
> at org.apache.catalina.core.StandardHostValve.invoke
> (StandardHostValve.java:137)
> at org.apache.catalina.core.StandardValveContext.invokeNext
> (StandardValveContext.java:104)
> at org.apache.catalina.valves.ErrorReportValve.invoke
> (ErrorReportValve.java:117)
> at org.apache.catalina.core.StandardValveContext.invokeNext
> (StandardValveContext.java:102)
> at org.apache.catalina.core.StandardPipeline.invoke
> (StandardPipeline.java:520)
> at org.apache.catalina.core.StandardEngineValve.invoke
> (StandardEngineValve.java:109)
> at org.apache.catalina.core.StandardValveContext.invokeNext
> (StandardValveContext.java:104)
> at org.apache.catalina.core.StandardPipeline.invoke
> (StandardPipeline.java:520)
> at org.apache.catalina.core.ContainerBase.invoke
> (ContainerBase.java:929)
> at org.apache.coyote.tomcat5.CoyoteAdapter.service
> (CoyoteAdapter.java:160)
> at org.apache.coyote.http11.Http11Processor.process
> (Http11Processor.java:799)
> at
> org.apache.coyote.http11.Http11Protocol
> $Http11ConnectionHandler.processConnecti
> on(Http11Protocol.java:705)
> at org.apache.tomcat.util.net.TcpWorkerThread.runIt
> (PoolTcpEndpoint.java:577)
> at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
> (ThreadPool.java:683)
> at java.lang.Thread.run(Thread.java:534)
> Caused by: java.lang.NullPointerException
> at
> org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLo
> gic
> (RawXMLINOutMessageReceiver.java:107)
> ... 30 more
>
> --------------------------------------------------------------
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] multiple ServiceClients problem
Posted by Bin Zhou <bi...@gmail.com>.
Michele Mazzucco <Michele.Mazzucco <at> ncl.ac.uk> writes:
>
> Hi all,
>
> I have to spare some threads, and each of them creates a new
> ServiceClient object in order to send messages. Now the problem is that
> they fail, since they try to use the same port (I guess). Is there any
> possibility to specify which port should they use?
>
> Thanks,
> Michele
>
Hi Michele,
I met the same problem too. I also try to use another thread to create
ServiceClient for sending message. The exceptions seems like the following
(sorry for the long list).
Is that similar to yours?
wishes,
Bin
-------------------------------------------------------
org.apache.axis2.AxisFault: null; nested exception is:
java.lang.NullPointerException
at org.apache.axis2.description.OutInAxisOperationClient.execute
(OutInAxisOperation.java:287)
at org.apache.axis2.client.ServiceClient.sendReceive
(ServiceClient.java:457)
at org.apache.axis2.client.ServiceClient.sendReceive
(ServiceClient.java:399)
at aop.core.Agent.processMails(Agent.java:140)
at aop.core.Agent.run(Agent.java:116)
Caused by: java.lang.Exception: org.apache.axis2.AxisFault: null; nested
exception is:
java.lang.NullPointerException
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:318)
at
org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic
(RawXMLINOutMessageReceiver.java:126)
at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive
(AbstractInOutSyncMessageReceiver.java:37)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest
(HTTPTransportUtils.java:284)
at org.apache.axis2.transport.http.AxisServlet.doPost
(AxisServlet.java:136)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext
(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal
(StandardContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext
(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:520)
at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:137)
at org.apache.catalina.core.StandardValveContext.invokeNext
(StandardValveContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardValveContext.invokeNext
(StandardValveContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:520)
at org.apache.catalina.core.StandardEngineValve.invoke
(StandardEngineValve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext
(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service
(CoyoteAdapter.java:160)
at org.apache.coyote.http11.Http11Processor.process
(Http11Processor.java:799)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnecti
on(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt
(PoolTcpEndpoint.java:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.NullPointerException
at
org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic
(RawXMLINOutMessageReceiver.java:107)
... 30 more
--------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] multiple ServiceClients problem
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Michele;
How do you create ServiceClient ?
You can avoid the problem by sharing the same configurationContext for
each ServiceClient. As you can see when you are creating a serviceClient
you can pass configurationContext ,so create configCtx first and then
create all the serviceClients using that configCtx.
Thanks
Deepal
Michele Mazzucco wrote:
>Hi all,
>
>I have to spare some threads, and each of them creates a new
>ServiceClient object in order to send messages. Now the problem is that
>they fail, since they try to use the same port (I guess). Is there any
>possibility to specify which port should they use?
>
>Thanks,
>Michele
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] multiple ServiceClients problem -- is it a bug???
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Jira AXIS2-1053 created.
Regards,
Michele
On 18 Aug 2006, at 20:07, Eran Chinthaka wrote:
> Can you create an issue out of this, explaining or better attaching
> some
> tests or code for us to re-gen the problem?
>
> Thanks,
> Chinthaka
>
> Michele Mazzucco wrote:
>> Hi again,
>>
>> unfortunately I cannot found a suitable solution for my problem. [1]
>> provides two possible solutions:
>> 1 - use a single sender object for all threads: this is not possible
>> since I want to send messages concurrently
>> 2 - create multiple senders using the same configuration context.
>>
>> According to the second option, the configuration context I'm
>> using is
>> ConfigurationContext configurationContext =
>> ConfigurationContextFactory.createConfigurationContextFromFileSystem(
>> null,
>> null);
>>
>> HttpClient httpClient = new HttpClient(new
>> MultiThreadedHttpConnectionManager());
>> configurationContext.setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
>> Boolean.TRUE);
>> configurationContext.setProperty(HTTPConstants.CACHED_HTTP_CLIENT,
>> httpClient);
>>
>> Now all senders should be able to send messages concurrently
>> (theoretically), but unfortunately they incur in a
>> ConcurrentModificationException
>> when they try to engage the addressing module (there is no way, at
>> least
>> on first instance, to synchronize this operation):
>>
>> Exception in thread "pool-1-thread-1"
>> java.util.ConcurrentModificationException
>> [java] at
>> java.util.AbstractList$Itr.checkForComodification
>> (AbstractList.java:449)
>> [java] at java.util.AbstractList$Itr.next
>> (AbstractList.java:420)
>> [java] at org.apache.axis2.engine.Phase.addHandler
>> (Phase.java:136)
>> [java] at
>> org.apache.axis2.phaseresolver.PhaseHolder.addHandler
>> (PhaseHolder.java:64)
>> [java] at
>> org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToOperation(
>> PhaseResolver.java:191)
>>
>> [java] at
>> org.apache.axis2.description.AxisOperation.engageModuleToOperation
>> (AxisOperation.java:154)
>>
>> [java] at
>> org.apache.axis2.description.AxisOperation.engageModule
>> (AxisOperation.java:128)
>>
>> [java] at
>> org.apache.axis2.description.AxisService.engageModule
>> (AxisService.java:479)
>> [java] at
>> org.apache.axis2.client.ServiceClient.engageModule
>> (ServiceClient.java:271)
>> [java] at
>> ncl.qosp.test.functional.client.Sender.run(Sender.java:138)
>> [java] at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask
>> (ThreadPoolExecutor.java:650)
>>
>> [java] at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run
>> (ThreadPoolExecutor.java:675)
>>
>> [java] at java.lang.Thread.run(Thread.java:613)
>>
>>
>> Is this a bug?
>>
>>
>> Regards,
>> Michele
>>
>>
>>
>> [1] http://www.wso2.net/kb/165
>> On 17 Aug 2006, at 15:32, Michele Mazzucco wrote:
>>
>>> Hi all,
>>>
>>> I have to spare some threads, and each of them creates a new
>>> ServiceClient object in order to send messages. Now the problem
>>> is that
>>> they fail, since they try to use the same port (I guess). Is
>>> there any
>>> possibility to specify which port should they use?
>>>
>>> Thanks,
>>> Michele
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] multiple ServiceClients problem -- is it a bug???
Posted by Eran Chinthaka <ch...@opensource.lk>.
Can you create an issue out of this, explaining or better attaching some
tests or code for us to re-gen the problem?
Thanks,
Chinthaka
Michele Mazzucco wrote:
> Hi again,
>
> unfortunately I cannot found a suitable solution for my problem. [1]
> provides two possible solutions:
> 1 - use a single sender object for all threads: this is not possible
> since I want to send messages concurrently
> 2 - create multiple senders using the same configuration context.
>
> According to the second option, the configuration context I'm using is
> ConfigurationContext configurationContext =
> ConfigurationContextFactory.createConfigurationContextFromFileSystem(null,
> null);
>
> HttpClient httpClient = new HttpClient(new
> MultiThreadedHttpConnectionManager());
> configurationContext.setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
> Boolean.TRUE);
> configurationContext.setProperty(HTTPConstants.CACHED_HTTP_CLIENT,
> httpClient);
>
> Now all senders should be able to send messages concurrently
> (theoretically), but unfortunately they incur in a
> ConcurrentModificationException
> when they try to engage the addressing module (there is no way, at least
> on first instance, to synchronize this operation):
>
> Exception in thread "pool-1-thread-1"
> java.util.ConcurrentModificationException
> [java] at
> java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449)
> [java] at java.util.AbstractList$Itr.next(AbstractList.java:420)
> [java] at org.apache.axis2.engine.Phase.addHandler(Phase.java:136)
> [java] at
> org.apache.axis2.phaseresolver.PhaseHolder.addHandler(PhaseHolder.java:64)
> [java] at
> org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToOperation(PhaseResolver.java:191)
>
> [java] at
> org.apache.axis2.description.AxisOperation.engageModuleToOperation(AxisOperation.java:154)
>
> [java] at
> org.apache.axis2.description.AxisOperation.engageModule(AxisOperation.java:128)
>
> [java] at
> org.apache.axis2.description.AxisService.engageModule(AxisService.java:479)
> [java] at
> org.apache.axis2.client.ServiceClient.engageModule(ServiceClient.java:271)
> [java] at
> ncl.qosp.test.functional.client.Sender.run(Sender.java:138)
> [java] at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>
> [java] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>
> [java] at java.lang.Thread.run(Thread.java:613)
>
>
> Is this a bug?
>
>
> Regards,
> Michele
>
>
>
> [1] http://www.wso2.net/kb/165
> On 17 Aug 2006, at 15:32, Michele Mazzucco wrote:
>
>> Hi all,
>>
>> I have to spare some threads, and each of them creates a new
>> ServiceClient object in order to send messages. Now the problem is that
>> they fail, since they try to use the same port (I guess). Is there any
>> possibility to specify which port should they use?
>>
>> Thanks,
>> Michele
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
Re: [Axis2] multiple ServiceClients problem -- is it a bug???
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Hi again,
unfortunately I cannot found a suitable solution for my problem. [1]
provides two possible solutions:
1 - use a single sender object for all threads: this is not possible
since I want to send messages concurrently
2 - create multiple senders using the same configuration context.
According to the second option, the configuration context I'm using is
ConfigurationContext configurationContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem
(null, null);
HttpClient httpClient = new HttpClient(new
MultiThreadedHttpConnectionManager());
configurationContext.setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.TRUE);
configurationContext.setProperty(HTTPConstants.CACHED_HTTP_CLIENT,
httpClient);
Now all senders should be able to send messages concurrently
(theoretically), but unfortunately they incur in a
ConcurrentModificationException
when they try to engage the addressing module (there is no way, at
least on first instance, to synchronize this operation):
Exception in thread "pool-1-thread-1"
java.util.ConcurrentModificationException
[java] at java.util.AbstractList$Itr.checkForComodification
(AbstractList.java:449)
[java] at java.util.AbstractList$Itr.next(AbstractList.java:
420)
[java] at org.apache.axis2.engine.Phase.addHandler
(Phase.java:136)
[java] at
org.apache.axis2.phaseresolver.PhaseHolder.addHandler
(PhaseHolder.java:64)
[java] at
org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToOperation
(PhaseResolver.java:191)
[java] at
org.apache.axis2.description.AxisOperation.engageModuleToOperation
(AxisOperation.java:154)
[java] at
org.apache.axis2.description.AxisOperation.engageModule
(AxisOperation.java:128)
[java] at
org.apache.axis2.description.AxisService.engageModule
(AxisService.java:479)
[java] at org.apache.axis2.client.ServiceClient.engageModule
(ServiceClient.java:271)
[java] at ncl.qosp.test.functional.client.Sender.run
(Sender.java:138)
[java] at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:650)
[java] at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:675)
[java] at java.lang.Thread.run(Thread.java:613)
Is this a bug?
Regards,
Michele
[1] http://www.wso2.net/kb/165
On 17 Aug 2006, at 15:32, Michele Mazzucco wrote:
> Hi all,
>
> I have to spare some threads, and each of them creates a new
> ServiceClient object in order to send messages. Now the problem is
> that
> they fail, since they try to use the same port (I guess). Is there any
> possibility to specify which port should they use?
>
> Thanks,
> Michele
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org