[JBoss JIRA] (GADGETS-59) Use file based h2 db created on installation
by Gary Brown (JIRA)
Gary Brown created GADGETS-59:
---------------------------------
Summary: Use file based h2 db created on installation
Key: GADGETS-59
URL: https://issues.jboss.org/browse/GADGETS-59
Project: Gadget Server and Gadgets
Issue Type: Task
Reporter: Gary Brown
Assignee: Jeff Yu
Fix For: 1.0.0.M5
Currently uses in-memory h2 db as default, with "hibernate.hbm2ddl.auto" set to "create-drop", so data is lost on restart.
Change to file based h2 db, created with installing the gadget server.
--
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
11 years, 7 months
[JBoss JIRA] (RTGOV-162) SLA report based on historic analysis of Situations
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-162?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-162:
----------------------------------
Need to also provide a solution that works with an Activity Validator to create and persist situations.
> SLA report based on historic analysis of Situations
> ---------------------------------------------------
>
> Key: RTGOV-162
> URL: https://issues.jboss.org/browse/RTGOV-162
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Gary Brown
> Priority: Critical
> Fix For: 1.0.0.Final
>
>
> Need to determine what information should be stored in the Situation to enable a report to be compiled based on service performance and availability.
> The criteria for what constitutes a violation of a particular customer's SLA needs to be defined. For example, the SLAs may only apply within particular day/time periods - which will also need to take into account timezones.
> Need to see whether this per customer information can be stored in SRAMP repo, and also reported via Polymita, as requires further analysis of the underlying information - and possibly needs to be presented in a tabular form.
--
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
11 years, 7 months
[JBoss JIRA] (RTGOV-194) "Key not found" error on ActiveMap when using activity client sample
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-194?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-194.
------------------------------
Resolution: Done
Was caused by activity events not having the 'interface' attribute, which is used as the key. Updated the mvel script to ignore service definitions without keys, and updated the test data to include the relevant information, so they can now also be used to build call trace data.
> "Key not found" error on ActiveMap when using activity client sample
> --------------------------------------------------------------------
>
> Key: RTGOV-194
> URL: https://issues.jboss.org/browse/RTGOV-194
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.Final
>
> Attachments: server.log
>
>
> The following error is reported when using "mvn install -Dcount=1" on the activity client:
> 11:03:03,764 SEVERE [org.overlord.rtgov.active.collection.ActiveMap] (Thread-3 (HornetQ-client-global-threads-763665750)) Key not defined
> This is eventually followed by some exceptions when trying to merge snapshots, shown in the attached server log.
--
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
11 years, 7 months