This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 165656 - bugzilla connection no longer functioning...
Summary: bugzilla connection no longer functioning...
Status: RESOLVED FIXED
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Bugzilla (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-20 21:57 UTC by mikee11
Modified: 2009-07-27 09:20 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mikee11 2009-05-20 21:57:48 UTC
Connecting to the bugzilla database to "find and issue" opens the new tab,
says "preparing query", but then times out after a couple of seconds, and never draws find-menu/table.
no errors, no logs.

This worked fine (and continues to works with 6.7beta). Did this get broken in response to "Issue 165012"?
(its not working with either LOCAL-Users or Not -- doesn't make a difference)
(I'm using HTTP authentication, and leaving the other authentication box blank -- worked in 6.7)
(validate option when setting up the bugzilla connection works as expected)

thanks,

 -- MikeE

Product Version: NetBeans IDE Dev (Build 200905200201)
Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b06
System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)
Userdir: C:\Documents and Settings\a235370\.netbeans\dev
Comment 1 mikee11 2009-05-20 22:13:12 UTC
hold off on this a bit... I think what I'm running into here is that version 6.7 with long user-names, and now going in
with local/valid user-names is confusing bugzilla... I'll validate that, perhaps this is not a netbeans 6.7beta+ problem.


(that being said, we need to get some sort of LOG/output screen so we can see the failures -- not just "preparing query"
and then nothing happening)

thanks guys
Comment 2 mikee11 2009-05-21 05:36:58 UTC
I cleaned up some old accounts in bugzilla, and restarted NB to get rid of some odd caching issues.

--

I can't put my finger on it, but something doesn't seem 100% right.
BugZilla does some odd things regarding case-sensitivity of accounts etc.

It appears (please confirm) that the NetBeans HTTP-authentication does a "tolower()" before passing up the user-ID, is
that true?

the svn commit seems to have worked, and then it threw an exception...

http://statistics.netbeans.org/analytics/exception.do?id=206212

Does the exception shed any light on what might be going on?
(I can also try to collect further info for you if the exception doesn't provide any insight)

thanks -- MikeE
Comment 3 Tomas Stupka 2009-05-21 16:46:39 UTC
> Connecting to the bugzilla database to "find and issue" opens the new tab,
> says "preparing query", but then times out after a couple of seconds, and never draws find-menu/table.
> no errors, no logs.
- times out means you have got an error dialog with a time out message?
- could you please attach your messages.log file?

to be honest - i'm a bit confused from your post:
- what exactly was the change since 6.7beta - you changed only your NetBeans build or did also your username and
authentication type (htttp, etc.) change?
- what exactly is your setup - how do you authenticate? http authentication, username or mail adress, etc. 
- what bugzilla version do you use?

- did you try to create a new account? did it help?

my guess is that the exception from Issue #165012 is something else

> It appears (please confirm) that the NetBeans HTTP-authentication does a "tolower()" before passing up the user-ID, is
> that true?
don't know anything about that - why do you ask?

thanks

Comment 4 Tomas Stupka 2009-05-21 16:50:09 UTC
one more thing - could you please give it a try with a new userdir?

thanks
Comment 5 mikee11 2009-05-21 17:09:55 UTC
I just grabbed this nightly and tried a commit + update bugzilla.

NO EXCEPTION! -- thats good.
It popped a screen saying that "bugzilla responded with..."  but the panel was BLANK. So its not clear what kind of
"issue" bugzilla had with the commit. (but its better than an exception)

When opening the bugzilla ticket, it showed it had been CLOSED and updated as part of the commit, so the functionality
appears to be working.

Product Version: NetBeans IDE Dev (Build 200905210201)
Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b06
System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)
Userdir: C:\Documents and Settings\a235370\.netbeans\dev
Comment 6 Tomas Stupka 2009-05-21 17:25:13 UTC
> It popped a screen saying that "bugzilla responded with..."  but the panel was BLANK
hm

what about find issues?
Comment 7 mikee11 2009-05-21 17:41:05 UTC
find issues seem to have cleared too.

I really think there was a problem where bugzilla was essentially confused being stuck between "fqdn-users" (with
6.7-beta) and the "local-users" option with the DEV builds.

Especially after the latest nightly, I'm not getting the exception anymore, although on 1 ticket I got the BLANK popup.
(possibly due to one one of those "mid-air collisions" since I had that issue "open" in another NetBeans tab.
(need a better debug capability there)

--

I did notice another issue that is likely related to this one though.

If I do a COMMIT and FIX/CLOSE a bugzilla issue (that is NOT OPEN in a NetBeans tab), the commit goes CLEAN, and the
BugZilla update goes without error or popup.  -- Then automatically the BugZilla ticket opens in a TAB (nice feature),
but it shows the ticket status from BEFORE the commit.  

EVEN THE refresh button does NOT seem to show the ticket in FIXED-state, with the updates from the commit.
I close the TAB, then go back into FIND_ISSUES, and now the ticket opens with the correct updates & state.

Can you confirm the above? (that a commit results in a STALE ticket being show, that doesn't refresh with the
refresh-button?)

thanks -- MikeE

Comment 8 Tomas Stupka 2009-05-22 13:09:20 UTC
ok. so what i see is actually three different issues:

1.) the originally reported problem - time out when opening find issues
2.) blank error msg when closing issue on commit 
3.) after closing an issue from commit dialog its opened in an unrefreshed state

1.) isn't reproducible in the last build - i will close this for now
2.) and 3.) filed separate issues for them - see issue #165805, #165807

thanks