You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Pavan Kumar <pa...@gmail.com> on 2006/03/22 12:43:13 UTC
Problem invoking the destination component from the Quartz component
Hi,
I wrote a very simple piece of esb script containing only two components.
The first is the servicemix quartz component which is configured to
run infinitely(ie with repeatInterval = -1). The second one is a servicemix
groovy component which contains a couple of groovy's "println" statements.
After every two mins the quartz component fires the groovy component (ie the
groovy script).
The problem is that , after 24-36 hrs the groovy component is not being
invoked.
I found that the problem was not with the quartz component ,as I can see the
log file and debug statements on screen from quartz. I am not able to see
the
output of the println statements from groovy after 25hrs to 28hrs
approximately.
ServiceMix version used : servicemix-2.1-SNAPSHOT
I also tried it running on both windows and linux systems with different
system loads.
The duration of successfully invoking the groovy script was varying from 25
hrs to 36 hrs.
I also didn't find any errors or atleast warnings in the debug mode.
Can someone help me in understanding the problem of why the destination
groovy
components is being invoked for only around 24 hrs and failing then after.
I am attaching the esb script file along with the mail.
Thanks,
Pavan Kumar
Re: Problem invoking the destination component from the Quartz component
Posted by Pavan Kumar <pa...@gmail.com>.
Guillaume,
Thanks a lot for the information.
It would be better for me to use the build for the
3.0-SNAPSHOTdistribution, as
I already have planned my things to port to 3.0.
Cheers,
Pavan Kumar
On 3/22/06, Guillaume Nodet <gn...@gmail.com> wrote:
>
> Thanks for reporting that.
> This is now fixed in svn head and will be available in next nightly
> build for the 3.0-SNAPSHOT distribution. You should upgrade to this
> one (not that the package names have changed to
> org.apache.servicemix.*)
>
> FYI, the problem was on the quartz component side. When a JBI
> exchange is send, the target component should return a DONE status
> (for an in-only). The script component was sending these messages but
> the quartz component did not read them from the delivery channel. So
> that when the delivery channel was full, the script component was
> blocked...
>
> Btw, the 2.1-SNAPSHOT should not be used as it will never be released.
> If you really want to stick with it, you can backport the changes in
> your source tree.
> See
> http://svn.apache.org/viewcvs/incubator/servicemix/trunk/servicemix-components/src/main/java/org/apache/servicemix/components/quartz/QuartzComponent.java?rev=387849&r1=387848&r2=387849&view=diff
> for the fix i checked in.
>
> Cheers,
> Guillaume Nodet
>
> On 3/22/06, Pavan Kumar <pa...@gmail.com> wrote:
> >
> >
> > Hi,
> >
> > I wrote a very simple piece of esb script containing only two
> components.
> > The first is the servicemix quartz component which is configured to
> > run infinitely(ie with repeatInterval = -1). The second one is a
> > servicemix
> > groovy component which contains a couple of groovy's "println"
> > statements.
> > After every two mins the quartz component fires the groovy component
> (ie
> > the groovy script).
> >
> > The problem is that , after 24-36 hrs the groovy component is not
> being
> > invoked.
> > I found that the problem was not with the quartz component ,as I can
> see
> > the
> > log file and debug statements on screen from quartz. I am not able to
> see
> > the
> > output of the println statements from groovy after 25hrs to 28hrs
> > approximately.
> >
> > ServiceMix version used : servicemix-2.1-SNAPSHOT
> >
> > I also tried it running on both windows and linux systems with
> different
> > system loads.
> > The duration of successfully invoking the groovy script was varying
> from 25
> > hrs to 36 hrs.
> > I also didn't find any errors or atleast warnings in the debug mode.
> >
> >
> > Can someone help me in understanding the problem of why the destination
> > groovy
> > components is being invoked for only around 24 hrs and failing then
> after.
> >
> > I am attaching the esb script file along with the mail.
> >
> > Thanks,
> >
> > Pavan Kumar
> >
> >
> >
> >
>
Re: Problem invoking the destination component from the Quartz component
Posted by Guillaume Nodet <gn...@gmail.com>.
Thanks for reporting that.
This is now fixed in svn head and will be available in next nightly
build for the 3.0-SNAPSHOT distribution. You should upgrade to this
one (not that the package names have changed to
org.apache.servicemix.*)
FYI, the problem was on the quartz component side. When a JBI
exchange is send, the target component should return a DONE status
(for an in-only). The script component was sending these messages but
the quartz component did not read them from the delivery channel. So
that when the delivery channel was full, the script component was
blocked...
Btw, the 2.1-SNAPSHOT should not be used as it will never be released.
If you really want to stick with it, you can backport the changes in
your source tree.
See http://svn.apache.org/viewcvs/incubator/servicemix/trunk/servicemix-components/src/main/java/org/apache/servicemix/components/quartz/QuartzComponent.java?rev=387849&r1=387848&r2=387849&view=diff
for the fix i checked in.
Cheers,
Guillaume Nodet
On 3/22/06, Pavan Kumar <pa...@gmail.com> wrote:
>
>
> Hi,
>
> I wrote a very simple piece of esb script containing only two components.
> The first is the servicemix quartz component which is configured to
> run infinitely(ie with repeatInterval = -1). The second one is a
> servicemix
> groovy component which contains a couple of groovy's "println"
> statements.
> After every two mins the quartz component fires the groovy component (ie
> the groovy script).
>
> The problem is that , after 24-36 hrs the groovy component is not being
> invoked.
> I found that the problem was not with the quartz component ,as I can see
> the
> log file and debug statements on screen from quartz. I am not able to see
> the
> output of the println statements from groovy after 25hrs to 28hrs
> approximately.
>
> ServiceMix version used : servicemix-2.1-SNAPSHOT
>
> I also tried it running on both windows and linux systems with different
> system loads.
> The duration of successfully invoking the groovy script was varying from 25
> hrs to 36 hrs.
> I also didn't find any errors or atleast warnings in the debug mode.
>
>
> Can someone help me in understanding the problem of why the destination
> groovy
> components is being invoked for only around 24 hrs and failing then after.
>
> I am attaching the esb script file along with the mail.
>
> Thanks,
>
> Pavan Kumar
>
>
>
>