You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Guillaume Nodet (JIRA)" <ji...@activemq.org> on 2006/03/22 15:47:25 UTC
[jira] Created: (SM-360) Quartz component will stop sending
messages after a certain amount of time
Quartz component will stop sending messages after a certain amount of time
--------------------------------------------------------------------------
Key: SM-360
URL: http://jira.activemq.org/jira//browse/SM-360
Project: ServiceMix
Type: Bug
Components: servicemix-components
Reporter: Guillaume Nodet
>From Pavan Kumar on servicemix-users:
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.activemq.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (SM-360) Quartz component will stop sending
messages after a certain amount of time
Posted by "Guillaume Nodet (JIRA)" <ji...@activemq.org>.
[ http://jira.activemq.org/jira//browse/SM-360?page=all ]
Guillaume Nodet resolved SM-360:
--------------------------------
Assign To: Guillaume Nodet
Resolution: Fixed
Fix Version: 3.0-M1
Author: gnodet
Date: Wed Mar 22 04:45:31 2006
New Revision: 387849
URL: http://svn.apache.org/viewcvs?rev=387849&view=rev
Log:
SM-360: Quartz component will stop sending messages after a certain amount of time
Modified:
incubator/servicemix/trunk/servicemix-components/src/main/java/org/apache/servicemix/components/quartz/QuartzComponent.java
> Quartz component will stop sending messages after a certain amount of time
> --------------------------------------------------------------------------
>
> Key: SM-360
> URL: http://jira.activemq.org/jira//browse/SM-360
> Project: ServiceMix
> Type: Bug
> Components: servicemix-components
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Fix For: 3.0-M1
>
>
> From Pavan Kumar on servicemix-users:
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.activemq.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira