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 166507 - NPE at org.eclipse.mylyn.internal.jira.core.JiraClientFactory.getJiraClient(JiraClientFactory.java:68)
Summary: NPE at org.eclipse.mylyn.internal.jira.core.JiraClientFactory.getJiraClient(J...
Status: REOPENED
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Jira (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-03 17:18 UTC by _ gtzabari
Modified: 2010-10-11 13:02 UTC (History)
0 users

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 _ gtzabari 2009-06-03 17:18:58 UTC
Netbeans 6.7 rc1
JIRA 3.13.1-#333

When I try connecting to a HTTPS-based JIRA server I get: "JIRA RPC services are not enabled. Please contract your JIRA
administrator."

I checked, RPC services *are* enabled. I noticed that messages.log contains the following error:

SEVERE [org.netbeans.modules.jira.Jira]
java.lang.NullPointerException
	at org.eclipse.mylyn.internal.jira.core.JiraClientFactory.getJiraClient(JiraClientFactory.java:68)
	at org.netbeans.modules.jira.Jira.getClient(Jira.java:178)
	at org.netbeans.modules.jira.repository.JiraRepository$1ConfigurationCommand.execute(JiraRepository.java:431)
[catch] at org.netbeans.modules.jira.commands.JiraExecutor.execute(JiraExecutor.java:101)
	at org.netbeans.modules.jira.repository.JiraRepository.getConfigurationIntern(JiraRepository.java:438)
	at org.netbeans.modules.jira.repository.JiraRepository.getConfiguration(JiraRepository.java:407)
	at org.netbeans.modules.jira.commands.JiraExecutor.execute(JiraExecutor.java:96)
	at org.netbeans.modules.jira.commands.JiraExecutor.execute(JiraExecutor.java:88)
	at org.netbeans.modules.jira.repository.RepositoryController$4.run(RepositoryController.java:302)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:577)
	at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1030)
Comment 1 Tomas Stupka 2009-06-17 20:01:49 UTC
- what version is your jira server?
- could you please attach the whole messages.log file?

the mentioned error msg comes from the external jira connector library (mylyn) we use and is returned in case of a HTTP
Status-Code 503: Service Unavailable. Might be it is somehow related to another kind of connection problem you got.
Unfortunately, i'm afraid there is nothing we could fix at this point - http returned "Service Unavailable" and it looks
like there is a configuration problem on your side. Just in case - please ensure that your server is setup according to
http://confluence.atlassian.com/display/JIRA/JIRA+XML-RPC+Overview

thanks
Comment 2 _ gtzabari 2009-06-19 01:17:45 UTC
My mistake, "Accept remote API calls" was disabled.

Is it possible to make the error message more obvious?

When I read "JIRA RPC services are not enabled" I went into JIRA -> Administration -> Plugins -> "RPC JIRA Plugin" and
saw it was enabled so I blamed Netbeans for not working. It wasn't obvious that having this plugin enabled is in itself
sufficient for using RPC.

I suggest the following error message instead: "JIRA RPC services are not enabled. Please see
http://confluence.atlassian.com/display/JIRA/JIRA+XML-RPC+Overview#JIRAXML-RPCOverview-EnabletheRPCplugin for more
information."

1) The link should be clickable
2) Please make sure the text isn't cut off by the horizontal size of the dialog

Also, the fact that messages.log contains NullPointerException is in itself misleading. Shouldn't you log an INFO-level
message instead?
Comment 3 Tomas Stupka 2009-09-11 09:55:49 UTC
> 1) The link should be clickable
will add some more explicit info to the error msg. Linking some other vendors web pages sounds a bit risky to me, 
the url might change or become obsolete in the future. Maybe a link to our faq...

> Also, the fact that messages.log contains NullPointerException is in itself misleading. Shouldn't you log an INFO-level
> message instead?
A npe was thrown, from a library we use. Reason enough to log it. I suggest that in a case like this, when there is a
explicit error message, users focus on the message, instead of analyzing logs in the messages.log file.