February 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (BAM-26) Investigate deserialising custom activity types

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-26?page=com.atlassian.jira.plugin.sys... ] Gary Brown updated BAM-26: -------------------------- Fix Version/s: 1.0.0.M4 (was: 1.0.0.M5) > Investigate deserialising custom activity types > ----------------------------------------------- > > Key: BAM-26 > URL: https://issues.jboss.org/browse/BAM-26 > Project: Business Activity Monitoring > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M4 > > > Currently the JSON deserialization uses a type field to determine the ActivityType. > However this is only possible because the types have been registered against the ActivityType class using the Jackson JsonSubTypes annotation. > The benefit of the type field approach is that it is language independent (whereas @class is Java specific) and the amount of information in the json encoding is smaller (i.e. no package name). > However this approach means it is not easy for users to add new ActivityType derived classes, as the class would need to be added to the JsonSubTypes derived in the annotations for ActivityType class. > Another approach would be to have own type registry that custom activity type classes could also be registered with. > Need to investigate the possibilities and how the user's custom classes would be added to the AS7 installation easily. May need to update the org.overlord.bam module? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (BAM-120) Transaction scope around activity server store

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-120?page=com.atlassian.jira.plugin.sy... ] Gary Brown resolved BAM-120. ---------------------------- Resolution: Done > Transaction scope around activity server store > ---------------------------------------------- > > Key: BAM-120 > URL: https://issues.jboss.org/browse/BAM-120 > Project: Business Activity Monitoring > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M4 > > > Issue is that when using in-memory H2 db, the hibernate schema export is being performed in a transaction scope, which causes it to throw an exception. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (BAM-120) Transaction scope around activity server store

by Gary Brown (JIRA)

Gary Brown created BAM-120: ------------------------------ Summary: Transaction scope around activity server store Key: BAM-120 URL: https://issues.jboss.org/browse/BAM-120 Project: Business Activity Monitoring Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.M4 Issue is that when using in-memory H2 db, the hibernate schema export is being performed in a transaction scope, which causes it to throw an exception. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (BAM-119) Exception in call trace builder

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-119?page=com.atlassian.jira.plugin.sy... ] Gary Brown resolved BAM-119. ---------------------------- Resolution: Done Was due to activity units being accessed in a random order (via a map.values() method) when attempting to locate a RequestReceived match for a previous RequestSent activity. As the testcase used the same operation multiple times, the wrong RequestSent/Received activities were not being paired correctly. > Exception in call trace builder > ------------------------------- > > Key: BAM-119 > URL: https://issues.jboss.org/browse/BAM-119 > Project: Business Activity Monitoring > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M4 > > > The following exception occurs after the same transaction is performed multiple times (i.e. with the same id). > {noformat} > Caused by: java.util.EmptyStackException > at java.util.Stack.peek(Stack.java:102) [rt.jar:1.7.0_07] > at org.overlord.bam.call.trace.CallTraceProcessor$CTState.finalizeScope(CallTraceProcessor.java:791) [call-trace-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at org.overlord.bam.call.trace.CallTraceProcessor.processAU(CallTraceProcessor.java:285) [call-trace-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at org.overlord.bam.call.trace.CallTraceProcessor.processAU(CallTraceProcessor.java:270) [call-trace-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at org.overlord.bam.call.trace.CallTraceProcessor.processAUs(CallTraceProcessor.java:164) [call-trace-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at org.overlord.bam.call.trace.CallTraceProcessor.createCallTrace(CallTraceProcessor.java:92) [call-trace-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at org.overlord.bam.call.trace.rest.RESTCallTraceServer.getCallTrace(RESTCallTraceServer.java:141) [call-trace-rests-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] > at org.overlord.bam.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:155) [resteasy-jaxrs-2.3.2.Final.jar:] > at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:257) [resteasy-jaxrs-2.3.2.Final.jar:] > at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:222) [resteasy-jaxrs-2.3.2.Final.jar:] > at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:211) [resteasy-jaxrs-2.3.2.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:525) [resteasy-jaxrs-2.3.2.Final.jar:] > {noformat} > Need to find a way to deal with data that may be corrupt, or invalid, without blowing up. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (GADGETS-25) Add service definition in the Response Time Gadget.

by Jeff Yu (JIRA)

