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 JBoss Issue Tracker by Ron Šmeral, 1 year ago
via JBoss Issue Tracker by Ron Šmeral, 2 years ago
via Stack Overflow by Ikthiander
, 2 years ago
via jboss.org by Unknown author, 2 years ago
via jboss.org by Unknown author, 1 year ago
java.lang.UnsupportedOperationException: no transaction	at org.jboss.seam.transaction.NoTransaction.begin(NoTransaction.java:36)	at org.jboss.seam.util.Work.workInTransaction(Work.java:58)	at org.jboss.seam.contexts.Contexts.flushAndDestroyContexts(Contexts.java:352)	at org.jboss.seam.contexts.Lifecycle.endCall(Lifecycle.java:101)	at org.jboss.seam.async.Asynchronous$ContextualAsynchronousRequest.cleanup(Asynchronous.java:106)	at org.jboss.seam.async.Asynchronous$ContextualAsynchronousRequest.run(Asynchronous.java:99)	at org.jboss.seam.async.AsynchronousInvocation.execute(AsynchronousInvocation.java:45)	at org.jboss.seam.async.ThreadPoolDispatcher$RunnableAsynchronous.run(ThreadPoolDispatcher.java:142)	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)	at java.lang.Thread.run(Thread.java:662)