Results of builds of deleted plans appear in dashboard. Cannot be deleted. Give exception when accessed

Hello,

While experimenting with some new build plans, we created and deleted some plans after performing some test builds. We did not delete all the history and test results for these plans before we deleted them.

The problem is that now the dashboard shows lots of these old experimental build results and we cannot find a way to delete them.

Furthermore, trying to access any of these gives the following exception.

How can we delete these old build results/history?

EXCEPTION:

Internal server error

Go to...

Site Homepage

A system error has occurred - our apologies!

Please create a problem report on our support system at http://support.atlassian.com with the following information:

a description of your problem and what you were doing at the time it occurred

cut & paste the error and system information found below

attach the atlassian-bamboo.log log file found in your application home.

We will respond as promptly as possible.

Thank you!

Version: 3.3.3

Build: 2719

Build Date: 14 Nov 2011

Request Information:

Request URL: https://(URL REMOVED FOR PRIVACY REASONS)/500.action

Scheme: https

Server: (SERVER REMOVED FOR PRIVACY REASONS)

Port: 443

URI: /500.action

Context Path:

Servlet Path: /500.action

Path Info:

Query String:

Stack Trace:

javax.servlet.ServletException: Could not find latest build for HDMAINBUILD-BISMUTHBASE

at com.atlassian.bamboo.filter.UrlRewriteFilter.getLatestUrl(UrlRewriteFilter.java:307)

at com.atlassian.bamboo.filter.UrlRewriteFilter.parseUrl(UrlRewriteFilter.java:199)

at com.atlassian.bamboo.filter.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:161)

at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1322)

at com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:46)

at com.atlassian.plugin.servlet.filter.ServletFilterModuleContainerFilter.doFilter(ServletFilterModuleContainerFilter.java:77)

at com.atlassian.plugin.servlet.filter.ServletFilterModuleContainerFilter.doFilter(ServletFilterModuleContainerFilter.java:63)

at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1322)

at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96)

at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:75)

at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1322)

at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:473)

at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)

at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:516)

at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)

at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:921)

at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:403)

at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:184)

at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:856)

at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)

at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:114)

at org.eclipse.jetty.server.Server.handle(Server.java:352)

at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:596)

at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:1052)

at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:590)

at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:212)

at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:426)

at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:510)

at org.eclipse.jetty.io.nio.SelectChannelEndPoint.access$000(SelectChannelEndPoint.java:34)

at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:40)

at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:450)

at java.lang.Thread.run(Thread.java:662)

1 answer

1 accepted

0 votes
Accepted answer

I would suggest reporting the issue to Atlassian Support.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Statuspage

194 years of downtime: looking back on incident data from 2018

Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the  104 years logged in 2017 , and we aren’t even through December yet....

49 views 1 5
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you