on 11-25-2014 3:14 AM
HI
I have a job running in Production set up as below:-
Job Chain A
Job Definition Step 1: Pull Report from SAP System
job Definition Step 2: Send the
spool file which get from step 1(step1/spool1.txt) to Recipients via email
When job submitted , Step 1 Job ran successfully, but Step 2 Job ended with error. Although Step 2 Job ended with error, recipients
successfully received spool file via email.
Could you suggest the solution to prevent the Step 2 Job ended with error?
Below is the error message log received from Step 2 Job:-
-- JOB RUN STACK TRACE --
javax.mail.MessagingException: Exception reading response;
nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sun.mail.smtp.SMTPTransport.readServerResponse(SMTPTransport.java:1611)
at com.sun.mail.smtp.SMTPTransport.close(SMTPTransport.java:698)
at javax.mail.Transport.send0(Transport.java:191)
at javax.mail.Transport.send(Transport.java:118)
at com.redwood.scheduler.infrastructure.mail.Mailer.sendMessage(Mailer.java:167)
at com.redwood.scheduler.infrastructure.mail.Mailer.sendMessage(Mailer.java:71)
at com.redwood.scheduler.infrastructure.mail.Mailer.sendMessage(Mailer.java:41)
at com.redwood.scheduler.mail.service.MailJob.execute(MailJob.java:161)
at com.redwood.scheduler.systemjobservice.impl.JobWorker.doWork(JobWorker.java:253)
at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:76)
at java.lang.Thread.run(Thread.java:743)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at com.sun.mail.util.TraceInputStream.read(TraceInputStream.java:110)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
at com.sun.mail.util.LineInputStream.readLine(LineInputStream.java:88)
at com.sun.mail.smtp.SMTPTransport.readServerResponse(SMTPTransport.java:1589)
... 10 more
Hello,
Yes this pops up every now and again, this is due to some timeout parameters on the mail jobs that have been introduced in a certain version.
What you can do is add the following two registry keys (Configuration->Registry)
/configuration/mail/Properties/mail.smtp.timeout
/configuration/mail/Properties/mail.smtp.connectiontimeout
both with value 60000 (milliseconds).
Regards Gerben
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.