PDA

View Full Version : Quartz OutOfMemoryException



rafeco
Oct 19th, 2004, 03:15 PM
I have a scheduled task that I've set up that works on all of my servers but one. Here's the stack trace. Anyone know how to go about troubleshooting this?



INFO JobRunShell.java(181) [15:19:34,620]: Job DEFAULT.ssnJobDetail threw a JobExecutionException:
org.quartz.JobExecutionException: Could not invoke method 'doIt' on target object [XXXXXXXXX@136bdda] [See nested exception: java.lang.reflect.InvocationTargetException]
at org.springframework.scheduling.quartz.MethodInvoki ngJobDetailFactoryBean$MethodInvokingJob.executeIn ternal(MethodInvokingJobDetailFactoryBean.java:135 )
at org.springframework.scheduling.quartz.QuartzJobBea n.execute(QuartzJobBean.java:66)
at org.quartz.core.JobRunShell.run(JobRunShell.java:1 78)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run (SimpleThreadPool.java:477)
* Nested Exception (Underlying Cause) ---------------
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.springframework.util.MethodInvoker.invoke(Meth odInvoker.java:216)
at org.springframework.scheduling.quartz.MethodInvoki ngJobDetailFactoryBean$MethodInvokingJob.executeIn ternal(MethodInvokingJobDetailFactoryBean.java:126 )
at org.springframework.scheduling.quartz.QuartzJobBea n.execute(QuartzJobBean.java:66)
at org.quartz.core.JobRunShell.run(JobRunShell.java:1 78)

at org.quartz.simpl.SimpleThreadPool$WorkerThread.run (SimpleThreadPool.java:477)
Caused by: java.lang.OutOfMemoryError

Colin Sampaleanu
Oct 20th, 2004, 09:25 AM
If this is working in most environments, but not this one, then the first thing I would do is take a look at the differences between the environments. i.e. it is possible in this environment you are running with less memory allocated to th VM. Alternately, are there differences in how the app is used in each environment?

You may have to get out a profile though and see how memory is being consumed...