Re: not able to run jmaki-comet demo today.. I'm the only one ?
Salut,
using trunk:
> jfarcand_at_jfarcand-desktop:/appserv80/grizzly/trunk/samples/comet/twitter$ java -jar /appserv80/grizzly/trunk/modules/bundles/comet/target/grizzly-c
> omet-webserver-1.9.17-SNAPSHOT.jar -p 8080 -a target/grizzly-twitter.war com.sun.grizzly.samples.comet.TwitterServlet
> 15-Jun-2009 12:45:08 PM com.sun.grizzly.standalone.StandaloneMainUtil appendWarContentToClassPath
> INFO: Servicing resources from: /tmp/grizzly-twitter
> Launching Servlet: com.sun.grizzly.samples.comet.TwitterServlet
> 15-Jun-2009 12:45:09 PM com.sun.grizzly.http.SelectorThread displayConfiguration
> INFO:
> Grizzly configuration for port 8080
> Thread Pool: StatsThreadPool[name=http, min-threads=10, max-threads=10, max-queue-size=2147483647, is-shutdown=false, port=8080]
> Read Selector: 2
> ByteBuffer size: 8192
> maxHttpHeaderSize: 8192
> maxKeepAliveRequests: 256
> keepAliveTimeoutInSeconds: 30
> Static File Cache enabled: true
> Static resources directory: /tmp/grizzly-twitter
> Adapter : com.sun.grizzly.http.servlet.ServletAdapter
> Asynchronous Request Processing enabled: true
> 15-Jun-2009 12:45:09 PM com.sun.grizzly.standalone.StandaloneMainUtil$1 listen
> INFO: Server started in 429 milliseconds.
A+
-- jeanfrancois
Survivant 00 wrote:
> thanks.. with that I'll be ok.
>
> no I don't remember. I try with deployer 1.9.11 and up and jmaki didn't
> work.. the only reason should be that I didn't commit the update..
>
> should be too hard to fix it since you gave me a working demo :)
>
>
> if I'm able to run it...
>
> C:\Source\grizzly\modules\comet\target>java -jar
> grizzly-comet-1.9.17-SNAPSHOT.jar -a grizzly-twitter.war
> com.sun.grizzly.samples.comet.TwitterServlet
> Failed to load Main-Class manifest attribute from
> grizzly-comet-1.9.17-SNAPSHOT.jar
>
>
>
> 2009/6/15 Jeanfrancois Arcand <Jeanfrancois.Arcand_at_sun.com
> <mailto:Jeanfrancois.Arcand_at_sun.com>>
>
> Salut,
>
>
> Survivant 00 wrote:
>
> tu aurais du me le dire avant :)
>
>
> I think I've filled an issue:
>
> https://grizzly.dev.java.net/issues/show_bug.cgi?id=560
>
>
> do you have a standalone main that work's with your demo ?
>
>
> I use the bundle module:
>
> java -jar grizzly-comet.jar -p 8080 -a grizzly-twitter.war
> com.sun.grizzly.samples.comet.TwitterServlet
>
>
> Will be
>
> easier to trace. Now I have to look into my history.. it was
> working before :(
>
>
> Do you recall when?
>
>
> A+
>
> -- Jeanfrancois
>
>
>
>
> 2009/6/15 Jeanfrancois Arcand <Jeanfrancois.Arcand_at_sun.com
> <mailto:Jeanfrancois.Arcand_at_sun.com>
> <mailto:Jeanfrancois.Arcand_at_sun.com
> <mailto:Jeanfrancois.Arcand_at_sun.com>>>
>
> Salut,
>
>
> Survivant 00 wrote:
>
> just trying to run the demo on GWS. (try with deployer.. but
> didn't work.. )
>
>
> obtain a Resource Not Found or a blank page.
>
>
> Yes that's something I wanted to talk with you. The Twitter
> demo is
> also giving the same error for awhile. I think the way the
> deployer
> set the context/servlet path might be problematic. Are you
> seeing to
> /? I don't think this is a regression as it never worked (at
> least
> for the Twitter case).
>
> A+
>
> -- Jeanfrancois
>
>
>
>
>
>
> 2009/6/15 Jeanfrancois Arcand
> <Jeanfrancois.Arcand_at_sun.com <mailto:Jeanfrancois.Arcand_at_sun.com>
> <mailto:Jeanfrancois.Arcand_at_sun.com
> <mailto:Jeanfrancois.Arcand_at_sun.com>>
> <mailto:Jeanfrancois.Arcand_at_sun.com
> <mailto:Jeanfrancois.Arcand_at_sun.com>
> <mailto:Jeanfrancois.Arcand_at_sun.com
> <mailto:Jeanfrancois.Arcand_at_sun.com>>>>
>
>
> Salut
>
>
> Survivant 00 wrote:
>
> I'm doing regression test for deployer, and I'm
> not able
> to run
> jmaki-demo on Deployer on both my computers.
>
> I try with 1.9.11 to 1.9.17 and it doesn't start. Was
> working
> perfectly before, that's why I want to know if someone
> else is
> able to get it to run.
> If you are able.. can you send me a test that will
> run.. will
> try on my side.
>
>
> can you explain what you are doing exactly? I will
> gives it a
> try.
>
> Thanks!
>
> --Jeanfrancois
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe_at_grizzly.dev.java.net
> <mailto:dev-unsubscribe_at_grizzly.dev.java.net>
> <mailto:dev-unsubscribe_at_grizzly.dev.java.net
> <mailto:dev-unsubscribe_at_grizzly.dev.java.net>>
> <mailto:dev-unsubscribe_at_grizzly.dev.java.net
> <mailto:dev-unsubscribe_at_grizzly.dev.java.net>
> <mailto:dev-unsubscribe_at_grizzly.dev.java.net
> <mailto:dev-unsubscribe_at_grizzly.dev.java.net>>>
>
> For additional commands, e-mail:
> dev-help_at_grizzly.dev.java.net
> <mailto:dev-help_at_grizzly.dev.java.net>
> <mailto:dev-help_at_grizzly.dev.java.net
> <mailto:dev-help_at_grizzly.dev.java.net>>
> <mailto:dev-help_at_grizzly.dev.java.net
> <mailto:dev-help_at_grizzly.dev.java.net>
> <mailto:dev-help_at_grizzly.dev.java.net
> <mailto:dev-help_at_grizzly.dev.java.net>>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> <mailto:dev-unsubscribe_at_grizzly.dev.java.net>
> <mailto:dev-unsubscribe_at_grizzly.dev.java.net
> <mailto:dev-unsubscribe_at_grizzly.dev.java.net>>
> For additional commands, e-mail:
> dev-help_at_grizzly.dev.java.net <mailto:dev-help_at_grizzly.dev.java.net>
> <mailto:dev-help_at_grizzly.dev.java.net
> <mailto:dev-help_at_grizzly.dev.java.net>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> <mailto:dev-unsubscribe_at_grizzly.dev.java.net>
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
> <mailto:dev-help_at_grizzly.dev.java.net>
>
>