Eclipse Community Forums: EPP » changes in UDC in Helios?

Help

Home

Home » Archived » EPP » changes in UDC in Helios?(and some small statistics from UDC.)

Show: Today's Messages :: Show Polls :: Message Navigator

changes in UDC in Helios? [message #530033]

Wed, 28 April 2010 09:05

David

Messages: 88
Registered: July 2009

Member

Has there been any work done in UDC for the Helios release?

As i am looking into the Helios release now and i need to find out if something has happened with UDC. I saw the post about possible activites with the Mylyn capture but did that lead to anything?

Some small statistics from us:

I got 128646 rows of data uploaded since first of November .
36 unique individuals has uploaded data, i assume quite a lot has declined to upload data. We have 172 machines that has Eclipse 3.5 so not that good penetration.
Its recorded some 36696 errors where "Unhandled event loop exception" is on top with 9142 hits. I think this has to do with to little ram on the machines (I have seen this on my own machines a couple of times) Without UDC we would not have known.

best regards

David

[Updated on: Wed, 28 April 2010 11:04]

Report message to a moderator

Re: chages in UDC in Helios? [message #530431 is a reply to message #530033]

Thu, 29 April 2010 15:44

Wayne Beaton

Messages: 554
Registered: December 2017

Senior Member

There has been no significant work done on the UDC for Helios. Minor bug
fixes has been all we've had time for.

Can you post a stack trace for these errors? Or open a bug report? Or
point me to an existing bug report (if any)? I'm not sure how UDC might
be responsible for an "Unhandled event loop exception".

Thanks,

Wayne

David wrote:
> Has there been any work done in UDC for the Helios release?
>
> As i am looking into the Helios release now and i need to find out if
> something has happened with UDC. I saw the post about possible activites
> with the Mylyn capture but did that lead to anything?
>
> Some small statistics from us:
>
> I got 128646 rows of data uploaded since first of November .
> 36 unique individuals has uploaded data, i assume quite a lot has
> declined to upload data. We have 172 machines that has Eclipse 3.5 so
> not that good penetration.
> Its recorded some 36696 errors where "Unhandled event loop exception" is
> on top with 9142 hits. I think this has to do with to little ram on the
> machines (I have seen this on my own machines a couple of times)
> Without UDC we would not have known.
>
> best regards
>
> David
>
>
>
>

Report message to a moderator

Re: chages in UDC in Helios? [message #530563 is a reply to message #530431]

Fri, 30 April 2010 07:57

David

Messages: 88
Registered: July 2009

Member

ok, no idea in persuing updating it further then from my side.

When i said the top error is the top error that UDC has reported to the database from the users.

I haven't dug deeper in it yet, i need to get out the top user who has this fault and go to him and grab the log files.

So the UDC is not responsible for the top 1 error!

That was one of the enhancement that could be done to UDC though, grab the stack trace and attach it when it found an error. Now we just have the title of the stack trace and it can possibly come from multiple places. I looked into it and its possible but decided to not pursue it due to that i think it will be to intrusive for the developers, and that the stack trace is quite a lot of data for uploading, also new tables etc need to be created to hold the data.

If you have an solution to that request i am all ears, as it has helped us in many cases to get rid of bugs from our eclipse environment. In the beginning we had tons of errors from our version control plugins that we could fix due to that we analyzed the top error during the beta phase of introducing galileo.

Best regards

David

Report message to a moderator

Re: chages in UDC in Helios? [message #530770 is a reply to message #530563]

Fri, 30 April 2010 18:48

Wayne Beaton

Messages: 554
Registered: December 2017

Senior Member

We decided explicitly to not include the entire stack trace. We are
concerned about privacy and including the stack trace would require that
we do something clever to hide the names of classes and such that could
divulge too much information about the individual.

Wayne

David wrote:
> ok, no idea in persuing updating it further then from my side.
>
> When i said the top error is the top error that UDC has reported to the
> database from the users.
>
> I haven't dug deeper in it yet, i need to get out the top user who has
> this fault and go to him and grab the log files.
> So the UDC is not responsible for the top 1 error!
>
> That was one of the enhancement that could be done to UDC though, grab
> the stack trace and attach it when it found an error. Now we just have
> the title of the stack trace and it can possibly come from multiple
> places. I looked into it and its possible but decided to not pursue it
> due to that i think it will be to intrusive for the developers, and that
> the stack trace is quite a lot of data for uploading, also new tables
> etc need to be created to hold the data.
>
> If you have an solution to that request i am all ears, as it has helped
> us in many cases to get rid of bugs from our eclipse environment. In the
> beginning we had tons of errors from our version control plugins that we
> could fix due to that we analyzed the top error during the beta phase of
> introducing galileo.
>
> Best regards
>
> David
>

Report message to a moderator