Is JVM slowing down for Groovy/Grails app when scan is initiated

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Is JVM slowing down for Groovy/Grails app when scan is initiated

Reshma Raghu
Groovy/Grails application is not working on specific time frame,on a daily basis.
It works after multiple refreshing of the page.Also in between each new request ,there is a time gap.Since it is single threaded a new request couldn't start until the one currently used gets complete.

Want to know like,if any scan is initiated will the JVM slows down the Groovy/grails app

Versions used are :

Grails Version = 2.3.11
Groovy Version = 2.1.9
SpringLoaded Version =1.1.3

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/748b4949-2061-4784-8d9b-e4d249b238ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Is JVM slowing down for Groovy/Grails app when scan is initiated

Jeff Scott Brown-4
On 16 Jul 2018, at 5:10, Reshma Raghu wrote:

> Groovy/Grails application is not working on specific time frame,on a
> daily
> basis.
> It works after multiple refreshing of the page.Also in between each
> new
> request ,there is a time gap.Since it is single threaded a new request
> couldn't start until the one currently used gets complete.
>
> Want to know like,if any scan is initiated will the JVM slows down the
> Groovy/grails app
>
> Versions used are :
>
> Grails Version = 2.3.11
> Groovy Version = 2.1.9
> SpringLoaded Version =1.1.3
>

If you have a single threaded situation such that the app can only deal
with 1 concurrent request then either you have something misconfigured
in your container or your app is doing something that bottlnecks
multiple concurrent requests into a single blocking point (like calling
some synchronized method/block or something along those lines).  A
single concurrent request model is of course not the default behavior of
the framework.



JSB

--
Jeff Scott Brown
OCI Partner and Principal Software Engineer
OCI Grails Practice Lead

Autism Strikes 1 in 166
Find The Cause ~ Find The Cure
http://www.autismspeaks.org/

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/BA5AD677-2C52-43ED-880A-3788A94C2A23%40objectcomputing.com.
For more options, visit https://groups.google.com/d/optout.