[
https://issues.apache.org/jira/browse/CXF-7374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018389#comment-16018389
]
Sergey Beryozkin commented on CXF-7374:
---------------------------------------
Actually, I got confused a bit. There appears to be an underlying issue with
JPA2 provider somewhere to do with saving the access tokens, will need to be
investigated as part of a sep issue
> Concurrent calls to refreshAccessToken() fails with SQL constraint violation
> ----------------------------------------------------------------------------
>
> Key: CXF-7374
> URL: https://issues.apache.org/jira/browse/CXF-7374
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS Security
> Affects Versions: 3.2.0
> Reporter: Viacheslav Gagara
> Assignee: Sergey Beryozkin
> Fix For: 3.2.0, 3.1.12
>
>
> When recycleRefreshTokens=false concurrent calls to refreshAccessToken()
> cause SQLException (2 accessTokens are created simultaneously and added to
> RefreshToken#accessTokens with the same index from different threads)
> {code}
> Batch entry 0 insert into RefreshToken_accessTokens (RefreshToken_tokenKey,
> accessTokens_ORDER, accessTokens) values ('fced31aaba6723ecc5956721e8f029f1',
> 1, '8c559d9f738f33a1b866e7172c9e5644') was aborted: ERROR: duplicate key
> value violates unique constraint "refreshtoken_accesstokens_pkey"
> Detail: Key (refreshtoken_tokenkey,
> accesstokens_order)=(fced31aaba6723ecc5956721e8f029f1, 1) already exists.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
