Hi,
Try to get thread dump of the Maven process. It may tell you what is
hanging.
In Unix like systems you can use:
kill -3 mavenProcessId
On any system you can use JDK's jps and jstack to get the dump as well.
On Fri, Oct 11, 2013 at 10:20 PM, Rob Alesi rob.al...@appdirect.com wrote:
Hey,
Am 12.10.2013 21:58, schrieb Martin Grigorov:
The problem is that most of us use Tomcat/Jetty and we don't test other web
containers.
Hi,
I always saw the decision between full Java EE and Spring Framework, and
Spring always made the impression to be a solution for all problems and
you have to
Hi,
On Mon, Oct 14, 2013 at 10:10 AM, Dieter Tremel
tre...@tremel-computer.dewrote:
Am 12.10.2013 21:58, schrieb Martin Grigorov:
The problem is that most of us use Tomcat/Jetty and we don't test other
web
containers.
Hi,
I always saw the decision between full Java EE and Spring
Hi,
I had a problem in Wicket6 with a datepicker that did not show
up in IE9 and saw that more had that issue but I could not find any
solution in the mail archives. Debugging the issue I saw that the
problem was that Yahoo.Dom.get() in IE grabbed the value from the
wicket:id attribute
Our current stack for big applications (10-20k concurrent users) is:
- wicket 6 (we upgrade with every release, across all projects almost
simultaneously, couple of million lines of code, about 3000 pages,
3000 panels, etc)
- spring for wiring hibernate, cxf and classpath scans, and some DI
-
Hi
we seem to face a little problem here with wicket 6.11:
Application.class:708
setPageManagerProvider(new DefaultPageManagerProvider(this));
sets the default provider here. Lateron [during init()] we replace this
one by using the snippet from HttpSessionDataStore's javadocs:
On 14.10.2013 21:10, uwe schaefer wrote:
Now for the question: what is the suggested way to register a
PageManagerProvider BEFORE anyone asks for it?
PS: rather than an initializer being the culprit, could it also be a
racecondition with clustering and
public void sessionUnbound(final
