java.lang.IllegalStateException

this method can only be called from the AWT event dispatch thread, and not from "Timer-2"

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web8

  • via Unknown by Roger L. Whitcomb,
  • via Unknown by Roger L. Whitcomb,
  • via Unknown by Roger L. Whitcomb,
  • Stack trace

    • java.lang.IllegalStateException: this method can only be called from the AWT event dispatch thread, and not from "Timer-2" at org.apache.pivot.wtk.Container$1.check(Container.java:872) at org.apache.pivot.wtk.Container.assertEventDispatchThread(Container.java:880) at org.apache.pivot.wtk.Component.invalidate(Component.java:1955) at org.apache.pivot.wtk.skin.ComponentSkin.invalidateComponent(ComponentSkin.java:340) at org.apache.pivot.wtk.skin.TextAreaSkinParagraphView.textRemoved(TextAreaSkinParagraphView.java:419) at org.apache.pivot.wtk.TextArea$Paragraph$ParagraphListenerList.textRemoved(TextArea.java:55) at org.apache.pivot.wtk.TextArea$Paragraph.removeText(TextArea.java:153) at org.apache.pivot.wtk.TextArea.insertText(TextArea.java:757) at org.apache.pivot.wtk.TextArea.insertText(TextArea.java:730) at cz.cgrim.alchemist.logger.TextAreaAppender.append(TextAreaAppender.java:41) at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251) at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66) at org.apache.log4j.Category.callAppenders(Category.java:206) at org.apache.log4j.Category.forcedLog(Category.java:391) at org.apache.log4j.Category.log(Category.java:856) at com.documentum.fc.common.DfLogger.warn(DfLogger.java:151) at com.documentum.fc.client.impl.bof.cache.ClassCacheManager$CacheCleanupTask.run(ClassCacheManager.java:602) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.