Archive for November 2003
Activities
Still closing some of the cycle 1 stories. The link-flap story still had some problems. Soon we’ll be able to test Siebel and Precision implementations as well. We also need to find ways to create automatic tests for Micromuse and Precision related stories.
Ongoing work on planning, responsibilities, Sourceforge, etc.
Re: Proposed method sending internal events to netcool
We might have to rethink the name of the “TicketAction” attribute. TicketAction=”open” causing an event to by send to netcool doesn’t quite fit the expectation induced by the name. Propably shortening it to just “Action” would be better. But don’t change anything just yet, since this would break a lot of things.
Ticket opening problem solved
Tickets open again in the deployed environment in the development environment. The reason this did not work was a configuration error I made when reverting a change I made in the SocketGatewayListener, in order to test event resending.
Sourceforge and checkin
When you check-in source into CVS, a notepad window is displayed in which you can enter commit messages. Also a line called Tracker: is shown. Here you can enter the story number that this check-in relates to.
However, do not delete the Tracker: line
It will cause the source forge home page and commit logger pages to fail. It is OK not to enter a number, just don’t delete the line itself.
J to E site
I use the excite translation site at http://www.excite.co.jp/world/text. Paste the text on the left, choose the lower of the two options in the middle (the one that says�@��[���p, and press the button.
Oracle install
Succesfully installed Oracle 9i/windows, after removing all traces of the old, failed install from the lunaris machine. Had to log in in safe mode to remove one particularly sticky file. I also deleted all registry entries manually.
Meeting with Micromuse VP of Product Management
We met with Brent Compton and Kristin Jordahl of Micromuse yesterday. The purpose was for them to update Y on the Micromuse product roadmap. I spoke with Brent for a while on direct database connection and functionality overlap between products.
Sourceforge problem solved
Sourceforge works normally again now.
This problem is caused somehow by a faulty commit message. Exactly what the problem is, is still unknown to me. We narrowed it down to 4 messages (deleting these 4 solved the problem). I sent them to sourceforge so that they can tell us what the problem might be. The original commit messages that were deleted to solve this problem can in principle be restored by a script that reads the messages from cvs and repopulates the database records.
Sourceforge problem workaround
This is the same problem we had before. We “solved” it last time by deleting all the commitlog records in the sourceforge oracle database.
As a workaround, don’t go to the project homepage but go to tracker or document manager pages. Only the project homepage and the cvs commit log won’t work. The rest should be fine.
Switchflapping story not closed
I did not close the switch flapping story. See the comments on the tracker.
I did close the Clear Uninteresting Events (96) story. Stories 29 en 59 still remain
to be tested.