January 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-141) Derivers unable to create relationships from original artifact to derived

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-141?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-141: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/166 > Derivers unable to create relationships from original artifact to derived > ------------------------------------------------------------------------- > > Key: SRAMP-141 > URL: https://issues.jboss.org/browse/SRAMP-141 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > If a deriver creates a relationship from the original artifact to a derived artifact, the persist of the original fails. Likely because the derived artifact has not yet been persisted. Will need to persist in two stages or change the order of persistence. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (BAM-22) Exception when EPN JMX class attempts to unregister network listener

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-22?page=com.atlassian.jira.plugin.sys... ] Gary Brown resolved BAM-22. --------------------------- Resolution: Done The associated AS7 fix didn't resolve this problem. Even though the ejb is being injected into the MBean, it still closed the EJB before the MBean had been destroyed. As this is only occurring in the MBeans, within the @PreDestroy method (so just prior to server shutdown), have just commented out the removal of the listener, as this should have no adverse effect. > Exception when EPN JMX class attempts to unregister network listener > -------------------------------------------------------------------- > > Key: BAM-22 > URL: https://issues.jboss.org/browse/BAM-22 > Project: Business Activity Monitoring > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M4 > > > Exception currently generated when the JMX EPNManagement class attempts to unregister itself as a network listener when the server is being shutdown - but probably due to undeployment of the overlord-bam war. > Appears to be a known issue fixed in AS7.1.Final: https://issues.jboss.org/browse/AS7-3487 > Needs to be confirmed when Switchyard 0.5.final available on AS7.1. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-141) Derivers unable to create relationships from original artifact to derived

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-141: ----------------------------------- Summary: Derivers unable to create relationships from original artifact to derived Key: SRAMP-141 URL: https://issues.jboss.org/browse/SRAMP-141 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: Milestone 3 (Workflow and Relationships) If a deriver creates a relationship from the original artifact to a derived artifact, the persist of the original fails. Likely because the derived artifact has not yet been persisted. Will need to persist in two stages or change the order of persistence. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-140) Create unit tests for shell commands

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-140: ----------------------------------- Summary: Create unit tests for shell commands Key: SRAMP-140 URL: https://issues.jboss.org/browse/SRAMP-140 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: Milestone 4 I currently have poor junit coverage in the s-ramp-shell project. I need to create some unit tests, both for executing commands as well as for ancillary functionality like tab-completion. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (BAM-116) Document installation instructions for different server configurations

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-116?page=com.atlassian.jira.plugin.sy... ] Gary Brown resolved BAM-116. ---------------------------- Resolution: Done > Document installation instructions for different server configurations > ---------------------------------------------------------------------- > > Key: BAM-116 > URL: https://issues.jboss.org/browse/BAM-116 > Project: Business Activity Monitoring > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M4 > > > mvn install > This installs the default 'server' profile which includes gadget server, activity server, EPN and active collections, aswell as the collector mechanism. > mvn install -Dtype=restc > The 'type' system property is used to specify the alternative installation. In this case the 'restc' refers to a cut down profile that only includes the collector mechanism, rest based active server client and the active collection mechanism (for where services e.g. order mgmt example, have policies that refer to info in an active collection). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (BAM-113) BAM should work in a clustered JBossAS environment

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-113?page=com.atlassian.jira.plugin.sy... ] Gary Brown commented on BAM-113: -------------------------------- >From the original description, (3) CEP configuration to work in a cluster, has not been done, as there are no CEP rules that currently need this. > BAM should work in a clustered JBossAS environment > -------------------------------------------------- > > Key: BAM-113 > URL: https://issues.jboss.org/browse/BAM-113 > Project: Business Activity Monitoring > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Critical > Fix For: 1.0.0.M4 > > > Current version works in a standalone server. Need to ensure that it can also work in a clustered environment. Areas to check: > (1) JMS event distribution - ensure event processor work is distributed across multiple servers without problem, and that all servers are notified of results to update their local active collection representations. > (2) When caching used in support of the event processing and/or active collections, ensure that caches are correctly configured to work in the cluster. > (3) CEP configuration to work in a cluster. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (BAM-113) BAM should work in a clustered JBossAS environment

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-113?page=com.atlassian.jira.plugin.sy... ] Gary Brown commented on BAM-113: -------------------------------- Documentation has been updated to include the new common config location $JBOSS_HOME/standalone/configuration/overlord-bam.properties, which includes the default infinispan container JNDI name to use. If running clustered config, then this property should be uncommented, and an explicit entry should be created under this default 'cluster' container for each cache. The one used to test the policy enforcement example was: {noformat} <cache-container name="cluster" aliases="ha-partition" default-cache="default"> <transport lock-timeout="60000"/> <replicated-cache name="default" mode="SYNC" batching="true"> <locking isolation="REPEATABLE_READ"/> </replicated-cache> <replicated-cache name="Principals" mode="SYNC"> <locking isolation="REPEATABLE_READ"/> <transaction mode="FULL_XA" locking="PESSIMISTIC"/> </replicated-cache> </cache-container> {noformat} > BAM should work in a clustered JBossAS environment > -------------------------------------------------- > > Key: BAM-113 > URL: https://issues.jboss.org/browse/BAM-113 > Project: Business Activity Monitoring > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Critical > Fix For: 1.0.0.M4 > > > Current version works in a standalone server. Need to ensure that it can also work in a clustered environment. Areas to check: > (1) JMS event distribution - ensure event processor work is distributed across multiple servers without problem, and that all servers are notified of results to update their local active collection representations. > (2) When caching used in support of the event processing and/or active collections, ensure that caches are correctly configured to work in the cluster. > (3) CEP configuration to work in a cluster. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (BAM-113) BAM should work in a clustered JBossAS environment

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-113?page=com.atlassian.jira.plugin.sy... ] Gary Brown resolved BAM-113. ---------------------------- Resolution: Done Works with AS7.1.3.Final with <security-enabled>false</security-enabled> set in the standalone-full-ha.xml under the <hornetq-server> element. Can use the switchyard 0.7.0.Final installer, but doesn't update the standalone-full-ha.xml - so need to manually copy over the subsystem element for switchyard. > BAM should work in a clustered JBossAS environment > -------------------------------------------------- > > Key: BAM-113 > URL: https://issues.jboss.org/browse/BAM-113 > Project: Business Activity Monitoring > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Critical > Fix For: 1.0.0.M4 > > > Current version works in a standalone server. Need to ensure that it can also work in a clustered environment. Areas to check: > (1) JMS event distribution - ensure event processor work is distributed across multiple servers without problem, and that all servers are notified of results to update their local active collection representations. > (2) When caching used in support of the event processing and/or active collections, ensure that caches are correctly configured to work in the cluster. > (3) CEP configuration to work in a cluster. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (BAM-117) Provide lazy instantiation option for active collections

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-117?page=com.atlassian.jira.plugin.sy... ] Gary Brown resolved BAM-117. ---------------------------- Resolution: Done > Provide lazy instantiation option for active collections > -------------------------------------------------------- > > Key: BAM-117 > URL: https://issues.jboss.org/browse/BAM-117 > Project: Business Activity Monitoring > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M4 > > > Currently the active collections are initialized when their source is registered. > Provide an option to enable the collection to be created on first use. This may be relevant in cases where a factory for the active collection has been defined, to avoid unnecessary processing when a collection may not be used. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (BAM-117) Provide lazy instantiation option for active collections

by Gary Brown (JIRA)

Gary Brown created BAM-117: ------------------------------ Summary: Provide lazy instantiation option for active collections Key: BAM-117 URL: https://issues.jboss.org/browse/BAM-117 Project: Business Activity Monitoring Issue Type: Feature Request Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.M4 Currently the active collections are initialized when their source is registered. Provide an option to enable the collection to be created on first use. This may be relevant in cases where a factory for the active collection has been defined, to avoid unnecessary processing when a collection may not be used. -- 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, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues January 2013