Error occurred while Jira bulk operation 'Bulk edit bean unexpectedly null. Perhaps session was lost'

Mayur Ingale

Hi Atlassian team,

 

In Bulk issue operation I'm getting below error. I have checked the General configuration & the Base URL and my JIRA browser url is same. Also the session time out in web.xml is 7200 (that is 5 day).

My JIRA version is v6.3.15

>>>>>>>>>>>>>>>>

2015-06-22 09:06:36,914 ajp-bio-127.0.0.1-21762-exec-99 INFO mayingal 546x102760x2 d8rtv 10.76.185.9,10.76.185.9 /secure/views/bulkedit/BulkEditDetails.jspa [jira.issue

.fields.CustomFieldImpl] No relevant config found for Artifact Id for the issue null
2015-06-22 09:07:07,183 ajp-bio-127.0.0.1-21762-exec-89 WARN mayingal 547x102800x2 1bwq11h 10.76.185.9,10.76.185.9 /secure/views/bulkedit/BulkOperationFinish.jspa [acti
on.issue.bulkedit.BulkOperationProgress] Bulk edit bean unexpectedly null. Perhaps session was lost (e.g. when URL used is different to base URL in General Configuratio
n)?
2015-06-22 09:07:20,356 ajp-bio-127.0.0.1-21762-exec-94 WARN mayingal 547x102805x2 1bwq11h 10.76.185.9,10.76.185.9 /secure/views/bulkedit/BulkOperationFinish.jspa [acti
on.issue.bulkedit.BulkOperationProgress] Bulk edit bean unexpectedly null. Perhaps session was lost (e.g. when URL used is different to base URL in General Configuratio
n)?

<<<<<<<<<<<<<<<<

 

Please suggest me the resolution steps here on priority.

 

Thanks...

Mayur Ingale.

Mayur Ingale

I have solved this issue. In our JIRA instance, initially communication happens using AJP Connectors between Apache and Tomcat. Due to this AJP connector, there is a time-out issue while importing Bulk import of issues and during Project import.

It is suggested to use HTTP Connectors in place of AJP which are high-bandwidth candidates.

Initially this conversion of AJP connectors to HTTP connectors is performed in our staging JIRA environment, after which a smooth operation achieved with all sort of tasks including JIRA Bulk Import.