[ https://issues.jboss.org/browse/GADGETS-25?page=com.atlassian.jira.plugin... ] Jeff Yu updated GADGETS-25: --------------------------- Fix Version/s: 1.0.0.M5 (was: 1.0.0.M4) > Add service definition in the Response Time Gadget. > --------------------------------------------------- > > Key: GADGETS-25 > URL: https://issues.jboss.org/browse/GADGETS-25 > Project: Gadget Server and Gadgets > Issue Type: Feature Request > Components: RT-Gadget > Affects Versions: 1.0.0.M1 > Reporter: Jeff Yu > Assignee: Jeff Yu > Priority: Critical > Fix For: 1.0.0.M5 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (GADGETS-13) configuration for gadget server url.

by Jeff Yu (JIRA)

[ https://issues.jboss.org/browse/GADGETS-13?page=com.atlassian.jira.plugin... ] Jeff Yu resolved GADGETS-13. ---------------------------- Resolution: Done Now it is assumed that gadget-web and gadget-server are deployed on same server. For the gadgets, if it is deployed on the same server, it should use the ${server}/whatever-url-to-the-gadget, the ${server} variable will be replaced at the runtime with the gadget-server's url. If it is deployed remotely, then use the url. > configuration for gadget server url. > ------------------------------------ > > Key: GADGETS-13 > URL: https://issues.jboss.org/browse/GADGETS-13 > Project: Gadget Server and Gadgets > Issue Type: Feature Request > Components: Gadget Server > Affects Versions: 1.0.0.M1 > Reporter: Jeff Yu > Assignee: Jeff Yu > Fix For: 1.0.0.M4 > > > It is hard-coded as http://localhost:8080/gadget-server at the moment, need to be updated to be configurable. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (GADGETS-38) Gadget web exception when using port offset

by Jeff Yu (JIRA)

[ https://issues.jboss.org/browse/GADGETS-38?page=com.atlassian.jira.plugin... ] Jeff Yu resolved GADGETS-38. ---------------------------- Resolution: Done > Gadget web exception when using port offset > ------------------------------------------- > > Key: GADGETS-38 > URL: https://issues.jboss.org/browse/GADGETS-38 > Project: Gadget Server and Gadgets > Issue Type: Bug > Reporter: Gary Brown > Assignee: Jeff Yu > Fix For: 1.0.0.M4 > > Attachments: server.log > > > When trying to use the port offset during server startup, e.g. > ./standalone.sh -c standalone-full.xml -Djboss.socket.binding.port-offset=1000 > I get the following exception when attempting to add gadgets to the webpage (using http://localhost:9080/gadget-web). First sign is that the images for the bam gadgets are missing, and then when going back to the web page it is blank. > {noformat} > 14:20:54,395 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (http-localhost.localdomain-127.0.0.1-9080-6) HHH000230: Schema export complete > 14:21:19,045 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) org.apache.http.conn.HttpHostConnectException: Connection to http://localhost:8080 refused > 14:21:19,046 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:158) > 14:21:19,050 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:149) > 14:21:19,050 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121) > 14:21:19,050 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:573) > 14:21:19,051 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:425) > 14:21:19,051 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820) > 14:21:19,052 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754) > 14:21:19,052 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.jboss.resteasy.client.core.executors.ApacheHttpClient4Executor.execute(ApacheHttpClient4Executor.java:109) > 14:21:19,053 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.jboss.resteasy.core.interception.ClientExecutionContextImpl.proceed(ClientExecutionContextImpl.java:39) > 14:21:19,053 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor.execute(AcceptEncodingGZIPInterceptor.java:40) > 14:21:19,054 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.jboss.resteasy.core.interception.ClientExecutionContextImpl.proceed(ClientExecutionContextImpl.java:45) > 14:21:19,054 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.jboss.resteasy.client.ClientRequest.execute(ClientRequest.java:443) > 14:21:19,055 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.jboss.resteasy.client.ClientRequest.httpMethod(ClientRequest.java:674) > 14:21:19,055 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.jboss.resteasy.client.ClientRequest.post(ClientRequest.java:565) > 14:21:19,055 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.jboss.resteasy.client.ClientRequest.post(ClientRequest.java:570) > 14:21:19,056 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.jboss.resteasy.client.ClientRequest.postTarget(ClientRequest.java:577) > 14:21:19,056 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.overlord.gadgets.web.server.ShindigGadgetMetadataService.getMetadata(ShindigGadgetMetadataService.java:154) > 14:21:19,057 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.overlord.gadgets.web.server.ShindigGadgetMetadataService.getGadgetMetadata(ShindigGadgetMetadataService.java:47) > 14:21:19,057 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9080-6) at org.overlord.gadgets.web.server.UserController.getPageModels(UserController.java:126) > {noformat} > Possibly a related issue - when using a server with a port offset, when an existing server is also running at port 8080 (so manages to avoid this exception), the gadgets don't appear to issue the requests to the offset port. > I've issued a REST query to the server and it returns data - but when using the gadget web, the gadgets are blank. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (BAM-101) Switchyard auditor not handling fault responses correctly

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-101?page=com.atlassian.jira.plugin.sy... ] Gary Brown resolved BAM-101. ---------------------------- Resolution: Done > Switchyard auditor not handling fault responses correctly > --------------------------------------------------------- > > Key: BAM-101 > URL: https://issues.jboss.org/browse/BAM-101 > Project: Business Activity Monitoring > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M4 > > > When the switchyard order mgmt example is used - if an unknown item is specified, this causes a fault response from the inventory service. This is not being correctly represented as an activity event. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (BAM-87) Document using JPA activity store

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-87?page=com.atlassian.jira.plugin.sys... ] Gary Brown resolved BAM-87. --------------------------- Resolution: Done > Document using JPA activity store > --------------------------------- > > Key: BAM-87 > URL: https://issues.jboss.org/browse/BAM-87 > Project: Business Activity Monitoring > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M4 > > > Document how to configure (i.e. build custom version of war). -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (BAM-84) Package persistence specific files in distribution

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-84?page=com.atlassian.jira.plugin.sys... ] Gary Brown resolved BAM-84. --------------------------- Resolution: Done > Package persistence specific files in distribution > -------------------------------------------------- > > Key: BAM-84 > URL: https://issues.jboss.org/browse/BAM-84 > Project: Business Activity Monitoring > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Critical > Fix For: 1.0.0.M5 > > > When the JPA activity store is selected, then we need to deploy additional files (persistence.xml) and possibly datasource. > An example of the persistence.xml is found in the jpa module's test resources. Shows example of using hibernate ORM and OGM. -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues February 2013