Grails Performance and Reliability

23 views
Skip to first unread message

karthi

unread,
Jan 20, 2011, 11:29:02 AM1/20/11
to ig...@googlegroups.com
Dear friends,

I have used grails 1.3.1 for about 6 months.

I have successfully deployed CRM, ERP based on grails and zk plugin.

But every time I deployed in the beginning, deployment was a difficulty, stack overflow problems mostly...

Now again I am looking forward to develop in grails(1.3.6).

I need your feedback on your deployments, it will be a huge help for me.

Thank you.

Karthi.m
Vmak Solutions


Venkatesh S

unread,
Jan 20, 2011, 12:00:46 PM1/20/11
to ig...@googlegroups.com
Hi Karthi,

I have done a deployment very recently. I have used grails 1.3.6. I did not have any problems. If you are having issues using grails zk plugin, then i would recommend you to have a look at their commercial support.

Regarding your stackoverflow exceptions, I have seen people complain about it in Grails version 1.1. I have not come across the problem recently.

Thanks
Venki

Yagnesh Chawda

unread,
Jan 20, 2011, 12:12:21 PM1/20/11
to Indian Groovy & Grails User Group
Agreed with Venki,
Karthi, best thing would be you put exception log in this thread if
you face any issue. Along with that you can specify heap, permgen etc.
if you have specified it explicitly.

Thanks And Regards,
Yagnesh Chawda.
: http://yagneshchawda.blogspot.com/
: http://twitter.com/yagneshchawda

On Jan 20, 10:00 pm, Venkatesh S <mailvenkate...@gmail.com> wrote:
> Hi Karthi,
>
> I have done a deployment very recently. I have used grails 1.3.6. I did not
> have any problems. If you are having issues using grails zk plugin, then i
> would recommend you to have a look at their commercial support.
>
> Regarding your stackoverflow exceptions, I have seen people complain about
> it in Grails version 1.1. I have not come across the problem recently.
>
> Thanks
> Venki
>

karthi

unread,
Jan 21, 2011, 7:11:17 AM1/21/11
to ig...@googlegroups.com
Thank you venkatesh and yagnesh

I have checked, the version i used was 1.1.x only...

I assume the problem is fixed now..

I will upgrade my app and check it out with normal heap memory.

Thanks for your reply

regards
karthi.m


I
Reply all
Reply to author
Forward
0 new messages