The error you mentioned:
Approx. 5 minutes after, I get a server startup failure saying "Server JBoss 7.0 Alpha Server was unable to start within 450 seconds. If the server requires more time, try increasing the timeout in the server editor."
is an IDE message.
The logs that you posted don't contain any error messages and they show that the server has started successfully.
Are you talking about these few lines:
10:55:01,291 ERROR [stderr] (MSC service thread 1-1) ********************************************************************
10:55:01,291 ERROR [stderr] (MSC service thread 1-1) *** WARNING: Wicket is running in DEVELOPMENT mode. ***
10:55:01,291 ERROR [stderr] (MSC service thread 1-1) *** ^^^^^^^^^^^ ***
10:55:01,292 ERROR [stderr] (MSC service thread 1-1) *** Do NOT deploy to your live server(s) without changing this. ***
10:55:01,292 ERROR [stderr] (MSC service thread 1-1) *** See Application#getConfigurationType() for more information. ***
10:55:01,292 ERROR [stderr] (MSC service thread 1-1) ********************************************************************
If yes, then those really aren't ERRORs. The Wicket code seems to be using System.err to log those messages which is why it's being logged at ERROR level. That messages is asking you to set some configuration within your wicket application to disable the development mode, in production.