Just to bring it to the list. Your fix is working fine and the Grails
app deploys fine using March 6th nightly and it takes around 9 secs.
thanks,
-vivek.
Jerome Dochez wrote:
> there is no workaround for now, we need to fix this properly in the
> web container, it will take a few days to hash it out.
>
> jerome
>
> On Feb 27, 2008, at 10:23 AM, Vivek Pandey wrote:
>
>> Cool! I am looking forward to the checkins to try it out. Is there
>> anyway user can get the nightly or is there any plan to make any
>> update release of v3 with these bits?
>>
>> thanks,
>>
>> -vivek.
>>
>> Jerome Dochez wrote:
>>> ok I have looked into this issue, this an issue with the Web
>>> application class loader and modularization... the entire webtier
>>> set of modules is currently visible to the web applications and I
>>> always knew we would have to fix it once the webtier stabilizes, it
>>> seems it will be sooner than expected... I will need to talk to the
>>> webtier team on how to solve this best but hacking around a solution
>>> in my workspace. I got :
>>>
>>> Feb 27, 2008 9:49:14 AM com.sun.enterprise.web.WebDeployer load
>>> INFO: Loading application myapp at /myapp
>>> Feb 27, 2008 9:49:14 AM
>>> com.sun.enterprise.v3.deployment.DeployCommand execute
>>> INFO: Deployment of myapp done is 9066 ms
>>>
>>> deployment took 9 seconds, of course I don't have such a nice
>>> machine as yours.
>>>
>>> browsing the localhost:8080/myapp, I got a Welcome To Grails page,
>>> so there seem to be progress...
>>>
>>> I will let you know once the webtier team and I have checked in a
>>> solution, there is no workaround today.
>>>
>>> Jerome
>>>
>>> On Feb 26, 2008, at 8:43 AM, Vivek Pandey wrote:
>>>
>>>> Jerome Dochez wrote:
>>>>> as a curiosity, how long does it take to deploy this in v2 ?
>>>>>
>>>> It is about 6 seconds. Please note that The numbers I mentioned for
>>>> v2 and v3 are from my machine, which is Intel Duo Quad Core 2.4
>>>> GHz/ 8GB RAM/Raptor Hard drives running Ubuntu 7.10.
>>>>
>>>> -vivek.
>>>>>
>>>>> On Feb 25, 2008, at 5:32 PM, Vivek Pandey wrote:
>>>>>
>>>>>> Jerome Dochez wrote:
>>>>>>> I have a theory, could you make your war file available
>>>>>>> somewhere so I can download and try...
>>>>>>>
>>>>>> Get it from here: http://javaweb.sfbay.sun.com/~vivekp/myapp.war
>>>>>>
>>>>>> I also reported a bug on this:
>>>>>>
>>>>>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=4255
>>>>>>
>>>>>> thanks,
>>>>>>
>>>>>> -vivek.
>>>>>>
>>>>>>> thx, jerome
>>>>>>>
>>>>>>> On Feb 25, 2008, at 4:34 PM, Vivek Pandey wrote:
>>>>>>>
>>>>>>>> [sending to users_at_glassfish as this is the right forum]
>>>>>>>> http://javaweb.sfbay.sun.com/~vivekp/myapp.war
>>>>>>>>
>>>>>>>> Well, it does not hang infinitely :-) I should have waited, it
>>>>>>>> takes around 9 mins for this to get deployed although
>>>>>>>> unsuccessfully:
>>>>>>>>
>>>>>>>> 'glassfish/bin/asadmin deploy myapp'
>>>>>>>>
>>>>>>>> SUCCESS : myapp deployed successfully
>>>>>>>> properties=(name=myapp)
>>>>>>>>
>>>>>>>>
>>>>>>>> the server.log displays this message:
>>>>>>>>
>>>>>>>>
>>>>>>>> [#|2008-02-26T00:21:34.646+0000|SEVERE|GlassFish10.0|org.apache.catalina.core.StandardContext|_ThreadID=11;_ThreadName=Thread-4;|PWC1306:
>>>>>>>> Startup of context /myapp failed due to previous errors|#]
>>>>>>>>
>>>>>>>> [#|2008-02-26T00:21:34.647+0000|INFO|GlassFish10.0|org.apache.catalina.core.StandardContext|_ThreadID=11;_ThreadName=Thread-4;|PWC1240:
>>>>>>>> Container WebModule[/myapp] has not been started|#]
>>>>>>>>
>>>>>>>> [#|2008-02-26T00:21:34.651+0000|SEVERE|GlassFish10.0|com.sun.org.apache.commons.modeler.Registry|_ThreadID=11;_ThreadName=Thread-4;|Null
>>>>>>>> component
>>>>>>>> com.sun.appserv:type=JspMonitor,name=jsp,WebModule=//server/myapp,J2EEApplication=null,J2EEServer=server|#]
>>>>>>>>
>>>>>>>>
>>>>>>>> [#|2008-02-26T00:21:34.653+0000|INFO|GlassFish10.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Thread-4;|Loading
>>>>>>>> application myapp at /myapp|#]
>>>>>>>>
>>>>>>>> [#|2008-02-26T00:21:34.655+0000|INFO|GlassFish10.0|javax.enterprise.system.tools.deployment|_ThreadID=11;_ThreadName=Thread-4;|Deployment
>>>>>>>> of myapp done is 526808 ms|#]
>>>>>>>>
>>>>>>>> when I try to access the application at: localhost:8080/myapp,
>>>>>>>> it gives 503, "The requested service () is not currently
>>>>>>>> available.".
>>>>>>>>
>>>>>>>> -vivek.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Vivek Pandey wrote:
>>>>>>>>> I have a simple grails application:
>>>>>>>>> http://javaweb.sfbay.sun.com/~vivekp/myapp.war
>>>>>>>>> - install grails [1]
>>>>>>>>> - grails create-app
>>>>>>>>> - grails war
>>>>>>>>>
>>>>>>>>> With the above 4 steps I have a grails application in war file
>>>>>>>>> ready, it is just a plain servlet. I try to copy the war to
>>>>>>>>> glassfish/domains/domain1/autodeploy, there are bunch of error
>>>>>>>>> messages, see the attachment and accessing the web page causes
>>>>>>>>> GF v3 to consume 100% CPU forever.
>>>>>>>>>
>>>>>>>>> I try directory based deployment and run 'asadmin deploy app1'
>>>>>>>>> where app1 is the exploded grails war directory, the
>>>>>>>>> deployment never finishes and again CPU utilization is 100%.
>>>>>>>>>
>>>>>>>>> This war deploys fine on GF v2 UR1.
>>>>>>>>>
>>>>>>>>> Anyone needs if there is any workaround or if not I should be
>>>>>>>>> report this as bug?
>>>>>>>>>
>>>>>>>>> thanks,
>>>>>>>>>
>>>>>>>>> -vivek.
>>>>>>>>>
>>>>>>>>> [1]http://grails.codehaus.org/Installation
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>
>>>>>>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>>>>>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>>>>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>>>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>