[JBoss JIRA] (SRAMP-186) Auditing: properly audit relationship changes
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-186:
-----------------------------------
Summary: Auditing: properly audit relationship changes
Key: SRAMP-186
URL: https://issues.jboss.org/browse/SRAMP-186
Project: S-RAMP
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Fix For: 0.2.0 - Milestone 4
The auditing implementation currently doesn't properly handle changes to relationships. The impl should be enhanced to include relationships.
--
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-186) Hibernate exception when accessing call trace
by Gary Brown (JIRA)
Gary Brown created RTGOV-186:
--------------------------------
Summary: Hibernate exception when accessing call trace
Key: RTGOV-186
URL: https://issues.jboss.org/browse/RTGOV-186
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M5
{noformat}
10:54:24,843 SEVERE [org.overlord.rtgov.call.trace.CallTraceProcessor] (http-/127.0.0.1:8080-2) Failed to retrieve activity events for context '1' : org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: org.overlord.rtgov.activity.model.ActivityType.context, could not initialize proxy - no Session
at org.hibernate.collection.internal.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:566) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.collection.internal.AbstractPersistentCollection.withTemporarySessionIfNeeded(AbstractPersistentCollection.java:186) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.collection.internal.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:545) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.collection.internal.AbstractPersistentCollection.read(AbstractPersistentCollection.java:124) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.hibernate.collection.internal.PersistentBag.iterator(PersistentBag.java:266) [hibernate-core-4.2.0.Final-redhat-1.jar:4.2.0.Final-redhat-1]
at org.overlord.rtgov.call.trace.CallTraceProcessor.loadActivityUnits(CallTraceProcessor.java:134) [call-trace-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at org.overlord.rtgov.call.trace.CallTraceProcessor.createCallTrace(CallTraceProcessor.java:90) [call-trace-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at org.overlord.rtgov.call.trace.rest.RESTCallTraceServer.getCallTrace(RESTCallTraceServer.java:141) [call-trace-rests-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at org.overlord.rtgov.call.trace.rest.RESTCallTraceServer.instance(RESTCallTraceServer.java:110) [call-trace-rests-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_07]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_07]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_07]
at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_07]
at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.5.Final-redhat-1.jar:2.3.5.Final-redhat-1]
at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:257) [resteasy-jaxrs-2.3.5.Final-redhat-1.jar:2.3.5.Final-redhat-1]
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:222) [resteasy-jaxrs-2.3.5.Final-redhat-1.jar:2.3.5.Final-redhat-1]
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:211) [resteasy-jaxrs-2.3.5.Final-redhat-1.jar:2.3.5.Final-redhat-1]
at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.5.Final-redhat-1.jar:2.3.5.Final-redhat-1]
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.5.Final-redhat-1.jar:2.3.5.Final-redhat-1]
{noformat}
--
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-185) Service overview based on activity event query
by Gary Brown (JIRA)
Gary Brown created RTGOV-185:
--------------------------------
Summary: Service overview based on activity event query
Key: RTGOV-185
URL: https://issues.jboss.org/browse/RTGOV-185
Project: RTGov (Run Time Governance)
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M5
Currently the service overview is built in realtime based on a rolling window of activity events.
User's may also need the ability to view the service overview at a particular point in time, based on activity events (and possibly situations) over a specified time period.
--
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-184) Investigate what alternative client side configurations/installation types may be required
by Gary Brown (JIRA)
Gary Brown created RTGOV-184:
--------------------------------
Summary: Investigate what alternative client side configurations/installation types may be required
Key: RTGOV-184
URL: https://issues.jboss.org/browse/RTGOV-184
Project: RTGov (Run Time Governance)
Issue Type: Task
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M5
Currently have the REST client configuration - but do we also need to (for example) support direct storage of activity events to db, bypassing the event processor network/active collection mechanisms.
This would still enable user to perform historic queries, e.g. call traces, and BAM queries, using polymita.
--
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