May 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-171) Offline activity logging and consolidation

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-171?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-171: ----------------------------- Fix Version/s: 1.1 (was: 1.0.0.M5) > Offline activity logging and consolidation > ------------------------------------------ > > Key: RTGOV-171 > URL: https://issues.jboss.org/browse/RTGOV-171 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.1 > > > Enable remote activity collection environments to support offline mode, where activity events will logged in a file/database. > Also provide import capability, to enable activities stored in such files to be loaded and submitted to an activity server/store. > For the clients, need way to switch between offline/online modes - when online, will use configured approach (e.g. REST) to communicate in near real-time with the 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

1
0
0 / 0

[JBoss JIRA] (RTGOV-179) Use Swyd ExchangeInitiatedEvent and ExchangeCompletionEvent

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-179?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-179: ----------------------------- Summary: Use Swyd ExchangeInitiatedEvent and ExchangeCompletionEvent (was: Investigate solution for obtaining provider information from camel ExchangeCreatedEvent) > Use Swyd ExchangeInitiatedEvent and ExchangeCompletionEvent > ----------------------------------------------------------- > > Key: RTGOV-179 > URL: https://issues.jboss.org/browse/RTGOV-179 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M5 > > > This event appears to be generated before the provider becomes established on the exchange. -- 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

1
0
0 / 0

[JBoss JIRA] (RTGOV-180) Service overview component ordering

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-180?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-180. ------------------------------ Resolution: Done > Service overview component ordering > ----------------------------------- > > Key: RTGOV-180 > URL: https://issues.jboss.org/browse/RTGOV-180 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M5 > > > The ordering of top level and child components appears random, so when refreshed it can generate a different order, and therefore even if the contents of the overview has not changed, the layout changes. > This is probably because the underlying information is built from iterating over maps - so just need to preserve the order in some way (probably alphabetically will be easiest). -- 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

1
0
0 / 0

[JBoss JIRA] (RTGOV-20) Define the BPM activity model components

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-20?page=com.atlassian.jira.plugin.s... ] Gary Brown resolved RTGOV-20. ----------------------------- Resolution: Done Initial model has been created to support the BPEL event collection. If further events (or changes) are required to support jBPM collection, then these can be added as part of that task. > Define the BPM activity model components > ---------------------------------------- > > Key: RTGOV-20 > URL: https://issues.jboss.org/browse/RTGOV-20 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Critical > Fix For: 1.0.0.M5 > > > Define a set of appropriate BPM related activity events to represent generic events that occur within a process engine. > These events will be required to describe the activities associated with the switchyard bpel (Riftsaw) and bpm (jBPM) components. > One of the objectives of these events should be to help trace the flow of information through a process. So when information is received (i.e. a received message), it would be useful to know the variable in which it is stored, and how subsequent variable values are derived from this initial information. Also expression evaluation for decision making could be useful. -- 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

1
0
0 / 0

[JBoss JIRA] (RTGOV-25) BPEL activity collector

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-25?page=com.atlassian.jira.plugin.s... ] Gary Brown resolved RTGOV-25. ----------------------------- Resolution: Done Initial integration has been done, although further work is required to link the BPEL events into the SOA events that scope the invocation in which the BPEL process is executed (RTGOV-181). > BPEL activity collector > ----------------------- > > Key: RTGOV-25 > URL: https://issues.jboss.org/browse/RTGOV-25 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Critical > Fix For: 1.0.0.M5 > > > Create an ActivityCollector to obtain information associated with the execution of a BPEL process. -- 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

1
0
0 / 0

[JBoss JIRA] (RTGOV-55) NPE when using H2 inmemory with JTA

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-55?page=com.atlassian.jira.plugin.s... ] Gary Brown resolved RTGOV-55. ----------------------------- Resolution: Done Fixed as part of Jeff's work on RTGOV-161. Thanks Jeff. > NPE when using H2 inmemory with JTA > ----------------------------------- > > Key: RTGOV-55 > URL: https://issues.jboss.org/browse/RTGOV-55 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Minor > Fix For: 1.0.0.M5 > > > When using H2 in-memory db configured to use the JTA transaction manager, we get a npe when creating the entity manager. > This was reported here: https://hibernate.onjira.com/browse/HHH-6522 > But was believed to be related to a lazy startup issue in AS7 (https://issues.jboss.org/browse/AS7-1864), but this does not seem to have resolved the problem in AS7.1.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, 7 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-187) Test for one way invocation (using camel JMS binding)

by Gary Brown (JIRA)

Gary Brown created RTGOV-187: -------------------------------- Summary: Test for one way invocation (using camel JMS binding) Key: RTGOV-187 URL: https://issues.jboss.org/browse/RTGOV-187 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.M5 Current exchange interceptor approach does not result in the activity unit scope being closed (and therefore submitting the activity unit to the server). Using the new event listener, the ExchangeCompletionEvent should be reported regardless of whether the exchange is one way or req/resp - so test that this does work correctly for the oneway/jms binding scenario. -- 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

1
0
0 / 0

[JBoss JIRA] (RTGOV-186) Hibernate exception when accessing call trace

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-186?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-186. ------------------------------ Resolution: Done > 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

1
0
0 / 0

[JBoss JIRA] (RTGOV-178) Unable to run arquillian tests against EAP 6.1

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-178?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-178. ------------------------------ Resolution: Done Fixed in branch - will merge shortly. Only solution was to revert the shrinkwrap and aether versions back to those used by AS7.1.1. > Unable to run arquillian tests against EAP 6.1 > ---------------------------------------------- > > Key: RTGOV-178 > URL: https://issues.jboss.org/browse/RTGOV-178 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M5 > > > After upgrading to EAP6.1 (RTGOV-177), was unable to run the arquillian tests under release/jbossas/tests due to shrinkwrap exception in maven dependency resolver. > Appears to be a known issue, but currently unsure of the best way forward: > https://issues.jboss.org/browse/SHRINKRES-44 -- 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

1
0
0 / 0

[JBoss JIRA] (SRAMP-184) Support sub-artifact sets in the S-RAMP query

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-184?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-184. --------------------------------- Resolution: Done > Support sub-artifact sets in the S-RAMP query > --------------------------------------------- > > Key: SRAMP-184 > URL: https://issues.jboss.org/browse/SRAMP-184 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.2.0 - Milestone 4 > > > Add support for sub-artifact sets, which would allow queries like this: > /s-ramp/wsdl/PortType[@name='OrderServicePT']/operation > This would return all of the Operation artifacts. This requires a 3-way join in JCR. -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues May 2013