Hello Ken,
Here [1] you can take a look how SOAP/TCP standalone server starts up.
Here is link on jax-ws package, where there is Servlet transport
implementation [2]. IMHO, you can have very similar code with Grizzly.
1) you'll need to create HTTP adapters [3], [4]
2) initialize Grizzly HTTP infrastructure, with custom GrizzlyAdapter
[5] , which will be invoked on each incoming HTTP request.
3) Redirect HTTP request to the corresponding HTTP WS Adapter [6]
Hope this will help.
Thanks.
WBR,
Alexey.
PS: GrizzlyAdapter and WS Adapter are different and not related
things ;) GrizzlyAdapter is servlet-like HTTP handler, WS Adapter
(com.sun.xml.ws.api.server.Adapter) represents WS endpoint.
[1]
http://fisheye5.atlassian.com/browse/wsit/wsit/rt/src/com/sun/xml/ws/transport/tcp/server/WSTCP.java?r=1.8
[2]
http://fisheye5.atlassian.com/browse/jax-ws-sources/jaxws-ri/servlet/src/com/sun/xml/ws/transport/http/servlet
[3]
http://fisheye5.atlassian.com/browse/jax-ws-sources/jaxws-ri/servlet/src/com/sun/xml/ws/transport/http/servlet/WSServletContextListener.java?r=1.4
[4]
http://fisheye5.atlassian.com/browse/jax-ws-sources/jaxws-ri/servlet/src/com/sun/xml/ws/transport/http/servlet/ServletAdapter.java?r=1.9
[5]
http://www.nabble.com/Question-about-http-on-grizzly-td16846432.html
[6]
http://fisheye5.atlassian.com/browse/jax-ws-sources/jaxws-ri/servlet/src/com/sun/xml/ws/transport/http/servlet/WSServletDelegate.java?r=1.6
On Jun 23, 2008, at 5:38 , Ken--_at_newsgroupstats.hk wrote:
>
> Dear Alexey,
>
> Thanks, Pls give me some hints.
>
> Regards,
> Ken
>
>
>
> Oleksiy Stashok wrote:
>>
>> Hello Ken,
>>
>>> Hi,
>>>
>>> I feel very disappointed that they cannot help me to solve the issue
>>> but ask
>>> me to buy a JAVA SE service plan instead. Even up to now, I have no
>>> idea
>>> about the root cause.
>>>
>>> http://forums.java.net/jive/thread.jspa?threadID=41517&tstart=0
>> :((
>>
>>
>>> I know there is a way to config tomcat / jetty on top grizzly. any
>>> chance to
>>> config standalone jax-ws run on grizzly instead of using their buggy
>>> lightweight http server?
>> I think only way for you right now - is to do that yourself. I have
>> an
>> experience implementing SOAP/TCP transport for jax-ws, which uses
>> Grizzly and is able to work in standalone mode.
>> IMHO, similar way it's possible to implement standalone Grizzly
>> support for regular SOAP/HTTP requests... As I understand you need
>> just basic functionality jax-ws proposes, no SOAP security, SOAP
>> reliable or similar?
>> I can point you to SOAP/TCP source code, think this will give you an
>> idea how to implement that.
>>
>> Thanks.
>>
>> WBR,
>> Alexey.
>>
>>>
>>>
>>> Thanks and Regards,
>>> Ken
>>>
>>>
>>>
>>>
>>> Jeanfrancois Arcand-2 wrote:
>>>>
>>>> Salut,
>>>>
>>>> let me ping the NIO lead to see if there is a solution for that.
>>>> I'm
>>>> travelling right now but will try to have a response before the end
>>>> of
>>>> the week. Sorry for the delay.
>>>>
>>>> A+
>>>>
>>>> -- Jeanfrancois
>>>>
>>>>
>>>>
>>>> Ken--_at_newsgroupstats.hk wrote:
>>>>> Sorry about that I have to reply this thread again. I have
>>>>> reported this
>>>>> issue in jax-ws forum for a week but no one replied. (It show that
>>>>> Grizlly
>>>>> community is very helpful instead!)
>>>>>
>>>>> JAX-WS is under glassfish and pls suggest any channels that I can
>>>>> get
>>>>> help
>>>>> from for solving the problem.
>>>>>
>>>>> Regards,
>>>>> Ken
>>>>>
>>>>>
>>>>>
>>>>> Oleksiy Stashok wrote:
>>>>>> 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
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>>>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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--tp17424006p18024042.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
>>>
>>
>>
>> ---------------------------------------------------------------------
>> 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--tp17424006p18062063.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
>
