You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Heshan Suriyaarachchi (Created) (JIRA)" <ji...@apache.org> on 2012/03/26 22:46:30 UTC
[jira] [Created] (AIRAVATA-352) A service update results in all the
services updated multiple times (by spawning new threads)
A service update results in all the services updated multiple times (by spawning new threads)
---------------------------------------------------------------------------------------------
Key: AIRAVATA-352
URL: https://issues.apache.org/jira/browse/AIRAVATA-352
Project: Airavata
Issue Type: Bug
Reporter: Heshan Suriyaarachchi
Steps to reproduce.
1. Create a multiple Service/Application descriptions.
2. Edit a service description and hit update.
3. Look at the logs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (AIRAVATA-352) A service update results in all the
services updated multiple times (by spawning new threads)
Posted by "Suresh Marru (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Marru closed AIRAVATA-352.
---------------------------------
Resolution: Not A Problem
Assignee: Heshan Suriyaarachchi
This issue went away with UI refactoring of service and application.
> A service update results in all the services updated multiple times (by spawning new threads)
> ---------------------------------------------------------------------------------------------
>
> Key: AIRAVATA-352
> URL: https://issues.apache.org/jira/browse/AIRAVATA-352
> Project: Airavata
> Issue Type: Bug
> Reporter: Heshan Suriyaarachchi
> Assignee: Heshan Suriyaarachchi
>
> Steps to reproduce.
> 1. Create a multiple Service/Application descriptions.
> 2. Edit a service description and hit update.
> 3. Look at the logs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira