The public JIRA has been spitting unusual (and some incomprehensible) Java error messages at people since this-morning. Sometimes it works and sometimes it doesn't. Rob Lanphier, Linden Lab's open source liaison says that Linden Lab have been working on the problem, but do not know what the cause is.

It seems to be happening less, at present, but there's been no further word that the issue has been isolated and repaired.

Sidewinder Linden has updated us on the status of the Havok 4.6 physics test on the Second Life Beta Grid (Aditi). Included is the news that Aditi has been updated today with a fresh code drop.

We've listed the changes below the fold, linked to their JIRA entries, where possible. The public JIRA has been having some difficulties this evening, however, so be prepared to be patient.

Starting around 1AM SLT (US Pacific), the Second Life Wiki, the Public JIRA and the Email-to-IM gateay were restored to service, however around the same time asset issues began cropping up with all the usual symptoms you expect to see from that (objects not appearing, assorted error messages when attaching or rezzing objects, all of that). These problems persisted until just approximately 2:40AM SLT.

At about 2:50AM SLT, map region-searches, global teleports and data-server requests all began failing. Some inworld scripts complained loudly and repeatedly. The problem cleared up approximately ten minutes later, but it looks like we're in for a potentially rough day.

When the public issue tracker is having an issue how do you report the issue?

Right now, the public JIRA system is not responding to logins. More specifically it's rejecting credentials with the message "The credentials you provided cannot be determined to be authentic."

It isn't clear at this point whether the issue is simply that the Second Life authentication service is overloaded by everyone throwing themselves into the grid all at once, or if the Heterogenous Grid updates have changed the authentication protocol/format. A case could be made for the latter, given the problems with the Support Portal this-afternoon.

Memory leaks aren't just a part of Linden Lab's own software, third-party components are prone to it too. In fact several of the worst memory leaks in the Second Life viewer were tracked down to third-party code.

In this case, however, there appear to be memory leaks that impact the public JIRA issue tracker (PJIRA) and the Second Life wiki. According to Rob Linden today, the leaks are causing severe slowdowns in both those systems every 72-96 hours. Until a solution is devised, both the Wiki and the PJIRA will be rebooted at 9PM SLT (US Pacific) every night.

Linden Lab announces its 2007 Innovation Awards, to acknowledge the work of open source contributors. Categories include Contributor of the Year, Best Contribution, Best Feature, Best Bug Hunter, Best Community Organizer.

Votes are being taken through JIRA, and Lindens and their family are not eligible. The full announcement is reproduced below the fold.

The public JIRA issue tracker used by Linden Lab has its share of difficulties. While most residents haven't ever heard of it, even fewer find it usable, though the folks who do have really been putting it through its paces. Aside from complaints about it's usability, the biggest issue with it has been actually logging in.

Logging in to the JIRA system failed from every part of it, except the top page, where it worked unreliably. That seems to be over. Issue WEB-47 has been fixed and JIRA logins are fast and snappy now, from any part of the JIRA system. So those of you who know how to use the system can get right on with things.