[JBoss JIRA] (RTGOV-269) Report activity logger problems via MBean
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/RTGOV-269?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on RTGOV-269:
-----------------------------------------------
Nick Cross <ncross(a)redhat.com> changed the Status of [bug 1005273|https://bugzilla.redhat.com/show_bug.cgi?id=1005273] from MODIFIED to ON_QA
> Report activity logger problems via MBean
> -----------------------------------------
>
> Key: RTGOV-269
> URL: https://issues.jboss.org/browse/RTGOV-269
> Project: RTGov (Run Time Governance)
> Issue Type: Enhancement
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.M1
>
>
> When the REST client fails to report a list of activity units to the server, then report issue via MBean.
> To avoid reporting a notification for each failure, only report the first occurrence within a 5 min window - if the issue persists, then send a further reminder each 5 mins.
> It may also be useful to provide an indication of the number of consecutive failures as a counter, so they can see when the issue is fixed. Alternatively send a notification when a failure is not reported for 1 min?
--
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
10 years, 9 months
[JBoss JIRA] (RTGOV-279) Situation requires an explicitly defined ID
by Gary Brown (JIRA)
Gary Brown created RTGOV-279:
--------------------------------
Summary: Situation requires an explicitly defined ID
Key: RTGOV-279
URL: https://issues.jboss.org/browse/RTGOV-279
Project: RTGov (Run Time Governance)
Issue Type: Enhancement
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.M1
Situation currently has a protected id set by Hibernate when the situation is persisted. However to enable Situations, that are created and published out as notifications, to be correlated back to the object stored in the db, we need to explicitly set the upon creation, to ensure the same ID is present when the object is published and persisted.
--
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
10 years, 9 months
[JBoss JIRA] (RTGOV-271) Drools 6.0.0.CR2 shows up a dependency on aether that is not packaged in the swyd drools module
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/RTGOV-271?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on RTGOV-271:
-----------------------------------------------
Keith Babo <kbabo(a)redhat.com> made a comment on [bug 1006709|https://bugzilla.redhat.com/show_bug.cgi?id=1006709]
Hey Mario - regarding #3, this is an error at runtime in AS, so it's a JBoss AS module dependency issue and not a Maven pom issue. I have asked David why the kie-ci module is included today. I did a quick scan of the code and I don't see any direct use of the contents of kie-ci in our codebase. Perhaps it was a dependency of the Drools codebase at some time in the past and David had to include it to get things working. Or maybe it's just a legacy of some prior experimentation with Maven resolution support. In any case, we can definitely investigate removing this module dependency altogether. Just to confirm: kie-ci is not a required dependency of Drools or jBPM if we are not using the Maven resolution feature, right?
Thanks for your help!
> Drools 6.0.0.CR2 shows up a dependency on aether that is not packaged in the swyd drools module
> -----------------------------------------------------------------------------------------------
>
> Key: RTGOV-271
> URL: https://issues.jboss.org/browse/RTGOV-271
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.M1
>
>
--
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
10 years, 9 months
[JBoss JIRA] (RTGOV-271) Drools 6.0.0.CR2 shows up a dependency on aether that is not packaged in the swyd drools module
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/RTGOV-271?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on RTGOV-271:
-----------------------------------------------
Mario Fusco <mfusco(a)redhat.com> made a comment on [bug 1006709|https://bugzilla.redhat.com/show_bug.cgi?id=1006709]
Quick premise: I'd need to reproduce this issue to have a full understanding of what is going wrong, but at the moment I don't know how, so this comment will be based on the following assumptions (that could be very likely wrong):
1. You have the kie-ci module in your classpath: org.kie.scanner.MavenClassLoaderResolver and org.kie.scanner.ArtifactResolver classes that I can see in the Exception stack belongs to that module, so this is hardly rebuttable.
2. Conversely you don't have aether-api in your classpath, or you have a different (older?) version from the 1.13.1 used by kie-ci and this is why you are getting that NoClassDefFoundError
3. Since aether-api is a dependency of kie-ci you explicitly excluded it from your pom file
If this is true, and you don't want to depend on aether, the quickest solution (that doesn't require any change to your code) is to just also exclude kie-ci on your classpath. In fact our ServiceRegistry is automatically choosing the MavenClassLoaderResolver class as implementation class for the ClassLoaderResolver service only because it can find it in the classpath. If it couldn't it would select the NoDepsClassLoaderResolver instead that doesn't require any aether dependency.
To cut it short, either have both kie-ci and aether-api in your classpath or none of them.
I hope this helps, but again if my assumptions are wrong please provide a test case that could allow me to investigate this issue in more details.
> Drools 6.0.0.CR2 shows up a dependency on aether that is not packaged in the swyd drools module
> -----------------------------------------------------------------------------------------------
>
> Key: RTGOV-271
> URL: https://issues.jboss.org/browse/RTGOV-271
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.M1
>
>
--
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
10 years, 9 months
[JBoss JIRA] (SRAMP-239) Remove default username/password from SrampWagon
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-239:
-----------------------------------
Summary: Remove default username/password from SrampWagon
Key: SRAMP-239
URL: https://issues.jboss.org/browse/SRAMP-239
Project: S-RAMP
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: IDE Integration
Affects Versions: 0.3.0 - JBPM6 Integration
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Fix For: 0.3.1 - jBPM - bugfix 1
Right now we default to admin/overlord. This should be changed to prompt the user for input.
--
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
10 years, 9 months