Hello Ken,
AFAIK standalone jax-ws uses some JDK bundled lightweight web server,
which is not Grizzly.
Thanks.
WBR,
Alexey.
On May 27, 2008, at 10:50 , Ken--_at_newsgroupstats.hk wrote:
>
> I think standalone jax-ws is build from grizzly right? My problem is
> invoking
> an invalid wsdl link will make the server connection leak. I have
> post the
> issue here:
>
> http://forums.java.net/jive/thread.jspa?threadID=41517&tstart=0
>
> Thanks!
>
>
>
>
> Ken--_at_newsgroupstats.hk wrote:
>>
>> Hi,
>>
>> It happen in one of our server with standard alone jax-ws enabled
>> (running
>> jax-ws without servlet container). The number of loopback
>> connections will
>> grow till 5000 connections under windows 2003 server.
>>
>> I have confirmed it today as the problem disappear when web service
>> disabled.
>>
>> Would you pls tell me the detail of the bug?
>>
>> Regards,
>> Ken
>>
>>
>> Jeanfrancois Arcand-2 wrote:
>>>
>>> Hi,
>>>
>>>
>>> Ken--_at_newsgroupstats.hk wrote:
>>>> I know this problem may not due to Grizzly but what I want to
>>>> know is..
>>>> whenever I start a nio server by using java.nio package, there
>>>> exist a
>>>> strange connection with no listening port! Please read the attached
>>>> screen
>>>> shot.
>>>
>>> For Alan Bateman, NIO leads:
>>>
>>> A Selector on Windows has a loopback connection that is used for the
>>> wakeup mechanism. Hence every Selector created will show what you
>>> just
>>> discovered.
>>>
>>>
>>> It it a problem? The SelectorFactory initialize by default a pool of
>>> Selector. We have fixed that recently. Which version of Grizzly
>>> are you
>>> using?
>>>
>>> Thanks
>>>
>>> -- Jeanfrancois
>>>
>>>>
>>>> The original problem is, I have my own nio framework (developed
>>>> in 3-4
>>>> years
>>>> ago). My server is running very well on first 3-4th day but after
>>>> certain of
>>>> time, the server will create many unknown connections like this:
>>>>
>>>> TCP 127.0.0.1:2408 127.0.0.1:2409 ESTABLISHED
>>>> TCP 127.0.0.1:2409 127.0.0.1:2408 ESTABLISHED
>>>> TCP 127.0.0.1:2410 127.0.0.1:2411 ESTABLISHED
>>>> TCP 127.0.0.1:2411 127.0.0.1:2410 ESTABLISHED
>>>> TCP 127.0.0.1:2412 127.0.0.1:2413 ESTABLISHED
>>>> TCP 127.0.0.1:2413 127.0.0.1:2412 ESTABLISHED
>>>>
>>>> before the server go down, it around has 5000 pairs of this kind of
>>>> connections(in windows 2003 server). That why I have to switch to
>>>> grizzly.
>>>>
>>>> So, my question is what's those connection for? what are they?
>>>>
>>>> http://www.nabble.com/file/p17424006/2008-05-23_193552.gif
>>>> 2008-05-23_193552.gif
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>
>>>
>>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/why-there-is-an-unknow-connection-when-starting-a-nio-server--tp17424006p17485839.html
> Sent from the Grizzly - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
