Sending invitation mails causes a 500 response with error logs
Some exception stack was deleted due to length limitation
====================
Technical details
Log's referral number: c6b7a92e-2537-4739-afbe-805b742c770e
Cause
Referer URL: http://jira.sunftech.org/secure/admin/user/InviteUser!default.jspa
java.lang.reflect.UndeclaredThrowableException
java.lang.reflect.UndeclaredThrowableException
at com.sun.proxy.$Proxy1704.addInvitation(Unknown Source) [?:?]
at com.atlassian.jira.plugin.inviteuser.InvitationManagerImpl.sendInvitation(InvitationManagerImpl.java:55) [?:?]
at com.atlassian.jira.plugin.inviteuser.InvitationServiceImpl.sendInvitation(InvitationServiceImpl.java:76) [?:?]
at com.atlassian.jira.plugin.inviteuser.InviteUser.doExecute(InviteUser.java:147) [?:?]
at webwork.action.ActionSupport.execute(ActionSupport.java:165) [webwork-1.4-atlassian-30.jar:?]
at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63) [jira-api-8.5.4.jar:?]
at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39) [webwork-1.4-atlassian-30.jar:?]
at webwork.interceptor.NestedInterceptorChain.proceed(NestedInterceptorChain.java:31) [webwork-1.4-atlassian-30.jar:?]
at webwork.interceptor.ChainedInterceptor.intercept(ChainedInterceptor.java:16) [webwork-1.4-atlassian-30.jar:?]
at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:35) [webwork-1.4-atlassian-30.jar:?]
at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:225) [webwork-1.4-atlassian-30.jar:?]
at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:154) [webwork-1.4-atlassian-30.jar:?]
at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:138) [classes/:?]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:741) [servlet-api.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [catalina.jar:8.5.42]
... 273 more
Caused by: com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:
Database:
- name:MySQL
- version:5.7.26-log
- minor version:7
- major version:5
Driver:
- name:MySQL Connector Java
- version:mysql-connector-java-5.1.49 ( Revision: ad86f36e100e104cd926c6b81c8cab9565750116 )
com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '0' for key 'PRIMARY'
at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.create(EntityManagedActiveObjects.java:94) [?:?]
at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects.create(TenantAwareActiveObjects.java:266) [?:?]
at sun.reflect.GeneratedMethodAccessor1866.invoke(Unknown Source) [?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [?:1.8.0_202]
at java.lang.reflect.Method.invoke(Method.java:498) [?:1.8.0_202]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:343) [spring-aop-5.0.10.RELEASE.jar:5.0.10.RELEASE]
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(
...
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '0' for key 'PRIMARY'
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [?:1.8.0_202]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) [?:1.8.0_202]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [?:1.8.0_202]
at java.lang.reflect.Constructor.newInstance(Constructor.java:423) [?:1.8.0_202]
at com.mysql.jdbc.Util.handleNewInstance(Util.java:403) [mysql-connector-java-5.1.49.jar:5.1.49]
at com.mysql.jdbc.Util.getInstance(Util.java:386) [mysql-connector-java-5.1.49.jar:5.1.49]
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:936) [mysql-connector-java-5.1.49.jar:5.1.49]
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3933) [mysql-connector-java-5.1.49.jar:5.1.49]
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3869) [mysql-connector-java-5.1.49.jar:5.1.49]
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2524) [mysql-connector-java-5.1.49.jar:5.1.49]
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2675) [mysql-connector-java-5.1.49.jar:5.1.49]
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2465) [mysql-connector-java-5.1.49.jar:5.1.49]
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1915) [mysql-connector-java-5.1.49.jar:5.1.49]
... 301 more
Hello @Sayaka
Thank you for reaching out.
By the description of your logs, it seems you are facing the same problem outlined in this question where the parameter of sql_mode is set to NO_AUTO_VALUE_ON_ZERO, causing the error you are facing.
To fix this error, you can follow the steps below:
my.cnf
file (often named my.ini
on Windows operating systems or my.cnf on UNIX operating systems) in your MySQL server.Remove NO_AUTO_VALUE_ON_ZERO
from sql_mode.
For more details about the problem and the steps provided, you can check the documentation below:
Duplicate entry errors in logs after upgrading Jira server with MySQL database
Let us know if you have any questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.