Configuring JIRA Plug-in
Locked
 
|
Hello All, I was able to figure out a previous error I was getting when trying to get this plug-in up and working ("Caused by: java.lang.IllegalStateException: Unable to find filter 'All-Open-Issues' in JIRA"). I had to log in as my sonar user and make the filter one of their favorites following this instructions under "Managing your filters" from here. Please update the documentation on the JIRA plugin site to include this information.
I am now getting the following exception that I can't resolve: 14:46:42.139 INFO p.PhasesTimeProfiler - Sensor JIRA issues sensor... 14:46:42.279 WARN o.a.a.u.JavaUtils - Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled.
14:46:42.967 ERROR o.s.p.j.m.JiraSensor - Error accessing Jira web service, please verify the parameters com.atlassian.jira.rpc.soap.client.RemoteException: null
Any help is appreciated. Sincerely, Jason |
Re: Configuring JIRA Plug-in
|
On Wed, Jul 18, 2012 at 3:20 PM, Jason Hunt <[hidden email]> wrote:
Hi Jason,
Actually, the link to the Atlassian Wiki page that you give is already present in our documentation, maybe you've just missed it.
Can you give us the project and/or global settings you've set in Sonar for the JIRA plugin?
|
|
|
Global Settings:
UserName: sonar P/W: ******* Server URL: http://jira:8000 SOAP base URL: <blank> Project Settings:
JIRA project key: PBJ Username: sonar P/W: ******* Server URL: http://jira:8000 Filter name: All-Open-Issues SOAP base URL: <blank>
On Thu, Jul 19, 2012 at 12:56 AM, Fabrice Bellingard <[hidden email]> wrote:
|
Re: Configuring JIRA Plug-in
|
|
OK, nothing looks strange there.
Do you have the possibility to activate the request logging on JIRA (must have admin rights) to see what request is sent by Sonar and why you get this error? Best regards,
On Thu, Jul 19, 2012 at 3:32 PM, Jason Hunt <[hidden email]> wrote: Global Settings: |
|
|
Here are the logs... 192.168.10.181 o454x4996x1 sonar [20/Jul/2012:07:34:42 -0600] "POST http://jira:8080/rpc/soap/jirasoapservice-v2/login?in0=sonar&in1=**masked** HTTP/1.0" 200 472 0.2970 - "Axis/1.3" "r1az3u"
192.168.10.181 o454x4997x1 sonar [20/Jul/2012:07:34:43 -0600] "POST http://jira:8080/rpc/soap/jirasoapservice-v2/getPriorities?in0=**masked** HTTP/1.0" 200 3604 0.0470 - "Axis/1.3" "r1az3u"
192.168.10.181 o454x4998x1 sonar [20/Jul/2012:07:34:43 -0600] "POST http://jira:8080/rpc/soap/jirasoapservice-v2/getFavouriteFilters?in0=**masked** HTTP/1.0" 200 1235 0.1090 - "Axis/1.3" "r1az3u"
192.168.10.181 o454x4999x1 sonar [20/Jul/2012:07:34:43 -0600] "POST http://jira:8080/rpc/soap/jirasoapservice-v2/getIssuesFromFilter?in0=**masked**&in1=10130 HTTP/1.0" 500 13752 0.1720 - "Axis/1.3" "r1az3u"
Noticeably Different On Fri, Jul 20, 2012 at 12:30 AM, Fabrice Bellingard <[hidden email]> wrote: OK, nothing looks strange there. |
|
|
Based on that log, I would assume that the filter continues to be the problem. Still have no idea what to do to fix it though. The owner of the filter is set to my sonar account and the filter is marked as a favorite and it is shared with everyone.
Jason Hunt BSc Noticeably Different On Fri, Jul 20, 2012 at 7:38 AM, Jason Hunt <[hidden email]> wrote:
|
|
|
In investigating further, I thought it would be of note to remind that I am using JIRA
v4.4.4#664-r167664
Jason Hunt BSc Noticeably Different On Fri, Jul 20, 2012 at 7:39 AM, Jason Hunt <[hidden email]> wrote: Based on that log, I would assume that the filter continues to be the problem. Still have no idea what to do to fix it though. The owner of the filter is set to my sonar account and the filter is marked as a favorite and it is shared with everyone. |
|
|
Just to complicate things... I decided to upgrade JIRA to see if this would help resolve the issue. The results are the same. I am now running JIRA 5.1 (v5.1#768-sha1:38ad524).
Jason Hunt BSc Noticeably Different On Fri, Jul 20, 2012 at 7:54 AM, Jason Hunt <[hidden email]> wrote: In investigating further, I thought it would be of note to remind that I am using JIRA v4.4.4#664-r167664 |
Re: Configuring JIRA Plug-in
|
|
Yes, this definitely doesn't seem to be related to the version of JIRA you are using, but to some settings which prevent the SOAP request that asks for issues to complete.
You get a HTTP 500 (= internal server error) on http://jira:8080/rpc/soap/jirasoapservice-v2/getIssuesFromFilter?in0=**masked**&in1=10130, can you try to retrieve the result of this request to see if there's more info in it?
Best regards,
On Fri, Jul 20, 2012 at 4:31 PM, Jason Hunt <[hidden email]> wrote: Just to complicate things... I decided to upgrade JIRA to see if this would help resolve the issue. The results are the same. I am now running JIRA 5.1 (v5.1#768-sha1:38ad524). |
|
|
I guess that the part that's confusing. I have to assume that, since 2 of the commands were successful, there must be something specific to how the third one is being called. Not certain whether this helps, but here are the contents of the SOAP dump for the same failures:
192.168.10.181 o454x4996x1 sonar [20/Jul/2012:07:34:42 -0600] "POST http://jira:8080/rpc/soap/jirasoapservice-v2/login?in0=sonar&in1=**masked** HTTP/1.0" 200 472 0.2970 - "Axis/1.3" "r1az3u"
REQ : <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:login soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://soap.rpc.jira.atlassian.com"><in0 xsi:type="xsd:string">sonar</in0><in1 xsi:type="xsd:string">sonar</in1></ns1:login></soapenv:Body></soapenv:Envelope>
RES : <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:loginResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://soap.rpc.jira.atlassian.com"><loginReturn xsi:type="xsd:string">2M6jKpwluB</loginReturn></ns1:loginResponse></soapenv:Body></soapenv:Envelope>
192.168.10.181 o454x4997x1 sonar [20/Jul/2012:07:34:43 -0600] "POST http://jira:8080/rpc/soap/jirasoapservice-v2/getPriorities?in0=**masked** HTTP/1.0" 200 3604 0.0470 - "Axis/1.3" "r1az3u"
REQ : <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:getPriorities soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://soap.rpc.jira.atlassian.com"><in0 xsi:type="xsd:string">2M6jKpwluB</in0></ns1:getPriorities></soapenv:Body></soapenv:Envelope>
RES : <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:getPrioritiesResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://soap.rpc.jira.atlassian.com"><getPrioritiesReturn soapenc:arrayType="ns2:RemotePriority[5]" xsi:type="soapenc:Array" xmlns:ns2="http://beans.soap.rpc.jira.atlassian.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><getPrioritiesReturn href="#id0"/><getPrioritiesReturn href="#id1"/><getPrioritiesReturn href="#id2"/><getPrioritiesReturn href="#id3"/><getPrioritiesReturn href="#id4"/></getPrioritiesReturn></ns1:getPrioritiesResponse><multiRef id="id1" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns3:RemotePriority" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns3="http://beans.soap.rpc.jira.atlassian.com"><color xsi:type="xsd:string">#ff0000</color><description xsi:type="xsd:string">Crashes, loss of data, severe memory leak.</description><icon xsi:type="xsd:string">http://jira:8080/images/icons/priority_critical.gif</icon><id xsi:type="xsd:string">2</id><name xsi:type="xsd:string">Critical</name></multiRef><multiRef id="id4" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns4:RemotePriority" xmlns:ns4="http://beans.soap.rpc.jira.atlassian.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><color xsi:type="xsd:string">#003300</color><description xsi:type="xsd:string">Cosmetic problem like misspelt words or misaligned text.</description><icon xsi:type="xsd:string">http://jira:8080/images/icons/priority_trivial.gif</icon><id xsi:type="xsd:string">5</id><name xsi:type="xsd:string">Trivial</name></multiRef><multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns5:RemotePriority" xmlns:ns5="http://beans.soap.rpc.jira.atlassian.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><color xsi:type="xsd:string">#cc0000</color><description xsi:type="xsd:string">Blocks development and/or testing work, production could not run.</description><icon xsi:type="xsd:string">http://jira:8080/images/icons/priority_blocker.gif</icon><id xsi:type="xsd:string">1</id><name xsi:type="xsd:string">Blocker</name></multiRef><multiRef id="id2" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns6:RemotePriority" xmlns:ns6="http://beans.soap.rpc.jira.atlassian.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><color xsi:type="xsd:string">#009900</color><description xsi:type="xsd:string">Major loss of function.</description><icon xsi:type="xsd:string">http://jira:8080/images/icons/priority_major.gif</icon><id xsi:type="xsd:string">3</id><name xsi:type="xsd:string">Major</name></multiRef><multiRef id="id3" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns7:RemotePriority" xmlns:ns7="http://beans.soap.rpc.jira.atlassian.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><color xsi:type="xsd:string">#006600</color><description xsi:type="xsd:string">Minor loss of function, or other problem where easy workaround is present.</description><icon xsi:type="xsd:string">http://jira:8080/images/icons/priority_minor.gif</icon><id xsi:type="xsd:string">4</id><name xsi:type="xsd:string">Minor</name></multiRef></soapenv:Body></soapenv:Envelope>
192.168.10.181 o454x4998x1 sonar [20/Jul/2012:07:34:43 -0600] "POST http://jira:8080/rpc/soap/jirasoapservice-v2/getFavouriteFilters?in0=**masked** HTTP/1.0" 200 1235 0.1090 - "Axis/1.3" "r1az3u"
REQ : <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:getFavouriteFilters soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://soap.rpc.jira.atlassian.com"><in0 xsi:type="xsd:string">2M6jKpwluB</in0></ns1:getFavouriteFilters></soapenv:Body></soapenv:Envelope>
RES : <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:getFavouriteFiltersResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://soap.rpc.jira.atlassian.com"><getFavouriteFiltersReturn soapenc:arrayType="ns2:RemoteFilter[1]" xsi:type="soapenc:Array" xmlns:ns2="http://beans.soap.rpc.jira.atlassian.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><getFavouriteFiltersReturn href="#id0"/></getFavouriteFiltersReturn></ns1:getFavouriteFiltersResponse><multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns3:RemoteFilter" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns3="http://beans.soap.rpc.jira.atlassian.com"><author xsi:type="xsd:string">sonar</author><description xsi:type="xsd:string" xsi:nil="true"/><id xsi:type="xsd:string">10130</id><name xsi:type="xsd:string">All-Open-Issues</name><project xsi:type="xsd:string" xsi:nil="true"/><xml xsi:type="xsd:string" xsi:nil="true"/></multiRef></soapenv:Body></soapenv:Envelope>
I am assuming it's the **masked** part that you are interested in most. For that I may have to figure out how to use fiddler or something like it.
Jason Hunt BSc Noticeably Different On Fri, Jul 20, 2012 at 9:16 AM, Fabrice Bellingard <[hidden email]> wrote: Yes, this definitely doesn't seem to be related to the version of JIRA you are using, but to some settings which prevent the SOAP request that asks for issues to complete. |
|
|
One other thing I can think may be something that _could_ be causing a problem is that we have the greenhopper plug-in installed for JIRA, though I think that's a long-shot.
Jason Hunt BSc Noticeably Different On Fri, Jul 20, 2012 at 11:55 AM, Jason Hunt <[hidden email]> wrote: I guess that the part that's confusing. I have to assume that, since 2 of the commands were successful, there must be something specific to how the third one is being called. Not certain whether this helps, but here are the contents of the SOAP dump for the same failures: |
Re: Configuring JIRA Plug-in
|
|
Well, I can't really help you more on this Jason, I'm sorry :-/
Hopefully you'll be able to track down the problem! Best regards,
On Fri, Jul 20, 2012 at 8:05 PM, Jason Hunt <[hidden email]> wrote: One other thing I can think may be something that _could_ be causing a problem is that we have the greenhopper plug-in installed for JIRA, though I think that's a long-shot. |
|
Same problem here - and we use Greenhopper as well in case that might be a hint. If anyone knows how to further debug this, I'd appreciate hearing it!
--erik <quote author="Fabrice Bellingard-4"> Well, I can't really help you more on this Jason, I'm sorry :-/ Hopefully you'll be able to track down the problem! Best regards, *Fabrice BELLINGARD | SonarSource** *http://sonarsource.com On Fri, Jul 20, 2012 at 8:05 PM, Jason Hunt < [hidden email]> wrote: > One other thing I can think may be something that _could_ be causing a > problem is that we have the greenhopper plug-in installed for JIRA, though > I think that's a long-shot. > > Jason Hunt BSc > Noticeably Different > > |
|
We use Jira v4.4.3#663-r165197 with greenhopper (we run over https on Jira.) and Sonar 3.1
I have successfully tested that this works, both the manual review and the dashboard widget works for us. We needed to rebuild projects in order to get the widget to show, but thats stated in the documentation. In order to test that the soap api works you can utilize the Jira commandline tools https://marketplace.atlassian.com/6398 to verify urls and that you get answers, its also better on spitting out potential errors. If that works, this integration should work. Best regards David |
«
Return to Sonar user
|
1 view|%1 views
Loading...
| Powered by Nabble | Edit this page |