PET merge requestshttps://git.fortiss.org/pmwt/PET/-/merge_requests2016-06-22T14:35:36Zhttps://git.fortiss.org/pmwt/PET/-/merge_requests/1Add wildfly swarm feature2016-06-22T14:35:36ZGhost UserAdd wildfly swarm featurehttps://git.fortiss.org/pmwt/PET/-/merge_requests/4Merge for sonar token2016-06-30T14:02:38ZGhost UserMerge for sonar tokenhttps://git.fortiss.org/pmwt/PET/-/merge_requests/2Pet 2 02016-06-22T16:37:38ZGhost UserPet 2 0https://git.fortiss.org/pmwt/PET/-/merge_requests/3Cassandra 3x Support2016-06-29T10:48:44ZGhost UserCassandra 3x Supporthttps://git.fortiss.org/pmwt/PET/-/merge_requests/5Improvements in Resource Environment Analysis and in Resource Container Utili...2018-01-15T08:35:24ZGhost UserImprovements in Resource Environment Analysis and in Resource Container Utilization Calculation* Improvement in Resource Environment Analysis: so far, if a resource container in PCM would have a CPU processing resource specification and this CPU would only be a single instance (i.e. Number Of Replicas = 1), the corresponding PCM ...* Improvement in Resource Environment Analysis: so far, if a resource container in PCM would have a CPU processing resource specification and this CPU would only be a single instance (i.e. Number Of Replicas = 1), the corresponding PCM resource environment XML element <activeResourceSpecifications\_ResourceContainer/> would miss the attribute numberOfReplicas. Using PET for a PCM like this would lead to a problem. The resource environment parser in PET tries to parse the attributes from the above mentioned XML element and would throw a NumberFormatException that leads to an internal server error \parencite{PET:ResourceParser}. We fixed this by adding a try and catch block. Once the exception is thrown, we programmatically set the number of CPU instances to one.
* Improvement of Resource Container Utilization Calculation: in cases, where users do not specify the utilization of the CPU, MEM, and/or HDD in PCM, there is obviously also no information about it added to PET. We improved a function in PET by adding checks whether certain performance parameters are valid Double values or NaN. This avoids NumberFormatExceptions that would also lead to an internal server error. Now, whenever a user does not add information about one or more of the above mentioned resource types, the corresponding parameters are set to zero.
* Also, we added a check whether a simulation has information about any linking resources in PCM. If not, we manually add an empty table to the database. This also increased the stability of PET in these scenarios.