[jira] [Commented] (TILES-599) stuck thread on hashmap
[ https://issues.apache.org/jira/browse/TILES-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16608455#comment-16608455 ] ASF GitHub Bot commented on TILES-599: -- Github user shakeelabbas1 closed the pull request at: https://github.com/apache/tiles/pull/16 > stuck thread on hashmap > --- > > Key: TILES-599 > URL: https://issues.apache.org/jira/browse/TILES-599 > Project: Tiles > Issue Type: Bug > Components: tiles-core >Reporter: Shakeel Abbas >Priority: Critical > Fix For: 3.1.x, 3.0.x > > > Thread stuck for Apache tiles BasicPreparerFactory. This happens in > concurrent environments. > Root cause and solution discussed here. > https://stackoverflow.com/questions/38761222/hashmap-hang-in-concurrent-access > Part of Stack trace here as below > ", which is more than the configured time (StuckThreadMaxTime) of "600" > seconds. Stack trace: > !java.util.HashMap.getEntry(HashMap.java:466) > !java.util.HashMap.containsKey(HashMap.java:450) > !org.apache.tiles.preparer.BasicPreparerFactory.getPreparer(BasicPrepare > rFactory.java:70) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TILES-599) stuck thread on hashmap
[ https://issues.apache.org/jira/browse/TILES-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16600530#comment-16600530 ] ASF GitHub Bot commented on TILES-599: -- GitHub user shakeelabbas1 opened a pull request: https://github.com/apache/tiles/pull/16 TILES-599 using ConcurrentHashMap https://issues.apache.org/jira/browse/TILES-599 You can merge this pull request into a Git repository by running: $ git pull https://github.com/shakeelabbas1/tiles TILES_3_0_X Alternatively you can review and apply these changes as the patch at: https://github.com/apache/tiles/pull/16.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #16 commit d1bda5413a4d1481702c7d99a6cff3b838026418 Author: shakeel.abbas Date: 2018-09-02T06:52:36Z TILES-599 using ConcurrentHashMap > stuck thread on hashmap > --- > > Key: TILES-599 > URL: https://issues.apache.org/jira/browse/TILES-599 > Project: Tiles > Issue Type: Bug > Components: tiles-core >Reporter: Shakeel Abbas >Priority: Critical > Fix For: 3.1.x, 3.0.x > > > Thread stuck for Apache tiles BasicPreparerFactory. This happens in > concurrent environments. > Root cause and solution discussed here. > https://stackoverflow.com/questions/38761222/hashmap-hang-in-concurrent-access > Part of Stack trace here as below > ", which is more than the configured time (StuckThreadMaxTime) of "600" > seconds. Stack trace: > !java.util.HashMap.getEntry(HashMap.java:466) > !java.util.HashMap.containsKey(HashMap.java:450) > !org.apache.tiles.preparer.BasicPreparerFactory.getPreparer(BasicPrepare > rFactory.java:70) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TILES-599) stuck thread on hashmap
[ https://issues.apache.org/jira/browse/TILES-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16599739#comment-16599739 ] ASF GitHub Bot commented on TILES-599: -- Github user asfgit closed the pull request at: https://github.com/apache/tiles/pull/15 > stuck thread on hashmap > --- > > Key: TILES-599 > URL: https://issues.apache.org/jira/browse/TILES-599 > Project: Tiles > Issue Type: Bug > Components: tiles-core >Reporter: Shakeel Abbas >Priority: Critical > Fix For: 3.1.x, 3.0.x > > > Thread stuck for Apache tiles BasicPreparerFactory. This happens in > concurrent environments. > Root cause and solution discussed here. > https://stackoverflow.com/questions/38761222/hashmap-hang-in-concurrent-access > Part of Stack trace here as below > ", which is more than the configured time (StuckThreadMaxTime) of "600" > seconds. Stack trace: > !java.util.HashMap.getEntry(HashMap.java:466) > !java.util.HashMap.containsKey(HashMap.java:450) > !org.apache.tiles.preparer.BasicPreparerFactory.getPreparer(BasicPrepare > rFactory.java:70) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TILES-599) stuck thread on hashmap
[ https://issues.apache.org/jira/browse/TILES-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16599733#comment-16599733 ] Nicolas Le Bas commented on TILES-599: -- Looks good to me, thanks Shakeel! We won't be releasing any further version of tiles 2, though. Not sure about tiles 3, see [https://mail-archives.apache.org/mod_mbox/tiles-users/201806.mbox/%3C1528069995.1512639.1395048960.2CECF94B%40webmail.messagingengine.com%3E] > stuck thread on hashmap > --- > > Key: TILES-599 > URL: https://issues.apache.org/jira/browse/TILES-599 > Project: Tiles > Issue Type: Bug > Components: tiles-core >Reporter: Shakeel Abbas >Priority: Critical > Fix For: 3.1.x, 3.0.x > > > Thread stuck for Apache tiles BasicPreparerFactory. This happens in > concurrent environments. > Root cause and solution discussed here. > https://stackoverflow.com/questions/38761222/hashmap-hang-in-concurrent-access > Part of Stack trace here as below > ", which is more than the configured time (StuckThreadMaxTime) of "600" > seconds. Stack trace: > !java.util.HashMap.getEntry(HashMap.java:466) > !java.util.HashMap.containsKey(HashMap.java:450) > !org.apache.tiles.preparer.BasicPreparerFactory.getPreparer(BasicPrepare > rFactory.java:70) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TILES-599) stuck thread on hashmap
[ https://issues.apache.org/jira/browse/TILES-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594841#comment-16594841 ] ASF GitHub Bot commented on TILES-599: -- GitHub user shakeelabbas1 opened a pull request: https://github.com/apache/tiles/pull/15 https://issues.apache.org/jira/browse/TILES-599 We are having issue of thread stuck waiting for hashmap. More details of exact issue mentioned here https://stackoverflow.com/questions/38761222/hashmap-hang-in-concurrent-access You can merge this pull request into a Git repository by running: $ git pull https://github.com/shakeelabbas1/tiles trunk Alternatively you can review and apply these changes as the patch at: https://github.com/apache/tiles/pull/15.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #15 commit ec90ffc8a0fa1930001350aa3bc3c65fa364452f Author: shakeel.abbas Date: 2018-08-28T11:10:35Z https://issues.apache.org/jira/browse/TILES-599 > stuck thread on hashmap > --- > > Key: TILES-599 > URL: https://issues.apache.org/jira/browse/TILES-599 > Project: Tiles > Issue Type: Bug > Components: tiles-core >Reporter: Shakeel Abbas >Priority: Major > Fix For: 2.2.x > > > Thread stuck for Apache tiles BasicPreparerFactory. This happens in > concurrent environments. > Root cause and solution discussed here. > https://stackoverflow.com/questions/38761222/hashmap-hang-in-concurrent-access > Part of Stack trace here as below > ", which is more than the configured time (StuckThreadMaxTime) of "600" > seconds. Stack trace: > !java.util.HashMap.getEntry(HashMap.java:466) > !java.util.HashMap.containsKey(HashMap.java:450) > !org.apache.tiles.preparer.BasicPreparerFactory.getPreparer(BasicPrepare > rFactory.java:70) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
