Hi, I'm managing JIRA Server 6.4, Outgoing mail is currently disabled. when i tried to enable it, it just got stuck and nothing happened.
Below are the WARN message i'm seeing after hitting the "enabled outgoing mail" button
/secure/admin/OutgoingMailServers.jspa [com.atlassian.ozymandias.SafePluginPointAccess] Unable to run plugin code because of 'com.atlassian.activeobjects.internal.ActiveObjectsInitException - bundle [com.tuncaysenturk.jira.plugins.time-to-sla-plugin]'.
What could be the fix to the issue? Thanks!
Are you using the Time to SLA App? If you're able to disable in (in the Manage Add-ons area of the Admin interface,) I would do that and then try to enable mail. If that works, then enable the Time to SLA App. It sounds like you may be running an incompatible version of the Time to SLA App. If you're not using that App, I would suggest removing it.
Thanks for the reply Dave! You got it right. We found out that someone installed the Time to SLA App. Problem is that it throws error when disabling it. so i went ahead and delete it manually ( delete the plugins inside installed-plugins folder). It's already deleted but seems that it didn't fixed the issue. It is still stuck on the greyed button after hitting it. see image below.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great. I'm glad it was something simple. Sounds like it's time to audit who has admin access to your Jira and start removing people. :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This might help someone in the future
I came across this issue today, I have no plugins installed and since I couldn't find any solution, I settled using a workaround.
curl --location --request PUT 'https://BASEURL/rest/jira-mail-plugin/1.0/outgoingMail/config' \
--header 'Authorization: Basic ---------------------------' \
--header 'Content-Type: application/json' \
--data-raw '{
"enabled": "true"
}'
By manually sending the request that the button "Enable outgoing mail" sends, I was able to bypass any problems that could be hidden in the JS code.
This is basically treating the symptom and not the issue, I still don't know what caused this to happen in the first place, and I'm expecting this behavior to show up soon in the future, I'm still investigating the root cause.
Currently suspecting a misconfigured reverse proxy.
We found the solution to this,
As expected, it was from the reverse proxy.
We are using Big IP and it was blocking the PUT and DELETE methods, allowing them solved the issues we had encoutered.
Another sign of this is the inability to delete statuses in the workflow, it too was solved the same way.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.