org.springframework.scheduling.quartz.JobMethodInvocationFailedException

>> >> Invocation of method 'doIt' on target class [class >> >> org.openmeetings.app.quartz.scheduler.MeetingReminderJob] failed; >> >> nested exception is java.lang.VerifyError: Expecting a stackmap >> >> frame >> >> at branch target 70 in method >> >> org.openmeetings.app.persistence.beans.user.UserContacts.<clinit>()V >> >> at offset 61 >> >> at >> >> >> org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean$MethodInvokingJob.executeInternal(MethodInvokingJobDetailFactoryBean.java:273) >> >> ~[org.springframework.context.support-3.0.6.RELEASE.jar:3.0.6.RELEASE] >> >> at >> >> >> org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86) >> >> ~[org.springframework.context.support-3.0.6.RELEASE.jar:3.0.6.RELEASE]

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 web3

Stack trace

  • org.springframework.scheduling.quartz.JobMethodInvocationFailedException: >> >> Invocation of method 'doIt' on target class [class >> >> org.openmeetings.app.quartz.scheduler.MeetingReminderJob] failed; >> >> nested exception is java.lang.VerifyError: Expecting a stackmap >> >> frame >> >> at branch target 70 in method >> >> org.openmeetings.app.persistence.beans.user.UserContacts.<clinit>()V >> >> at offset 61 >> >> at >> >> >> org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean$MethodInvokingJob.executeInternal(MethodInvokingJobDetailFactoryBean.java:273) >> >> ~[org.springframework.context.support-3.0.6.RELEASE.jar:3.0.6.RELEASE] >> >> at >> >> >> org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86) >> >> ~[org.springframework.context.support-3.0.6.RELEASE.jar:3.0.6.RELEASE] at org.quartz.core.JobRunShell.run(JobRunShell.java:216)

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.