Here are some comments that could be of use:
1) My initial thought is that this problem isn't on the server side. So, lets rule that out for now and focus on the client side.
2) You didn't answer my initial question about the sensor log. I would hope that the Jira Sensor would have a log file that looks something like the following (of course the Sensor Data Types should be Issue instead of what is shown here):
>> #> Activity [add, Open File, f:/java/cvs/hackyStdExt/src/org/hackystat/stdext/activity/analysis/activetime/ActiveTimeTrend.java]
Activity add OK (1 total)
#> Activity [statechange, f:/java/cvs/hackyStdExt/src/org/hackystat/stdext/activity/analysis/activetime/ActiveTimeTrend.java, 6418]
Activity statechange OK (initial file name and buffer size)
#> Activity [add, Open File, f:/java/cvs/hackyStdExt/src/org/hackystat/stdext/workspace/map/javamap/ProjectJavaClassWorkspaceMapManager.java]
Activity add OK (2 total)
Again, I think that something funny is going on in the Sensor and you can hopefully use the log file to help debug.
thanks, aaron
At 12:07 AM 11/14/2004 -1000, you wrote:
I have been able to consistently reproduce the error.
It appears that this occurs whenever I: (Assuming both Hackystat and Jira are running from the beginning) 1. Shutdown Hackystat 2. Initiate some Jira issue events, which generates offline sensor data. Let's say I do 2 events. 3. Bring Hackystat back up 4. Shutdown Jira and restart it 5. Again initiate a Jira issue event (this is necessary because the Jira sensor is "lazy" initialized) 6. When I look at sensor data on Hackystat webpage it shows an overwritten "tool" fields: in #2 I did 2 events, on the webpage it shows that the last 2 previous sensor data entries immediately before the newest entries just received were the ones overwritten.
Note: it does not matter whether "quickStart" or "freshStart" ant tasks are used.
Does anyone have comments on this?
Thanks, Burt
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:owner-hackystat-dev- > [EMAIL PROTECTED] On Behalf Of Aaron Kagawa > Sent: Saturday, November 13, 2004 12:05 PM > To: [EMAIL PROTECTED] > Subject: [HACKYSTAT-DEV-L:296] Re: Issue "tool" field getting overwritten > > Do you have a client side logging mechanism that prints out adding the > issues to the sensorshell before sending it off to the server? I believe > that would be useful in debugging this problem. > > thanks, aaron > > > At 10:02 AM 11/13/2004 -1000, you wrote: > >Hello Everyone, > > > >I'm testing the Jira sensor and I recently implemented an initialization > >mechanism that will fetch all pre-existing issues on Jira upon installing > >the sensor. > > > >For the most part it's looking good, the sensor data is showing up as it > >should on my localhost Hackystat server. > > > >The problem is that occasionally when I have initiated some Jira issue > >events and then click on the "Analyze" button in the "Sensor Data Links" > >section to verify that the data is being received correctly, some Issue > >sensor data entries show the "tool" field as "Sensor Shell" instead of > >"Jira". Here's another thing that is strange: it appears that the sensor > >data entries that say tool=Sensor Shell are actually older entries than > the > >new entries that were just sent by the sensor. Closer examination > revealed > >that some older sensor data entries had their tool field overwritten from > >"Jira" to "Sensor Shell". > > > >What could be causing this problem? Does it have anything to do with the > >fact that the Jira sensor invokes "send()" upon each issue event instead > of > >only once at server shutdown? The current implementation invokes the > setTool > >doCommand on each instance of SensorShell at creation so setting the tool > is > >not the problem. > > > >Thank you for your help! > >Burt
