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

Solutions on the web

via vineetmanohar.com by Unknown author, 2 years ago
Could not create Component: org.jboss.seam.async.dispatcher
via JBoss Issue Tracker by Anton Klimkovich, 2 years ago
Could not create Component: accept
via blogspot.com by Unknown author, 2 years ago
java.lang.RuntimeException: Could not create Component: renderManager at org.jboss.seam.init.Initialization.addComponent(Initialization.java:989) at org.jboss.seam.init.Initialization.installComponents(Initialization.java:911) at org.jboss.seam.init.Initialization.init(Initialization.java:589) at org.jboss.seam.mock.BaseSeamTest.startSeam(BaseSeamTest.java:939) at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:923) at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42)Caused by: java.lang.NoClassDefFoundError: edu/emory/mathcs/backport/java/util/concurrent/ScheduledThreadPoolExecutor at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2395) at java.lang.Class.getDeclaredMethods(Class.java:1763) at org.jboss.seam.Component.initMembers(Component.java:530) at org.jboss.seam.Component.<init>(Component.java:254) at org.jboss.seam.Component.<init>(Component.java:217) at org.jboss.seam.init.Initialization.addComponent(Initialization.java:974) ... 6 more