Error when clicking on JIGIT tab (Invocation of method 'renderActivityModule')

[Former user]

Hi,

We install the JIGIT plugin on JIRA (connecting to GitLab), and got the same error log as reported in this issue: https://bitbucket.org/dmitry_apanasevich/jira-jigit-plugin/issues/1/error-during-invocation-of-method-gethtml (Also attached as jigitError.txt)

For our case, this problem occurs for all issues. We have already downloaded the latest plugin. When we click Test Connectivity, it went OK, but have the following warning:

WARNING [http-nio-8082-exec-9] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI http://jiradev.mda.ca:8082/rest/jigit/1.0/repo/test, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected. 

That is similar to the comment in this issue: https://bitbucket.org/dmitry_apanasevich/jira-jigit-plugin/issues/15/jigit-plug-in-error-when-adding-gitlab

We do not have special character on the repository name/group name. We run the curl commands as suggested in the comment and all of them return 200 with proper JSON response. We check our GitLab instance for all the access log and there is no error return.

What other logs should we be looking for to help diagnose this problem? We are using: JIRA: v7.3.6 GitLab: v9.3.11-ee

[Jeannie Chan]

I apologize of not logging in before creating the issue. I am Jeannie.

[Dmitrii Apanasevich]

Hi Jeannie!

Well, the issue you've mentioned is not related to the problem of tab rendering. There was no need in using curl, actually.

But your attachment is very useful and clear, it contains all necessary information. There is a problem while interacting with JIRA database:

at com.atlassian.activeobjects.tx.TransactionalProxy.invoke(TransactionalProxy.java:33) ... 391 more Caused by: com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library: Database: - name:Microsoft SQL Server - version:11.00.6607 - minor version:0 - major version:11 Driver: - name:jTDS Type 4 JDBC Driver for MS SQL Server and Sybase - version:1.3.1 java.sql.SQLException: Incorrect syntax near the keyword 'commit'.

I'll try to fix it asap.

[Dmitrii Apanasevich]

Fixes #18: Error when clicking on JIGIT tab (Invocation of method 'renderActivityModule')

Changes reserved word as table alias to a correct one.

→ <<cset 625c29237506>>

[Dmitrii Apanasevich]

I've fixed the bug and released a new version: https://marketplace.atlassian.com/plugins/com.apanasevich.jira-jigit-plugin/versions#b1000100

Please, update add-on.

[Jeannie Chan]

Thank you very much for your quick turnaround! It works now :) Just another quick question. Is there plan to upgrade to use GitLab API v4 as v3 is no longer supported in the latest version?

[Dmitrii Apanasevich]

*Thank you very much for your quick turnaround! It works now :) *

You are welcome. I'll be grateful if you post a review here

Is there plan to upgrade to use GitLab API v4 as v3 is no longer supported in the latest version?

Could you give a link to GitLab release notes? As I can see API v3 is still working on https://gitlab.com (GitLab EE 10.2.3).

Actually, changes that needed to upgrade API up to v4 are trivial: string "v3" should be replaced with "v4" :) I've just tested this.

[Jeannie Chan]

This page: https://docs.gitlab.com/ce/api/v3_to_v4.html It mention that v3 will be removed from GitLab 9.5 or later (probably all new installs) It doesn't look like a huge change on the API side from the list.

I will post a review :)