Jira ошибка 500

Symptoms

The following page appears when trying access to the Statuses page:

Or you can’t see any workflow listed when navigating to workflows page.

With the following Error when expanded:

Technical details
Log's referral number: 0b8255e1-5025-4373-bbbb-744ded4b9177

Cause
Referer URL: http://10.60.5.147:8624/jira624/secure/admin/ViewStatuses.jspa
com.google.template.soy.tofu.SoyTofuException: In template JIRA.Templates.Statuses.success: In 'foreach' command {foreach $status in $statuses}{call .statusRow}{param status: $status /}{/call}{/foreach}, the data reference does not resolve to a SoyListData.
com.google.template.soy.tofu.SoyTofuException: In template JIRA.Templates.Statuses.success: In 'foreach' command {foreach $status in $statuses}{call .statusRow}{param status: $status /}{/call}{/foreach}, the data reference does not resolve to a SoyListData.
	at com.google.template.soy.tofu.internal.BaseTofu.renderMainHelper(BaseTofu.java:341)
	at com.google.template.soy.tofu.internal.BaseTofu.renderMain(BaseTofu.java:300)
	at com.google.template.soy.tofu.internal.BaseTofu.access$100(BaseTofu.java:56)
	at com.google.template.soy.tofu.internal.BaseTofu$RendererImpl.render(BaseTofu.java:427)

Referral number can be used to search for the relevant log.

errorId=0b8255e1-5025-4373-bbbb-744ded4b9177

Diagnosis

Check in the atlassian-jira.log whether the following error is written:

Caused by: com.atlassian.cache.CacheException: java.lang.IllegalStateException: There are more than one draft workflows associated with the workflow named '<workflow name>'
	at com.atlassian.cache.memory.DelegatingCache.get(DelegatingCache.java:67)
	at com.atlassian.jira.workflow.CachingDraftWorkflowStore.getDraftWorkflow(CachingDraftWorkflowStore.java:55)
	at com.atlassian.jira.workflow.OSWorkflowManager.getDraftWorkflow(OSWorkflowManager.java:249)

or 

Caused by: com.atlassian.cache.CacheException: java.lang.IllegalStateException: There are more than one workflows associated with '<workflow name>' in the database!
	at com.atlassian.cache.memory.DelegatingCache$DelegatingLoadingCache.get(DelegatingCache.java:270)
	at com.atlassian.jira.workflow.CachingWorkflowDescriptorStore.getWorkflow(CachingWorkflowDescriptorStore.java:68)
	at com.atlassian.jira.workflow.JiraWorkflowFactory.getWorkflow(JiraWorkflowFactory.java:37)
	at com.opensymphony.workflow.config.DefaultConfiguration.getWorkflow(DefaultConfiguration.java:89)

or 

2016-04-07 15:35:49,564 http-nio-8711-exec-20 ERROR <username> 935x813x1 r6dcz1 172.18.66.246 /secure/admin/workflows/ListWorkflows.jspa [webwork.util.ValueStack] query="inactiveWorkflows" {[id="inactiveWorkflows" type="8" values=""]}
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 

Cause

1) The JIRA application database has a duplicate record for a draft workflow. The problem is likely to occur when there are multiple Administrators who are creating workflow drafts of the same workflow at roughly the same time.

JRA-40009
—
Getting issue details…
STATUS

1.1) The Jira application has a corrupted draft workflow(only one). We cannot open the original workflow for editing.

2) The JIRA application database has a duplicate record for a workflow. 

3) There are orphaned scheme references (e.g. workflow, permission, notification) in the nodeassociation JIRA table referencing a deleted project. This produces a NullPointerException when the workflow list is populated. The following SQL query can be used to diagnose the problem:

select * from nodeassociation where SOURCE_NODE_ENTITY='Project' AND SOURCE_NODE_ID not in (select ID from project);

4) Workflow contains duplicate actions

