> upper links on the top component tab
not sure what links in what tab you refer to

describing the io exception and attaching the messages.log could be also usefull

I/O error occurred while communicating with http://netbeans.org/bugzilla.

Socket exception: Connection reset

messages.log contains no messages regarding this.

> upper links on the top component tab
not sure what links in what tab you refer to

are the "missing links" the only thing which is wrong with "the tab"? any chance to attach a screenshot?

> messages.log contains no messages regarding this.
thanks for analyzing the messages log, but i still would like to ask you to attach it to the issue. there still might be other useful information for us you aren't aware of. 

thanks

The links:

Add to Tasklist | Refresh Issue | Reload Attributes | Show in Browser

that are shown when a bug is normally displayed.

so its the issue editor where the links are missing

i still need the messages.log file

A Step by Step Guide to filing a useful bug report for the NetBeans Community
http://wiki.netbeans.org/IssueReportingGuidelines

Created attachment 95796 [details]
messages.log

Attached messages.log. Now you can waste your time checking it has nothing that helps you there.

Acting like you are doing will just cause users not to collaborate. Please be less arrogant, especially when you are talking to someone who has been helping NB for years.

(In reply to comment #5)
> The links:
> 
> Add to Tasklist | Refresh Issue | Reload Attributes | Show in Browser
> 
> that are shown when a bug is normally displayed.

Well, I think that what Michael means is when an exception is thrown when trying to open an issue inside the IDE, for example an IO exception, at least the links should be shown allowing to user for example reload the issue or open it in the browser. Personally I agree this is really useful.

> at least the links should be shown allowing to user for example reload the 
> issue or open it in the browser. Personally I agree this is really useful.
of course, i agree with that

> Attached messages.log. Now you can waste your time checking it has nothing > that helps you there
now, after i have seen the log file i agree that there is nothing about the error indeed. I have no problem to admit that. As a matter of fact, now i also know what build you use and that there are no other warnings or errors from other modules which might have their part in the problem and you might have overseen them. 

in the mean time i've tried to reproduce the problem by forcing an io.exception from where i though it might have happen but without success. The issue dialog was properly rendered anyway, so i would need more detailed log info from you. 
please run netbeans with the switches 
-J-Dorg.netbeans.modules.bugzilla.Bugzilla.level=-1
-J-Dorg.netbeans.modules.bugracking.BugtrackingManager.level=-1

and attach you log after you are able to reproduce the problem.

thanks again

Well, it is an random problem since in the truth it happens when bz hangs or is out. To reproduce it you can just do these steps:
1. open Exception Reporter and click at Show My Issues. You can see the exceptions you sent previously;
2. Turn off your internet connection, for example removing your lan cable;
3. Click at any Issue (second column) and you will see an IO error.

Well, in this point you should be able to reproduce the problem since the issue tab is closed and you need to click in the link again. Indeed when you face this problem when clicking at bug link when an issue is just sent, sometimes the link go away since another bug was already sent and the page have just be replaced.

> 2. Turn off your internet connection, for example removing your lan cable;
i've tried that already with no effect

Michel's steps to reproduce work for me. Strange they don't work for you, Tomas. I will attach the log produced with the flags on.

Created attachment 95836 [details]
messages.log with flags turned on

Now it contains the exception and other information you need.

i've tried a few more times but still without success. 

now - what exactly did i do:
- steps 1.) - 3.)
- after the io error i've turned the connection on and clicked the same issue - it was opened and the links were visible.

did i get right or do i still miss something from your description?

and more - I've even changed my font settings to default and played with the topcomponent arrangement,  if that could have, for whatever reason, some effect 
.

could you attach a screenshot from your whole IDE so i could try with the same layout as you have?

Ok, Tomas, from your description you were able to reproduce the issue; it seems you didn't understand what I meant though.

Current behaviour: when an I/O error occurs when clicking on the issue, a dialog is shown and once the users clicks on it, the tab for the issue is closed.

Expected behaviour: when the error occurs, the dialog is shown and after the user clicks on it the tab *keeps being shown* with the upper links available (Add to Tasklist | Refresh Issue | Reload Attributes | Show in Browser).

Justification/use case: I'm getting several slowness reports on my IDE. When I'm done doing my main work on the IDE and hit Build, for instance, I start submiting all of these, one by one. Once the Exception reporter brings the result for the submission, I click on the bug if it exists and start submitting a new one. So, I no longer have the link for the bug. That's why it's important that I can either try to load the issue again from the tab or open it in the browser.

I hope it is clear now.

ah! so it's not only that the links aren't shown in the issue top component, it's that the whole TC you miss. I think i've got it now.

>  So, I no longer have the link for the bug. 
the links for all issues reported by you are easily available via the "Show my issues" button and sorter in the order the relevant exception reports were created. 

few more things:
1.) the problem as described is a situation caused by a slow responsiveness of our bugzilla (which should be fixed on the server) and doesn't seem to be a typical scenario anyway
2.) this isn't a defect and everything works as designed. To fix as suggested would:
2A.) ask for deeper changes in the actual bugracking infrastructure and bring only minor additional value - issues are still accessible without big effort from the exception reporter window
2B.) probably not everybody will be happy about an empty window taking up place in the editor just to work as a container for an action which does something that already is available via "Show my issues":
- to eventually reopen the issue again
- "Open in browser" makes no sense if the connection would be really down
- "reload attributes" makes no sense at all. 

invalid or wontfix, not really sure about the resolution ...

xdesign on cc

> 1.) the problem as described is a situation caused by a slow responsiveness of
> our bugzilla (which should be fixed on the server) and doesn't seem to be a
> typical scenario anyway

This happens to me several times a day.

> 2B.) probably not everybody will be happy about an empty window taking up place
> in the editor just to work as a container for an action which does something
> that already is available via "Show my issues":

Not quite true. If you submit several issues on a row and try to open all of them asynchronously, by the time you get the I/O error you don't know which issue you were trying to open in the first place and there might 5 or 6 submitted in this session which you have checked. So it is a major inconvenience.

> - "Open in browser" makes no sense if the connection would be really down

Every time this happened to me, bz wasn't down. In fact, its web version was working pretty fast, btw.

Would you please reconsider?

As a netbeans UI responsible, I was approached and requested opinion on this issue. 

While I understand that for the reporter, this particular situation was an inconvenience, I do believe that the kind of workflow this was encountered in is not common and and even when this happens the workaround is easily available. 

So I suggest to keep closed and focus on other issues still existing and affecting significant amount of our users instead. We can always reopen if we encounter duplicates in the future.