[JBoss JIRA] (RTGOV-245) Querying activity via REST API results in hibernate lazy instantiation exception
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/RTGOV-245?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on RTGOV-245:
-----------------------------------------------
Gary Brown <gbrown(a)redhat.com> made a comment on [bug 996030|https://bugzilla.redhat.com/show_bug.cgi?id=996030]
Description of problem:
When querying activity events through the Activity Server REST API, using a REST client, the server throws a lazy instantiation exception in hibernate when trying to construct the JSON representation of the activity events.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Execute a business transaction to create some activity events in the server.
2. POST the following message to: http://localhost:8080/overlord-rtgov/activity/query with basic auth credentials of user: admin password: overlord
{
"format" : "jpql",
"expression" : "SELECT at FROM ActivityType at"
}
Actual results:
Exception
Expected results:
List of activity events
Additional info:
> Querying activity via REST API results in hibernate lazy instantiation exception
> --------------------------------------------------------------------------------
>
> Key: RTGOV-245
> URL: https://issues.jboss.org/browse/RTGOV-245
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.1.0.Final
>
>
> Using a REST client to query activity events results in a hibernate lazy instantiation exception.
> First solution would be to change to EAGER fetch, although this results in another hibernate exception. Possible workaround is to change ActivityType.context from being a list to a set.
> Another solution would be to expand the txn boundary to encompass the REST query operation.
--
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, 4 months
[JBoss JIRA] (RTGOV-246) Repeated errors logged if activity server is down
by Gary Brown (JIRA)
Gary Brown created RTGOV-246:
--------------------------------
Summary: Repeated errors logged if activity server is down
Key: RTGOV-246
URL: https://issues.jboss.org/browse/RTGOV-246
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.1.0.Final
If the remote activity server is down, this can cause a large number of error messages to be reported to the log.
Only the first detected error should result in a log message, with subsequent messages being ignored until the connection is available again, at which point an INFO message should be reported indicating reporting has resumed.
NOTE: Potentially a periodic error message should be reported if the connection remains down (possibly every hour? to indicate that it is still unavailable).
--
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, 4 months
[JBoss JIRA] (RTGOV-245) Querying activity via REST API results in hibernate lazy instantiation exception
by Gary Brown (JIRA)
Gary Brown created RTGOV-245:
--------------------------------
Summary: Querying activity via REST API results in hibernate lazy instantiation exception
Key: RTGOV-245
URL: https://issues.jboss.org/browse/RTGOV-245
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.1.0.Final
Using a REST client to query activity events results in a hibernate lazy instantiation exception.
First solution would be to change to EAGER fetch, although this results in another hibernate exception. Possible workaround is to change ActivityType.context from being a list to a set.
Another solution would be to expand the txn boundary to encompass the REST query operation.
--
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, 4 months