Line 5899: Caused by: .GenericDataSourceException: SQL Exception while executing the following: UPDATE jiraschema.OS_CURRENTSTEP SET START_DATE=? WHERE ID=? (Transaction (Process ID 90) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Line 3869: Caused by: .GenericDataSourceException: Generic Entity Exception occurred in deleteAll (SQL Exception while executing the following: DELETE FROM jiraschema.customfieldvalue WHERE ID=? (Transaction (Process ID 57) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Line 3011: Caused by: .GenericDataSourceException: SQL Exception while executing the following: UPDATE jiraschema.jiraissue SET UPDATED=? WHERE ID=? (Transaction (Process ID 88) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. =true -Datlassian.standalone=JIRA .Bod圜ontentImpl.LIMIT_BUFFER=true =true =.InterningDocumentFactory -XX:-OmitStackTraceInFastThrow -XX:+ExplicitGCInvokesConcurrent -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintGCCause -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=20M -Xloggc:C:\Program Files\Atlassian\JIRA\logs\atlassian-jira-gc-%t.log -XX:InitialCodeCacheSize=32m -XX:ReservedCodeCacheSize=512m =C:\Program Files\Atlassian\JIRA -Dcatalina.base=C:\Program Files\Atlassian\JIRA =C:\Program Files\Atlassian\JIRA\endorsed -Djava.io.tmpdir=C:\Program Files\Atlassian\JIRA\temp = .file=C:\Program Files\Atlassian\JIRA\conf\logging.properties -Dfile.encoding=utf-8 =UTF-8 =true -XX:+UseG1GC exit abort -Xms12288m -Xmx12288m Tried the solution here with no success ( utm_medium = scheduledLogScan & utm_source = STP), Screenshot attachedĬomplete JVM Input Arguments: JVM Input Arguments CLONE THE DB (since the first one was used by another application too, Decysion - xxxxxxxxx, with no success.Ģ. The tests we have done are the following:ġ. It happens practically every day on many agents, we can't understand what it comes from. Often it is enough to repeat the action to make it successful, other times it is necessary to reload the ticket page and then repeat the action. "Deadlock errors in logs when running Jira server with SQL Server database" Often, when we update a ticket, we get the error:
Rerun the transaction.Īt .SQLServerException.makeFromDatabaseError(SQLServerException.java:259)Īt .SQLServerResultSet$FetchBuffer.nextRow(SQLServerResultSet.java:6388)Īt .SQLServerResultSet.fetchBufferNext(SQLServerResultSet.java:1647)Īt .SQLServerResultSet.next(SQLServerResultSet.java:988)Īt .(WrappedResultSet.java:2689)Īt .processResultSet(Loader.java:986)Īt .doQuery(Loader.java:948)Īt .doQueryAndInitializeNonLaz圜ollections(Loader.java:340)Īt .doList(Loader.Since June we have encountered an error that slows down our work. T14:55:13.373Z keycloak ERROR (default task-1) Uncaught server error: : : could not execute queryĪt .wrapLockException(ExceptionConverterImpl.java:277)Īt .convert(ExceptionConverterImpl.java:98)Īt .convert(ExceptionConverterImpl.java:181)Īt .AbstractProducedQuery.list(AbstractProducedQuery.java:1514)Īt .getResultList(Query.java:132)Īt .UserAdapter.getRoleMappings(UserAdapter.java:468)Īt .UserAdapter.hasRole(UserAdapter.java:420)Īt .antRole(UserAdapter.java:434)Īt .DefaultRoles.addDefaultRoles(DefaultRoles.java:48)Īt .JpaUserProvider.addUser(JpaUserProvider.java:107)Īt .JpaUserProvider.addUser(JpaUserProvider.java:127)Īt .addUser(UserStorageManager.java:151)Īt .(UserCacheSession.java:768)Īt .UsersManagementResourceProvider.createUser(UsersManagementResourceProvider.java:221)Īt .UsersManagementResourceProvider.registerUser(UsersManagementResourceProvider.java:138)Ĭaused by: : could not execute queryĪt .nvert(SQLStateConversionDelegate.java:123)Īt .nvert(StandardSQLExceptionConverter.java:42)Īt .(SqlExceptionHelper.java:113)Īt .doList(Loader.java:2692)Ĭaused by: .SQLServerException: Transaction (Process ID 54) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. T14:55:13.364Z keycloak ERROR (default task-1) Transaction (Process ID 54) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. When concurrent request queries are issued to Microsoft SQL Server, one request query succeeds, whereas the other fails with error message: T14:55:09.095Z keycloak INFO (default task-2) Creating user with XXX:RegisterUserRequest(username=rh1-1-0000, roles=null)
0 kommentar(er)
