Caesium-1-3 ERROR ServiceRunner ...Error while refreshing rate limiting settings:

Question

Hi,

JIRA 13.3 - trying to examine some log file errors.  What's it doing and how to fix the error?

This is in a JIRAService stdout .  Presumably some automatic JIRA housekeeping looking at the times of it.

2021-02-07 23:06:44,037+0000 Caesium-1-3 ERROR ServiceRunner [c.a.r.internal.settings.SettingsReloaderJob] Error while refreshing rate limiting settings:
com.atlassian.jira.transaction.TransactionRuntimeException: org.ofbiz.core.entity.GenericTransactionException: Error occurred while starting transaction. (Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
)

Sue Bridges_o1cif3 · Answer

Hi,

I think everything is OK from the Oracle side, but the Listener can be a pain.  How can I check what connect descriptor it's using is as that's the key here?

I am also interested as to why JIRA would be performing this operation anyway.  Checking what Rate Limiting is, it relates to JIRA Service Centre which we don't have.  I can't set Rate Limiting under System (I'd turn it off if I could I think).

Thanks

Sue

Nic Brough -Adaptavist- · Answer

Ok, this suggests a transient error with your TNS service - for some reason Jira could not reach it at that time, or it did not respond.

Sue Bridges_o1cif3 · Answer

Hi Nic,

Apologies, Jira Server 8.13.3.

Jira uses the Oracle database and it is up and running, which is why I am asking the question.  Jira works fine against it.  I am also interested in what the housekeeping task actually is.

Thanks

Sue