You are viewing a plain text version of this content. The canonical link for it is here.

Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2022/05/09 02:02:00 UTC

[jira] [Closed] (JAMES-1608) Spool manager getting deadlocked

     [ https://issues.apache.org/jira/browse/JAMES-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benoit Tellier closed JAMES-1608.
---------------------------------
    Resolution: Won't Fix

James 2.3 is unmaintained, end of life.

> Spool manager getting deadlocked
> --------------------------------
>
>                 Key: JAMES-1608
>                 URL: https://issues.apache.org/jira/browse/JAMES-1608
>             Project: James Server
>          Issue Type: Bug
>          Components: James Core, SpoolManager &amp; Processors, UsersStore &amp; UsersRepository
>    Affects Versions: 2.3.2
>         Environment: Windows 2012 Server R2, SQL Server 2014 and Tomcat 7.0
>            Reporter: manasi
>            Priority: Major
>              Labels: performance
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> I am using the Jdbc Repository for the James mail server and it gets deadlocked. Have noticed that one of the update statement which is executed on a primary key field of "Varchar" locks the key in SQL 2014. When traced the SQL statements executed in SQL Server 2014, noticed that the column's data type is implicitly converted to nvarchar. So the update statement is trying to update the key in nvarchar format, though the data type is varchar.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org