Grizzly configuration on Glassfish v3
|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
| < Prev | 1 - 2 | Next > |
 |
Grizzly configuration on Glassfish v3
by melshami
::
Rate this Message:
Hi everyone,
I can't seem to find any documentation for how to configure grizlly listeners and connectors on GlassFish v3. So far I can find only this page http://wiki.glassfish.java.net/Wiki.jsp?page=GrizzlyConfigOnePager, which refers to a new scheme and it's not complete yet. Anyone can help with this please? BR, Mohamed |
|
|
Re: Grizzly configuration on Glassfish v3
by Oleksiy Stashok
::
Rate this Message:
Hi Mohamed,
> I can't seem to find any documentation for how to configure grizlly > listeners and connectors on GlassFish v3. Currently doc team is working on that. > So far I can find only this page > http://wiki.glassfish.java.net/Wiki.jsp?page=GrizzlyConfigOnePager, > which > refers to a new scheme and it's not complete yet. > > Anyone can help with this please? Do you have any specific item in mind you'd like to configure? Thanks. WBR, Alexey. > > BR, > Mohamed > -- > View this message in context: http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25750048.html > Sent from the Grizzly - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Grizzly configuration on Glassfish v3
by melshami
::
Rate this Message:
Hi Alexey,
Thanks very much for the prompt reply. I am a bit confused to be honest since I am new to Grizzly. But I wish to configure a listener which listens to custom TCP based protocol. As a starting point I am trying to configure a simple echo server which replies to socket connections on GlassFish v3. Regards, Mohamed
|
|
|
Re: Grizzly configuration on Glassfish v3
by melshami
::
Rate this Message:
For instance is the following configuration is valid:
<http-listener port="8787" id="tcprpc-listener-1" address="0.0.0.0" default-virtual-server="server" server-name="" transport="tcp" protocol="rpc"> </http-listener>
|
|
|
Re: Grizzly configuration on Glassfish v3
by Oleksiy Stashok
::
Rate this Message:
Hi,
you can take a look at config module in grizzly workspace [1]. There you can find unit tests with different configurations like [2], which actually has port unification enabled, but you can redefine config to use X-protocol directly without port unification. WBR, Alexey. [1] svn checkout https://www.dev.java.net/svn/grizzly/trunk/code/modules/config
[2] <network-config> <transports> <transport name="tcp"/> </transports> <protocols> <protocol name="pu-protocol"> <port-unification> <protocol-finder name="http-finder" classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" protocol="http"/> <protocol-finder name="X-protocol-finder" classname="com.sun.grizzly.config.XProtocolFinder" protocol="X-protocol"/> </port-unification> </protocol> <protocol name="http"> <http enable-comet-support="true"/> </protocol> <protocol name="X-protocol"> <protocol-chain-instance-handler> <protocol-chain> <protocol-filter name="x-filter" classname="com.sun.grizzly.config.XProtocolFilter"/> </protocol-chain> </protocol-chain-instance-handler> </protocol> </protocols> <network-listeners> <thread-pool name="defaultThreadPool"/> <network-listener name="http-listener" port="38082" transport="tcp" protocol="pu-protocol" thread-pool="defaultThreadPool"/> </network-listeners> </network-config> On Oct 5, 2009, at 15:14 , melshami wrote:
|
|
|
Re: Grizzly configuration on Glassfish v3
by melshami
::
Rate this Message:
Thanks Alexey,
I think since I am using glassfish-prelude v3 it still uses v2 configuraiton scheme, if I am correct it's sun-domain_1_3.dtd which has all network configuration under the <http-service> element. So I am not sure where to set the protocol-finder name under this scheme. Thanks, Mohamed
|
|
|
Re: Grizzly configuration on Glassfish v3
by Oleksiy Stashok
::
Rate this Message:
> I think since I am using glassfish-prelude v3 it still uses v2
> configuraiton > scheme, if I am correct it's sun-domain_1_3.dtd which has all network > configuration under the <http-service> element. So I am not sure > where to > set the protocol-finder name under this scheme. I think there is no way to use port unification with prelude :( Will it be a problem for you to use latest promoted GFv3 [1]? Thanks. WBR, Alexey. [1] http://download.java.net/glassfish/v3/promoted/ > > Thanks, > Mohamed > > Oleksiy Stashok wrote: >> >> Hi, >> >> you can take a look at config module in grizzly workspace [1]. >> There you can find unit tests with different configurations like [2], >> which actually has port unification enabled, but you can redefine >> config to use X-protocol directly without port unification. >> >> WBR, >> Alexey. >> >> >> [1] svn checkout >> https://www.dev.java.net/svn/grizzly/trunk/code/modules/config >> [2] >> <network-config> >> <transports> >> <transport name="tcp"/> >> </transports> >> <protocols> >> <protocol name="pu-protocol"> >> <port-unification> >> <protocol-finder name="http-finder" >> classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" >> protocol="http"/> >> <protocol-finder name="X-protocol-finder" >> classname="com.sun.grizzly.config.XProtocolFinder" protocol="X- >> protocol"/> >> </port-unification> >> </protocol> >> >> <protocol name="http"> >> <http enable-comet-support="true"/> >> </protocol> >> >> <protocol name="X-protocol"> >> <protocol-chain-instance-handler> >> <protocol-chain> >> <protocol-filter name="x-filter" >> classname="com.sun.grizzly.config.XProtocolFilter"/> >> </protocol-chain> >> </protocol-chain-instance-handler> >> </protocol> >> >> </protocols> >> <network-listeners> >> <thread-pool name="defaultThreadPool"/> >> <network-listener name="http-listener" port="38082" >> transport="tcp" protocol="pu-protocol" thread- >> pool="defaultThreadPool"/> >> </network-listeners> >> </network-config> >> >> >> On Oct 5, 2009, at 15:14 , melshami wrote: >> >>> >>> Hi Alexey, >>> >>> Thanks very much for the prompt reply. I am a bit confused to be >>> honest >>> since I am new to Grizzly. But I wish to configure a listener which >>> listens >>> to custom TCP based protocol. As a starting point I am trying to >>> configure a >>> simple echo server which replies to socket connections on GlassFish >>> v3. >>> >>> Regards, >>> Mohamed >>> >>> >>> Oleksiy Stashok wrote: >>>> >>>> Hi Mohamed, >>>> >>>>> I can't seem to find any documentation for how to configure >>>>> grizlly >>>>> listeners and connectors on GlassFish v3. >>>> Currently doc team is working on that. >>>> >>>>> So far I can find only this page >>>>> http://wiki.glassfish.java.net/Wiki.jsp? >>>>> page=GrizzlyConfigOnePager, >>>>> which >>>>> refers to a new scheme and it's not complete yet. >>>>> >>>>> Anyone can help with this please? >>>> Do you have any specific item in mind you'd like to configure? >>>> >>>> Thanks. >>>> >>>> WBR, >>>> Alexey. >>>> >>>>> >>>>> BR, >>>>> Mohamed >>>>> -- >>>>> View this message in context: >>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25750048.html >>>>> Sent from the Grizzly - Users mailing list archive at Nabble.com. >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>> For additional commands, e-mail: users-help@... >>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscribe@... >>>> For additional commands, e-mail: users-help@... >>>> >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25750628.html >>> Sent from the Grizzly - Users mailing list archive at Nabble.com. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscribe@... >>> For additional commands, e-mail: users-help@... >>> >> >> >> > > -- > View this message in context: http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25752899.html > Sent from the Grizzly - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Grizzly configuration on Glassfish v3
by melshami
::
Rate this Message:
It's not a problem at all, am still testing we have enough time before production so I hope there will be a new release soon. I will try that and will get back to you.
Thanks for your help:)
|
|
|
Re: Grizzly configuration on Glassfish v3
by melshami
::
Rate this Message:
Hi Alexey,
I Can't seem to get this right, here is my configuration: <network-config> <protocols> <protocol name="pu-protocol"> <port-unification> <protocol-finder protocol="rpc" name="rpc-protocol-finder" classname="scedev.grizzly.protocols.TCPProtocolFinder" /> </port-unification> </protocol> <protocol name="rpc"> <protocol-chain-instance-handler> <protocol-chain> <protocol-filter name="rpc" classname="scedev.grizzly.protocols.TCPProtocolFilter" /> </protocol-chain> </protocol-chain-instance-handler> </protocol> <protocol name="http-listener-1"> <http default-virtual-server="server" max-connections="250" server-name=""> <file-cache enabled="false" /> </http> </protocol> <protocol security-enabled="true" name="http-listener-2"> <http default-virtual-server="server" max-connections="250" server-name=""> <file-cache enabled="false" /> </http> <ssl ssl3-enabled="false" cert-nickname="s1as" /> </protocol> <protocol name="admin-listener"> <http default-virtual-server="__asadmin" max-connections="250" server-name=""> <file-cache enabled="false" /> </http> </protocol> </protocols> <network-listeners> <network-listener port="8787" protocol="pu-protocol" transport="tcp" name="tcprpc-listener" thread-pool="http-thread-pool" /> <network-listener port="8080" protocol="http-listener-1" transport="tcp" name="http-listener-1" thread-pool="http-thread-pool" /> <network-listener port="8181" protocol="http-listener-2" transport="tcp" name="http-listener-2" thread-pool="http-thread-pool" /> <network-listener port="4848" protocol="admin-listener" transport="tcp" name="admin-listener" thread-pool="http-thread-pool" /> </network-listeners> <transports> <transport name="tcp" /> </transports> </network-config> GlassFish won't start due to this exception: #|2009-10-06T09:48:46.654+0100|SEVERE|glassfish|null|_ThreadID=11;_ThreadName=Thread-3;|Unable to start v3. Closing all ports java.lang.NullPointerException at com.sun.grizzly.config.GrizzlyServiceListener.initializeListener(GrizzlyServiceListener.java:83) at com.sun.grizzly.config.GrizzlyServiceListener.configure(GrizzlyServiceListener.java:77) at com.sun.enterprise.v3.services.impl.GrizzlyListener.configure(GrizzlyListener.java:59) at com.sun.enterprise.v3.services.impl.GrizzlyProxy.configureGrizzly(GrizzlyProxy.java:125) at com.sun.enterprise.v3.services.impl.GrizzlyProxy.<init>(GrizzlyProxy.java:116) at com.sun.enterprise.v3.services.impl.GrizzlyService.createNetworkProxy(GrizzlyService.java:344) at com.sun.enterprise.v3.services.impl.GrizzlyService.postConstruct(GrizzlyService.java:266) at com.sun.hk2.component.AbstractWombImpl.inject(AbstractWombImpl.java:174) at com.sun.hk2.component.ConstructorWomb$1.run(ConstructorWomb.java:91) at java.security.AccessController.doPrivileged(Native Method) I have set the classpath for the custom protocol filter and finder in the JVM classpath settings. Is there anything else I am missing? Regards, Mohamed
|
|
|
Re: Grizzly configuration on Glassfish v3
by Oleksiy Stashok
::
Rate this Message:
Hi Mohamed,
hmm, this is a bug - I'll fix it for coming GF release. Meanwhile you can workaround this issue by declaring http protocol, within the port unification declaration, together with rpc protocol, like: <protocol name="pu-protocol"> <port-unification> <protocol-finder name="http-finder" classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" protocol="http"/> <protocol-finder name="rpc-protocol-finder" classname="scedev.grizzly.protocols.TCPProtocolFinder" protocol="rpc"/> </port-unification> </protocol> <protocol name="http"> </protocol> WBR, Alexey. On Oct 6, 2009, at 10:55 , melshami wrote: > > Hi Alexey, > > I Can't seem to get this right, here is my configuration: > > <network-config> > <protocols> > <protocol name="pu-protocol"> > <port-unification> > <protocol-finder protocol="rpc" name="rpc-protocol- > finder" > classname="scedev.grizzly.protocols.TCPProtocolFinder" /> > </port-unification> > </protocol> > <protocol name="rpc"> > <protocol-chain-instance-handler> > <protocol-chain> > <protocol-filter name="rpc" > classname="scedev.grizzly.protocols.TCPProtocolFilter" /> > </protocol-chain> > </protocol-chain-instance-handler> > </protocol> > <protocol name="http-listener-1"> > <http default-virtual-server="server" max-connections="250" > server-name=""> > <file-cache enabled="false" /> > </http> > </protocol> > <protocol security-enabled="true" name="http-listener-2"> > <http default-virtual-server="server" max-connections="250" > server-name=""> > <file-cache enabled="false" /> > </http> > <ssl ssl3-enabled="false" cert-nickname="s1as" /> > </protocol> > <protocol name="admin-listener"> > <http default-virtual-server="__asadmin" max- > connections="250" > server-name=""> > <file-cache enabled="false" /> > </http> > </protocol> > </protocols> > <network-listeners> > <network-listener port="8787" protocol="pu-protocol" > transport="tcp" name="tcprpc-listener" thread-pool="http-thread- > pool" /> > <network-listener port="8080" protocol="http-listener-1" > transport="tcp" name="http-listener-1" thread-pool="http-thread- > pool" /> > <network-listener port="8181" protocol="http-listener-2" > transport="tcp" name="http-listener-2" thread-pool="http-thread- > pool" /> > <network-listener port="4848" protocol="admin-listener" > transport="tcp" name="admin-listener" thread-pool="http-thread- > pool" /> > </network-listeners> > <transports> > <transport name="tcp" /> > </transports> > </network-config> > > GlassFish won't start due to this exception: > > #|2009-10-06T09:48:46.654+0100|SEVERE|glassfish|null| > _ThreadID=11;_ThreadName=Thread-3;|Unable > to start v3. Closing all ports > java.lang.NullPointerException > at > com > .sun > .grizzly > .config > .GrizzlyServiceListener > .initializeListener(GrizzlyServiceListener.java:83) > at > com > .sun > .grizzly > .config.GrizzlyServiceListener.configure(GrizzlyServiceListener.java: > 77) > at > com > .sun > .enterprise > .v3.services.impl.GrizzlyListener.configure(GrizzlyListener.java:59) > at > com > .sun > .enterprise > .v3.services.impl.GrizzlyProxy.configureGrizzly(GrizzlyProxy.java:125) > at > com > .sun > .enterprise.v3.services.impl.GrizzlyProxy.<init>(GrizzlyProxy.java: > 116) > at > com > .sun > .enterprise > .v3 > .services.impl.GrizzlyService.createNetworkProxy(GrizzlyService.java: > 344) > at > com > .sun > .enterprise > .v3.services.impl.GrizzlyService.postConstruct(GrizzlyService.java: > 266) > at > com.sun.hk2.component.AbstractWombImpl.inject(AbstractWombImpl.java: > 174) > at com.sun.hk2.component.ConstructorWomb$1.run(ConstructorWomb.java: > 91) > at java.security.AccessController.doPrivileged(Native Method) > > I have set the classpath for the custom protocol filter and finder > in the > JVM classpath settings. > > Is there anything else I am missing? > > Regards, > Mohamed > > melshami wrote: >> >> >> It's not a problem at all, am still testing we have enough time >> before >> production so I hope there will be a new release soon. I will try >> that and >> will get back to you. >> >> Thanks for your help:) >> >> >> Oleksiy Stashok wrote: >>> >>>> I think since I am using glassfish-prelude v3 it still uses v2 >>>> configuraiton >>>> scheme, if I am correct it's sun-domain_1_3.dtd which has all >>>> network >>>> configuration under the <http-service> element. So I am not sure >>>> where to >>>> set the protocol-finder name under this scheme. >>> I think there is no way to use port unification with prelude :( >>> Will it be a problem for you to use latest promoted GFv3 [1]? >>> >>> Thanks. >>> >>> WBR, >>> Alexey. >>> >>> [1] http://download.java.net/glassfish/v3/promoted/ >>> >>>> >>>> Thanks, >>>> Mohamed >>>> >>>> Oleksiy Stashok wrote: >>>>> >>>>> Hi, >>>>> >>>>> you can take a look at config module in grizzly workspace [1]. >>>>> There you can find unit tests with different configurations like >>>>> [2], >>>>> which actually has port unification enabled, but you can redefine >>>>> config to use X-protocol directly without port unification. >>>>> >>>>> WBR, >>>>> Alexey. >>>>> >>>>> >>>>> [1] svn checkout >>>>> https://www.dev.java.net/svn/grizzly/trunk/code/modules/config >>>>> [2] >>>>> <network-config> >>>>> <transports> >>>>> <transport name="tcp"/> >>>>> </transports> >>>>> <protocols> >>>>> <protocol name="pu-protocol"> >>>>> <port-unification> >>>>> <protocol-finder name="http-finder" >>>>> classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" >>>>> protocol="http"/> >>>>> <protocol-finder name="X-protocol-finder" >>>>> classname="com.sun.grizzly.config.XProtocolFinder" protocol="X- >>>>> protocol"/> >>>>> </port-unification> >>>>> </protocol> >>>>> >>>>> <protocol name="http"> >>>>> <http enable-comet-support="true"/> >>>>> </protocol> >>>>> >>>>> <protocol name="X-protocol"> >>>>> <protocol-chain-instance-handler> >>>>> <protocol-chain> >>>>> <protocol-filter name="x-filter" >>>>> classname="com.sun.grizzly.config.XProtocolFilter"/> >>>>> </protocol-chain> >>>>> </protocol-chain-instance-handler> >>>>> </protocol> >>>>> >>>>> </protocols> >>>>> <network-listeners> >>>>> <thread-pool name="defaultThreadPool"/> >>>>> <network-listener name="http-listener" port="38082" >>>>> transport="tcp" protocol="pu-protocol" thread- >>>>> pool="defaultThreadPool"/> >>>>> </network-listeners> >>>>> </network-config> >>>>> >>>>> >>>>> On Oct 5, 2009, at 15:14 , melshami wrote: >>>>> >>>>>> >>>>>> Hi Alexey, >>>>>> >>>>>> Thanks very much for the prompt reply. I am a bit confused to be >>>>>> honest >>>>>> since I am new to Grizzly. But I wish to configure a listener >>>>>> which >>>>>> listens >>>>>> to custom TCP based protocol. As a starting point I am trying to >>>>>> configure a >>>>>> simple echo server which replies to socket connections on >>>>>> GlassFish >>>>>> v3. >>>>>> >>>>>> Regards, >>>>>> Mohamed >>>>>> >>>>>> >>>>>> Oleksiy Stashok wrote: >>>>>>> >>>>>>> Hi Mohamed, >>>>>>> >>>>>>>> I can't seem to find any documentation for how to configure >>>>>>>> grizlly >>>>>>>> listeners and connectors on GlassFish v3. >>>>>>> Currently doc team is working on that. >>>>>>> >>>>>>>> So far I can find only this page >>>>>>>> http://wiki.glassfish.java.net/Wiki.jsp? >>>>>>>> page=GrizzlyConfigOnePager, >>>>>>>> which >>>>>>>> refers to a new scheme and it's not complete yet. >>>>>>>> >>>>>>>> Anyone can help with this please? >>>>>>> Do you have any specific item in mind you'd like to configure? >>>>>>> >>>>>>> Thanks. >>>>>>> >>>>>>> WBR, >>>>>>> Alexey. >>>>>>> >>>>>>>> >>>>>>>> BR, >>>>>>>> Mohamed >>>>>>>> -- >>>>>>>> View this message in context: >>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25750048.html >>>>>>>> Sent from the Grizzly - Users mailing list archive at >>>>>>>> Nabble.com. >>>>>>>> >>>>>>>> >>>>>>>> --------------------------------------------------------------------- >>>>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>>>> For additional commands, e-mail: users- >>>>>>>> help@... >>>>>>>> >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>>> For additional commands, e-mail: users-help@... >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25750628.html >>>>>> Sent from the Grizzly - Users mailing list archive at Nabble.com. >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>> For additional commands, e-mail: users-help@... >>>>>> >>>>> >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25752899.html >>>> Sent from the Grizzly - Users mailing list archive at Nabble.com. >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscribe@... >>>> For additional commands, e-mail: users-help@... >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscribe@... >>> For additional commands, e-mail: users-help@... >>> >>> >>> >> >> > > -- > View this message in context: http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25765021.html > Sent from the Grizzly - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Grizzly configuration on Glassfish v3
by melshami
::
Rate this Message:
Hi Alexey,
Thanks for bearing with me, still no luck. I tried your suggestion and I tried different variations of configuration protocol element. here is my current configuration: <network-config> <protocols> <protocol name="pu-protocol"> <port-unification> <protocol-finder protocol="http" classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" name="http-finder" /> <protocol-finder protocol="rpc" classname="scedev.grizzly.protocols.TCPProtocolFinder" name="rpc-protocol-finder" /> </port-unification> </protocol> <protocol name="http" /> <protocol name="rpc"> <protocol-chain-instance-handler> <protocol-chain> <protocol-filter classname="scedev.grizzly.protocols.TCPProtocolFilter" name="rpc-filter" /> </protocol-chain> </protocol-chain-instance-handler> </protocol> <protocol name="http-listener-1"> <http max-connections="250" default-virtual-server="server" server-name=""> <file-cache enabled="false" /> </http> </protocol> <protocol security-enabled="true" name="http-listener-2"> <http max-connections="250" default-virtual-server="server" server-name=""> <file-cache enabled="false" /> </http> <ssl ssl3-enabled="false" cert-nickname="s1as" /> </protocol> <protocol name="admin-listener"> <http max-connections="250" default-virtual-server="__asadmin" server-name=""> <file-cache enabled="false" /> </http> </protocol> </protocols> <network-listeners> <network-listener port="8787" protocol="pu-protocol" transport="tcp" name="tcprpc-listener" thread-pool="thread-pool-1" /> <network-listener port="8080" protocol="pu-protocol" transport="tcp" name="http-listener-1" thread-pool="http-thread-pool" /> <network-listener port="4848" protocol="pu-protocol" transport="tcp" name="admin-listener" thread-pool="thread-pool-1" /> </network-listeners> <transports> <transport name="tcp" /> </transports> </network-config>
|
|
|
Re: Grizzly configuration on Glassfish v3
by Oleksiy Stashok
::
Rate this Message:
Hi Mohamed,
my fault, please try following config: <network-config> <protocols> <protocol name="pu-protocol"> <port-unification> <protocol-finder protocol="http" classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" name="http-finder" /> <protocol-finder protocol="rpc" classname="scedev.grizzly.protocols.TCPProtocolFinder" name="rpc- protocol-finder" /> </port-unification> </protocol> <protocol name="http"> <http max-connections="250" default-virtual- server="server" server-name="" /> </protocol> <protocol name="rpc"> <protocol-chain-instance-handler> <protocol-chain> <protocol-filter classname="scedev.grizzly.protocols.TCPProtocolFilter" name="rpc- filter" /> </protocol-chain> </protocol-chain-instance-handler> </protocol> <protocol name="http-listener-1"> <http max-connections="250" default-virtual- server="server" server-name=""> <file-cache enabled="false" /> </http> </protocol> <protocol security-enabled="true" name="http-listener-2"> <http max-connections="250" default-virtual- server="server" server-name=""> <file-cache enabled="false" /> </http> <ssl ssl3-enabled="false" cert-nickname="s1as" /> </protocol> <protocol name="admin-listener"> <http max-connections="250" default-virtual- server="__asadmin" server-name=""> <file-cache enabled="false" /> </http> </protocol> </protocols> <network-listeners> <network-listener port="8787" protocol="pu-protocol" transport="tcp" name="tcprpc-listener" thread-pool="thread-pool-1" /> <network-listener port="8080" protocol="http-listener-1" transport="tcp" name="http-listener-1" thread-pool="http-thread-pool" /> <network-listener port="4848" protocol="admin-listener" transport="tcp" name="admin-listener" thread-pool="thread-pool-1" /> </network-listeners> <transports> <transport name="tcp" /> </transports> </network-config> WBR, Alexey. On Oct 6, 2009, at 12:53 , melshami wrote: > > Hi Alexey, > > Thanks for bearing with me, still no luck. I tried your suggestion > and I > tried different variations of configuration protocol element. > > here is my current configuration: > <network-config> > <protocols> > <protocol name="pu-protocol"> > <port-unification> > <protocol-finder protocol="http" > classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" > name="http-finder" /> > <protocol-finder protocol="rpc" > classname="scedev.grizzly.protocols.TCPProtocolFinder" > name="rpc-protocol-finder" /> > </port-unification> > </protocol> > <protocol name="http" /> > <protocol name="rpc"> > <protocol-chain-instance-handler> > <protocol-chain> > <protocol-filter > classname="scedev.grizzly.protocols.TCPProtocolFilter" name="rpc- > filter" /> > </protocol-chain> > </protocol-chain-instance-handler> > </protocol> > <protocol name="http-listener-1"> > <http max-connections="250" default-virtual-server="server" > server-name=""> > <file-cache enabled="false" /> > </http> > </protocol> > <protocol security-enabled="true" name="http-listener-2"> > <http max-connections="250" default-virtual-server="server" > server-name=""> > <file-cache enabled="false" /> > </http> > <ssl ssl3-enabled="false" cert-nickname="s1as" /> > </protocol> > <protocol name="admin-listener"> > <http max-connections="250" default-virtual- > server="__asadmin" > server-name=""> > <file-cache enabled="false" /> > </http> > </protocol> > </protocols> > <network-listeners> > <network-listener port="8787" protocol="pu-protocol" > transport="tcp" name="tcprpc-listener" thread-pool="thread-pool-1" /> > <network-listener port="8080" protocol="pu-protocol" > transport="tcp" name="http-listener-1" thread-pool="http-thread- > pool" /> > <network-listener port="4848" protocol="pu-protocol" > transport="tcp" name="admin-listener" thread-pool="thread-pool-1" /> > </network-listeners> > <transports> > <transport name="tcp" /> > </transports> > </network-config> > > Oleksiy Stashok wrote: >> >> Hi Mohamed, >> >> hmm, this is a bug - I'll fix it for coming GF release. >> Meanwhile you can workaround this issue by declaring http protocol, >> within the port unification declaration, together with rpc protocol, >> like: >> >> <protocol name="pu-protocol"> >> <port-unification> >> <protocol-finder name="http-finder" >> classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" >> protocol="http"/> >> <protocol-finder name="rpc-protocol-finder" >> classname="scedev.grizzly.protocols.TCPProtocolFinder" >> protocol="rpc"/> >> </port-unification> >> </protocol> >> >> <protocol name="http"> >> </protocol> >> >> >> WBR, >> Alexey. >> >> On Oct 6, 2009, at 10:55 , melshami wrote: >> >>> >>> Hi Alexey, >>> >>> I Can't seem to get this right, here is my configuration: >>> >>> <network-config> >>> <protocols> >>> <protocol name="pu-protocol"> >>> <port-unification> >>> <protocol-finder protocol="rpc" name="rpc-protocol- >>> finder" >>> classname="scedev.grizzly.protocols.TCPProtocolFinder" /> >>> </port-unification> >>> </protocol> >>> <protocol name="rpc"> >>> <protocol-chain-instance-handler> >>> <protocol-chain> >>> <protocol-filter name="rpc" >>> classname="scedev.grizzly.protocols.TCPProtocolFilter" /> >>> </protocol-chain> >>> </protocol-chain-instance-handler> >>> </protocol> >>> <protocol name="http-listener-1"> >>> <http default-virtual-server="server" max- >>> connections="250" >>> server-name=""> >>> <file-cache enabled="false" /> >>> </http> >>> </protocol> >>> <protocol security-enabled="true" name="http-listener-2"> >>> <http default-virtual-server="server" max- >>> connections="250" >>> server-name=""> >>> <file-cache enabled="false" /> >>> </http> >>> <ssl ssl3-enabled="false" cert-nickname="s1as" /> >>> </protocol> >>> <protocol name="admin-listener"> >>> <http default-virtual-server="__asadmin" max- >>> connections="250" >>> server-name=""> >>> <file-cache enabled="false" /> >>> </http> >>> </protocol> >>> </protocols> >>> <network-listeners> >>> <network-listener port="8787" protocol="pu-protocol" >>> transport="tcp" name="tcprpc-listener" thread-pool="http-thread- >>> pool" /> >>> <network-listener port="8080" protocol="http-listener-1" >>> transport="tcp" name="http-listener-1" thread-pool="http-thread- >>> pool" /> >>> <network-listener port="8181" protocol="http-listener-2" >>> transport="tcp" name="http-listener-2" thread-pool="http-thread- >>> pool" /> >>> <network-listener port="4848" protocol="admin-listener" >>> transport="tcp" name="admin-listener" thread-pool="http-thread- >>> pool" /> >>> </network-listeners> >>> <transports> >>> <transport name="tcp" /> >>> </transports> >>> </network-config> >>> >>> GlassFish won't start due to this exception: >>> >>> #|2009-10-06T09:48:46.654+0100|SEVERE|glassfish|null| >>> _ThreadID=11;_ThreadName=Thread-3;|Unable >>> to start v3. Closing all ports >>> java.lang.NullPointerException >>> at >>> com >>> .sun >>> .grizzly >>> .config >>> .GrizzlyServiceListener >>> .initializeListener(GrizzlyServiceListener.java:83) >>> at >>> com >>> .sun >>> .grizzly >>> .config >>> .GrizzlyServiceListener.configure(GrizzlyServiceListener.java: >>> 77) >>> at >>> com >>> .sun >>> .enterprise >>> .v3.services.impl.GrizzlyListener.configure(GrizzlyListener.java:59) >>> at >>> com >>> .sun >>> .enterprise >>> .v3.services.impl.GrizzlyProxy.configureGrizzly(GrizzlyProxy.java: >>> 125) >>> at >>> com >>> .sun >>> .enterprise.v3.services.impl.GrizzlyProxy.<init>(GrizzlyProxy.java: >>> 116) >>> at >>> com >>> .sun >>> .enterprise >>> .v3 >>> .services >>> .impl.GrizzlyService.createNetworkProxy(GrizzlyService.java: >>> 344) >>> at >>> com >>> .sun >>> .enterprise >>> .v3.services.impl.GrizzlyService.postConstruct(GrizzlyService.java: >>> 266) >>> at >>> com.sun.hk2.component.AbstractWombImpl.inject(AbstractWombImpl.java: >>> 174) >>> at com.sun.hk2.component.ConstructorWomb >>> $1.run(ConstructorWomb.java: >>> 91) >>> at java.security.AccessController.doPrivileged(Native Method) >>> >>> I have set the classpath for the custom protocol filter and finder >>> in the >>> JVM classpath settings. >>> >>> Is there anything else I am missing? >>> >>> Regards, >>> Mohamed >>> >>> melshami wrote: >>>> >>>> >>>> It's not a problem at all, am still testing we have enough time >>>> before >>>> production so I hope there will be a new release soon. I will try >>>> that and >>>> will get back to you. >>>> >>>> Thanks for your help:) >>>> >>>> >>>> Oleksiy Stashok wrote: >>>>> >>>>>> I think since I am using glassfish-prelude v3 it still uses v2 >>>>>> configuraiton >>>>>> scheme, if I am correct it's sun-domain_1_3.dtd which has all >>>>>> network >>>>>> configuration under the <http-service> element. So I am not sure >>>>>> where to >>>>>> set the protocol-finder name under this scheme. >>>>> I think there is no way to use port unification with prelude :( >>>>> Will it be a problem for you to use latest promoted GFv3 [1]? >>>>> >>>>> Thanks. >>>>> >>>>> WBR, >>>>> Alexey. >>>>> >>>>> [1] http://download.java.net/glassfish/v3/promoted/ >>>>> >>>>>> >>>>>> Thanks, >>>>>> Mohamed >>>>>> >>>>>> Oleksiy Stashok wrote: >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> you can take a look at config module in grizzly workspace [1]. >>>>>>> There you can find unit tests with different configurations like >>>>>>> [2], >>>>>>> which actually has port unification enabled, but you can >>>>>>> redefine >>>>>>> config to use X-protocol directly without port unification. >>>>>>> >>>>>>> WBR, >>>>>>> Alexey. >>>>>>> >>>>>>> >>>>>>> [1] svn checkout >>>>>>> https://www.dev.java.net/svn/grizzly/trunk/code/modules/config >>>>>>> [2] >>>>>>> <network-config> >>>>>>> <transports> >>>>>>> <transport name="tcp"/> >>>>>>> </transports> >>>>>>> <protocols> >>>>>>> <protocol name="pu-protocol"> >>>>>>> <port-unification> >>>>>>> <protocol-finder name="http-finder" >>>>>>> classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" >>>>>>> protocol="http"/> >>>>>>> <protocol-finder name="X-protocol-finder" >>>>>>> classname="com.sun.grizzly.config.XProtocolFinder" protocol="X- >>>>>>> protocol"/> >>>>>>> </port-unification> >>>>>>> </protocol> >>>>>>> >>>>>>> <protocol name="http"> >>>>>>> <http enable-comet-support="true"/> >>>>>>> </protocol> >>>>>>> >>>>>>> <protocol name="X-protocol"> >>>>>>> <protocol-chain-instance-handler> >>>>>>> <protocol-chain> >>>>>>> <protocol-filter name="x-filter" >>>>>>> classname="com.sun.grizzly.config.XProtocolFilter"/> >>>>>>> </protocol-chain> >>>>>>> </protocol-chain-instance-handler> >>>>>>> </protocol> >>>>>>> >>>>>>> </protocols> >>>>>>> <network-listeners> >>>>>>> <thread-pool name="defaultThreadPool"/> >>>>>>> <network-listener name="http-listener" port="38082" >>>>>>> transport="tcp" protocol="pu-protocol" thread- >>>>>>> pool="defaultThreadPool"/> >>>>>>> </network-listeners> >>>>>>> </network-config> >>>>>>> >>>>>>> >>>>>>> On Oct 5, 2009, at 15:14 , melshami wrote: >>>>>>> >>>>>>>> >>>>>>>> Hi Alexey, >>>>>>>> >>>>>>>> Thanks very much for the prompt reply. I am a bit confused to >>>>>>>> be >>>>>>>> honest >>>>>>>> since I am new to Grizzly. But I wish to configure a listener >>>>>>>> which >>>>>>>> listens >>>>>>>> to custom TCP based protocol. As a starting point I am trying >>>>>>>> to >>>>>>>> configure a >>>>>>>> simple echo server which replies to socket connections on >>>>>>>> GlassFish >>>>>>>> v3. >>>>>>>> >>>>>>>> Regards, >>>>>>>> Mohamed >>>>>>>> >>>>>>>> >>>>>>>> Oleksiy Stashok wrote: >>>>>>>>> >>>>>>>>> Hi Mohamed, >>>>>>>>> >>>>>>>>>> I can't seem to find any documentation for how to configure >>>>>>>>>> grizlly >>>>>>>>>> listeners and connectors on GlassFish v3. >>>>>>>>> Currently doc team is working on that. >>>>>>>>> >>>>>>>>>> So far I can find only this page >>>>>>>>>> http://wiki.glassfish.java.net/Wiki.jsp? >>>>>>>>>> page=GrizzlyConfigOnePager, >>>>>>>>>> which >>>>>>>>>> refers to a new scheme and it's not complete yet. >>>>>>>>>> >>>>>>>>>> Anyone can help with this please? >>>>>>>>> Do you have any specific item in mind you'd like to configure? >>>>>>>>> >>>>>>>>> Thanks. >>>>>>>>> >>>>>>>>> WBR, >>>>>>>>> Alexey. >>>>>>>>> >>>>>>>>>> >>>>>>>>>> BR, >>>>>>>>>> Mohamed >>>>>>>>>> -- >>>>>>>>>> View this message in context: >>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25750048.html >>>>>>>>>> Sent from the Grizzly - Users mailing list archive at >>>>>>>>>> Nabble.com. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>> To unsubscribe, e-mail: users- >>>>>>>>>> unsubscribe@... >>>>>>>>>> For additional commands, e-mail: users- >>>>>>>>>> help@... >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> --------------------------------------------------------------------- >>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>>>>> For additional commands, e-mail: users-help@... >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> View this message in context: >>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25750628.html >>>>>>>> Sent from the Grizzly - Users mailing list archive at >>>>>>>> Nabble.com. >>>>>>>> >>>>>>>> >>>>>>>> --------------------------------------------------------------------- >>>>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>>>> For additional commands, e-mail: users- >>>>>>>> help@... >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25752899.html >>>>>> Sent from the Grizzly - Users mailing list archive at Nabble.com. >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>> For additional commands, e-mail: users-help@... >>>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>> For additional commands, e-mail: users-help@... >>>>> >>>>> >>>>> >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25765021.html >>> Sent from the Grizzly - Users mailing list archive at Nabble.com. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscribe@... >>> For additional commands, e-mail: users-help@... >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> >> > > -- > View this message in context: http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25766557.html > Sent from the Grizzly - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Grizzly configuration on Glassfish v3
by melshami
::
Rate this Message:
Hi Alexey,
I see the changes is with network listener protocol attribute value for the http and admin listeners. I tested all possible alternatives before bothering you with one more question:). btw I am using glassfish-v3-b66-windows version. Could it be the a problem with this build? I have attached TCPProtcol.jar in case if you wanted to test it yourself, but I doubt it even reached the pointer where the classes were loaded TCPProtocol.jar
|
|
|
Re: Grizzly configuration on Glassfish v3
by Oleksiy Stashok
::
Rate this Message:
Hello again :)
> I see the changes is with network listener protocol attribute value > for the > http and admin listeners. I tested all possible alternatives before > bothering you with one more question:). Just to check, do you see any exceptions in a log? > btw I am using glassfish-v3-b66-windows version. Could it be the a > problem > with this build? It should be fine, I believe. > I have attached TCPProtcol.jar in case if you wanted to test it > yourself, > but I doubt it even reached the pointer where the classes were loaded > http://www.nabble.com/file/p25767056/TCPProtocol.jar TCPProtocol.jar Ok, how do you include jar above to a GF? :) IMO this is the issue. AFAIK you have to create osgi module from your jar and install it to GFv3. 1) How to create osgi module? Here I'm not big expert. You can take a look on internet, or check grizzly project's maven scripts to see how you can make osgi module. What I did with the jar you sent - is unpacked it and changed MANIFEST.MF file, so it looks like [1] and then repackaged jar file again. 2) Install osgi module to GFv3 Not sure, may be it could be done easier way, but here are steps I did. 2.1) Enabled Felix shell for GFv3 You can take a look here [2], but note that paths there are incorrect. Here are correct paths [3] 2.2) Install osgi module Please look at [4], starting from step 5, but run glassfish using (suppose you're in glassfishv3/bin folder) java -Xmx512m -jar ../glassfish/modules/glassfish.jar 2.3) Done After installing osgi module, restart GFv3 - it should work. Seems it works for me. Thanks. WBR, Alexey. [1] Manifest-Version: 1.0 Ant-Version: Apache Ant 1.7.1 Created-By: 14.0-b16 (Sun Microsystems Inc.) X-COMMENT: Main-Class will be added automatically by build Export-Package: scedev.grizzly.protocols implementation-version: 0.1 package: scedev.grizzly.protocols Bundle-Name: scedev-grizzly Bundle-Vendor: scedev Bundle-Version: 0.1 Bnd-LastModified: 1254747835722 Bundle-ManifestVersion: 2 Bundle-SymbolicName: scedev.grizzly.protocols Import-Package: com .sun .grizzly ,com .sun .grizzly .filter ,com .sun .grizzly .http ,com .sun.grizzly.http.portunif,com.sun.grizzly.portunif,com.sun.grizzly.util [2] http://blogs.sun.com/arungupta/entry/totd_34_using_felix_shell [3] felix.auto.start.1= \ reference:${com.sun.aas.installRootURI}modules/osgi-main.jar\ ${com.sun.aas.installRootURI}modules/org.apache.felix.shell.jar \ ${com.sun.aas.installRootURI}modules/org.apache.felix.shell.tui.jar [4] http://blogs.sun.com/arungupta/entry/totd_36_deploy_osgi_bundles > > Oleksiy Stashok wrote: >> >> Hi Mohamed, >> >> my fault, please try following config: >> >> <network-config> >> <protocols> >> <protocol name="pu-protocol"> >> <port-unification> >> <protocol-finder protocol="http" >> classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" >> name="http-finder" /> >> <protocol-finder protocol="rpc" >> classname="scedev.grizzly.protocols.TCPProtocolFinder" name="rpc- >> protocol-finder" /> >> </port-unification> >> </protocol> >> <protocol name="http"> >> <http max-connections="250" default-virtual- >> server="server" server-name="" /> >> </protocol> >> <protocol name="rpc"> >> <protocol-chain-instance-handler> >> <protocol-chain> >> <protocol-filter >> classname="scedev.grizzly.protocols.TCPProtocolFilter" name="rpc- >> filter" /> >> </protocol-chain> >> </protocol-chain-instance-handler> >> </protocol> >> <protocol name="http-listener-1"> >> <http max-connections="250" default-virtual- >> server="server" server-name=""> >> <file-cache enabled="false" /> >> </http> >> </protocol> >> <protocol security-enabled="true" name="http-listener-2"> >> <http max-connections="250" default-virtual- >> server="server" server-name=""> >> <file-cache enabled="false" /> >> </http> >> <ssl ssl3-enabled="false" cert-nickname="s1as" /> >> </protocol> >> <protocol name="admin-listener"> >> <http max-connections="250" default-virtual- >> server="__asadmin" server-name=""> >> <file-cache enabled="false" /> >> </http> >> </protocol> >> </protocols> >> <network-listeners> >> <network-listener port="8787" protocol="pu-protocol" >> transport="tcp" name="tcprpc-listener" thread-pool="thread-pool-1" /> >> <network-listener port="8080" protocol="http-listener-1" >> transport="tcp" name="http-listener-1" thread-pool="http-thread- >> pool" /> >> <network-listener port="4848" protocol="admin-listener" >> transport="tcp" name="admin-listener" thread-pool="thread-pool-1" /> >> </network-listeners> >> <transports> >> <transport name="tcp" /> >> </transports> >> </network-config> >> >> WBR, >> Alexey. >> >> On Oct 6, 2009, at 12:53 , melshami wrote: >> >>> >>> Hi Alexey, >>> >>> Thanks for bearing with me, still no luck. I tried your suggestion >>> and I >>> tried different variations of configuration protocol element. >>> >>> here is my current configuration: >>> <network-config> >>> <protocols> >>> <protocol name="pu-protocol"> >>> <port-unification> >>> <protocol-finder protocol="http" >>> classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" >>> name="http-finder" /> >>> <protocol-finder protocol="rpc" >>> classname="scedev.grizzly.protocols.TCPProtocolFinder" >>> name="rpc-protocol-finder" /> >>> </port-unification> >>> </protocol> >>> <protocol name="http" /> >>> <protocol name="rpc"> >>> <protocol-chain-instance-handler> >>> <protocol-chain> >>> <protocol-filter >>> classname="scedev.grizzly.protocols.TCPProtocolFilter" name="rpc- >>> filter" /> >>> </protocol-chain> >>> </protocol-chain-instance-handler> >>> </protocol> >>> <protocol name="http-listener-1"> >>> <http max-connections="250" default-virtual- >>> server="server" >>> server-name=""> >>> <file-cache enabled="false" /> >>> </http> >>> </protocol> >>> <protocol security-enabled="true" name="http-listener-2"> >>> <http max-connections="250" default-virtual- >>> server="server" >>> server-name=""> >>> <file-cache enabled="false" /> >>> </http> >>> <ssl ssl3-enabled="false" cert-nickname="s1as" /> >>> </protocol> >>> <protocol name="admin-listener"> >>> <http max-connections="250" default-virtual- >>> server="__asadmin" >>> server-name=""> >>> <file-cache enabled="false" /> >>> </http> >>> </protocol> >>> </protocols> >>> <network-listeners> >>> <network-listener port="8787" protocol="pu-protocol" >>> transport="tcp" name="tcprpc-listener" thread-pool="thread- >>> pool-1" /> >>> <network-listener port="8080" protocol="pu-protocol" >>> transport="tcp" name="http-listener-1" thread-pool="http-thread- >>> pool" /> >>> <network-listener port="4848" protocol="pu-protocol" >>> transport="tcp" name="admin-listener" thread-pool="thread-pool-1" /> >>> </network-listeners> >>> <transports> >>> <transport name="tcp" /> >>> </transports> >>> </network-config> >>> >>> Oleksiy Stashok wrote: >>>> >>>> Hi Mohamed, >>>> >>>> hmm, this is a bug - I'll fix it for coming GF release. >>>> Meanwhile you can workaround this issue by declaring http protocol, >>>> within the port unification declaration, together with rpc >>>> protocol, >>>> like: >>>> >>>> <protocol name="pu-protocol"> >>>> <port-unification> >>>> <protocol-finder name="http-finder" >>>> classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" >>>> protocol="http"/> >>>> <protocol-finder name="rpc-protocol-finder" >>>> classname="scedev.grizzly.protocols.TCPProtocolFinder" >>>> protocol="rpc"/> >>>> </port-unification> >>>> </protocol> >>>> >>>> <protocol name="http"> >>>> </protocol> >>>> >>>> >>>> WBR, >>>> Alexey. >>>> >>>> On Oct 6, 2009, at 10:55 , melshami wrote: >>>> >>>>> >>>>> Hi Alexey, >>>>> >>>>> I Can't seem to get this right, here is my configuration: >>>>> >>>>> <network-config> >>>>> <protocols> >>>>> <protocol name="pu-protocol"> >>>>> <port-unification> >>>>> <protocol-finder protocol="rpc" name="rpc-protocol- >>>>> finder" >>>>> classname="scedev.grizzly.protocols.TCPProtocolFinder" /> >>>>> </port-unification> >>>>> </protocol> >>>>> <protocol name="rpc"> >>>>> <protocol-chain-instance-handler> >>>>> <protocol-chain> >>>>> <protocol-filter name="rpc" >>>>> classname="scedev.grizzly.protocols.TCPProtocolFilter" /> >>>>> </protocol-chain> >>>>> </protocol-chain-instance-handler> >>>>> </protocol> >>>>> <protocol name="http-listener-1"> >>>>> <http default-virtual-server="server" max- >>>>> connections="250" >>>>> server-name=""> >>>>> <file-cache enabled="false" /> >>>>> </http> >>>>> </protocol> >>>>> <protocol security-enabled="true" name="http-listener-2"> >>>>> <http default-virtual-server="server" max- >>>>> connections="250" >>>>> server-name=""> >>>>> <file-cache enabled="false" /> >>>>> </http> >>>>> <ssl ssl3-enabled="false" cert-nickname="s1as" /> >>>>> </protocol> >>>>> <protocol name="admin-listener"> >>>>> <http default-virtual-server="__asadmin" max- >>>>> connections="250" >>>>> server-name=""> >>>>> <file-cache enabled="false" /> >>>>> </http> >>>>> </protocol> >>>>> </protocols> >>>>> <network-listeners> >>>>> <network-listener port="8787" protocol="pu-protocol" >>>>> transport="tcp" name="tcprpc-listener" thread-pool="http-thread- >>>>> pool" /> >>>>> <network-listener port="8080" protocol="http-listener-1" >>>>> transport="tcp" name="http-listener-1" thread-pool="http-thread- >>>>> pool" /> >>>>> <network-listener port="8181" protocol="http-listener-2" >>>>> transport="tcp" name="http-listener-2" thread-pool="http-thread- >>>>> pool" /> >>>>> <network-listener port="4848" protocol="admin-listener" >>>>> transport="tcp" name="admin-listener" thread-pool="http-thread- >>>>> pool" /> >>>>> </network-listeners> >>>>> <transports> >>>>> <transport name="tcp" /> >>>>> </transports> >>>>> </network-config> >>>>> >>>>> GlassFish won't start due to this exception: >>>>> >>>>> #|2009-10-06T09:48:46.654+0100|SEVERE|glassfish|null| >>>>> _ThreadID=11;_ThreadName=Thread-3;|Unable >>>>> to start v3. Closing all ports >>>>> java.lang.NullPointerException >>>>> at >>>>> com >>>>> .sun >>>>> .grizzly >>>>> .config >>>>> .GrizzlyServiceListener >>>>> .initializeListener(GrizzlyServiceListener.java:83) >>>>> at >>>>> com >>>>> .sun >>>>> .grizzly >>>>> .config >>>>> .GrizzlyServiceListener.configure(GrizzlyServiceListener.java: >>>>> 77) >>>>> at >>>>> com >>>>> .sun >>>>> .enterprise >>>>> .v3.services.impl.GrizzlyListener.configure(GrizzlyListener.java: >>>>> 59) >>>>> at >>>>> com >>>>> .sun >>>>> .enterprise >>>>> .v3.services.impl.GrizzlyProxy.configureGrizzly(GrizzlyProxy.java: >>>>> 125) >>>>> at >>>>> com >>>>> .sun >>>>> .enterprise >>>>> .v3.services.impl.GrizzlyProxy.<init>(GrizzlyProxy.java: >>>>> 116) >>>>> at >>>>> com >>>>> .sun >>>>> .enterprise >>>>> .v3 >>>>> .services >>>>> .impl.GrizzlyService.createNetworkProxy(GrizzlyService.java: >>>>> 344) >>>>> at >>>>> com >>>>> .sun >>>>> .enterprise >>>>> .v3 >>>>> .services.impl.GrizzlyService.postConstruct(GrizzlyService.java: >>>>> 266) >>>>> at >>>>> com >>>>> .sun.hk2.component.AbstractWombImpl.inject(AbstractWombImpl.java: >>>>> 174) >>>>> at com.sun.hk2.component.ConstructorWomb >>>>> $1.run(ConstructorWomb.java: >>>>> 91) >>>>> at java.security.AccessController.doPrivileged(Native Method) >>>>> >>>>> I have set the classpath for the custom protocol filter and finder >>>>> in the >>>>> JVM classpath settings. >>>>> >>>>> Is there anything else I am missing? >>>>> >>>>> Regards, >>>>> Mohamed >>>>> >>>>> melshami wrote: >>>>>> >>>>>> >>>>>> It's not a problem at all, am still testing we have enough time >>>>>> before >>>>>> production so I hope there will be a new release soon. I will try >>>>>> that and >>>>>> will get back to you. >>>>>> >>>>>> Thanks for your help:) >>>>>> >>>>>> >>>>>> Oleksiy Stashok wrote: >>>>>>> >>>>>>>> I think since I am using glassfish-prelude v3 it still uses v2 >>>>>>>> configuraiton >>>>>>>> scheme, if I am correct it's sun-domain_1_3.dtd which has all >>>>>>>> network >>>>>>>> configuration under the <http-service> element. So I am not >>>>>>>> sure >>>>>>>> where to >>>>>>>> set the protocol-finder name under this scheme. >>>>>>> I think there is no way to use port unification with prelude :( >>>>>>> Will it be a problem for you to use latest promoted GFv3 [1]? >>>>>>> >>>>>>> Thanks. >>>>>>> >>>>>>> WBR, >>>>>>> Alexey. >>>>>>> >>>>>>> [1] http://download.java.net/glassfish/v3/promoted/ >>>>>>> >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Mohamed >>>>>>>> >>>>>>>> Oleksiy Stashok wrote: >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> you can take a look at config module in grizzly workspace [1]. >>>>>>>>> There you can find unit tests with different configurations >>>>>>>>> like >>>>>>>>> [2], >>>>>>>>> which actually has port unification enabled, but you can >>>>>>>>> redefine >>>>>>>>> config to use X-protocol directly without port unification. >>>>>>>>> >>>>>>>>> WBR, >>>>>>>>> Alexey. >>>>>>>>> >>>>>>>>> >>>>>>>>> [1] svn checkout >>>>>>>>> https://www.dev.java.net/svn/grizzly/trunk/code/modules/config >>>>>>>>> [2] >>>>>>>>> <network-config> >>>>>>>>> <transports> >>>>>>>>> <transport name="tcp"/> >>>>>>>>> </transports> >>>>>>>>> <protocols> >>>>>>>>> <protocol name="pu-protocol"> >>>>>>>>> <port-unification> >>>>>>>>> <protocol-finder name="http-finder" >>>>>>>>> classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" >>>>>>>>> protocol="http"/> >>>>>>>>> <protocol-finder name="X-protocol-finder" >>>>>>>>> classname="com.sun.grizzly.config.XProtocolFinder" >>>>>>>>> protocol="X- >>>>>>>>> protocol"/> >>>>>>>>> </port-unification> >>>>>>>>> </protocol> >>>>>>>>> >>>>>>>>> <protocol name="http"> >>>>>>>>> <http enable-comet-support="true"/> >>>>>>>>> </protocol> >>>>>>>>> >>>>>>>>> <protocol name="X-protocol"> >>>>>>>>> <protocol-chain-instance-handler> >>>>>>>>> <protocol-chain> >>>>>>>>> <protocol-filter name="x-filter" >>>>>>>>> classname="com.sun.grizzly.config.XProtocolFilter"/> >>>>>>>>> </protocol-chain> >>>>>>>>> </protocol-chain-instance-handler> >>>>>>>>> </protocol> >>>>>>>>> >>>>>>>>> </protocols> >>>>>>>>> <network-listeners> >>>>>>>>> <thread-pool name="defaultThreadPool"/> >>>>>>>>> <network-listener name="http-listener" port="38082" >>>>>>>>> transport="tcp" protocol="pu-protocol" thread- >>>>>>>>> pool="defaultThreadPool"/> >>>>>>>>> </network-listeners> >>>>>>>>> </network-config> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Oct 5, 2009, at 15:14 , melshami wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Hi Alexey, >>>>>>>>>> >>>>>>>>>> Thanks very much for the prompt reply. I am a bit confused to >>>>>>>>>> be >>>>>>>>>> honest >>>>>>>>>> since I am new to Grizzly. But I wish to configure a listener >>>>>>>>>> which >>>>>>>>>> listens >>>>>>>>>> to custom TCP based protocol. As a starting point I am trying >>>>>>>>>> to >>>>>>>>>> configure a >>>>>>>>>> simple echo server which replies to socket connections on >>>>>>>>>> GlassFish >>>>>>>>>> v3. >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> Mohamed >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Oleksiy Stashok wrote: >>>>>>>>>>> >>>>>>>>>>> Hi Mohamed, >>>>>>>>>>> >>>>>>>>>>>> I can't seem to find any documentation for how to configure >>>>>>>>>>>> grizlly >>>>>>>>>>>> listeners and connectors on GlassFish v3. >>>>>>>>>>> Currently doc team is working on that. >>>>>>>>>>> >>>>>>>>>>>> So far I can find only this page >>>>>>>>>>>> http://wiki.glassfish.java.net/Wiki.jsp? >>>>>>>>>>>> page=GrizzlyConfigOnePager, >>>>>>>>>>>> which >>>>>>>>>>>> refers to a new scheme and it's not complete yet. >>>>>>>>>>>> >>>>>>>>>>>> Anyone can help with this please? >>>>>>>>>>> Do you have any specific item in mind you'd like to >>>>>>>>>>> configure? >>>>>>>>>>> >>>>>>>>>>> Thanks. >>>>>>>>>>> >>>>>>>>>>> WBR, >>>>>>>>>>> Alexey. >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> BR, >>>>>>>>>>>> Mohamed >>>>>>>>>>>> -- >>>>>>>>>>>> View this message in context: >>>>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25750048.html >>>>>>>>>>>> Sent from the Grizzly - Users mailing list archive at >>>>>>>>>>>> Nabble.com. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>>>> To unsubscribe, e-mail: users- >>>>>>>>>>>> unsubscribe@... >>>>>>>>>>>> For additional commands, e-mail: users- >>>>>>>>>>>> help@... >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>>>>>>> For additional commands, e-mail: users-help@... >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> View this message in context: >>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25750628.html >>>>>>>>>> Sent from the Grizzly - Users mailing list archive at >>>>>>>>>> Nabble.com. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>> To unsubscribe, e-mail: users- >>>>>>>>>> unsubscribe@... >>>>>>>>>> For additional commands, e-mail: users- >>>>>>>>>> help@... >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> View this message in context: >>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25752899.html >>>>>>>> Sent from the Grizzly - Users mailing list archive at >>>>>>>> Nabble.com. >>>>>>>> >>>>>>>> >>>>>>>> --------------------------------------------------------------------- >>>>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>>>> For additional commands, e-mail: users- >>>>>>>> help@... >>>>>>>> >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>>> For additional commands, e-mail: users-help@... >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> -- >>>>> View this message in context: >>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25765021.html >>>>> Sent from the Grizzly - Users mailing list archive at Nabble.com. >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>> For additional commands, e-mail: users-help@... >>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscribe@... >>>> For additional commands, e-mail: users-help@... >>>> >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25766557.html >>> Sent from the Grizzly - Users mailing list archive at Nabble.com. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscribe@... >>> For additional commands, e-mail: users-help@... >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> >> > > -- > View this message in context: http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25767056.html > Sent from the Grizzly - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Grizzly configuration on Glassfish v3
by melshami
::
Rate this Message:
Thanks Alexey, I managed to install the bundle using Flex shell, I think in the current build there is no need to add other paths to felix.auto.start.1, now I will need to test the custom filter:)
|
|
|
Re: Grizzly configuration on Glassfish v3
by melshami
::
Rate this Message:
Hi Alexey,
Sorry for cross posting but I posted another question regarding TCP/SOAP in GlassFish here http://www.nabble.com/SOAP-TCP-has-been-integrated-to-Glassfish-V3-td25045927.html#a25045927. After reading Paul's and your blog posts. I realise TCP-SOAP is already integrated, I can find soap-tcp.jar under the modules. I added a configuration similiar to the one you posted but Glassfish fails to start.
|
|
|
Re: Grizzly configuration on Glassfish v3
by Oleksiy Stashok
::
Rate this Message:
Hi Mohamed,
> Sorry for cross posting but I posted another question regarding TCP/ > SOAP in > GlassFish here > http://www.nabble.com/SOAP-TCP-has-been-integrated-to-Glassfish-V3-td25045927.html#a25045927 > . Oh, it's difficult to follow all the forums :) > > After reading Paul's and your blog posts. I realise TCP-SOAP is > already > integrated, That's true. > I can find soap-tcp.jar under the modules. I added a > configuration similiar to the one you posted but Glassfish fails to > start. What exactly error you see? Can you pls. run the GF is standalone mode like: java -Xmx512m -jar ../glassfish/modules/glassfish.jar cause there is some logging issue now, and you may not see entire log in server.log file. Thanks. WBR, Alexey. > > melshami wrote: >> >> Thanks Alexey, I managed to install the bundle using Flex shell, I >> think >> in the current build there is no need to add other paths to >> felix.auto.start.1, now I will need to test the custom filter:) >> >> The exception is similiar to the previous one but I don't think it's >> ClassDefNotFound exception. >> >> java.lang.NullPointerException >> at >> com >> .sun >> .grizzly >> .config >> .GrizzlyServiceListener >> .initializeListener(GrizzlyServiceListener.java:83) >> at >> com >> .sun >> .grizzly >> .config >> .GrizzlyServiceListener.configure(GrizzlyServiceListener.java:77) >> at >> com >> .sun >> .enterprise >> .v3.services.impl.GrizzlyListener.configure(GrizzlyListener.java:59) >> at >> com >> .sun >> .enterprise >> .v3.services.impl.GrizzlyProxy.configureGrizzly(GrizzlyProxy.java: >> 125) >> at >> com >> .sun >> .enterprise.v3.services.impl.GrizzlyProxy.<init>(GrizzlyProxy.java: >> 116) >> >> BR, >> Mohamed >> >> Oleksiy Stashok wrote: >>> >>> Hello again :) >>> >>>> I see the changes is with network listener protocol attribute value >>>> for the >>>> http and admin listeners. I tested all possible alternatives before >>>> bothering you with one more question:). >>> Just to check, do you see any exceptions in a log? >>> >>> >>>> btw I am using glassfish-v3-b66-windows version. Could it be the a >>>> problem >>>> with this build? >>> It should be fine, I believe. >>> >>>> I have attached TCPProtcol.jar in case if you wanted to test it >>>> yourself, >>>> but I doubt it even reached the pointer where the classes were >>>> loaded >>>> http://www.nabble.com/file/p25767056/TCPProtocol.jar >>>> TCPProtocol.jar >>> Ok, how do you include jar above to a GF? :) IMO this is the issue. >>> >>> AFAIK you have to create osgi module from your jar and install it to >>> GFv3. >>> >>> 1) How to create osgi module? >>> Here I'm not big expert. You can take a look on internet, or check >>> grizzly project's maven scripts to see how you can make osgi module. >>> What I did with the jar you sent - is unpacked it and changed >>> MANIFEST.MF file, so it looks like [1] and then repackaged jar file >>> again. >>> >>> 2) Install osgi module to GFv3 >>> Not sure, may be it could be done easier way, but here are steps I >>> did. >>> >>> 2.1) Enabled Felix shell for GFv3 >>> You can take a look here [2], but note that paths there are >>> incorrect. >>> Here are correct paths [3] >>> >>> 2.2) Install osgi module >>> Please look at [4], starting from step 5, but run glassfish using >>> (suppose you're in glassfishv3/bin folder) >>> java -Xmx512m -jar ../glassfish/modules/glassfish.jar >>> >>> 2.3) Done >>> After installing osgi module, restart GFv3 - it should work. >>> Seems it works for me. >>> >>> Thanks. >>> >>> WBR, >>> Alexey. >>> >>> >>> [1] >>> Manifest-Version: 1.0 >>> Ant-Version: Apache Ant 1.7.1 >>> Created-By: 14.0-b16 (Sun Microsystems Inc.) >>> X-COMMENT: Main-Class will be added automatically by build >>> Export-Package: scedev.grizzly.protocols >>> implementation-version: 0.1 >>> package: scedev.grizzly.protocols >>> Bundle-Name: scedev-grizzly >>> Bundle-Vendor: scedev >>> Bundle-Version: 0.1 >>> Bnd-LastModified: 1254747835722 >>> Bundle-ManifestVersion: 2 >>> Bundle-SymbolicName: scedev.grizzly.protocols >>> Import-Package: >>> com >>> .sun >>> .grizzly >>> ,com >>> .sun >>> .grizzly >>> .filter >>> ,com >>> .sun >>> .grizzly >>> .http >>> ,com >>> .sun >>> .grizzly.http.portunif,com.sun.grizzly.portunif,com.sun.grizzly.util >>> >>> [2] http://blogs.sun.com/arungupta/entry/totd_34_using_felix_shell >>> >>> [3] felix.auto.start.1= \ >>> reference:${com.sun.aas.installRootURI}modules/osgi-main.jar\ >>> ${com.sun.aas.installRootURI}modules/org.apache.felix.shell.jar \ >>> ${com.sun.aas.installRootURI}modules/org.apache.felix.shell.tui.jar >>> >>> [4] http://blogs.sun.com/arungupta/entry/totd_36_deploy_osgi_bundles >>> >>> >>>> >>>> Oleksiy Stashok wrote: >>>>> >>>>> Hi Mohamed, >>>>> >>>>> my fault, please try following config: >>>>> >>>>> <network-config> >>>>> <protocols> >>>>> <protocol name="pu-protocol"> >>>>> <port-unification> >>>>> <protocol-finder protocol="http" >>>>> classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" >>>>> name="http-finder" /> >>>>> <protocol-finder protocol="rpc" >>>>> classname="scedev.grizzly.protocols.TCPProtocolFinder" name="rpc- >>>>> protocol-finder" /> >>>>> </port-unification> >>>>> </protocol> >>>>> <protocol name="http"> >>>>> <http max-connections="250" default-virtual- >>>>> server="server" server-name="" /> >>>>> </protocol> >>>>> <protocol name="rpc"> >>>>> <protocol-chain-instance-handler> >>>>> <protocol-chain> >>>>> <protocol-filter >>>>> classname="scedev.grizzly.protocols.TCPProtocolFilter" name="rpc- >>>>> filter" /> >>>>> </protocol-chain> >>>>> </protocol-chain-instance-handler> >>>>> </protocol> >>>>> <protocol name="http-listener-1"> >>>>> <http max-connections="250" default-virtual- >>>>> server="server" server-name=""> >>>>> <file-cache enabled="false" /> >>>>> </http> >>>>> </protocol> >>>>> <protocol security-enabled="true" name="http-listener-2"> >>>>> <http max-connections="250" default-virtual- >>>>> server="server" server-name=""> >>>>> <file-cache enabled="false" /> >>>>> </http> >>>>> <ssl ssl3-enabled="false" cert-nickname="s1as" /> >>>>> </protocol> >>>>> <protocol name="admin-listener"> >>>>> <http max-connections="250" default-virtual- >>>>> server="__asadmin" server-name=""> >>>>> <file-cache enabled="false" /> >>>>> </http> >>>>> </protocol> >>>>> </protocols> >>>>> <network-listeners> >>>>> <network-listener port="8787" protocol="pu-protocol" >>>>> transport="tcp" name="tcprpc-listener" thread-pool="thread- >>>>> pool-1" /> >>>>> <network-listener port="8080" protocol="http-listener-1" >>>>> transport="tcp" name="http-listener-1" thread-pool="http-thread- >>>>> pool" /> >>>>> <network-listener port="4848" protocol="admin-listener" >>>>> transport="tcp" name="admin-listener" thread-pool="thread- >>>>> pool-1" /> >>>>> </network-listeners> >>>>> <transports> >>>>> <transport name="tcp" /> >>>>> </transports> >>>>> </network-config> >>>>> >>>>> WBR, >>>>> Alexey. >>>>> >>>>> On Oct 6, 2009, at 12:53 , melshami wrote: >>>>> >>>>>> >>>>>> Hi Alexey, >>>>>> >>>>>> Thanks for bearing with me, still no luck. I tried your >>>>>> suggestion >>>>>> and I >>>>>> tried different variations of configuration protocol element. >>>>>> >>>>>> here is my current configuration: >>>>>> <network-config> >>>>>> <protocols> >>>>>> <protocol name="pu-protocol"> >>>>>> <port-unification> >>>>>> <protocol-finder protocol="http" >>>>>> classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" >>>>>> name="http-finder" /> >>>>>> <protocol-finder protocol="rpc" >>>>>> classname="scedev.grizzly.protocols.TCPProtocolFinder" >>>>>> name="rpc-protocol-finder" /> >>>>>> </port-unification> >>>>>> </protocol> >>>>>> <protocol name="http" /> >>>>>> <protocol name="rpc"> >>>>>> <protocol-chain-instance-handler> >>>>>> <protocol-chain> >>>>>> <protocol-filter >>>>>> classname="scedev.grizzly.protocols.TCPProtocolFilter" name="rpc- >>>>>> filter" /> >>>>>> </protocol-chain> >>>>>> </protocol-chain-instance-handler> >>>>>> </protocol> >>>>>> <protocol name="http-listener-1"> >>>>>> <http max-connections="250" default-virtual- >>>>>> server="server" >>>>>> server-name=""> >>>>>> <file-cache enabled="false" /> >>>>>> </http> >>>>>> </protocol> >>>>>> <protocol security-enabled="true" name="http-listener-2"> >>>>>> <http max-connections="250" default-virtual- >>>>>> server="server" >>>>>> server-name=""> >>>>>> <file-cache enabled="false" /> >>>>>> </http> >>>>>> <ssl ssl3-enabled="false" cert-nickname="s1as" /> >>>>>> </protocol> >>>>>> <protocol name="admin-listener"> >>>>>> <http max-connections="250" default-virtual- >>>>>> server="__asadmin" >>>>>> server-name=""> >>>>>> <file-cache enabled="false" /> >>>>>> </http> >>>>>> </protocol> >>>>>> </protocols> >>>>>> <network-listeners> >>>>>> <network-listener port="8787" protocol="pu-protocol" >>>>>> transport="tcp" name="tcprpc-listener" thread-pool="thread- >>>>>> pool-1" /> >>>>>> <network-listener port="8080" protocol="pu-protocol" >>>>>> transport="tcp" name="http-listener-1" thread-pool="http-thread- >>>>>> pool" /> >>>>>> <network-listener port="4848" protocol="pu-protocol" >>>>>> transport="tcp" name="admin-listener" thread-pool="thread- >>>>>> pool-1" /> >>>>>> </network-listeners> >>>>>> <transports> >>>>>> <transport name="tcp" /> >>>>>> </transports> >>>>>> </network-config> >>>>>> >>>>>> Oleksiy Stashok wrote: >>>>>>> >>>>>>> Hi Mohamed, >>>>>>> >>>>>>> hmm, this is a bug - I'll fix it for coming GF release. >>>>>>> Meanwhile you can workaround this issue by declaring http >>>>>>> protocol, >>>>>>> within the port unification declaration, together with rpc >>>>>>> protocol, >>>>>>> like: >>>>>>> >>>>>>> <protocol name="pu-protocol"> >>>>>>> <port-unification> >>>>>>> <protocol-finder name="http-finder" >>>>>>> classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" >>>>>>> protocol="http"/> >>>>>>> <protocol-finder name="rpc-protocol-finder" >>>>>>> classname="scedev.grizzly.protocols.TCPProtocolFinder" >>>>>>> protocol="rpc"/> >>>>>>> </port-unification> >>>>>>> </protocol> >>>>>>> >>>>>>> <protocol name="http"> >>>>>>> </protocol> >>>>>>> >>>>>>> >>>>>>> WBR, >>>>>>> Alexey. >>>>>>> >>>>>>> On Oct 6, 2009, at 10:55 , melshami wrote: >>>>>>> >>>>>>>> >>>>>>>> Hi Alexey, >>>>>>>> >>>>>>>> I Can't seem to get this right, here is my configuration: >>>>>>>> >>>>>>>> <network-config> >>>>>>>> <protocols> >>>>>>>> <protocol name="pu-protocol"> >>>>>>>> <port-unification> >>>>>>>> <protocol-finder protocol="rpc" name="rpc-protocol- >>>>>>>> finder" >>>>>>>> classname="scedev.grizzly.protocols.TCPProtocolFinder" /> >>>>>>>> </port-unification> >>>>>>>> </protocol> >>>>>>>> <protocol name="rpc"> >>>>>>>> <protocol-chain-instance-handler> >>>>>>>> <protocol-chain> >>>>>>>> <protocol-filter name="rpc" >>>>>>>> classname="scedev.grizzly.protocols.TCPProtocolFilter" /> >>>>>>>> </protocol-chain> >>>>>>>> </protocol-chain-instance-handler> >>>>>>>> </protocol> >>>>>>>> <protocol name="http-listener-1"> >>>>>>>> <http default-virtual-server="server" max- >>>>>>>> connections="250" >>>>>>>> server-name=""> >>>>>>>> <file-cache enabled="false" /> >>>>>>>> </http> >>>>>>>> </protocol> >>>>>>>> <protocol security-enabled="true" name="http-listener-2"> >>>>>>>> <http default-virtual-server="server" max- >>>>>>>> connections="250" >>>>>>>> server-name=""> >>>>>>>> <file-cache enabled="false" /> >>>>>>>> </http> >>>>>>>> <ssl ssl3-enabled="false" cert-nickname="s1as" /> >>>>>>>> </protocol> >>>>>>>> <protocol name="admin-listener"> >>>>>>>> <http default-virtual-server="__asadmin" max- >>>>>>>> connections="250" >>>>>>>> server-name=""> >>>>>>>> <file-cache enabled="false" /> >>>>>>>> </http> >>>>>>>> </protocol> >>>>>>>> </protocols> >>>>>>>> <network-listeners> >>>>>>>> <network-listener port="8787" protocol="pu-protocol" >>>>>>>> transport="tcp" name="tcprpc-listener" thread-pool="http- >>>>>>>> thread- >>>>>>>> pool" /> >>>>>>>> <network-listener port="8080" protocol="http-listener-1" >>>>>>>> transport="tcp" name="http-listener-1" thread-pool="http- >>>>>>>> thread- >>>>>>>> pool" /> >>>>>>>> <network-listener port="8181" protocol="http-listener-2" >>>>>>>> transport="tcp" name="http-listener-2" thread-pool="http- >>>>>>>> thread- >>>>>>>> pool" /> >>>>>>>> <network-listener port="4848" protocol="admin-listener" >>>>>>>> transport="tcp" name="admin-listener" thread-pool="http-thread- >>>>>>>> pool" /> >>>>>>>> </network-listeners> >>>>>>>> <transports> >>>>>>>> <transport name="tcp" /> >>>>>>>> </transports> >>>>>>>> </network-config> >>>>>>>> >>>>>>>> GlassFish won't start due to this exception: >>>>>>>> >>>>>>>> #|2009-10-06T09:48:46.654+0100|SEVERE|glassfish|null| >>>>>>>> _ThreadID=11;_ThreadName=Thread-3;|Unable >>>>>>>> to start v3. Closing all ports >>>>>>>> java.lang.NullPointerException >>>>>>>> at >>>>>>>> com >>>>>>>> .sun >>>>>>>> .grizzly >>>>>>>> .config >>>>>>>> .GrizzlyServiceListener >>>>>>>> .initializeListener(GrizzlyServiceListener.java:83) >>>>>>>> at >>>>>>>> com >>>>>>>> .sun >>>>>>>> .grizzly >>>>>>>> .config >>>>>>>> .GrizzlyServiceListener.configure(GrizzlyServiceListener.java: >>>>>>>> 77) >>>>>>>> at >>>>>>>> com >>>>>>>> .sun >>>>>>>> .enterprise >>>>>>>> .v3 >>>>>>>> .services.impl.GrizzlyListener.configure(GrizzlyListener.java: >>>>>>>> 59) >>>>>>>> at >>>>>>>> com >>>>>>>> .sun >>>>>>>> .enterprise >>>>>>>> .v3 >>>>>>>> .services.impl.GrizzlyProxy.configureGrizzly(GrizzlyProxy.java: >>>>>>>> 125) >>>>>>>> at >>>>>>>> com >>>>>>>> .sun >>>>>>>> .enterprise >>>>>>>> .v3.services.impl.GrizzlyProxy.<init>(GrizzlyProxy.java: >>>>>>>> 116) >>>>>>>> at >>>>>>>> com >>>>>>>> .sun >>>>>>>> .enterprise >>>>>>>> .v3 >>>>>>>> .services >>>>>>>> .impl.GrizzlyService.createNetworkProxy(GrizzlyService.java: >>>>>>>> 344) >>>>>>>> at >>>>>>>> com >>>>>>>> .sun >>>>>>>> .enterprise >>>>>>>> .v3 >>>>>>>> .services >>>>>>>> .impl.GrizzlyService.postConstruct(GrizzlyService.java: >>>>>>>> 266) >>>>>>>> at >>>>>>>> com >>>>>>>> .sun >>>>>>>> .hk2.component.AbstractWombImpl.inject(AbstractWombImpl.java: >>>>>>>> 174) >>>>>>>> at com.sun.hk2.component.ConstructorWomb >>>>>>>> $1.run(ConstructorWomb.java: >>>>>>>> 91) >>>>>>>> at java.security.AccessController.doPrivileged(Native Method) >>>>>>>> >>>>>>>> I have set the classpath for the custom protocol filter and >>>>>>>> finder >>>>>>>> in the >>>>>>>> JVM classpath settings. >>>>>>>> >>>>>>>> Is there anything else I am missing? >>>>>>>> >>>>>>>> Regards, >>>>>>>> Mohamed >>>>>>>> >>>>>>>> melshami wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> It's not a problem at all, am still testing we have enough >>>>>>>>> time >>>>>>>>> before >>>>>>>>> production so I hope there will be a new release soon. I >>>>>>>>> will try >>>>>>>>> that and >>>>>>>>> will get back to you. >>>>>>>>> >>>>>>>>> Thanks for your help:) >>>>>>>>> >>>>>>>>> >>>>>>>>> Oleksiy Stashok wrote: >>>>>>>>>> >>>>>>>>>>> I think since I am using glassfish-prelude v3 it still >>>>>>>>>>> uses v2 >>>>>>>>>>> configuraiton >>>>>>>>>>> scheme, if I am correct it's sun-domain_1_3.dtd which has >>>>>>>>>>> all >>>>>>>>>>> network >>>>>>>>>>> configuration under the <http-service> element. So I am not >>>>>>>>>>> sure >>>>>>>>>>> where to >>>>>>>>>>> set the protocol-finder name under this scheme. >>>>>>>>>> I think there is no way to use port unification with >>>>>>>>>> prelude :( >>>>>>>>>> Will it be a problem for you to use latest promoted GFv3 [1]? >>>>>>>>>> >>>>>>>>>> Thanks. >>>>>>>>>> >>>>>>>>>> WBR, >>>>>>>>>> Alexey. >>>>>>>>>> >>>>>>>>>> [1] http://download.java.net/glassfish/v3/promoted/ >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>>> Mohamed >>>>>>>>>>> >>>>>>>>>>> Oleksiy Stashok wrote: >>>>>>>>>>>> >>>>>>>>>>>> Hi, >>>>>>>>>>>> >>>>>>>>>>>> you can take a look at config module in grizzly workspace >>>>>>>>>>>> [1]. >>>>>>>>>>>> There you can find unit tests with different configurations >>>>>>>>>>>> like >>>>>>>>>>>> [2], >>>>>>>>>>>> which actually has port unification enabled, but you can >>>>>>>>>>>> redefine >>>>>>>>>>>> config to use X-protocol directly without port unification. >>>>>>>>>>>> >>>>>>>>>>>> WBR, >>>>>>>>>>>> Alexey. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> [1] svn checkout >>>>>>>>>>>> https://www.dev.java.net/svn/grizzly/trunk/code/modules/config >>>>>>>>>>>> [2] >>>>>>>>>>>> <network-config> >>>>>>>>>>>> <transports> >>>>>>>>>>>> <transport name="tcp"/> >>>>>>>>>>>> </transports> >>>>>>>>>>>> <protocols> >>>>>>>>>>>> <protocol name="pu-protocol"> >>>>>>>>>>>> <port-unification> >>>>>>>>>>>> <protocol-finder name="http-finder" >>>>>>>>>>>> classname >>>>>>>>>>>> ="com.sun.grizzly.http.portunif.HttpProtocolFinder" >>>>>>>>>>>> protocol="http"/> >>>>>>>>>>>> <protocol-finder name="X-protocol-finder" >>>>>>>>>>>> classname="com.sun.grizzly.config.XProtocolFinder" >>>>>>>>>>>> protocol="X- >>>>>>>>>>>> protocol"/> >>>>>>>>>>>> </port-unification> >>>>>>>>>>>> </protocol> >>>>>>>>>>>> >>>>>>>>>>>> <protocol name="http"> >>>>>>>>>>>> <http enable-comet-support="true"/> >>>>>>>>>>>> </protocol> >>>>>>>>>>>> >>>>>>>>>>>> <protocol name="X-protocol"> >>>>>>>>>>>> <protocol-chain-instance-handler> >>>>>>>>>>>> <protocol-chain> >>>>>>>>>>>> <protocol-filter name="x-filter" >>>>>>>>>>>> classname="com.sun.grizzly.config.XProtocolFilter"/> >>>>>>>>>>>> </protocol-chain> >>>>>>>>>>>> </protocol-chain-instance-handler> >>>>>>>>>>>> </protocol> >>>>>>>>>>>> >>>>>>>>>>>> </protocols> >>>>>>>>>>>> <network-listeners> >>>>>>>>>>>> <thread-pool name="defaultThreadPool"/> >>>>>>>>>>>> <network-listener name="http-listener" port="38082" >>>>>>>>>>>> transport="tcp" protocol="pu-protocol" thread- >>>>>>>>>>>> pool="defaultThreadPool"/> >>>>>>>>>>>> </network-listeners> >>>>>>>>>>>> </network-config> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Oct 5, 2009, at 15:14 , melshami wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Hi Alexey, >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks very much for the prompt reply. I am a bit >>>>>>>>>>>>> confused to >>>>>>>>>>>>> be >>>>>>>>>>>>> honest >>>>>>>>>>>>> since I am new to Grizzly. But I wish to configure a >>>>>>>>>>>>> listener >>>>>>>>>>>>> which >>>>>>>>>>>>> listens >>>>>>>>>>>>> to custom TCP based protocol. As a starting point I am >>>>>>>>>>>>> trying >>>>>>>>>>>>> to >>>>>>>>>>>>> configure a >>>>>>>>>>>>> simple echo server which replies to socket connections on >>>>>>>>>>>>> GlassFish >>>>>>>>>>>>> v3. >>>>>>>>>>>>> >>>>>>>>>>>>> Regards, >>>>>>>>>>>>> Mohamed >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Oleksiy Stashok wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Hi Mohamed, >>>>>>>>>>>>>> >>>>>>>>>>>>>>> I can't seem to find any documentation for how to >>>>>>>>>>>>>>> configure >>>>>>>>>>>>>>> grizlly >>>>>>>>>>>>>>> listeners and connectors on GlassFish v3. >>>>>>>>>>>>>> Currently doc team is working on that. >>>>>>>>>>>>>> >>>>>>>>>>>>>>> So far I can find only this page >>>>>>>>>>>>>>> http://wiki.glassfish.java.net/Wiki.jsp? >>>>>>>>>>>>>>> page=GrizzlyConfigOnePager, >>>>>>>>>>>>>>> which >>>>>>>>>>>>>>> refers to a new scheme and it's not complete yet. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Anyone can help with this please? >>>>>>>>>>>>>> Do you have any specific item in mind you'd like to >>>>>>>>>>>>>> configure? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks. >>>>>>>>>>>>>> >>>>>>>>>>>>>> WBR, >>>>>>>>>>>>>> Alexey. >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> BR, >>>>>>>>>>>>>>> Mohamed >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> View this message in context: >>>>>>>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25750048.html >>>>>>>>>>>>>>> Sent from the Grizzly - Users mailing list archive at >>>>>>>>>>>>>>> Nabble.com. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>>>>>>> To unsubscribe, e-mail: users- >>>>>>>>>>>>>>> unsubscribe@... >>>>>>>>>>>>>>> For additional commands, e-mail: users- >>>>>>>>>>>>>>> help@... >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>>>>>>>>>> For additional commands, e-mail: >>>>>>>>>>>>>> users-help@... >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> View this message in context: >>>>>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25750628.html >>>>>>>>>>>>> Sent from the Grizzly - Users mailing list archive at >>>>>>>>>>>>> Nabble.com. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>>>>> To unsubscribe, e-mail: users- >>>>>>>>>>>>> unsubscribe@... >>>>>>>>>>>>> For additional commands, e-mail: users- >>>>>>>>>>>>> help@... >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> View this message in context: >>>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25752899.html >>>>>>>>>>> Sent from the Grizzly - Users mailing list archive at >>>>>>>>>>> Nabble.com. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>>>>>>> For additional commands, e-mail: users- >>>>>>>>>>> help@... >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>> To unsubscribe, e-mail: users- >>>>>>>>>> unsubscribe@... >>>>>>>>>> For additional commands, e-mail: users-help@... >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> View this message in context: >>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25765021.html >>>>>>>> Sent from the Grizzly - Users mailing list archive at >>>>>>>> Nabble.com. >>>>>>>> >>>>>>>> >>>>>>>> --------------------------------------------------------------------- >>>>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>>>> For additional commands, e-mail: users- >>>>>>>> help@... >>>>>>>> >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>>> For additional commands, e-mail: users-help@... >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25766557.html >>>>>> Sent from the Grizzly - Users mailing list archive at Nabble.com. >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>> For additional commands, e-mail: users-help@... >>>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>> For additional commands, e-mail: users-help@... >>>>> >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25767056.html >>>> Sent from the Grizzly - Users mailing list archive at Nabble.com. >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscribe@... >>>> For additional commands, e-mail: users-help@... >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscribe@... >>> For additional commands, e-mail: users-help@... >>> >>> >>> >> >> > > -- > View this message in context: http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25802994.html > Sent from the Grizzly - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Grizzly configuration on Glassfish v3
by melshami
::
Rate this Message:
Hi Alexey,
Thanks again for your reply. I normally run java -Xmx512m -jar ../glassfish/modules/glassfish.jar by default, exception above was captured from the console. I luanched glassfish again and compared server.log to the console, couldn't really find differences. I have attached server.log if you like to have a look. Thanks. BR, Mohamedserver.log
|
|
|
Re: Grizzly configuration on Glassfish v3
by Oleksiy Stashok
::
Rate this Message:
Hi Mohamed,
can you pls. send me your domain.xml? Thanks. WBR, Alexey. > Thanks again for your reply. I normally run java -Xmx512m -jar > ../glassfish/modules/glassfish.jar by default, exception above was > captured > from the console. I luanched glassfish again and compared server.log > to the > console, couldn't really find differences. I have attached > server.log if you > like to have a look. Thanks. > > BR, > Mohamed http://www.nabble.com/file/p25817601/server.log server.log > > Oleksiy Stashok wrote: >> >> Hi Mohamed, >> >> >>> Sorry for cross posting but I posted another question regarding TCP/ >>> SOAP in >>> GlassFish here >>> http://www.nabble.com/SOAP-TCP-has-been-integrated-to-Glassfish-V3-td25045927.html#a25045927 >>> . >> Oh, it's difficult to follow all the forums :) >> >>> >>> After reading Paul's and your blog posts. I realise TCP-SOAP is >>> already >>> integrated, >> That's true. >> >>> I can find soap-tcp.jar under the modules. I added a >>> configuration similiar to the one you posted but Glassfish fails to >>> start. >> What exactly error you see? >> Can you pls. run the GF is standalone mode like: >> java -Xmx512m -jar ../glassfish/modules/glassfish.jar >> >> cause there is some logging issue now, and you may not see entire log >> in server.log file. >> >> Thanks. >> >> WBR, >> Alexey. >> >>> >>> melshami wrote: >>>> >>>> Thanks Alexey, I managed to install the bundle using Flex shell, I >>>> think >>>> in the current build there is no need to add other paths to >>>> felix.auto.start.1, now I will need to test the custom filter:) >>>> >>>> The exception is similiar to the previous one but I don't think >>>> it's >>>> ClassDefNotFound exception. >>>> >>>> java.lang.NullPointerException >>>> at >>>> com >>>> .sun >>>> .grizzly >>>> .config >>>> .GrizzlyServiceListener >>>> .initializeListener(GrizzlyServiceListener.java:83) >>>> at >>>> com >>>> .sun >>>> .grizzly >>>> .config >>>> .GrizzlyServiceListener.configure(GrizzlyServiceListener.java:77) >>>> at >>>> com >>>> .sun >>>> .enterprise >>>> .v3.services.impl.GrizzlyListener.configure(GrizzlyListener.java: >>>> 59) >>>> at >>>> com >>>> .sun >>>> .enterprise >>>> .v3.services.impl.GrizzlyProxy.configureGrizzly(GrizzlyProxy.java: >>>> 125) >>>> at >>>> com >>>> .sun >>>> .enterprise.v3.services.impl.GrizzlyProxy.<init>(GrizzlyProxy.java: >>>> 116) >>>> >>>> BR, >>>> Mohamed >>>> >>>> Oleksiy Stashok wrote: >>>>> >>>>> Hello again :) >>>>> >>>>>> I see the changes is with network listener protocol attribute >>>>>> value >>>>>> for the >>>>>> http and admin listeners. I tested all possible alternatives >>>>>> before >>>>>> bothering you with one more question:). >>>>> Just to check, do you see any exceptions in a log? >>>>> >>>>> >>>>>> btw I am using glassfish-v3-b66-windows version. Could it be >>>>>> the a >>>>>> problem >>>>>> with this build? >>>>> It should be fine, I believe. >>>>> >>>>>> I have attached TCPProtcol.jar in case if you wanted to test it >>>>>> yourself, >>>>>> but I doubt it even reached the pointer where the classes were >>>>>> loaded >>>>>> http://www.nabble.com/file/p25767056/TCPProtocol.jar >>>>>> TCPProtocol.jar >>>>> Ok, how do you include jar above to a GF? :) IMO this is the >>>>> issue. >>>>> >>>>> AFAIK you have to create osgi module from your jar and install >>>>> it to >>>>> GFv3. >>>>> >>>>> 1) How to create osgi module? >>>>> Here I'm not big expert. You can take a look on internet, or check >>>>> grizzly project's maven scripts to see how you can make osgi >>>>> module. >>>>> What I did with the jar you sent - is unpacked it and changed >>>>> MANIFEST.MF file, so it looks like [1] and then repackaged jar >>>>> file >>>>> again. >>>>> >>>>> 2) Install osgi module to GFv3 >>>>> Not sure, may be it could be done easier way, but here are steps I >>>>> did. >>>>> >>>>> 2.1) Enabled Felix shell for GFv3 >>>>> You can take a look here [2], but note that paths there are >>>>> incorrect. >>>>> Here are correct paths [3] >>>>> >>>>> 2.2) Install osgi module >>>>> Please look at [4], starting from step 5, but run glassfish using >>>>> (suppose you're in glassfishv3/bin folder) >>>>> java -Xmx512m -jar ../glassfish/modules/glassfish.jar >>>>> >>>>> 2.3) Done >>>>> After installing osgi module, restart GFv3 - it should work. >>>>> Seems it works for me. >>>>> >>>>> Thanks. >>>>> >>>>> WBR, >>>>> Alexey. >>>>> >>>>> >>>>> [1] >>>>> Manifest-Version: 1.0 >>>>> Ant-Version: Apache Ant 1.7.1 >>>>> Created-By: 14.0-b16 (Sun Microsystems Inc.) >>>>> X-COMMENT: Main-Class will be added automatically by build >>>>> Export-Package: scedev.grizzly.protocols >>>>> implementation-version: 0.1 >>>>> package: scedev.grizzly.protocols >>>>> Bundle-Name: scedev-grizzly >>>>> Bundle-Vendor: scedev >>>>> Bundle-Version: 0.1 >>>>> Bnd-LastModified: 1254747835722 >>>>> Bundle-ManifestVersion: 2 >>>>> Bundle-SymbolicName: scedev.grizzly.protocols >>>>> Import-Package: >>>>> com >>>>> .sun >>>>> .grizzly >>>>> ,com >>>>> .sun >>>>> .grizzly >>>>> .filter >>>>> ,com >>>>> .sun >>>>> .grizzly >>>>> .http >>>>> ,com >>>>> .sun >>>>> .grizzly >>>>> .http.portunif,com.sun.grizzly.portunif,com.sun.grizzly.util >>>>> >>>>> [2] http://blogs.sun.com/arungupta/entry/totd_34_using_felix_shell >>>>> >>>>> [3] felix.auto.start.1= \ >>>>> reference:${com.sun.aas.installRootURI}modules/osgi-main.jar\ >>>>> ${com.sun.aas.installRootURI}modules/org.apache.felix.shell.jar \ >>>>> ${com.sun.aas.installRootURI}modules/ >>>>> org.apache.felix.shell.tui.jar >>>>> >>>>> [4] http://blogs.sun.com/arungupta/entry/totd_36_deploy_osgi_bundles >>>>> >>>>> >>>>>> >>>>>> Oleksiy Stashok wrote: >>>>>>> >>>>>>> Hi Mohamed, >>>>>>> >>>>>>> my fault, please try following config: >>>>>>> >>>>>>> <network-config> >>>>>>> <protocols> >>>>>>> <protocol name="pu-protocol"> >>>>>>> <port-unification> >>>>>>> <protocol-finder protocol="http" >>>>>>> classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" >>>>>>> name="http-finder" /> >>>>>>> <protocol-finder protocol="rpc" >>>>>>> classname="scedev.grizzly.protocols.TCPProtocolFinder" >>>>>>> name="rpc- >>>>>>> protocol-finder" /> >>>>>>> </port-unification> >>>>>>> </protocol> >>>>>>> <protocol name="http"> >>>>>>> <http max-connections="250" default-virtual- >>>>>>> server="server" server-name="" /> >>>>>>> </protocol> >>>>>>> <protocol name="rpc"> >>>>>>> <protocol-chain-instance-handler> >>>>>>> <protocol-chain> >>>>>>> <protocol-filter >>>>>>> classname="scedev.grizzly.protocols.TCPProtocolFilter" >>>>>>> name="rpc- >>>>>>> filter" /> >>>>>>> </protocol-chain> >>>>>>> </protocol-chain-instance-handler> >>>>>>> </protocol> >>>>>>> <protocol name="http-listener-1"> >>>>>>> <http max-connections="250" default-virtual- >>>>>>> server="server" server-name=""> >>>>>>> <file-cache enabled="false" /> >>>>>>> </http> >>>>>>> </protocol> >>>>>>> <protocol security-enabled="true" name="http- >>>>>>> listener-2"> >>>>>>> <http max-connections="250" default-virtual- >>>>>>> server="server" server-name=""> >>>>>>> <file-cache enabled="false" /> >>>>>>> </http> >>>>>>> <ssl ssl3-enabled="false" cert-nickname="s1as" /> >>>>>>> </protocol> >>>>>>> <protocol name="admin-listener"> >>>>>>> <http max-connections="250" default-virtual- >>>>>>> server="__asadmin" server-name=""> >>>>>>> <file-cache enabled="false" /> >>>>>>> </http> >>>>>>> </protocol> >>>>>>> </protocols> >>>>>>> <network-listeners> >>>>>>> <network-listener port="8787" protocol="pu-protocol" >>>>>>> transport="tcp" name="tcprpc-listener" thread-pool="thread- >>>>>>> pool-1" /> >>>>>>> <network-listener port="8080" protocol="http-listener-1" >>>>>>> transport="tcp" name="http-listener-1" thread-pool="http-thread- >>>>>>> pool" /> >>>>>>> <network-listener port="4848" protocol="admin-listener" >>>>>>> transport="tcp" name="admin-listener" thread-pool="thread- >>>>>>> pool-1" /> >>>>>>> </network-listeners> >>>>>>> <transports> >>>>>>> <transport name="tcp" /> >>>>>>> </transports> >>>>>>> </network-config> >>>>>>> >>>>>>> WBR, >>>>>>> Alexey. >>>>>>> >>>>>>> On Oct 6, 2009, at 12:53 , melshami wrote: >>>>>>> >>>>>>>> >>>>>>>> Hi Alexey, >>>>>>>> >>>>>>>> Thanks for bearing with me, still no luck. I tried your >>>>>>>> suggestion >>>>>>>> and I >>>>>>>> tried different variations of configuration protocol element. >>>>>>>> >>>>>>>> here is my current configuration: >>>>>>>> <network-config> >>>>>>>> <protocols> >>>>>>>> <protocol name="pu-protocol"> >>>>>>>> <port-unification> >>>>>>>> <protocol-finder protocol="http" >>>>>>>> classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" >>>>>>>> name="http-finder" /> >>>>>>>> <protocol-finder protocol="rpc" >>>>>>>> classname="scedev.grizzly.protocols.TCPProtocolFinder" >>>>>>>> name="rpc-protocol-finder" /> >>>>>>>> </port-unification> >>>>>>>> </protocol> >>>>>>>> <protocol name="http" /> >>>>>>>> <protocol name="rpc"> >>>>>>>> <protocol-chain-instance-handler> >>>>>>>> <protocol-chain> >>>>>>>> <protocol-filter >>>>>>>> classname="scedev.grizzly.protocols.TCPProtocolFilter" >>>>>>>> name="rpc- >>>>>>>> filter" /> >>>>>>>> </protocol-chain> >>>>>>>> </protocol-chain-instance-handler> >>>>>>>> </protocol> >>>>>>>> <protocol name="http-listener-1"> >>>>>>>> <http max-connections="250" default-virtual- >>>>>>>> server="server" >>>>>>>> server-name=""> >>>>>>>> <file-cache enabled="false" /> >>>>>>>> </http> >>>>>>>> </protocol> >>>>>>>> <protocol security-enabled="true" name="http-listener-2"> >>>>>>>> <http max-connections="250" default-virtual- >>>>>>>> server="server" >>>>>>>> server-name=""> >>>>>>>> <file-cache enabled="false" /> >>>>>>>> </http> >>>>>>>> <ssl ssl3-enabled="false" cert-nickname="s1as" /> >>>>>>>> </protocol> >>>>>>>> <protocol name="admin-listener"> >>>>>>>> <http max-connections="250" default-virtual- >>>>>>>> server="__asadmin" >>>>>>>> server-name=""> >>>>>>>> <file-cache enabled="false" /> >>>>>>>> </http> >>>>>>>> </protocol> >>>>>>>> </protocols> >>>>>>>> <network-listeners> >>>>>>>> <network-listener port="8787" protocol="pu-protocol" >>>>>>>> transport="tcp" name="tcprpc-listener" thread-pool="thread- >>>>>>>> pool-1" /> >>>>>>>> <network-listener port="8080" protocol="pu-protocol" >>>>>>>> transport="tcp" name="http-listener-1" thread-pool="http- >>>>>>>> thread- >>>>>>>> pool" /> >>>>>>>> <network-listener port="4848" protocol="pu-protocol" >>>>>>>> transport="tcp" name="admin-listener" thread-pool="thread- >>>>>>>> pool-1" /> >>>>>>>> </network-listeners> >>>>>>>> <transports> >>>>>>>> <transport name="tcp" /> >>>>>>>> </transports> >>>>>>>> </network-config> >>>>>>>> >>>>>>>> Oleksiy Stashok wrote: >>>>>>>>> >>>>>>>>> Hi Mohamed, >>>>>>>>> >>>>>>>>> hmm, this is a bug - I'll fix it for coming GF release. >>>>>>>>> Meanwhile you can workaround this issue by declaring http >>>>>>>>> protocol, >>>>>>>>> within the port unification declaration, together with rpc >>>>>>>>> protocol, >>>>>>>>> like: >>>>>>>>> >>>>>>>>> <protocol name="pu-protocol"> >>>>>>>>> <port-unification> >>>>>>>>> <protocol-finder name="http-finder" >>>>>>>>> classname="com.sun.grizzly.http.portunif.HttpProtocolFinder" >>>>>>>>> protocol="http"/> >>>>>>>>> <protocol-finder name="rpc-protocol-finder" >>>>>>>>> classname="scedev.grizzly.protocols.TCPProtocolFinder" >>>>>>>>> protocol="rpc"/> >>>>>>>>> </port-unification> >>>>>>>>> </protocol> >>>>>>>>> >>>>>>>>> <protocol name="http"> >>>>>>>>> </protocol> >>>>>>>>> >>>>>>>>> >>>>>>>>> WBR, >>>>>>>>> Alexey. >>>>>>>>> >>>>>>>>> On Oct 6, 2009, at 10:55 , melshami wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Hi Alexey, >>>>>>>>>> >>>>>>>>>> I Can't seem to get this right, here is my configuration: >>>>>>>>>> >>>>>>>>>> <network-config> >>>>>>>>>> <protocols> >>>>>>>>>> <protocol name="pu-protocol"> >>>>>>>>>> <port-unification> >>>>>>>>>> <protocol-finder protocol="rpc" name="rpc-protocol- >>>>>>>>>> finder" >>>>>>>>>> classname="scedev.grizzly.protocols.TCPProtocolFinder" /> >>>>>>>>>> </port-unification> >>>>>>>>>> </protocol> >>>>>>>>>> <protocol name="rpc"> >>>>>>>>>> <protocol-chain-instance-handler> >>>>>>>>>> <protocol-chain> >>>>>>>>>> <protocol-filter name="rpc" >>>>>>>>>> classname="scedev.grizzly.protocols.TCPProtocolFilter" /> >>>>>>>>>> </protocol-chain> >>>>>>>>>> </protocol-chain-instance-handler> >>>>>>>>>> </protocol> >>>>>>>>>> <protocol name="http-listener-1"> >>>>>>>>>> <http default-virtual-server="server" max- >>>>>>>>>> connections="250" >>>>>>>>>> server-name=""> >>>>>>>>>> <file-cache enabled="false" /> >>>>>>>>>> </http> >>>>>>>>>> </protocol> >>>>>>>>>> <protocol security-enabled="true" name="http- >>>>>>>>>> listener-2"> >>>>>>>>>> <http default-virtual-server="server" max- >>>>>>>>>> connections="250" >>>>>>>>>> server-name=""> >>>>>>>>>> <file-cache enabled="false" /> >>>>>>>>>> </http> >>>>>>>>>> <ssl ssl3-enabled="false" cert-nickname="s1as" /> >>>>>>>>>> </protocol> >>>>>>>>>> <protocol name="admin-listener"> >>>>>>>>>> <http default-virtual-server="__asadmin" max- >>>>>>>>>> connections="250" >>>>>>>>>> server-name=""> >>>>>>>>>> <file-cache enabled="false" /> >>>>>>>>>> </http> >>>>>>>>>> </protocol> >>>>>>>>>> </protocols> >>>>>>>>>> <network-listeners> >>>>>>>>>> <network-listener port="8787" protocol="pu-protocol" >>>>>>>>>> transport="tcp" name="tcprpc-listener" thread-pool="http- >>>>>>>>>> thread- >>>>>>>>>> pool" /> >>>>>>>>>> <network-listener port="8080" protocol="http-listener-1" >>>>>>>>>> transport="tcp" name="http-listener-1" thread-pool="http- >>>>>>>>>> thread- >>>>>>>>>> pool" /> >>>>>>>>>> <network-listener port="8181" protocol="http-listener-2" >>>>>>>>>> transport="tcp" name="http-listener-2" thread-pool="http- >>>>>>>>>> thread- >>>>>>>>>> pool" /> >>>>>>>>>> <network-listener port="4848" protocol="admin-listener" >>>>>>>>>> transport="tcp" name="admin-listener" thread-pool="http- >>>>>>>>>> thread- >>>>>>>>>> pool" /> >>>>>>>>>> </network-listeners> >>>>>>>>>> <transports> >>>>>>>>>> <transport name="tcp" /> >>>>>>>>>> </transports> >>>>>>>>>> </network-config> >>>>>>>>>> >>>>>>>>>> GlassFish won't start due to this exception: >>>>>>>>>> >>>>>>>>>> #|2009-10-06T09:48:46.654+0100|SEVERE|glassfish|null| >>>>>>>>>> _ThreadID=11;_ThreadName=Thread-3;|Unable >>>>>>>>>> to start v3. Closing all ports >>>>>>>>>> java.lang.NullPointerException >>>>>>>>>> at >>>>>>>>>> com >>>>>>>>>> .sun >>>>>>>>>> .grizzly >>>>>>>>>> .config >>>>>>>>>> .GrizzlyServiceListener >>>>>>>>>> .initializeListener(GrizzlyServiceListener.java:83) >>>>>>>>>> at >>>>>>>>>> com >>>>>>>>>> .sun >>>>>>>>>> .grizzly >>>>>>>>>> .config >>>>>>>>>> .GrizzlyServiceListener >>>>>>>>>> .configure(GrizzlyServiceListener.java: >>>>>>>>>> 77) >>>>>>>>>> at >>>>>>>>>> com >>>>>>>>>> .sun >>>>>>>>>> .enterprise >>>>>>>>>> .v3 >>>>>>>>>> .services >>>>>>>>>> .impl.GrizzlyListener.configure(GrizzlyListener.java: >>>>>>>>>> 59) >>>>>>>>>> at >>>>>>>>>> com >>>>>>>>>> .sun >>>>>>>>>> .enterprise >>>>>>>>>> .v3 >>>>>>>>>> .services >>>>>>>>>> .impl.GrizzlyProxy.configureGrizzly(GrizzlyProxy.java: >>>>>>>>>> 125) >>>>>>>>>> at >>>>>>>>>> com >>>>>>>>>> .sun >>>>>>>>>> .enterprise >>>>>>>>>> .v3.services.impl.GrizzlyProxy.<init>(GrizzlyProxy.java: >>>>>>>>>> 116) >>>>>>>>>> at >>>>>>>>>> com >>>>>>>>>> .sun >>>>>>>>>> .enterprise >>>>>>>>>> .v3 >>>>>>>>>> .services >>>>>>>>>> .impl.GrizzlyService.createNetworkProxy(GrizzlyService.java: >>>>>>>>>> 344) >>>>>>>>>> at >>>>>>>>>> com >>>>>>>>>> .sun >>>>>>>>>> .enterprise >>>>>>>>>> .v3 >>>>>>>>>> .services >>>>>>>>>> .impl.GrizzlyService.postConstruct(GrizzlyService.java: >>>>>>>>>> 266) >>>>>>>>>> at >>>>>>>>>> com >>>>>>>>>> .sun >>>>>>>>>> .hk2.component.AbstractWombImpl.inject(AbstractWombImpl.java: >>>>>>>>>> 174) >>>>>>>>>> at com.sun.hk2.component.ConstructorWomb >>>>>>>>>> $1.run(ConstructorWomb.java: >>>>>>>>>> 91) >>>>>>>>>> at java.security.AccessController.doPrivileged(Native >>>>>>>>>> Method) >>>>>>>>>> >>>>>>>>>> I have set the classpath for the custom protocol filter and >>>>>>>>>> finder >>>>>>>>>> in the >>>>>>>>>> JVM classpath settings. >>>>>>>>>> >>>>>>>>>> Is there anything else I am missing? >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> Mohamed >>>>>>>>>> >>>>>>>>>> melshami wrote: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> It's not a problem at all, am still testing we have enough >>>>>>>>>>> time >>>>>>>>>>> before >>>>>>>>>>> production so I hope there will be a new release soon. I >>>>>>>>>>> will try >>>>>>>>>>> that and >>>>>>>>>>> will get back to you. >>>>>>>>>>> >>>>>>>>>>> Thanks for your help:) >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Oleksiy Stashok wrote: >>>>>>>>>>>> >>>>>>>>>>>>> I think since I am using glassfish-prelude v3 it still >>>>>>>>>>>>> uses v2 >>>>>>>>>>>>> configuraiton >>>>>>>>>>>>> scheme, if I am correct it's sun-domain_1_3.dtd which has >>>>>>>>>>>>> all >>>>>>>>>>>>> network >>>>>>>>>>>>> configuration under the <http-service> element. So I am >>>>>>>>>>>>> not >>>>>>>>>>>>> sure >>>>>>>>>>>>> where to >>>>>>>>>>>>> set the protocol-finder name under this scheme. >>>>>>>>>>>> I think there is no way to use port unification with >>>>>>>>>>>> prelude :( >>>>>>>>>>>> Will it be a problem for you to use latest promoted GFv3 >>>>>>>>>>>> [1]? >>>>>>>>>>>> >>>>>>>>>>>> Thanks. >>>>>>>>>>>> >>>>>>>>>>>> WBR, >>>>>>>>>>>> Alexey. >>>>>>>>>>>> >>>>>>>>>>>> [1] http://download.java.net/glassfish/v3/promoted/ >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks, >>>>>>>>>>>>> Mohamed >>>>>>>>>>>>> >>>>>>>>>>>>> Oleksiy Stashok wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>> >>>>>>>>>>>>>> you can take a look at config module in grizzly workspace >>>>>>>>>>>>>> [1]. >>>>>>>>>>>>>> There you can find unit tests with different >>>>>>>>>>>>>> configurations >>>>>>>>>>>>>> like >>>>>>>>>>>>>> [2], >>>>>>>>>>>>>> which actually has port unification enabled, but you can >>>>>>>>>>>>>> redefine >>>>>>>>>>>>>> config to use X-protocol directly without port >>>>>>>>>>>>>> unification. >>>>>>>>>>>>>> >>>>>>>>>>>>>> WBR, >>>>>>>>>>>>>> Alexey. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> [1] svn checkout >>>>>>>>>>>>>> https://www.dev.java.net/svn/grizzly/trunk/code/modules/config >>>>>>>>>>>>>> [2] >>>>>>>>>>>>>> <network-config> >>>>>>>>>>>>>> <transports> >>>>>>>>>>>>>> <transport name="tcp"/> >>>>>>>>>>>>>> </transports> >>>>>>>>>>>>>> <protocols> >>>>>>>>>>>>>> <protocol name="pu-protocol"> >>>>>>>>>>>>>> <port-unification> >>>>>>>>>>>>>> <protocol-finder name="http-finder" >>>>>>>>>>>>>> classname >>>>>>>>>>>>>> ="com.sun.grizzly.http.portunif.HttpProtocolFinder" >>>>>>>>>>>>>> protocol="http"/> >>>>>>>>>>>>>> <protocol-finder name="X-protocol-finder" >>>>>>>>>>>>>> classname="com.sun.grizzly.config.XProtocolFinder" >>>>>>>>>>>>>> protocol="X- >>>>>>>>>>>>>> protocol"/> >>>>>>>>>>>>>> </port-unification> >>>>>>>>>>>>>> </protocol> >>>>>>>>>>>>>> >>>>>>>>>>>>>> <protocol name="http"> >>>>>>>>>>>>>> <http enable-comet-support="true"/> >>>>>>>>>>>>>> </protocol> >>>>>>>>>>>>>> >>>>>>>>>>>>>> <protocol name="X-protocol"> >>>>>>>>>>>>>> <protocol-chain-instance-handler> >>>>>>>>>>>>>> <protocol-chain> >>>>>>>>>>>>>> <protocol-filter name="x-filter" >>>>>>>>>>>>>> classname="com.sun.grizzly.config.XProtocolFilter"/> >>>>>>>>>>>>>> </protocol-chain> >>>>>>>>>>>>>> </protocol-chain-instance-handler> >>>>>>>>>>>>>> </protocol> >>>>>>>>>>>>>> >>>>>>>>>>>>>> </protocols> >>>>>>>>>>>>>> <network-listeners> >>>>>>>>>>>>>> <thread-pool name="defaultThreadPool"/> >>>>>>>>>>>>>> <network-listener name="http-listener" port="38082" >>>>>>>>>>>>>> transport="tcp" protocol="pu-protocol" thread- >>>>>>>>>>>>>> pool="defaultThreadPool"/> >>>>>>>>>>>>>> </network-listeners> >>>>>>>>>>>>>> </network-config> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Oct 5, 2009, at 15:14 , melshami wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi Alexey, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Thanks very much for the prompt reply. I am a bit >>>>>>>>>>>>>>> confused to >>>>>>>>>>>>>>> be >>>>>>>>>>>>>>> honest >>>>>>>>>>>>>>> since I am new to Grizzly. But I wish to configure a >>>>>>>>>>>>>>> listener >>>>>>>>>>>>>>> which >>>>>>>>>>>>>>> listens >>>>>>>>>>>>>>> to custom TCP based protocol. As a starting point I am >>>>>>>>>>>>>>> trying >>>>>>>>>>>>>>> to >>>>>>>>>>>>>>> configure a >>>>>>>>>>>>>>> simple echo server which replies to socket connections >>>>>>>>>>>>>>> on >>>>>>>>>>>>>>> GlassFish >>>>>>>>>>>>>>> v3. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>> Mohamed >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Oleksiy Stashok wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi Mohamed, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I can't seem to find any documentation for how to >>>>>>>>>>>>>>>>> configure >>>>>>>>>>>>>>>>> grizlly >>>>>>>>>>>>>>>>> listeners and connectors on GlassFish v3. >>>>>>>>>>>>>>>> Currently doc team is working on that. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> So far I can find only this page >>>>>>>>>>>>>>>>> http://wiki.glassfish.java.net/Wiki.jsp? >>>>>>>>>>>>>>>>> page=GrizzlyConfigOnePager, >>>>>>>>>>>>>>>>> which >>>>>>>>>>>>>>>>> refers to a new scheme and it's not complete yet. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Anyone can help with this please? >>>>>>>>>>>>>>>> Do you have any specific item in mind you'd like to >>>>>>>>>>>>>>>> configure? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Thanks. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> WBR, >>>>>>>>>>>>>>>> Alexey. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> BR, >>>>>>>>>>>>>>>>> Mohamed >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> View this message in context: >>>>>>>>>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25750048.html >>>>>>>>>>>>>>>>> Sent from the Grizzly - Users mailing list archive at >>>>>>>>>>>>>>>>> Nabble.com. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>>>>>>>>> To unsubscribe, e-mail: users- >>>>>>>>>>>>>>>>> unsubscribe@... >>>>>>>>>>>>>>>>> For additional commands, e-mail: users- >>>>>>>>>>>>>>>>> help@... >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>>>>>>>> To unsubscribe, e-mail: >>>>>>>>>>>>>>>> users-unsubscribe@... >>>>>>>>>>>>>>>> For additional commands, e-mail: >>>>>>>>>>>>>>>> users-help@... >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> View this message in context: >>>>>>>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25750628.html >>>>>>>>>>>>>>> Sent from the Grizzly - Users mailing list archive at >>>>>>>>>>>>>>> Nabble.com. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>>>>>>> To unsubscribe, e-mail: users- >>>>>>>>>>>>>>> unsubscribe@... >>>>>>>>>>>>>>> For additional commands, e-mail: users- >>>>>>>>>>>>>>> help@... >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> View this message in context: >>>>>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25752899.html >>>>>>>>>>>>> Sent from the Grizzly - Users mailing list archive at >>>>>>>>>>>>> Nabble.com. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>>>>>>>>> For additional commands, e-mail: users- >>>>>>>>>>>>> help@... >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>>>> To unsubscribe, e-mail: users- >>>>>>>>>>>> unsubscribe@... >>>>>>>>>>>> For additional commands, e-mail: users-help@... >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> View this message in context: >>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25765021.html >>>>>>>>>> Sent from the Grizzly - Users mailing list archive at >>>>>>>>>> Nabble.com. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>> To unsubscribe, e-mail: users- >>>>>>>>>> unsubscribe@... >>>>>>>>>> For additional commands, e-mail: users- >>>>>>>>>> help@... >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> --------------------------------------------------------------------- >>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>>>>> For additional commands, e-mail: users-help@... >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> View this message in context: >>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25766557.html >>>>>>>> Sent from the Grizzly - Users mailing list archive at >>>>>>>> Nabble.com. >>>>>>>> >>>>>>>> >>>>>>>> --------------------------------------------------------------------- >>>>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>>>> For additional commands, e-mail: users- >>>>>>>> help@... >>>>>>>> >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>>> For additional commands, e-mail: users-help@... >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25767056.html >>>>>> Sent from the Grizzly - Users mailing list archive at Nabble.com. >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>>> For additional commands, e-mail: users-help@... >>>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>> For additional commands, e-mail: users-help@... >>>>> >>>>> >>>>> >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25802994.html >>> Sent from the Grizzly - Users mailing list archive at Nabble.com. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscribe@... >>> For additional commands, e-mail: users-help@... >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> >> > > -- > View this message in context: http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25817601.html > Sent from the Grizzly - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Grizzly configuration on Glassfish v3
by melshami
::
Rate this Message:
Hi Alexey,
I tried again on a fresh current build of glassfish and seems that the configuration works. But looks like I have to stik to glassfish v2.1 as for a stable release. As I was testing SOAP/TCP today following instructions on your blog, I am curious to know how the com.sun.xml.ws.transport.tcp.grizzly.WSTCPProtocolHandler is configured in glassfishv2.1. What I am trying to do is implement my own protocol handler in a way similar to WSIT SOAP TCP. What I understand is port unification was integrated since glassfishv2 but wasn't available through configuration as per current GFv3. Jean-Francois mention using jvm options as following: <jvm-options>-Dcom.sun.enterprise.web.connector.grizzly.protocolHandlers= com.sun.enterprise.web.portunif.protocols.http.HttpProtocolHandler</jvm-options> <jvm-options>-Dcom.sun.enterprise.web.connector.grizzly.protocolFinders= com.sun.enterprise.web.portunif.protocols.http.HttpsProtocolFinder, com.sun.enterprise.web.portunif.protocols.http.HttpProtocolFinder</jvm-options> Any pointers please? BR, Mohamed
|
| < Prev | 1 - 2 | Next > |
| Free embeddable forum powered by Nabble | Forum Help |
