[
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