Salut,
doris chen wrote:
> Jeanfrancois,
> There is something wrong with GF v3 ea b39. I have updated 2 modules
> for kernal.jar and cometd.jar all with your most updated one. -However,
> now the problem is the chat application is not working properly between
> 2 clients. A lot of times, I don't see the message showed up properly
> on 2 clients.
>
> -Also, I noticed the channel topic (/chat/demo) is used instead of the
> contextpath (/cometd/cometd) to create CometContext.
Yes, this is something we have improved. Now you can notify per channel
instead of per application.
> I see the Cometd Servlet is mapped to /cometd/*
> <servlet-mapping>
> <servlet-name>Grizzly Cometd Servlet</servlet-name>
> <url-pattern>/cometd/*</url-pattern>
> </servlet-mapping>
>
> But the root context for the project is
> <context-root>/javaapicometd</context-root>
>
I've removed sun-web.xml as it was quite confusing...but for me doing:
> jfarcand_at_jfarcand-desktop:/appserv80/grizzly/trunk/samples/comet/cometd-javaapiupdate-chat$ java -jar /appserv80/grizzly/trunk/modules/bundles/comet
> d/target/grizzly-cometd-webserver-1.9.9-SNAPSHOT.jar -p 8080 -a target/grizzly-cometd-bayeux.war com.sun.grizzly.bayeux.BayeuxExternalServlet
> 6-Mar-2009 9:48:44 AM com.sun.grizzly.standalone.StandaloneMainUtil appendWarContentToClassPath
> INFO: Servicing resources from: /tmp/grizzly-cometd-bayeux
> INFO: ServletRequest will be serviced from http://host:port/BayeuxExternalServlet
> Launching Servlet: com.sun.grizzly.bayeux.BayeuxExternalServlet
> 6-Mar-2009 9:48:44 AM com.sun.grizzly.standalone.cometd.Cometd createSelectorThread
> INFO: Enabling Grizzly Bayeux support.
> 6-Mar-2009 9:48:44 AM com.sun.grizzly.http.SelectorThread displayConfiguration
> INFO:
> Grizzly configuration for port 8080
> Thread Pool: StatsThreadPool[name=http, priority=10, min-threads=5, max-threads=5, max-queue-size=4096, initial-byte-buffer-size=8192, byte-buffer-type=HEAP_VIEW, is-shutdown=false, port=8080]
> ByteBuffer size: 8192
> maxHttpHeaderSize: 8192
> maxKeepAliveRequests: 256
> keepAliveTimeoutInSeconds: 30
> Static File Cache enabled: false
> Static resources directory: /tmp/grizzly-cometd-bayeux
> Adapter : com.sun.grizzly.tcp.http11.GrizzlyAdapterChain
> Asynchronous Request Processing enabled: true
> 6-Mar-2009 9:48:44 AM com.sun.grizzly.standalone.StandaloneMainUtil$1 listen
> INFO: Server started in 387 milliseconds.
> Data is sent.
Issuing:
http://192.168.0.101:8080/BayeuxExternalServlet/?message=aaa
But in Grizzly it is deployed as "/". Now if I try with GlassFish v3, it
works when I do (after removing the sun-web.xml)
http://192.168.0.101:8080/grizzly-cometd-bayeux/
http://192.168.0.101:8080/grizzly-cometd-bayeux/BayeuxExternalServlet/?message=aaa,user=jf
> 6-Mar-2009 9:57:47 AM org.apache.catalina.loader.WebappLoader setClassPath
> INFO: Unknown loader org.glassfish.internal.api.DelegatingClassLoader_at_76438d class org.glassfish.internal.api.DelegatingClassLoader
> 6-Mar-2009 9:57:47 AM com.sun.enterprise.web.WebApplication start
> INFO: Loading application grizzly-cometd-bayeux at /grizzly-cometd-bayeux
> 6-Mar-2009 9:57:47 AM org.glassfish.deployment.admin.DeployCommand execute
> INFO: Deployment of grizzly-cometd-bayeux done is 232 ms
> 6-Mar-2009 9:57:47 AM org.glassfish.deployment.autodeploy.AutoOperation run
> INFO: [AutoDeploy] Successfully autodeployed : /home/jfarcand/workspace/v3/glassfish/domains/domain1/autodeploy/grizzly-cometd-bayeux.war.
> 6-Mar-2009 9:58:46 AM
> INFO: Data is sent.
> 6-Mar-2009 9:58:56 AM
> INFO: Data is sent.
If you keep sun-web.xml, it works with:
http://192.168.0.101:8080/javaapicometd/
http://192.168.0.101:8080/javaapicometd/BayeuxExternalServlet/?message=aaa,user=jf
> Will this be a problem?
>
> -Is the source code for BayeuxExternalServlet still the same as the
> following?
> https://grizzly.dev.java.net/nonav/xref/com/sun/grizzly/bayeux/BayeuxExternalServlet.html
>
>
> May be I should wait for a stable GF v3 to test this application again.
> I am getting a little frustrated ...
I understand. b39 is broken so you really need to patch. We may try to
fix it by integrating 1.9.9 next week, but I would prefer stabilizing v3
first before integrating a new Grizzly.
A+
-- Jeanfrancois
>
> Thanks,
>
> Doris
>
>
> Jeanfrancois Arcand wrote:
>> Salut,
>>
>> doris chen wrote:
>>> Jeanfrancois Arcand wrote:
>>>> Salut,
>>>>
>>>> doris chen wrote:
>>>>> Hi,
>>>>>
>>>>> Jeanfrancois Arcand wrote:
>>>>>> Salut,
>>>>>>
>>>>>> doris chen wrote:
>>>>>>> Hi,
>>>>>>> I am testing the BayeuxExternalServlet for new GF v3 b39 (built
>>>>>>> last night 3/4). However, I can not even make the chat
>>>>>>> application working (which is working on the previous builds).
>>>>>>> Here are the issues:
>>>>>>> 1. I see the user joined, but then no chat message will show up
>>>>>>> anymore.
>>>>>>
>>>>>> Is it the latest nightly? I've fixed b39 yesterday night. Is the
>>>>>> build from today?
>>>>> I did download the build b39 (dated 3/4). The message in Chat is
>>>>> fixed only after I apply *patch-kernal.jar* onto the module in *b39
>>>>> build. *Not sure if b39 has the latest kernal.jar.
>>>>>>
>>>>>>> 2. When I try to run BayeuxExternalServlet
>>>>>>> (http://host:port/BayeuxExternalServlet/?message=hello,user=moi),
>>>>>>> I get the response"no data is sent".
>>>>
>>>> Strange it works for me...are you using the latest version of that
>>>> sample?
>>> Any major change? I think just comment out setFinished() method,
>>> right?
>>
>> We added back setFinished support:
>>
>> https://grizzly.dev.java.net/issues/show_bug.cgi?id=473
>>
>>
>> Can you send me latest one?
>>
>> Right here (all sample are available)
>>
>> http://download.java.net/maven/2/com/sun/grizzly/samples/
>>
>> Thanks!
>>
>> -- Jeanfrancois
>>
>>
>>>
>>> Thanks,
>>>
>>> Doris
>>>
>>>>
>>>> Thanks
>>>>
>>>> -- jeanfrancois
>>>>
>>>>
>>>>
>>>>>>
>>>>>> Yes we fixed one issue yesterday night. So you need to download
>>>>>> the latest grizzly 1.9.9-SNAPSHOT from here:
>>>>>>
>>>>>> http://download.java.net/maven/2/com/sun/grizzly/grizzly-cometd/1.9.9-SNAPSHOT/grizzly-cometd-1.9.9-20090304.174759-33.jar
>>>>>>
>>>>>>
>>>>>> and replace the cometd.jar under ${glassfish.home}/modules/.
>>>>> Yes, I updated the cometd.jar with the above 1.9.9 cometd.jar.
>>>>> However I am still having the same probem "data is not sent".
>>>>>
>>>>> Did I miss anything else?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Doris
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> -- Jeanfrancois
>>>>>>
>>>>>>>
>>>>>>> I believe this build (b39) has the latest Grizzly bits. Any ideas?
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Doris
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> 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
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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
>