Bug 165364 - java.net.SocketException: Connection reset
java.net.SocketException: Connection reset
Status: NEW
Product: connecteddeveloper
Classification: Unclassified
Component: Jira
6.x
All All
: P4 (vote)
: TBD
Assigned To: Tomas Stupka
issues@connecteddeveloper
http://statistics.netbeans.org/except...
EXCEPTIONS_REPORT
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-05-18 06:24 UTC by Jaromir Uhrik
Modified: 2009-07-27 09:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
:


Attachments
stacktrace (3.74 KB, text/plain)
2009-05-18 06:25 UTC, Jaromir Uhrik
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jaromir Uhrik 2009-05-18 06:24:53 UTC
Build: NetBeans IDE Dev (Build 090517)
VM: Java HotSpot(TM) Client VM, 1.5.0_16-133, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_16-b06-284
OS: Mac OS X, 10.5.7, i386

User Comments:
juhrik: after submit changes the exception appeared (issue type, changed status and resolution at once).



Stacktrace: 
org.eclipse.mylyn.internal.jira.core.service.JiraException: java.net.SocketException: Connection reset
        at org.eclipse.mylyn.internal.jira.core.service.web.JiraWebSession.doInSession(JiraWebSession.java:96)
        at org.eclipse.mylyn.internal.jira.core.service.web.rss.JiraRssClient.doInSession(JiraRssClient.java:46)
        at org.eclipse.mylyn.internal.jira.core.service.web.rss.JiraRssClient.findIssues(JiraRssClient.java:76)
        at org.eclipse.mylyn.internal.jira.core.service.JiraClient.findIssues(JiraClient.java:222)
        at org.eclipse.mylyn.internal.jira.core.service.JiraClient.search(JiraClient.java:453)
        at org.eclipse.mylyn.internal.jira.core.JiraRepositoryConnector.performQuery(JiraRepositoryConnector.java:133)
Comment 1 Jaromir Uhrik 2009-05-18 06:25:02 UTC
Created attachment 82279 [details]
stacktrace
Comment 2 Jaromir Uhrik 2009-05-18 10:14:16 UTC
Sorry but I cannot reproduce. I think it is not relevant what kind of action I have made. This was probably caused by
some problem with network - seems like this is not primarily the trouble of NetBeans.
Comment 3 Tomas Stupka 2009-06-17 20:02:46 UTC
however - we should handle it in a nicer way.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo