Salut,
doris chen wrote:
> Jeanfrancois,
>
> See my questions below:
>>> 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
>>
> Do you see user name jf and message aaa showed up in the chat browser?
Yes
> I also see the message "Data is sent" in my test but I don't see
> anything like "jf:aaa" showed up in the chat browser and I do see it
> with the prelude GF v3 testing. Also the chatpinger message "wake up"
> never shows up in the chat browser and it is supposed to show every 10
> seconds. This seems to me the data is either not pushed back to the
> right context or the right channel.
Are you 100% sure you are using the latest .war file? It works for me
using b39 + cometd-1.9.9-SNAPSHOT.jar
> One question I am having is in web.xml, the cometd servlet is mapped to
> /comet/*, but now the above url is invoking using "javaapicometd".
yes that's because of sun-web.xml. So all path must start with
/javaapicometd/cometd/
My
> question is when the cometd servlet is called as it seems to me the url
> is not calling it.
>
> Can you let me know when will be a good time to retest my application as
> it seems I have a lot of problem with GF v3? The lab material is due
> in about 2 weeks so I am a little concerned.
Next GF promoted build will still use Grizzly 1.9.8, and we don't know
yet when we will integrate. So for awhile you will have to:
+ use a GF nightly
+ replace cometd.jar with cometd-1.9.9-SNAPSHOT.jar
This is painful I agree.
A+
- jeanfrancois
>
> Thanks,
>
> Doris
>
>>
>>
>>> 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
>>>
>>
>> ---------------------------------------------------------------------
>> 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
>