Hi All,
Further to the investigation done to support coordination=false in MT mode,
following is implemented.
With coordination=false inbound endpoint will not schedule any task, but
run as a background thread. When starting the ESB, if there is a task
scheduled tenant gets loaded automatically.
Hi All,
We have a parameter called sequential for polling inbound. Following is the
behavior.
sequential == true -> Will be injecting the message withing the same thread
and will take the next message after processing the current message.
sequential == false -> Will be injecting the message to a
Hi Malaka,
Noted. I added the functionality to support the polling interval less than
1000 ms in Kafka Inbound EP. I created a new method for starting task
service in Kafka inbound EP for that. As you recommended I will use the
common inbound task method in Kafka inbound EP.
Thanks,
Kathees
On T
Hi All,
I have added the functionality to support polling interval less than 1
second for inbound endpoints.
This is implemented when user adds the inbound endpoint, it schedule a task
with NTASK. If the interval is less than 1000ms will be scheduling the task
for 1000ms. When executing such an i
According to the offline chat I had with Anjana, we are going to load the
tenant as required when executing the task.
On Wed, Oct 1, 2014 at 12:04 PM, Anjana Fernando wrote:
> I hope you understood, what I told is, not what you mentioned earlier, you
> do not have to store anything in the regist
I hope you understood, what I told is, not what you mentioned earlier, you
do not have to store anything in the registry, and the ESB does not have to
load anything themselves. The tasks will be automatically loaded.
Cheers,
Anjana.
On Wed, Oct 1, 2014 at 12:00 PM, Malaka Silva wrote:
> Hi Anja
Hi Anjana,
Yes that is the plan. Will be implementing this at the task adapter level.
Best Regards,
Malaka
On Wed, Oct 1, 2014 at 11:23 AM, Anjana Fernando wrote:
> Hi Malaka,
>
> Kasun sometime earlier asked me about this; And basically, from ntask, the
> tasks will automatically start up whe
Hi Malaka,
Kasun sometime earlier asked me about this; And basically, from ntask, the
tasks will automatically start up when the server is started up. It does
not wait till a tenant is loaded or anything like that, it is automatically
handled by ntask. If the task itself wants some tenant specific
Hi All,
At the time of inbound EP code review Azeez has identified an issue with
ntask integration in tenant mode.
The problem is when a task is schedules in tenant mode this will not run
until the tenant is loaded.
Following is the solution I'm planning to implement.
When a task is scheduled i
We have implemented the $subject and it is available in the ESB's git repo.
As we initially planned we will be releasing this new task manager with our
next release.
Thanks,
Ishan.
On Mon, Apr 21, 2014 at 5:27 PM, Ishan Jayawardena wrote:
> Today we had a discussion to review the current imple
Today we had a discussion to review the current implementation of $subject.
We have developed two task providers/managers to manage quartz and ntask
based task types. The correct task manager gets registered according to the
synapse configuration, during the startup. When a user deploys a new task
Hi Kasun,
We managed to solve the issue and now we are working on the final stage of
the development. We will complete this within this week.
Thanks,
Ishan.
On Tue, Apr 15, 2014 at 9:48 AM, Kasun Indrasiri wrote:
> Did you check whether the required packages are osgi imported properly?
> On a
Did you check whether the required packages are osgi imported properly?
On a separate note, what's the ETA of a working deliverable of this?
On Sun, Apr 13, 2014 at 12:43 PM, Anjana Fernando wrote:
> Obviously, check if that class is available and where it is referred from
> in the code. As I
Obviously, check if that class is available and where it is referred from
in the code. As I remember, there isn't a package called "ntaskint", so
check where this is coming from.
Cheers,
Anjana.
On Sat, Apr 12, 2014 at 6:46 AM, Ishan Jayawardena wrote:
> We developed the quartz task manager an
We developed the quartz task manager and we are currently working on the
ntask task manager. While developing the task handling component that uses
ntask, we observed that we cannot schedule a task in it due to a class not
found error. See the below error message. The ntask component (which is
used
Hi Paul,
Task Server is actually another server itself. NTask component is the task
scheduling component we put to all our Carbon server when we need
distributed task scheduling functionality. That component support
scheduling tasks in a standalone manner (in a single server), or in a
clustered mo
Can someone clarify? I'm lost but I really don't understand why we are
creating any other approach than task server. It is the only approach that
scales clearly. Is our task server code too heavyweight?
Paul
On 5 April 2014 08:47, Chanaka Fernando wrote:
> Hi Kasun/Anjana,
>
> I think what Anj
Hi Kasun/Anjana,
I think what Anjana mentioned and Ishan mentioned are somewhat converge to
same idea (even though they looks different).
What we have discussed and agreed was that we are developing a separate
carbon-component which is used for executing the ntask component. Since we
need a commo
On Sat, Apr 5, 2014 at 9:22 AM, Anjana Fernando wrote:
> Hi Ishan,
>
> On Sat, Apr 5, 2014 at 7:33 AM, Ishan Jayawardena wrote:
>
>> Currently, we have developed following design and started to work on it.
>>
>> Synapse will have defined the TaskManager, and Task interfaces whose
>> implementati
Hi Ishan,
On Sat, Apr 5, 2014 at 7:33 AM, Ishan Jayawardena wrote:
> Currently, we have developed following design and started to work on it.
>
> Synapse will have defined the TaskManager, and Task interfaces whose
> implementations will provide the concrete tasks and management of those
> tasks
Hi,
On Mon, Mar 24, 2014 at 8:04 PM, Sagara Gunathunga wrote:
>
>
>
> On Mon, Mar 24, 2014 at 11:52 AM, Kasun Indrasiri wrote:
>
>> I would like to clarify the objective of this task:
>>
>> - Introduce the concept of a Task provider in to ESB. Which means any
>> existing task (task config) can
Currently, we have developed following design and started to work on it.
Synapse will have defined the TaskManager, and Task interfaces whose
implementations will provide the concrete tasks and management of those
tasks depending on the scheduler(ie quartz or ntask).
For instance, for inbuilt quar
On Mon, Mar 24, 2014 at 8:04 PM, Sagara Gunathunga wrote:
>
>
>
> On Mon, Mar 24, 2014 at 11:52 AM, Kasun Indrasiri wrote:
>
>> I would like to clarify the objective of this task:
>>
>> - Introduce the concept of a Task provider in to ESB. Which means any
>> existing task (task config) can be ra
On Mon, Mar 24, 2014 at 11:52 AM, Kasun Indrasiri wrote:
> I would like to clarify the objective of this task:
>
> - Introduce the concept of a Task provider in to ESB. Which means any
> existing task (task config) can be ran on the available task provider( this
> can be ntask, quartz or anything
I would like to clarify the objective of this task:
- Introduce the concept of a Task provider in to ESB. Which means any
existing task (task config) can be ran on the available task provider( this
can be ntask, quartz or anything)
- However, the recipes concept is completely transparent at Synaps
I am working on $subject to support scheduled invocation of recipes in the
ESB. This mainly includes replacing the existing quartz based task
scheduler with ntask scheduler. The new task type is based on ntask, and it
will be added as a new component in the mediation category. We can use the
existi
26 matches
Mail list logo
