So I have this TaskScheduler that has 5 jobs being triggered by integration.

For testing purposes what I did was create a simple java class that retrieves data using MyBatis mappers.

Here is the code

public class BlahBlah implements Runnable { @Autowired private EmailTemplateService emailTemplateService; EmailTemplate emailTemplate; private String smth(){ emailTemplate = new EmailTemplate(); emailTemplate=emailTemplateService.selectTemplateByCode(6); return emailTemplate.toString(); @Override public void run() { System.out.println(smth()+" "+ new Date());

Then at the main class, Im currently doing a Java Project but this is really a dynamic web project but for testing purposes.

public static void main(String[] args){ ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext("classpath:/spring/application-context.xml"); BlahBlah blah = new BlahBlah(); BlahBlah2 blah2 = new BlahBlah2(); OrderJob job = new OrderJob(); ThreadPoolTaskScheduler scheduler = (ThreadPoolTaskScheduler) context.getBean("scheduler"); CronTrigger trigger = new CronTrigger("0 0/1 * 1/1 * ? "); CronTrigger trigger2 = new CronTrigger("0 0/2 * 1/1 * ? "); ScheduledFuture<BlahBlah> scedulefuture= scheduler.schedule(blah, trigger ); ScheduledFuture<BlahBlah2> scedulefuture2= scheduler.schedule(blah2, trigger2 );

I ran the code this exception appear at the console

TaskUtils$LoggingErrorHandler -- Unexpected error occurred in scheduled task. java.lang.NullPointerException at com.irsis.integration.test.BlahBlah.smth(BlahBlah.java:22) at com.irsis.integration.test.BlahBlah.run(BlahBlah.java:30) at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:53) at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

For some reason every time the project begins a transaction with the database it produces an npe. Any ideas why?

Thanks,
Jet Jayesh A Lalwani wrote: The NPE is not when it begins the transaction. The NPE is happening on line 22 of BlahBlah. At least that's what the stack trace tells me. What is on line 22? One of the references used on line 22 has got to be null.

Sorry didn't put the whole line of code, but for your reference here it s:

package com.irsis.integration.test; import java.util.Date; import java.util.List; import org.springframework.beans.factory.annotation.Autowired; import org.springframework.context.annotation.Bean; import com.irsis.batch.model.EmailTemplate; import com.irsis.batch.service.EmailTemplateService; import com.irsis.integration.mail.OrderJob; public class BlahBlah implements Runnable { @Autowired private EmailTemplateService emailTemplateService; EmailTemplate emailTemplate; private String smth(){ emailTemplate = new EmailTemplate(); emailTemplate=emailTemplateService.selectTemplateByCode(6); return emailTemplate.toString(); // @Bean(name="sampleTask") @Override public void run() { OrderJob job = new OrderJob(); job.scheduledStampOrderHandling();

added console message.

TaskUtils$LoggingErrorHandler -- Unexpected error occurred in scheduled task. java.lang.NullPointerException at com.irsis.integration.test.BlahBlah.smth(BlahBlah.java:23) at com.irsis.integration.test.BlahBlah.run(BlahBlah.java:32) at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:53) at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) <span class="postbody ">No that's not right. You have copy pasted your code wrong. Line 22 is just constructing an object of type email template. That line cannot throw NPE. Don't make me look at line 22, because of the way you copy pasted, the line numbers might have changed. Also, that doesn't help you learn how to solve the problem for yourself. Look at line 22 in your own <a href="https://coderanch.com/wiki/696337/IntelliJ-IDEA" class="api" title="Why should you try IntelliJ IDEA ?" target="_new">IDE</a>. That will point you to the right place <br/> <br/> Generally, any time you get a stack trace, <a href="http://www.permies.com/t/36936/tnk/" class="api" title="Did you just should on me? A silly thread about the word 'should'" target="_new">you should</a> go to the exact line that threw the exception and try to figure out why it threw that exception. This is no different. An NPE simply means you tried to call a method on a reference that is null. You need to find out what variable is null in this case.</span> <cite>Jayesh A Lalwani wrote:</cite>No that's not right. You have copy pasted your code wrong. Line 22 is just constructing an object of type email template. That line cannot throw NPE. Don't make me look at line 22, because of the way you copy pasted, the line numbers might have changed. Also, that doesn't help you learn how to solve the problem for yourself. Look at line 22 in your own IDE. That will point you to the right place <br/> <br/> Generally, any time you get a stack trace, you should go to the exact line that threw the exception and try to figure out why it threw that exception. This is no different. An NPE simply means you tried to call a method on a reference that is null. You need to find out what variable is null in this case.</p> </blockquote> <br/> <br/> Sorry, about that my bad. Updated my reply with the console message it's actually having a npe exception at line 23 : emailTemplate=emailTemplateService.selectTemplateByCode(6); <br/> <br/> But it's not supposed to have an exception since an email template with an email code of 6 exists in the database and the method I'm using is working since I'm using it on a another class and it seems to work fine there. </span> <span class="postbody ">Once you eliminate everything that is impossible, whatever remains, however improbable, must be the truth. <br/> <br/> Now, in that sentence, there are 3 things happening. <br/> 1) 6 is passed as a parameter <br/> 2) select template by code method on email template service is called <br/> 3) reference to the object returned by the method is stored in email template <br/> <br/> <br/> It is impossible for 1) and 2) to throw NPE? So, it has to be 2) the only way 2) I will throw an NPE will be when emailTemplateService is null. So, it has to be null, however improbable you think that might be. If you like you can verify this by debugging the code, or by adding a log before line 23. <br/> <br/> <br/> So, the question is why is it null. Well, that reference is autowired. You'll have to figure out from the sprig configuration. Has to be so,e reason why spring wouldn't autowired it.</span> <cite>Jayesh A Lalwani wrote:</cite>Once you eliminate everything that is impossible, whatever remains, however improbable, must be the truth. <br/> <br/> Now, in that sentence, there are 3 things happening. <br/> 1) 6 is passed as a parameter <br/> 2) select template by code method on email template service is called <br/> 3) reference to the object returned by the method is stored in email template <br/> <br/> <br/> It is impossible for 1) and 2) to throw NPE? So, it has to be 2) the only way 2) I will throw an NPE will be when emailTemplateService is null. So, it has to be null, however improbable you think that might be. If you like you can verify this by debugging the code, or by adding a log before line 23. <br/> <br/> <br/> So, the question is why is it null. Well, that reference is autowired. You'll have to figure out from the sprig configuration. Has to be so,e reason why spring wouldn't autowired it.</p> </blockquote> <br/> <br/> Thanks for the advice finally found my mistake. Removed the @Autowired annotation on the service and injected the service impl into the application-context.xml. Then used the .getBean method on my class so I can finally get my data. <img src="https://www.coderanch.com/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif"/></span>