I am receiving the following error in JIRA: Error creating issue: Could not load FunctionProvider class

[neha kaul]

I have looked through all the solutions available but still and facing the issue.I thought it was due to one of the custom self made plugins that i created but i receive the same error even if the plugin is unistalled.

Please help..Im stuck!

[Theinvisibleman · Accepted solution]

Hi Neha,

I suspect that this is happening because your instance is expecting the presence of a certain plugin, (there might be settings or configurations that are only possible with the plugin) which you have uninstalled. Have you uninstalled any plugins recently?

Cheers,

Joe

[Florin Manaila]

com.opensymphony.user.User has been removed from Jira 5.0 upwards. Are you sure the plugin is compatible with Jira 5.1.3? Maybe you could contact the developer for further assistance.

[neha kaul]

Hi Manalia,

I have checked..The plugin is getting compiled..i checked with atlassian plugin checkup also!

Unfortunately the developer is not available..

[neha kaul]

hey thanx for the answer!

I had uninstalled a diiferent customized plugin.I uploaded the plugin But now i am receiving a different error..!!!!!:(

Error creating issue: Error creating bean with name 'com.gy.jira.workflow.function.AutoUpdateFunction': Initialization of bean failed; nested exception is java.lang.NoClassDefFoundError: com/opensymphony/user/User

The plugin is compiled for jira 5.1.3..still it is not working!

[C_ Faysal]

are there any changes in the workflow for the first step where an issue gets created?

maybe you try using jiras default workflow and see if the issue gets created as it is supposed to.

in that case you might have some validators or post functions in the Create step that are broke?

[neha kaul]

i was able to create issue using the default jira workflow..the workflow for this project is very different.

i checked all the conditions and validators in the workflow but nothing seems wrong.

how do i debug the workflow?????

[C_ Faysal]

In Logging & Profilng i suppose "com.atlassian.jira.workflow" should be set to DEBUG.

then do a "tail -f /path/of/your/catalina.out" while you simultaneously try creating an issue

[C_ Faysal]

i think it cannot be that conditions and validators are fine.

did you set loggin to DEBUG ?

maybe this will tell you more details about what is going wrong when you try to create a issue using your modded Workflow

[Florin Manaila]

I believe the logs you are looking for are in JIRA_HOME/logs/atlassian-jira.log

It's normal for the error to appear if the plugin is uninstalled. When you add a function to a workflow JIRA will save the name of the class so when you try to execute the transition it will attempt to load the specified class. If the plugin is uninstalled, it will show the error you specified, since the class is unloaded.

This can also be caused by some refactoring in the code like changing the name or the package of the class that implements FunctionProvider.

To start with, enable your plugin and check the Create Issue transition for conditions, validators or post-functions that will not load in the workflow screen (the one where you add more post-functions). If it cannot load any of them, it will show the class it was saved with. You can work your way to a solution from there.

HTH

[Naren]

It seems that post function for create issue in the workflow is missing. What are the logs generated in catalina.out.

[neha kaul]

Nov 14, 2012 11:33:51 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 191435 ms
Nov 14, 2012 12:21:44 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-8080"]
Nov 14, 2012 12:21:44 PM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
Nov 14, 2012 12:21:49 PM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-bio-8080"]
Nov 14, 2012 12:21:55 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Atlassian\JIRA\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;E:\app\Oracle11g\product\11.2.0\dbhome_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\TortoiseSVN\bin;E:\app\Stack2012\Server\win_b64\code\bin;C:\IFOR\WIN\BIN;C:\IFOR\WIN\BIN\EN_US;C:\Program Files (x86)\TortoiseSVN\bin;E:\app\Java\JDK\bin;E:\JIRAshared\atlassian-plugin-sdk-3.7\apache-maven\bin;E:\JIRAshared\atlassian-plugin-sdk-3.7\bin;C:\Users\nehaka\atlassian-plugin-sdk-4.0\apache-maven\bin;C:\Users\nehaka\atlassian-plugin-sdk-4.0\bin
Nov 14, 2012 12:21:55 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Nov 14, 2012 12:21:55 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 463 ms
Nov 14, 2012 12:21:55 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Nov 14, 2012 12:21:55 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.29
Nov 14, 2012 12:24:16 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Nov 14, 2012 12:24:16 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 141261 ms