500 and traceback when inviting user

RR September 26, 2019

Hello,

 

We have just begun installing our pilot for JIRA.  Upon trying to invite our first users (after configuring and testing Outgoing e-mail settings), we are receiving a traceback when trying to use the "Invite Users" feature.

 

The administrator attempting to perform this task is met with a 500 "oops that's an error" message.  

 

This is on JIRA 8.4.1 running on Ubuntu 18.04 with MySQL 5.7

 

Upon reviewing the traceback and looking up the log referral ID in our logs, the traceback is incomplete, it ends with:

 

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185) [spring-aop-5.0.10.RELEASE.jar:5.0.10.RELEASE]
at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57) [?:?]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185) [spring-aop-5.0.10.RELEASE.jar:5.0.10.RELEASE]
at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:136) [spring-aop-5.0.10.RELEASE.jar:5.0.10.RELEASE]
at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:124) [spring-aop-5.0.10.RELEASE.jar:5.0.10.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185) [spring-aop-5.0.10.RELEASE.jar:5.0.10.RELEASE]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212) [spring-aop-5.0.10.RELEASE.jar:5.0.10.RELEASE]
at com.sun.proxy.$Proxy1689.create(Unknown Source) [?:?]
at com.atlassian.jira.plugin.inviteuser.ao.AOInvitationStoreImpl.addInvitation(AOInvitationStoreImpl.java:55) [?:?]
... 276 more

 

and another instance of the same issue:

 

legatingPreparedStatement.java:98) [commons-dbcp2-2.1.jar:2.1]
at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(De
legatingPreparedStatement.java:98) [commons-dbcp2-2.1.jar:2.1]
at com.atlassian.jira.ofbiz.sql.PreparedStatementWrapper.executeUpdate(P
reparedStatementWrapper.java:47) [classes/:?]
at com.atlassian.jira.diagnostic.connection.DiagnosticPreparedStatement.
lambda$executeUpdate$7(DiagnosticPreparedStatement.java:69) [classes/:?]
at com.atlassian.diagnostics.internal.platform.monitor.db.DefaultDatabas
eDiagnosticsCollector.recordExecutionTime(DefaultDatabaseDiagnosticsCollector.ja
va:69) [atlassian-diagnostics-platform-1.1.10.jar:?]
at com.atlassian.jira.diagnostic.connection.DatabaseDiagnosticsCollectorDelegate.recordExecutionTime(DatabaseDiagnosticsCollectorDelegate.java:55) [classes/:?]
at com.atlassian.jira.diagnostic.connection.DiagnosticPreparedStatement.executeUpdate(DiagnosticPreparedStatement.java:69) [classes/:?]
at net.java.ao.DatabaseProvider.executeInsertReturningKey(DatabaseProvider.java:1954) [?:?]
at net.java.ao.DatabaseProvider.insertReturningKey(DatabaseProvider.java:1868) [?:?]
at net.java.ao.EntityManager.create(EntityManager.java:366) [?:?]
at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.create(EntityManagedActiveObjects.java:92) [?:?]
... 299 more

1 answer

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 27, 2019

Hi RR,

Sorry to hear that you are having this problem within Jira when trying to invite users.  I can see that the stacktraces are calling a few different packages here in relation to the storage of this data in the database.

I suspect the problem could be in regards to a bad JDBC driver version, or an incorrectly setup database for Jira, but these are largely educated guesses with the information we have right now.  I would want to make sure that you followed the steps in Connecting Jira applications to MySQL 5.7 when setting up Jira here with MySQL.

If you have done these steps, then I'd be interested to take a closer look at the $JIRAHOME/log/atlassian-jira.log file from this system if possible.  This will have much more details about your environment, as well as a more complete set of stacktraces when this problem happens.   If you could share this file with us here, I'd be happy to take a closer look.  However you would need to use a filesharing service like Google Drive or Dropbox and then share the link here with us, as our Community site will not allow the upload of non-image attachments.

Cheers,

Andy

Suggest an answer

Log in or Sign up to answer