You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by roddo123 <rf...@rogers.com> on 2012/03/31 04:43:33 UTC
1.4.7 migration to 1.5.5 failing on AWS Elastic Beanstalk caused by
Form class
I have been running a wicket 1.4.7 application on the aws elastic beanstalk.
(It controls the server so the user only needs to deploy the war). I
migrated to 1.5.5 and was able to run the application without issue in my
local environment. However, when I deploy the 1.5.5 application to aws
after 2 minutes of running, the application is brought down with only the
following error in the logs.
Tomcat did not stop in time, killing process.
Killing Tomcat with the PID: 2514
Tomcat was killed but the PID file could not be removed.
This happens whether I am actively browsing the application or simply
opening up my main page and leaving it alone. What I found after many
iterations of deploying is that it only happens if I use the wicket Form
object. Its not an issue If I use WebMarkupContainer. I tested without
other components on the panel just to be sure.
Again, If I flip back to the 1.4.7 version there is no issue. I actually
tried a test commenting out much of the Form class, but the application
would still die after about 2 minutes.
Is there anything new running in the Form class immediately from
initialization that some external process may notice? There is likely some
aws process that is acting on the application, but it must be the result of
something that occurs by having a form on the panel.
It is very bizarre but very consistent. I tried running wicket 6.0 beta1
and found the same issue.
thanks for any direction
--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/1-4-7-migration-to-1-5-5-failing-on-AWS-Elastic-Beanstalk-caused-by-Form-class-tp4521002p4521002.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: 1.4.7 migration to 1.5.5 failing on AWS Elastic Beanstalk
caused by Form class
Posted by roddo123 <rf...@rogers.com>.
Just to be clear.
I agree that using AWS EC2 in itself is ok.
However, Elastic Beanstalk is a very specific AWS feature where AWS provides
a configured server.
Are you including Elastic Beanstalk, when you say that 1.5.5 Form
applications have been deployed to AWS?
--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/1-4-7-migration-to-1-5-5-failing-on-AWS-Elastic-Beanstalk-caused-by-Form-class-tp4521002p4524135.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: 1.4.7 migration to 1.5.5 failing on AWS Elastic Beanstalk caused
by Form class
Posted by Igor Vaynberg <ig...@gmail.com>.
we run a few 1.5.x apps in aws on tomcat and have not experienced a
problem like this. its probably something weird in your environment.
-igor
On Sat, Mar 31, 2012 at 10:58 AM, roddo123 <rf...@rogers.com> wrote:
> I haven't been able to have much success with visualvm in that environment.
> But a test I did do was create a wicket quickstart program, add appropriate
> jars, remove the wicket label and replace it with a wicket form.
>
> I then created a war, and deployed it to a new elastic beanstalk
> environment.
>
> I had the exact same environment failure within about 2 minutes. Just to
> note, a similar test with an unmodified quickstart program worked fine.
>
> I can't afford more time on this any further at this point, unless there is
> a simple change I am informed about. Instead I am simply upgrading to
> 1.4.9.
>
> Perhaps this is better taken as a heads up that there appears to be some
> incompatibility issue introduced in 1.5 Form class.
>
> thanks for your assistance.
>
> --
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/1-4-7-migration-to-1-5-5-failing-on-AWS-Elastic-Beanstalk-caused-by-Form-class-tp4521002p4522023.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: 1.4.7 migration to 1.5.5 failing on AWS Elastic Beanstalk
caused by Form class
Posted by roddo123 <rf...@rogers.com>.
I haven't been able to have much success with visualvm in that environment.
But a test I did do was create a wicket quickstart program, add appropriate
jars, remove the wicket label and replace it with a wicket form.
I then created a war, and deployed it to a new elastic beanstalk
environment.
I had the exact same environment failure within about 2 minutes. Just to
note, a similar test with an unmodified quickstart program worked fine.
I can't afford more time on this any further at this point, unless there is
a simple change I am informed about. Instead I am simply upgrading to
1.4.9.
Perhaps this is better taken as a heads up that there appears to be some
incompatibility issue introduced in 1.5 Form class.
thanks for your assistance.
--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/1-4-7-migration-to-1-5-5-failing-on-AWS-Elastic-Beanstalk-caused-by-Form-class-tp4521002p4522023.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: 1.4.7 migration to 1.5.5 failing on AWS Elastic Beanstalk caused
by Form class
Posted by Igor Vaynberg <ig...@gmail.com>.
attach visualvm to your aws instance and see whats hanging it up.
-igor
On Fri, Mar 30, 2012 at 7:43 PM, roddo123 <rf...@rogers.com> wrote:
> I have been running a wicket 1.4.7 application on the aws elastic beanstalk.
> (It controls the server so the user only needs to deploy the war). I
> migrated to 1.5.5 and was able to run the application without issue in my
> local environment. However, when I deploy the 1.5.5 application to aws
> after 2 minutes of running, the application is brought down with only the
> following error in the logs.
>
> Tomcat did not stop in time, killing process.
> Killing Tomcat with the PID: 2514
> Tomcat was killed but the PID file could not be removed.
>
> This happens whether I am actively browsing the application or simply
> opening up my main page and leaving it alone. What I found after many
> iterations of deploying is that it only happens if I use the wicket Form
> object. Its not an issue If I use WebMarkupContainer. I tested without
> other components on the panel just to be sure.
>
> Again, If I flip back to the 1.4.7 version there is no issue. I actually
> tried a test commenting out much of the Form class, but the application
> would still die after about 2 minutes.
>
> Is there anything new running in the Form class immediately from
> initialization that some external process may notice? There is likely some
> aws process that is acting on the application, but it must be the result of
> something that occurs by having a form on the panel.
>
> It is very bizarre but very consistent. I tried running wicket 6.0 beta1
> and found the same issue.
>
> thanks for any direction
>
>
> --
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/1-4-7-migration-to-1-5-5-failing-on-AWS-Elastic-Beanstalk-caused-by-Form-class-tp4521002p4521002.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org