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
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.
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 rfr...@rogers.com wrote:
I haven't been able to have much success with visualvm in that environment.
But a
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
attach visualvm to your aws instance and see whats hanging it up.
-igor
On Fri, Mar 30, 2012 at 7:43 PM, roddo123 rfr...@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
