Hi Jeanfrancois,
Thanks for replying. The protocol is my own custom protocal based on TCP. Do
you mean org.apache.coyote.Adapter? I tried to follow the actuall http
classes in grizzly-framework-http-1.0.30, and find how HttpServlets are
implementing the Adapter.
Looks like I have to configure my own shared context at runtime where it
will fire events to my business logic to process the request/response.
Any recommendation on this approach?
BR,
Mohamed
Jeanfrancois Arcand-2 wrote:
>
> Salut,
>
> melshami wrote:
>> Hi Alexey,
>>
>> Looks like things could have been a bit easier if I used glassfishv3 as I
>> may have been able to extend GrizzlyAdapter.
>
> You can also do that with v2 BTW using the Adapter interface. Is you
> protocol HTTP based?
>
> Anyway refrasing my question
>> how should the ProtocolHandler delivers a parsed request to to a servlet?
>
> You can't do that IMO (I might misunderstand this thread). Sorry for
> jumping so late in the thread, but since the target is a Servlet, the
> protocol needs to be http. Is it?
>
> A+
>
> -- Jeanfrancois
>
>
>>
>> BR,
>> Mohamed
>>
>>
>> melshami wrote:
>>> Hi Alexey,
>>>
>>> This is my researcg, but I would appreciate it if you have time to give
>>> me
>>> a hand on this. I went through the WSTCPProtocolHandler, following the
>>> request it's passed to IncomeMessageProcessor where it's by it's turn
>>> starts a ConnectionSession and TCPMessageListener, then it continue the
>>> journy perhaps until it finally reachs the TCP109Adapter, this seems to
>>> be
>>> bigger than what I need due to all SOAP WS stuff and abstaction stuff.
>>> As
>>> for my case I only need to implement simple TCP protocol, if you can
>>> point
>>> me to simpler example or just tell me what are the general interfaces to
>>> complete the request life-cycle to for instance XTCPServlet, O would be
>>> greatful.
>>>
>>> BR,
>>> Mohamed
>>>
>>>
>>> melshami wrote:
>>>> Wow:) I would have never imagined it could be that silly. I thought I
>>>> must be doing something terribly wrong.
>>>>
>>>> I will try now to do the actual TCP stuff.
>>>>
>>>> Thanks again.
>>>>
>>>>
>>>> Oleksiy Stashok wrote:
>>>>> Oh, it's Grizzly issue, please use only lowercase letters in protocol
>>>>> name both in finder and handler.
>>>>> This will be fixed in next Grizzly version.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> WBR,
>>>>> Alexey.
>>>>>
>>>>> On Oct 26, 2009, at 15:39 , melshami wrote:
>>>>>
>>>>>> Hi Alexey,
>>>>>>
>>>>>> Here is the project including the source for the handler and finder
>>>>>> and the
>>>>>> domain.xml. You will notice that I hardcoded the
>>>>>> requestInfo.protocol and
>>>>>> this is just for testing.
>>>>>>
>>>>>> BR,
>>>>>> Mohamed
>>>>>>
>>>>>> Oleksiy Stashok wrote:
>>>>>>> Hi Mohamed,
>>>>>>>
>>>>>>> can you pls. share your code (finder and handler) and domain.xml?
>>>>>>> I'll
>>>>>>> check it.
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> WBR,
>>>>>>> Alexey.
>>>>>>>
>>>>>>> On Oct 26, 2009, at 14:59 , melshami wrote:
>>>>>>>
>>>>>>>> Hi Alexey,
>>>>>>>>
>>>>>>>> Thanks for clarifying. I can see the
>>>>>>>> XProtocolHandler.getProtocols()
>>>>>>>> gets
>>>>>>>> called and returns the matching protocol Id. But the handle method
>>>>>>>> never
>>>>>>>> gets called. Do you think it's something I do wrong with the
>>>>>>>> client? Or is
>>>>>>>> there any other configuration I should do for the http listener
>>>>>>>> beside the
>>>>>>>> -D..XProtocolFinders, -DXProtocolHandlers system properties?
>>>>>>>>
>>>>>>>> BR,
>>>>>>>> Mohamed
>>>>>>>>
>>>>>>>>
>>>>>>>> Oleksiy Stashok wrote:
>>>>>>>>> Hi Mohamed,
>>>>>>>>>
>>>>>>>>>> Thanks very much for your help again. I spent fair amount of time
>>>>>>>>>> until I
>>>>>>>>>> got myself familiar with how this works. I was able to get a
>>>>>>>>>> custom
>>>>>>>>>> protocol
>>>>>>>>>> finder to work. But I couldn't got the custom handler to work. I
>>>>>>>>>> understand
>>>>>>>>>> that the handler is mapped to the protocol once the
>>>>>>>>>> protocolInfo.protocol is
>>>>>>>>>> set by the finder. Which is what I did. My feeling is that this
>>>>>>>>>> has
>>>>>>>>>> to do
>>>>>>>>>> with the proxiedProtocols which is how the TCP/SOAP is
>>>>>>>>>> registered:
>>>>>>>>>>
>>>>>>>>>> supportedProtocols.put(
>>>>>>>>>>
>>>>>>>>>> "ws/
>>>>>>>>>> tcp","com.sun.xml.ws.transport.tcp.grizzly.WSTCPProtocolFinder");
>>>>>>>>>>
>>>>>>>>>> But I am also confused because it looks like the
>>>>>>>>>> PortUnificationPipeline.PUTask iterates over each finder and
>>>>>>>>>> finds
>>>>>>>>>> the
>>>>>>>>>> matching handler then invokes it's handle callback.
>>>>>>>>> right. Finder is responsible for parsing the header and find out
>>>>>>>>> if
>>>>>>>>> it's known protocol. If yes - set protocolInfo.protocol some
>>>>>>>>> unique
>>>>>>>>> protocol name.
>>>>>>>>> Handler in its turn has method String[] getProtocols(), which
>>>>>>>>> should
>>>>>>>>> return names of all protocols it supports.
>>>>>>>>>
>>>>>>>>> So binding should work, if finder will set protocolInfo.protocol
>>>>>>>>> to
>>>>>>>>> let's say "customProtocol" and some Handler will have String[]
>>>>>>>>> getProtocols() implemented to return {"customProtocol", ...}. In
>>>>>>>>> this
>>>>>>>>> case PortUnficiationPipeline will call handler's handle() method.
>>>>>>>>>
>>>>>>>>>>> In GF v2.1, SOAP/TCP is configured internally via
>>>>>>>>>>> proxiedProtocols
>>>>>>>>>>> element, but it works only for known protocols, so is not
>>>>>>>>>>> acceptable
>>>>>>>>>>> for custom ones.
>>>>>>>>>> Is this the reason? does this mean proxiedProtocols are only
>>>>>>>>>> hardcoded? I
>>>>>>>>>> hope there is a safe way to provide custom handler withouth the
>>>>>>>>>> need
>>>>>>>>>> to
>>>>>>>>>> recompile or batch glassfish v2.1.
>>>>>>>>> proxiedProtocols was used just to simplify configuration file for
>>>>>>>>> known protocols.
>>>>>>>>>
>>>>>>>>> Hope this will help.
>>>>>>>>>
>>>>>>>>> WBR,
>>>>>>>>> Alexey.
>>>>>>>>>
>>>>>>>>>> I will keep looking, but your replies are always big life saver:)
>>>>>>>>>>
>>>>>>>>>> BR,
>>>>>>>>>> Mohamed
>>>>>>>>>>
>>>>>>>>>> Oleksiy Stashok wrote:
>>>>>>>>>>> Hi Mohamed,
>>>>>>>>>>>
>>>>>>>>>>>> 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.
>>>>>>>>>>> In GF v2.1, SOAP/TCP is configured internally via
>>>>>>>>>>> proxiedProtocols
>>>>>>>>>>> element, but it works only for known protocols, so is not
>>>>>>>>>>> acceptable
>>>>>>>>>>> for custom ones.
>>>>>>>>>>>
>>>>>>>>>>>> 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>
>>>>>>>>>>> Absolutely. That's what you'll need.
>>>>>>>>>>> To provide custom Finder - just include it to System property
>>>>>>>>>>> (jvm-
>>>>>>>>>>> option) like:
>>>>>>>>>>> <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
>>>>>>>>>>> ,
>>>>>>>>>>> my.custom.ProtocolFinder</jvm-options>
>>>>>>>>>>> the same with the handler.
>>>>>>>>>>>
>>>>>>>>>>> Here are interfaces for GFv2.1 [1], [2].
>>>>>>>>>>> Here are SOAP/TCP implementations [3], [4]. Though in your
>>>>>>>>>>> finder
>>>>>>>>>>> try
>>>>>>>>>>> to avoid the additional reading from channel, which you see in
>>>>>>>>>>> sample.
>>>>>>>>>>>
>>>>>>>>>>> WBR,
>>>>>>>>>>> Alexey.
>>>>>>>>>>>
>>>>>>>>>>> [1]
>>>>>>>>>>> https://grizzly.dev.java.net/source/browse/grizzly/trunk/code/extras/grizzly1.0/src/main/java/com/sun/enterprise/web/portunif/ProtocolFinder.java?rev=3149&view=markup
>>>>>>>>>>> [2]
>>>>>>>>>>> https://grizzly.dev.java.net/source/browse/grizzly/trunk/code/extras/grizzly1.0/src/main/java/com/sun/enterprise/web/portunif/ProtocolHandler.java?rev=3149&view=markup
>>>>>>>>>>> [3]
>>>>>>>>>>> http://fisheye5.cenqua.com/browse/wsit/wsit/rt/src/com/sun/xml/ws/transport/tcp/grizzly/WSTCPProtocolFinder.java?r=1.5
>>>>>>>>>>> [4]
>>>>>>>>>>> http://fisheye5.cenqua.com/browse/wsit/wsit/rt/src/com/sun/xml/ws/transport/tcp/grizzly/WSTCPProtocolHandler.java?r=1.9
>>>>>>>>>>>
>>>>>>>>>>>> Any pointers please?
>>>>>>>>>>>>
>>>>>>>>>>>> BR,
>>>>>>>>>>>> Mohamed
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Oleksiy Stashok wrote:
>>>>>>>>>>>>> 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_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> For additional commands, e-mail: users-
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> help_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> users-unsubscribe_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> users-help_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>>>>>> View this message in context:
>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25750628.html
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Sent from the Grizzly - Users mailing list
>>>>>>>>>>>>>>>>>>>>>>>>>>>> archive
>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Nabble.com.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>>>>>>>>> To unsubscribe, e-mail: users-
>>>>>>>>>>>>>>>>>>>>>>>>>>>> unsubscribe_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>>>>>>>>>> For additional commands, e-mail: users-
>>>>>>>>>>>>>>>>>>>>>>>>>>>> help_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>>>> 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_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>>>>>>>> For additional commands, e-mail: users-
>>>>>>>>>>>>>>>>>>>>>>>>>> help_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>>>>>> To unsubscribe, e-mail: users-
>>>>>>>>>>>>>>>>>>>>>>>>> unsubscribe_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>>>>>>>>>>>>>> users-help_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>> View this message in context:
>>>>>>>>>>>>>>>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25765021.html
>>>>>>>>>>>>>>>>>>>>>>> Sent from the Grizzly - Users mailing list archive
>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>> Nabble.com.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>>>> To unsubscribe, e-mail: users-
>>>>>>>>>>>>>>>>>>>>>>> unsubscribe_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>>>>> For additional commands, e-mail: users-
>>>>>>>>>>>>>>>>>>>>>>> help_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>>>>>>>>>>> users-unsubscribe_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>>>>>>>>>>> users-help_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> View this message in context:
>>>>>>>>>>>>>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25766557.html
>>>>>>>>>>>>>>>>>>>>> Sent from the Grizzly - Users mailing list archive at
>>>>>>>>>>>>>>>>>>>>> Nabble.com.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>> To unsubscribe, e-mail: users-
>>>>>>>>>>>>>>>>>>>>> unsubscribe_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>>> For additional commands, e-mail: users-
>>>>>>>>>>>>>>>>>>>>> help_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>>>>>>>>> users-unsubscribe_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>>>>>>>>> users-help_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> View this message in context:
>>>>>>>>>>>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25767056.html
>>>>>>>>>>>>>>>>>>> Sent from the Grizzly - Users mailing list archive at
>>>>>>>>>>>>>>>>>>> Nabble.com.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>> To unsubscribe, e-mail: users-
>>>>>>>>>>>>>>>>>>> unsubscribe_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>> For additional commands, e-mail: users-
>>>>>>>>>>>>>>>>>>> help_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>>>>>>> users-unsubscribe_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>>>>>>> users-help_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> View this message in context:
>>>>>>>>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25802994.html
>>>>>>>>>>>>>>>> Sent from the Grizzly - Users mailing list archive at
>>>>>>>>>>>>>>>> Nabble.com.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>>>>> users-unsubscribe_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>>>>> users-help_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>>>> To unsubscribe, e-mail: users-
>>>>>>>>>>>>>>> unsubscribe_at_grizzly.dev.java.net
>>>>>>>>>>>>>>> For additional commands, e-mail: users-
>>>>>>>>>>>>>>> help_at_grizzly.dev.java.net
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> View this message in context:
>>>>>>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p25817601.html
>>>>>>>>>>>>>> Sent from the Grizzly - Users mailing list archive at
>>>>>>>>>>>>>> Nabble.com.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>>> users-unsubscribe_at_grizzly.dev.java.net
>>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>>> users-help_at_grizzly.dev.java.net
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>>>>>>>>>>>> For additional commands, e-mail: users-
>>>>>>>>>>>>> help_at_grizzly.dev.java.net
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> View this message in context:
>>>>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p26013307.html
>>>>>>>>>>>> Sent from the Grizzly - Users mailing list archive at
>>>>>>>>>>>> Nabble.com.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>> users-help_at_grizzly.dev.java.net
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>>>>>>>>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> View this message in context:
>>>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p26034151.html
>>>>>>>>>> Sent from the Grizzly - Users mailing list archive at Nabble.com.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>>>>>>>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> --
>>>>>>>> View this message in context:
>>>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p26060328.html
>>>>>>>> Sent from the Grizzly - Users mailing list archive at Nabble.com.
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>>>>>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>>>>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> http://www.nabble.com/file/p26061009/xpro.zip xpro.zip
>>>>>> --
>>>>>> View this message in context:
>>>>>> http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p26061009.html
>>>>>> Sent from the Grizzly - Users mailing list archive at Nabble.com.
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>>>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
>
>
--
View this message in context: http://www.nabble.com/Grizzly-configuration-on-Glassfish-v3-tp25750048p26097874.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.