Closed GoogleCodeExporter closed 9 years ago
hello berry,
Thanks for reporting the issue. Can you please paste what config props you used
and what's xml you use to create the job?
And what version of myschedule are you using?
Thanks,
Zemian
Original comment by saltnlight5
on 29 Oct 2012 at 1:28
Hi, please find the attached files for config and xml files. I'm using 2.4.4
version of myschedule.
Original comment by berryapp...@gmail.com
on 29 Oct 2012 at 2:49
Attachments:
Hi berry, I can't reproduce your error with your config and xml job. It runs
fine on my box (I used ping instead of curl since I don't have that installed.)
According to your stacktrace, the line
"myschedule.quartz.extra.SchedulerTemplate.getNextFireTimes(SchedulerTemplate.ja
va:647)" will only occur if the trigger no longer exists. I don't see how
that's possible with your xml job since it's a repeating trigger without an end
date.
Perhaps you can print me your full server log with all the quartz activities
and see if I find the cause.
Original comment by saltnlight5
on 31 Oct 2012 at 1:12
Hi, Thanks for your reply.
It seems to be working now..
Can you tell me how to set the end date to stop the trigger according to my
XML..
Original comment by berryapp...@gmail.com
on 1 Nov 2012 at 5:41
Hi, can you please tell me how to add the username and password in the XML
file. So that if any user runs the scheduler that user details(username) has to
be saved in database..Kindly help me in this. Thanks
Original comment by berryapp...@gmail.com
on 9 Nov 2012 at 10:09
Hello Berry,
I am not understanding what you are asking about username and password. The XML
that quartz provides are used to add Trigger or Job entries into the scheduler,
and they don't support username nor password. The xml are supported by Quartz
project. You can read the XSD schema provide by the xml and see what elements
are supported. Or you can post your XML related questions to Quartz to see if
their user can help you.
The MySchedule app itself also provided few examples as well.
Original comment by saltnlight5
on 10 Nov 2012 at 1:32
If this is non-issue, I would like to close it now.
Original comment by saltnlight5
on 2 Mar 2013 at 2:07
Closing issue as invalid.
Original comment by saltnlight5
on 8 Jun 2013 at 3:36
Original issue reported on code.google.com by
berryapp...@gmail.com
on 26 Oct 2012 at 9:57