Hi all,

It is a known fact that some operations in Carbon are somewhat long
running, and need sometime to complete. On the other hand, we have the
stuck thread detection logic which will ensure processes complete in a
timely manner. The two concepts don't quite complement each other,
especially when there is something that takes more than 10 minutes. As a
solution to this, Azeez and I discussed a solution around Job Management in
Carbon. Right now, after a service, webapp, registry resource is uploaded,
we just ask the user to keep refreshing the page to see what happened, and
we have worked around the limitation of the stuck thread detection by
introducing a separate thread. So the idea here is to create some sort of
"Pending Tasks" in the Carbon UIs, which allows both user to see what's
pending and existing JSPs to display proper "loading" icons etc.

Also, another benefit of this approach is that if you want to deploy
multiple services, and it takes really long or if you want to upload an
archive containing 1000s of resources in to G-Reg, you no longer need to
keep staring at the screen until the task completes. So, I have created a
JIRA item to make sure we introduce this useful feature into Carbon, [1].

Also, at the same time, there is a serious resource clean-up bug around the
stuck thread detection logic. If a thread dies, the resources allocated are
not recycled. This is very harmful (for example DB connections in
registry). So, we need some hooks to register resource clean-up logic, [2].

[1] https://wso2.org/jira/browse/CARBONROADMAP-29
[2] https://wso2.org/jira/browse/CARBON-12182

Thanks,
Senaka.

-- 
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

*Lean . Enterprise . Middleware
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to