Always back up your data before performing any modifications to the database. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.

Resolution 1 — Remove duplicate draft workflows

We will find draft workflows with identical names and then delete one.  Look at the jiradraftworkflows.descriptor column on the duplicate draft rows to determine which one to delete.  

1. Run the following SQL query on the database (to identify the drafts with more than one entry):

   SELECT count(*), parentname FROM jiradraftworkflows group by parentname having count(*) > 1;

2. Delete one of the Id which have the same parentname.

   SELECT id, parentname from jiradraftworkflows;

   (i) This would list the 2 rows on *jiradraftworkflows* DB table having same *workflowname*. In the next step, please delete one of the rows from the above output so that duplication is resolved.

   DELETE from jiradraftworkflows where id = <chosen_id_with_duplicated_parentname>;

3. Restart JIRA.
4. Run a re-index of your instance.

Resolution 1.1 — Remove corrupted draft workflow

We will use the following steps to identify corrupted draft workflow records and delete them.  The administrator will decide what constitutes a bad record.

Run the following SQL query on the database (to identify all the draft workflows):

select id,parentname from jiradraftworkflows ;

Try to open each of the workflows for editing and notice if you face any issue while opening any.

If you face an error while opening a workflow for editing, you will need to follow these steps: 

1. Shutdown JIRA (as the draft workflow XML could be cached in memory).

2. Run the following SQL:

   -- Confirm the draft workflow ID being deleted (should return 1 and only 1 row)
   SELECT id, parentname from jiradraftworkflows where id = <workflow_id_with_error>;
   
   -- Run the delete
   DELETE from jiradraftworkflows where id = <workflow_id_with_error>;
   
   -- You should get 1 row affected
   
   -- Check that the workflow is now gone (should return 0 rows)
   SELECT id, parentname from jiradraftworkflows where id = <workflow_id_with_error>;
   
   -- You may need to run COMMIT if your SQL editor does not do auto-commit
   commit;

3. Start JIRA and check that you can now click on JIRA Administration » Issues » Statuses without errors.

Resolution 2 — Remove workflows records with the same name

We will find workflow records with the same case-insensitive names, then remove one of them and verify we have the correct workflow mapped to the project’s workflow scheme. 

1. Run the following SQL query on the database to identify workflow records with duplicate names:

   SELECT count(*), workflowname FROM jiraworkflows group by workflowname having count(*) > 1;

2. Remove one of the duplicate rows:

   SELECT id,workflowname FROM jiraworkflows;

   (i) This would list the 2 rows on *jiraworkflows* DB table having same *workflowname*. In the next step, please delete one of the rows from the above output so that duplication is resolved.

   DELETE from jiraworkflows where id = <chosen_id_with_duplicated_workflowname>;

3. Restart JIRA.
4. Run a re-index of your instance.

Resolution 3 — Remove orphaned schemes

We will find and remove schemes to projects that do not exist.

1. Run the following SQL query on the JIRA database to identify orphaned schemes associated to a deleted JIRA project. If the following query returns a result, then you are likely affected by this:

   Diagnosis: orphaned rows in the nodeassociation table

   select * from nodeassociation where SOURCE_NODE_ENTITY='Project' AND SOURCE_NODE_ID not in (select ID from project);

2. Run the following query to delete these orphaned schemes for non-existent projects: 

   Remove orphaned rows in the nodeassociation table

   delete from nodeassociation where SOURCE_NODE_ENTITY='Project' AND SOURCE_NODE_ID not in (select ID from project);

3. Restart JIRA.
4. Run a re-index of your instance.

Resolution 4 — Remove duplicate workflow actions

Resolution 5 — Resolve problem using ScriptRunner

This is a third party solution, not supported by Atlassian.

In case you are using ScriptRunner plugin, then issue can be resolved by executing below code in ScriptRunner console:

