Repository Settings Page Fails With "500 The call failed on the server"

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

When accessing the repositories page under Administration, the following message is displayed on screen:

An error has occurred
Error
Error calling server:com.google.gwt.user.client.rpc.StatusCodeException: 500 The call failed on the server; see server log for details Unknown.p6b(Unknown Source) Unknown.$8b(Unknown Source) Unknown.Xyb(Unknown Source) Unknown.zzb(Unknown Source) Unknown.<anonymous>(Unknown Source) Unknown.etb(Unknown Source) Unknown.htb(Unknown Source)

And in the logs:

2012-08-15 17:27:17,491 ERROR - Exception while dispatching incoming RPC call
com.google.gwt.user.server.rpc.UnexpectedException: Service method 'public abstract com.atlassian.fecru.gwt.admin.shared.repositories.FullRepositoryInfo com.atlassian.fecru.gwt.admin.client.RepositoryAdminRpcService.getFullRepositoryInfo(java.lang.String) throws com.atlassian.fecru.gwt.admin.shared.AuthorizationException,com.atlassian.fecru.gwt.admin.shared.OperationFailureException,com.atlassian.fecru.gwt.admin.shared.NoSuchRepositoryException' threw an unexpected exception: java.lang.IllegalArgumentException: 'https://jira.test.tes/test/${0} ' is invalid.
	at com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:385)
	at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:588)
	at com.atlassian.fecru.gwt.servlet.GwtRPCRoutingServlet.invokeRequest(GwtRPCRoutingServlet.java:73)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
	...
Caused by: java.lang.IllegalArgumentException: 'https://jira.test.tes/test//${0} ' is invalid.
	at com.atlassian.fisheye.spi.admin.data.SimpleLinker.setHref(SimpleLinker.java:59)
	at com.atlassian.fisheye.spi.admin.data.SimpleLinker.<init>(SimpleLinker.java:24)
	... 77 more
2012-08-15 17:27:17,552 ERROR - Error calling server:com.google.gwt.user.client.rpc.StatusCodeException: 500 The call failed on the server; see server log for details
        Unknown.p6b(Unknown Source)
...

Cause

The config.xml file has been corrupted by either a manual edit or another operation. Eg: Deleting a repository.

Most commonly it is caused by a wrong linker definition under the repository defaults resulting in the following error:

Caused by: java.lang.IllegalArgumentException: 'https://jira.test.tes/test/${0} ' is invalid.

In this case there is an extra space before the quote:

'https://jira.test.tes/test/${0} '

Resolution

  1. Stop Fisheye/Crucible.
  2. Edit FISHEYE_INST/config.xml and identify the "corrupted" section. If it's related to the linker section, locate:

    <linker>
    	<simple regex="[a-zA-Z]{2,}-\d+" href="https://jira.test.test/test/${0} " description="Jira"/>
    </linker> 

    And remove the extra space before the double quote.

  3. Save the changes and restart Fisheye/Crucible

Due to the complexity of the config.xml file structure, when not able to identify the "corrupted" part, please raise a support ticket at http://support.atlassian.com .

Last modified on Jul 31, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.