org.apache.wicket.WicketRuntimeException: After 1 minute the Pagemap null is still locked by: Thread[TP-Processor2,5,main], giving up trying to get the page for path: 2:tabbedPanel:panel:tabs- container:tabs:0:link

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

Do you know how to solve this issue? Write a tip to help other users and build your expert profile.

Solutions on the web

via Google Groups by Kaizen, 5 months ago
After 1 minute the Pagemap null is still locked by: Thread[TP-Processor2,5,main], giving up trying to get the page for path: 2:tabbedPanel:panel:tabs- container:tabs:0:link
via JIRA by Robert David, 1 year ago
After 1 minute the Pagemap null is still locked by: Thread[http-0.0.0.0-8080-11,5,jboss], giving up trying to get the page for path: 3 Begin of stack trace of Thread[http-0.0.0.0-8080-11,5,jboss] java.lang.Class.getInterfaces(Native Method
org.apache.wicket.WicketRuntimeException: After 1 minute the Pagemap null is still locked by: Thread[TP-Processor2,5,main], giving up trying to get the page for path: 2:tabbedPanel:panel:tabs- container:tabs:0:link
at org.apache.wicket.Session.getPage(Session.java:739)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.