That may be the issue then. If ofbiz's database
connection goes stale, which will occur after 8 hours
of database inactivity with MySql (it's a security
feature ;) )there is no way for the service to create
another record in the JobSandbox entity. In our
deployment we run a service every three hours that
simply creates a record in an relatively unused entity
and then delete that record. This may be of value to
add somewhere in the wiki, but with all of the
rearranging going on, I'm not sure where to put it.
This is the simple method that our service calls:
<simple-method method-name="hitTheDatabase"
short-description="store and delete an entry to keep
Mysql Database Alive">
<make-value entity-name="GeoType"
value-name="hitEntity"/>
<set field="hitEntity.geoTypeId"
value="XXXXXXXXXX"/>
<create-value value-name="hitEntity"/>
<entity-one entity-name="GeoType"
value-name="thisEntity">
<field-map field-name="geoTypeId"
env-name="hitEntity.geoTypeId"/>
</entity-one>
<remove-value value-name="thisEntity"/>
</simple-method>
--- Vamsi <[EMAIL PROTECTED]> wrote:
>
> hi
> Thanks for responding
> I am Using Mysql database
> regards
> Vamsi
>
> cjhowe wrote:
> >
> > Services that are scheduled are registered in the
> > JobSandbox entity. After they run, they
> reschedule
> > themselves as defined. So you may check there that
> > your scheduled service had the right field values.
> >
> > If you are using MySql, it is possible that the
> > service runs because the start time might be
> > registered in cache but then when the service goes
> to
> > reschedule itself it cannot create the reschedule
> > entry because the MySql connection will close
> after 8
> > hours of inactivity.
> >
> > What database are you running?
> >
> >
> > --- Vamsi <[EMAIL PROTECTED]> wrote:
> >
> >>
> >> Hi everyone,
> >> I want know that "is there any possiblity that
> >> service scheduled will be
> >> stopped"
> >> why i am asking this question is I had scheduled
> a
> >> service to run forever
> >> it ran successfully for 10 days after that when I
> >> restarted the server one
> >> of the service was not started .
> >>
> >> regards
> >> Vamsi
> >> --
> >> View this message in context:
> >>
> >
>
http://www.nabble.com/Regarding-Scheduled-services-tf2937798.html#a8213433
> >> Sent from the OFBiz - Dev mailing list archive at
> >> Nabble.com.
> >>
> >>
> >
> >
> >
>
> --
> View this message in context:
>
http://www.nabble.com/Regarding-Scheduled-services-tf2937798.html#a8213612
> Sent from the OFBiz - Dev mailing list archive at
> Nabble.com.
>
>
