It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

I am getting refresh failed with error code 414 and message - HTTP status 414 Request-URI Too Long]

Does this relate to https://community.atlassian.com/t5/Jira-questions/Getting-error-414-Request-URI-Too-Large/qaq-p/1035970 ?

If yes, where do i modify the files to increase the apache limits as suggested?

Help and suggestions are greatly appreciated.

My full error message is:

at java.lang.Thread.run(Thread.java:748)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:35)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:60)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:66)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:382)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJobWithRecoveryGuard(CaesiumSchedulerService.java:454)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:430)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:435)
at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:90)
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:106)
at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:134)
at com.atlassian.jira.plugin.devstatus.provider.DevSummaryUpdateJob.runJob(DevSummaryUpdateJob.java:85)
at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
at com.atlassian.jira.plugin.devstatus.provider.DefaultDevSummaryPollService.performPull(DefaultDevSummaryPollService.java:47)
at com.atlassian.jira.plugin.devstatus.provider.source.applink.PollResult$PollResultSuccess.fold(PollResult.java:51)
at com.atlassian.jira.plugin.devstatus.provider.DefaultDevSummaryPollService.lambda$performPull$1(DefaultDevSummaryPollService.java:51)
at com.atlassian.jira.plugin.devstatus.provider.DefaultDevSummaryPollService.handlePollingSuccess(DefaultDevSummaryPollService.java:69)
at com.atlassian.jira.plugin.devstatus.provider.DefaultCachingProviderHelper.refreshProvider(DefaultCachingProviderHelper.java:78)
com.atlassian.jira.plugin.devstatus.provider.DataProviderRefreshFailure: Data Provider [Id: 357391f5-9c2c-3951-800b-e301726eb575, Type: stash] refresh failed with error code 414 and message - HTTP status 414 Request-URI Too Long]
2019-11-03 20:08:48,548 Caesium-1-1 ERROR ServiceRunner [c.a.j.p.devstatus.provider.DefaultDevSummaryPollService] Refresh failure

1 answer

0 votes
Andy Heinzer Atlassian Team Tuesday

Hi Paul,

I see that you are getting an HTTP error code 414 error message in the logs of Jira.  It certainly seems like it is related to the KB referenced in that other thread of Long URLs Are Rejected by Apache with 'Request-URI Too Large' Error.

However that KB is specifically dealing with a Jira server that is using Apache as a reverse proxy in front of Jira to filter/redirect traffic to it.  In your case, it looks like Jira is seeing this error when trying to refresh data from Stash (aka Bitbucket).  So it might not be anything that you can configure from Jira's side at all.  Instead I suspect that this problem could be more on Bitbucket/Stash's configuration side instead.  Or possibly any reverse proxy that might sit in front of Bitbucket/Stash.  If that is the case, then the steps in that KB article could potentially still be applied here to make this work.

But from what we see here, it's not clear to me if your Bitbucket server is using an Apache proxy specifically or not.  It could be using that, or some other variety of proxy like nginx, or perhaps none at all.  I would recommend reaching out to your network administrator or the team that manages your Bitbucket site to better understand if they can help with this specific HTTP 414 error here.

Try this and let me know if you have any questions or concerns about this.

Andy

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Jira Cloud for Google Sheets: Automatically Refresh Your Data!

Remember that time you realized it was possible to refresh your Jira data in Google sheets with just one click? What if we told you that you can now get the latest data with no clicks at all?! Zero! ...

7,371 views 33 29
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you