Bug #1054 (closed)
Opened 16 years ago
Closed 15 years ago
Quartz may still be running before server is ready
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | major | Cc: | cxallan |
Sprint: | n.a. | ||
Total Remaining Time: | n.a. |
Description
09:13:00,061 INFO [DBPatchCheck] Verified database patch: OMERO3A__9 09:13:00,065 INFO [ServerVersionCheck] ------------------------------------------------- 09:13:00,065 INFO [ServerVersionCheck] OMERO Version: 3.0-Beta3 (Rev: 2461) Ready. 09:13:00,065 INFO [ServerVersionCheck] ------------------------------------------------- 09:13:00,099 INFO [UpgradeCheck] no update needed 09:13:00,225 INFO [FullTextThread] Initializing Full-Text Indexer 09:13:00,312 INFO [SchedulerFactoryBean] Starting Quartz Scheduler now
...
09:13:00,369 WARN [ServiceHandler] Unknown exception thrown. java.lang.NullPointerException at ome.logic.AdminImpl.userProxy(AdminImpl.java:218) at ome.security.basic.BasicSecuritySystem.loadEventContext(BasicSecuritySystem.java:281) at ome.security.basic.EventHandler.invoke(EventHandler.java:90) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.orm.hibernate3.HibernateInterceptor.invoke(HibernateInterceptor.java:111) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at ome.tools.hibernate.ProxyCleanupFilter$Interceptor.invoke(ProxyCleanupFilter.java:169) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at ome.services.util.ServiceHandler.invoke(ServiceHandler.java:86) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at ome.services.util.Executor$Impl$Interceptor.invoke(Executor.java:278) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy198.doWork(Unknown Source) at ome.services.util.Executor$Impl.execute(Executor.java:205) at ome.services.sessions.SessionManagerImpl.executeUpdate(SessionManagerImpl.java:623) at ome.services.sessions.SessionManagerImpl.createSession(SessionManagerImpl.java:215) at ome.services.sessions.SessionManagerImpl.create(SessionManagerImpl.java:186) at ome.services.util.ExecutionThread.sessionInit(ExecutionThread.java:80) at ome.services.util.ExecutionThread.run(ExecutionThread.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.springframework.util.MethodInvoker.invoke(MethodInvoker.java:283) at org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean$MethodInvokingJob.executeInternal(MethodInvokingJobDetailFactoryBean.java:272) at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86) at org.quartz.core.JobRunShell.run(JobRunShell.java:203) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
Change History (2)
comment:1 Changed 16 years ago by jmoore
- Milestone changed from 3.0-Beta3.1 to 3.0-Beta4
comment:2 Changed 15 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
This issue has not reappeared after some larger reworkings of the spring configurations. Closing.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
This occurs when the server is sufficiently fast during startup. Though its disconcerting for sysadmins to see the exception, the race condition has no further side-effects.
Pushing to milestone:3.0-Beta4 to not make any large-scale changes this close to release.