Hello Aaron, Thank you for your input.
I've closely monitored the Jira log file and now my earlier observations may have been incorrect. Currently what is known is that ALL offline data has its tool field sent as "Sensor Shell" instead of "Jira". Here is an excerpt of the log file that is commented: /** @@@ A log session for both Jira and Hackystat running */ Hackystat Version: 6.3.1114 (November 14 2004 12:05:59) SensorShell started at: 11/14/2004 13:34:10 Type 'help' for a list of commands. Host: http://localhost:8080/ is available and key is valid. Defined shell command: Issue Defined shell command: Perf Defined shell command: FileMetric Defined shell command: ReviewIssue Defined shell command: Activity Defined shell command: Cli Defined shell command: ReviewActivity Defined shell command: Coverage Defined shell command: BuffTrans Defined shell command: Commit Defined shell command: UnitTest Defined shell command: Build AutoSend not enabled. Checking for offline data to recover. No offline data found. #> Issue [setTool, Jira] setTool OK #> Issue [add, Task1 for proj2, Task, Critical, ISSUE_WORKSTARTED, , project=10010,status=In Progress] Issue add OK (1) #> send Sending sensor data (11/14 13:34:11) Ping: Ping OK (contacted server http://localhost:8080/ with valid key.) AutoSend: AutoSend OK ('send' command ignored) Issue: Send OK (1 entries) Perf: Send OK (No entries to send.) FileMetric: Send OK (No entries to send.) ReviewIssue: Send OK (No entries to send.) Activity: Send OK (No entries to send.) Cli: Send OK (No entries to send.) ReviewActivity: Send OK (No entries to send.) Coverage: Send OK (No entries to send.) BuffTrans: Send OK (No entries to send.) Commit: Send OK (No entries to send.) UnitTest: Send OK (No entries to send.) Build: Send OK (No entries to send.) >> #> Issue [add, Task1 for proj2, Task, Critical, ISSUE_WORKSTOPPED, , project=10010,status=Open] Issue add OK (1) #> send Sending sensor data (11/14 13:35:05) Ping: Ping OK (contacted server http://localhost:8080/ with valid key.) AutoSend: AutoSend OK ('send' command ignored) Issue: Send OK (1 entries) Perf: Send OK (No entries to send.) FileMetric: Send OK (No entries to send.) ReviewIssue: Send OK (No entries to send.) Activity: Send OK (No entries to send.) Cli: Send OK (No entries to send.) ReviewActivity: Send OK (No entries to send.) Coverage: Send OK (No entries to send.) BuffTrans: Send OK (No entries to send.) Commit: Send OK (No entries to send.) UnitTest: Send OK (No entries to send.) Build: Send OK (No entries to send.) >> #> Issue [add, Task1 for proj2, Task, Critical, ISSUE_WORKSTARTED, , project=10010,status=In Progress] Issue add OK (1) #> send /** @@@ At this point I took my localhost Hackystat server offline */ Server not available. Storing commands offline. >> #> Issue [add, Task1 for proj2, Task, Critical, ISSUE_WORKSTOPPED, , project=10010,status=Open] Issue add OK (2) #> send Server not available. Storing commands offline. >> /** @@@ At this point I brought the Hackystat server online again and restarted Jira */ Hackystat Version: 6.3.1114 (November 14 2004 12:05:59) SensorShell started at: 11/14/2004 13:37:15 Type 'help' for a list of commands. Host: http://localhost:8080/ is available and key is valid. Defined shell command: Issue Defined shell command: Perf Defined shell command: FileMetric Defined shell command: ReviewIssue Defined shell command: Activity Defined shell command: Cli Defined shell command: ReviewActivity Defined shell command: Coverage Defined shell command: BuffTrans Defined shell command: Commit Defined shell command: UnitTest Defined shell command: Build AutoSend not enabled. Checking for offline data to recover. #> Issue [add, Task1 for proj2, Task, Critical, ISSUE_WORKSTARTED, , project=10010,status=In Progress] Issue add OK (1) #> Issue [add, Task1 for proj2, Task, Critical, ISSUE_WORKSTOPPED, , project=10010,status=Open] Issue add OK (2) Summary of recovered offline data: 11/14/2004 13:35:49#Issue#add#Task1 for proj2#Task#Critical#ISSUE_WORKSTARTED##project=10010,status=In Progress 11/14/2004 13:35:53#Issue#add#Task1 for proj2#Task#Critical#ISSUE_WORKSTOPPED##project=10010,status=Open /** @@@ All the offline data sent has its tool as "Sensor Shell" instead of "Jira" */ #> send Sending sensor data (11/14 13:37:15) Ping: Ping OK (contacted server http://localhost:8080/ with valid key.) AutoSend: AutoSend OK ('send' command ignored) Issue: Send OK (2 entries) Perf: Send OK (No entries to send.) FileMetric: Send OK (No entries to send.) ReviewIssue: Send OK (No entries to send.) Activity: Send OK (No entries to send.) Cli: Send OK (No entries to send.) ReviewActivity: Send OK (No entries to send.) Coverage: Send OK (No entries to send.) BuffTrans: Send OK (No entries to send.) Commit: Send OK (No entries to send.) UnitTest: Send OK (No entries to send.) Build: Send OK (No entries to send.) >> #> Issue [setTool, Jira] setTool OK #> Issue [add, Task1 for proj2, Task, Critical, ISSUE_WORKSTARTED, , project=10010,status=In Progress] Issue add OK (1) #> send Sending sensor data (11/14 13:37:15) Ping: Ping OK (contacted server http://localhost:8080/ with valid key.) AutoSend: AutoSend OK ('send' command ignored) Issue: Send OK (1 entries) Perf: Send OK (No entries to send.) FileMetric: Send OK (No entries to send.) ReviewIssue: Send OK (No entries to send.) Activity: Send OK (No entries to send.) Cli: Send OK (No entries to send.) ReviewActivity: Send OK (No entries to send.) Coverage: Send OK (No entries to send.) BuffTrans: Send OK (No entries to send.) Commit: Send OK (No entries to send.) UnitTest: Send OK (No entries to send.) Build: Send OK (No entries to send.) >> > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:owner-hackystat-dev- > [EMAIL PROTECTED] On Behalf Of Aaron Kagawa > Sent: Sunday, November 14, 2004 3:30 AM > To: [EMAIL PROTECTED] > Subject: [HACKYSTAT-DEV-L:304] Re: Issue "tool" field getting overwritten > > 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/activet > ime/ActiveTimeTrend.java] > Activity add OK (1 total) > #> Activity [statechange, > f:/java/cvs/hackyStdExt/src/org/hackystat/stdext/activity/analysis/activet > ime/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/Pro > jectJavaClassWorkspaceMapManager.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
