Found an existing issue for the jboss try below local change as per your module  

<cache-container name="web" default-cache="passivation" module="org.wildfly.clustering.web.infinispan">
    <local-cache name="passivation">
        <locking acquire-timeout="60000" isolation="READ_COMMITTED" striping="false"/>
        <!-- change here from REPEATABLE_READ to READ_COMMITTED -->
        <transaction locking="OPTIMISTIC" mode="BATCH"/>
        <!-- change here from PESSIMISTIC to OPTIMISTIC -->
        <file-store passivation="true" purge="false"/>
    </local-cache>
    <local-cache name="persistent">
        <locking acquire-timeout="60000" isolation="READ_COMMITTED" striping="false"/>
        <!-- change here from REPEATABLE_READ to READ_COMMITTED -->
        <transaction locking="OPTIMISTIC" mode="BATCH"/>
        <!-- change here from PESSIMISTIC to OPTIMISTIC -->
        <file-store passivation="false" purge="false"/>
    </local-cache>
</cache-container>
<cache-container name="ejb" aliases="sfsb" default-cache="passivation" module="org.wildfly.clustering.ejb.infinispan">
    <local-cache name="passivation">
        <locking acquire-timeout="60000" isolation="READ_COMMITTED" striping="false"/>
        <!-- change here from REPEATABLE_READ to READ_COMMITTED -->
        <transaction locking="OPTIMISTIC" mode="BATCH"/>
        <!-- change here from PESSIMISTIC to OPTIMISTIC -->
        <file-store passivation="true" purge="false"/>
    </local-cache>
    <local-cache name="persistent">
        <locking acquire-timeout="60000" isolation="READ_COMMITTED" striping="false"/>
        <!-- change here from REPEATABLE_READ to READ_COMMITTED -->
        <transaction locking="OPTIMISTIC" mode="BATCH"/>
        <!-- change here from PESSIMISTIC to OPTIMISTIC -->
        <file-store passivation="false" purge="false"/>
    </local-cache>
</cache-container>

Root Cause :

A defect or configuration issue in the operating environment is identified as root cause. By default transaction locking in JBoss EAP 7 is "PESSIMISTIC" and locking isolation is "REPEATABLE_READ" , which means that "Pessimistic locking of cache entries effectively ensures that only a single client on a single node ever accesses a given session at any given time." Set the transaction locking as "OPTIMISTIC" and locking isolation as "READ_COMMITTED" so that it will able to serve concurrent requests within the same HTTP session.

You can also have a look into below article

https://stackoverflow.com/questions/35711423/how-to-fix-unable-to-acquire-lock-after-15-seconds-errors-in-wildfly

Thanks,

Arun