import com.atlassian.jira.component.ComponentAccessor 
def workflowManager = ComponentAccessor.workflowManager 
workflowManager.getConfiguration().removeWorkflow('NAME OF WORKFLOW')

Navigator produces a 500 error page in JIRA and you have no clue why?

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Let’s take a look at how our Support Team recently helped a customer when their Issue Navigator produced a 500 error page in JIRA.

Why does Issue Navigator Produce a 500 error page in JIRA?

The 500 error page often appears after modifying an agile simplified workflow for a specific project by deleting it rather than recreating one manually and associating it with the Project that still had issues. This results in no access to the Issue Navigator as well as the 500 error page.

For instance, you will see a warning similar to the one below:

"Generated by JIRA Agile version 6.6.0-D20140904T040435. This workflow is managed internally by JIRA Agile. 
Do not manually modify this workflow."

Although we do not have access to the cloud instance’s logs, we can still observe the following in the atlassian-jira.log file:

2021-11-10 11:12:13.794451500 Sep 10, 2014 11:12:13 AM org.apache.catalina.core.ApplicationDispatcher invoke

2021-11-10 11:12:13.794453500 SEVERE: Servlet.service() for servlet action threw exception

2021-11-10 11:12:13.794453500 java.lang.NullPointerException

An unknown exception occurred executing Validator com.atlassian.jira.workflow.SkippableValidator@130d55: root cause: java.lang.NullPointerException

What to do if Navigator produces a 500 error page in JIRA

According to our Support Engineers, this error is due to deleting the simplified workflow without moving all the associated issues to the project to a new project. Furthermore, the status of these issues is stuck in the “To Do, In Progress, Done” status.

However, the statuses no longer exist after deleting the project key association. Thereby, resulting in the 500 error page.

Fortunately, our team of skilled Support Techs has come up with an innovative solution that involves bulk editing the status of these issues.

1. First, we will head to View All Projects under Projects.
2. Then, we have to select the project causing the error.
3. Next, we will select Issues in the Summary section.
4. Finally, we have to click All Issues in order to be able to perform a bulk edit.

[Need for a solution to another query? We are just a click away.]

Conclusion

In essence, the skilled Support Engineers at Bobcares demonstrated what to do when the Issue Navigator produces a 500 error page in JIRA.

Created a new Jira issue and added it to a variable, then i tried to add a attachment to the newly created Jira issue where i get a «WARNING: Jira returned HTTP error 500 — InternalServerError»

Expected Behavior

File to be added to the new jira issue.

Current Behavior

«WARNING: Jira returned HTTP error 500 — InternalServerError»

Possible Solution

Steps to Reproduce (for bugs)

1. $newissue = New-JiraIssue -Project $Project -IssueType $IssueType -Summary $Summary -Description $Description
2. Add-JiraIssueAttachment -Issue $newissue -FilePath «C:tempout.txt»

Context

Your Environment

Get-Module JiraPS -ListAvailable | select version
$PSVersionTable

Get-Module JiraPS -ListAvailable | select version
Version

2.7.0

$PSVersionTable
Name Value

PSVersion 5.1.17134.48
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
BuildVersion 10.0.17134.48
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

You usually need the email + password or username + password. Or when using API Token, you would use your Atlassian username + API token.

It sounds strange… when your colleage is able to use same jira instance to connect with you should not have any issues either.
Unless your Jira account has some restrictions in the permissions, which i dont assume atm as the plain connection test does not require any special permissions.

Sry that i am not that helpful. Its just quite impossible for me to look into your user account jira issue as an outsider.
The only known issues i am aware of are possible interferences when using Google Login with Jira (https://github.com/ljay79/jira-tools/tree/master#known-issues) or when the Jira instance itself is within a local network. Both appear not to apply to you.

On top of this.
When the credentials are wrong, Jira would quit the connection usually with an error code 401 (for unauthorized). While you expiriencing an error 500 (internal server error).

Are you or your colleage able to test the jira api connection with curl if i instruct you on the api call?