Facing errors in logs

srrekanth February 4, 2013

we are facing following erros in logs

1)/rest/greenhopper/1.0/xboard/work/allData.json [greenhopper.service.rank.RankCustomFieldServiceImpl] The rank custom field with name Global Rank and id customfield_12082 shares a name with one or more other custom fields. In order to use a rank custom field its name must be uniqu

2)http-9881-26 ERROR anonymous 748x1387x35 - 172.21.54.53:2292,10.33.130.51 /secure/Dashboard.jspa [NoModule] There was an error getting a DBCP datasource.
java.lang.RuntimeException: Unable to obtain a connection from the underlying connection pool

can any one share why these eerors are occuring

4 answers

0 votes
srrekanth February 4, 2013

Hi Alex,

Yes there is one custom field created with this same name.If we delete this custom is there will be any impact on greenhopper?

0 votes
Alex Suslin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 4, 2013

delete or rename it, at least it will solve the 1st error log entry. If you manage to rename/delete the one that is not from greenhopper - no impact for it will be

0 votes
Alex Suslin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 4, 2013

check all your custom fields and be sure the name of your rank custom field is not the same as some other

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 4, 2013

The first one is exactly what it says on the tin - you've managed to configure two custom fields with the same name.

Rename one of them, it will be fine.

The second is a lot harder to track down, as it could be anything. I'd lean towards your database connection being badly configured, your system is coming under a very heavy load and running out of connections, or a plugin that's trying to directly read a database and is set up incorrectly. You'll need to read more of the log around that error, possibly increase logging in the "profiling and logging" page and maybe monitor the database and SQL being issued.

Suggest an answer

Log in or Sign up to answer