[JBoss JIRA] (JBTM-2182) [quickstart] NoClassDefFoundError on ArjunaJTA/maven
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2182?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-2182:
-------------------------------------
Thanks Andrew, we can take a look then
> [quickstart] NoClassDefFoundError on ArjunaJTA/maven
> ----------------------------------------------------
>
> Key: JBTM-2182
> URL: https://issues.jboss.org/browse/JBTM-2182
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Demonstrator
> Reporter: Andrew Rubinger
> Assignee: Tom Jenkinson
> Fix For: 5.0.3
>
>
> [INFO] --- exec-maven-plugin:1.2:exec (default-cli) @ maven ---
> Exception in thread "main" java.lang.RuntimeException: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager;
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:81)
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:49)
> at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42)
> at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:71)
> at TransactionManagerExample.main(TransactionManagerExample.java:39)
> Caused by: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager;
> at java.lang.Class.getDeclaredFields0(Native Method)
> at java.lang.Class.privateGetDeclaredFields(Class.java:2570)
> at java.lang.Class.getDeclaredFields(Class.java:1903)
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:135)
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:78)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: javax.transaction.TransactionManager
> at java.net.URLClassLoader$1.run(URLClassLoader.java:372)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:360)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 9 more
> Probably due to Tx API being in provided scope, not included in exec:exec under src/java/main?
> [INFO] +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.0.Final:provided
> Also: NCDFE in javax_transaction/TransactionExample:
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger
> Probably wanna audit the whole module; is this not tested in CI? Would suggest re-implementing perhaps as unit tests instead of Main classes.
> From Mike: It gets run under CI regularly (and the last build was on 22-May-2014 16:13:23). I can't remember the last time it failed. You should be able to just check out the repo and type mvn clean install from the top
> From Tom: I said that we might not run exec:exec in CI as some of the QS are quite intricate and difficult to script.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months
[JBoss JIRA] (JBTM-2182) [quickstart] NoClassDefFoundError on ArjunaJTA/maven
by Andrew Rubinger (JIRA)
[ https://issues.jboss.org/browse/JBTM-2182?page=com.atlassian.jira.plugin.... ]
Andrew Rubinger commented on JBTM-2182:
---------------------------------------
I don't have a great solution with the Mains approach that fixes point 1) above.
I *could* fix 2), but the issue there is in scope=provided in dependencyManagement in a parent POM, and I'm not certain what else this would affect by changing the parent. Conversely, overriding on the child level is likely to not cover all the cases in which a NCDFE my occur; I've run into 3 of these already in various test cases.
Honestly sounds like more a task for those guys familiar w/ the layout. :/ And I'd also recommend putting "exec:exec" into your CI jobs so that if you're not tracking proper unit tests, at least you'd get failure notifications in your builds.
S,
ALR
> [quickstart] NoClassDefFoundError on ArjunaJTA/maven
> ----------------------------------------------------
>
> Key: JBTM-2182
> URL: https://issues.jboss.org/browse/JBTM-2182
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Demonstrator
> Reporter: Andrew Rubinger
> Assignee: Tom Jenkinson
> Fix For: 5.0.3
>
>
> [INFO] --- exec-maven-plugin:1.2:exec (default-cli) @ maven ---
> Exception in thread "main" java.lang.RuntimeException: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager;
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:81)
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:49)
> at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42)
> at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:71)
> at TransactionManagerExample.main(TransactionManagerExample.java:39)
> Caused by: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager;
> at java.lang.Class.getDeclaredFields0(Native Method)
> at java.lang.Class.privateGetDeclaredFields(Class.java:2570)
> at java.lang.Class.getDeclaredFields(Class.java:1903)
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:135)
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:78)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: javax.transaction.TransactionManager
> at java.net.URLClassLoader$1.run(URLClassLoader.java:372)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:360)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 9 more
> Probably due to Tx API being in provided scope, not included in exec:exec under src/java/main?
> [INFO] +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.0.Final:provided
> Also: NCDFE in javax_transaction/TransactionExample:
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger
> Probably wanna audit the whole module; is this not tested in CI? Would suggest re-implementing perhaps as unit tests instead of Main classes.
> From Mike: It gets run under CI regularly (and the last build was on 22-May-2014 16:13:23). I can't remember the last time it failed. You should be able to just check out the repo and type mvn clean install from the top
> From Tom: I said that we might not run exec:exec in CI as some of the QS are quite intricate and difficult to script.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months
[JBoss JIRA] (JBTM-2182) [quickstart] NoClassDefFoundError on ArjunaJTA/maven
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2182?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-2182:
-------------------------------------
If you have a fix locally that is still with the Main approach then please do raise a PR for it - it would be greatly appreciated. I know you work for JBoss but would you mind signing our CLA? (JBoss Transactions - https://cla.jboss.org/index.seam) I will mark you as a Patch contributor and assign the issue to you if would like to go down this route.
Thanks!
Tom
> [quickstart] NoClassDefFoundError on ArjunaJTA/maven
> ----------------------------------------------------
>
> Key: JBTM-2182
> URL: https://issues.jboss.org/browse/JBTM-2182
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Demonstrator
> Reporter: Andrew Rubinger
> Assignee: Tom Jenkinson
> Fix For: 5.0.3
>
>
> [INFO] --- exec-maven-plugin:1.2:exec (default-cli) @ maven ---
> Exception in thread "main" java.lang.RuntimeException: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager;
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:81)
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:49)
> at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42)
> at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:71)
> at TransactionManagerExample.main(TransactionManagerExample.java:39)
> Caused by: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager;
> at java.lang.Class.getDeclaredFields0(Native Method)
> at java.lang.Class.privateGetDeclaredFields(Class.java:2570)
> at java.lang.Class.getDeclaredFields(Class.java:1903)
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:135)
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:78)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: javax.transaction.TransactionManager
> at java.net.URLClassLoader$1.run(URLClassLoader.java:372)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:360)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 9 more
> Probably due to Tx API being in provided scope, not included in exec:exec under src/java/main?
> [INFO] +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.0.Final:provided
> Also: NCDFE in javax_transaction/TransactionExample:
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger
> Probably wanna audit the whole module; is this not tested in CI? Would suggest re-implementing perhaps as unit tests instead of Main classes.
> From Mike: It gets run under CI regularly (and the last build was on 22-May-2014 16:13:23). I can't remember the last time it failed. You should be able to just check out the repo and type mvn clean install from the top
> From Tom: I said that we might not run exec:exec in CI as some of the QS are quite intricate and difficult to script.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months
[JBoss JIRA] (JBTM-2182) [quickstart] NoClassDefFoundError on ArjunaJTA/maven
by Andrew Rubinger (JIRA)
[ https://issues.jboss.org/browse/JBTM-2182?page=com.atlassian.jira.plugin.... ]
Andrew Rubinger commented on JBTM-2182:
---------------------------------------
[~mmusgrov] You won't be looking for a failure; you should be looking for this test *passing*. And as I say, it's not implemented as a test, nor is it executed as part of "mvn install" phase. The issue is as I note; the JTA API is in "provided" scope which is not available to the "exec" plugin.
So, there are a few issues here:
1) This isn't included in the testsuite
2) The JTA API isn't on the --classpath when running
>From what I've seen, this isn't isolated to the Arjuna/maven quickstart. :/
I'd have issued a PR for fixing, but unsure of how you guys would like to proceed.
> [quickstart] NoClassDefFoundError on ArjunaJTA/maven
> ----------------------------------------------------
>
> Key: JBTM-2182
> URL: https://issues.jboss.org/browse/JBTM-2182
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Demonstrator
> Reporter: Andrew Rubinger
> Assignee: Tom Jenkinson
> Fix For: 5.0.3
>
>
> [INFO] --- exec-maven-plugin:1.2:exec (default-cli) @ maven ---
> Exception in thread "main" java.lang.RuntimeException: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager;
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:81)
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:49)
> at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42)
> at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:71)
> at TransactionManagerExample.main(TransactionManagerExample.java:39)
> Caused by: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager;
> at java.lang.Class.getDeclaredFields0(Native Method)
> at java.lang.Class.privateGetDeclaredFields(Class.java:2570)
> at java.lang.Class.getDeclaredFields(Class.java:1903)
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:135)
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:78)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: javax.transaction.TransactionManager
> at java.net.URLClassLoader$1.run(URLClassLoader.java:372)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:360)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 9 more
> Probably due to Tx API being in provided scope, not included in exec:exec under src/java/main?
> [INFO] +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.0.Final:provided
> Also: NCDFE in javax_transaction/TransactionExample:
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger
> Probably wanna audit the whole module; is this not tested in CI? Would suggest re-implementing perhaps as unit tests instead of Main classes.
> From Mike: It gets run under CI regularly (and the last build was on 22-May-2014 16:13:23). I can't remember the last time it failed. You should be able to just check out the repo and type mvn clean install from the top
> From Tom: I said that we might not run exec:exec in CI as some of the QS are quite intricate and difficult to script.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months
[JBoss JIRA] (JBTM-2182) [quickstart] NoClassDefFoundError on ArjunaJTA/maven
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2182?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2182:
--------------------------------
Reporter: Andrew Rubinger (was: Tom Jenkinson)
> [quickstart] NoClassDefFoundError on ArjunaJTA/maven
> ----------------------------------------------------
>
> Key: JBTM-2182
> URL: https://issues.jboss.org/browse/JBTM-2182
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Demonstrator
> Reporter: Andrew Rubinger
> Assignee: Tom Jenkinson
> Fix For: 5.0.3
>
>
> [INFO] --- exec-maven-plugin:1.2:exec (default-cli) @ maven ---
> Exception in thread "main" java.lang.RuntimeException: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager;
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:81)
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:49)
> at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42)
> at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:71)
> at TransactionManagerExample.main(TransactionManagerExample.java:39)
> Caused by: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager;
> at java.lang.Class.getDeclaredFields0(Native Method)
> at java.lang.Class.privateGetDeclaredFields(Class.java:2570)
> at java.lang.Class.getDeclaredFields(Class.java:1903)
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:135)
> at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:78)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: javax.transaction.TransactionManager
> at java.net.URLClassLoader$1.run(URLClassLoader.java:372)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:360)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 9 more
> Probably due to Tx API being in provided scope, not included in exec:exec under src/java/main?
> [INFO] +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.0.Final:provided
> Also: NCDFE in javax_transaction/TransactionExample:
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger
> Probably wanna audit the whole module; is this not tested in CI? Would suggest re-implementing perhaps as unit tests instead of Main classes.
> From Mike: It gets run under CI regularly (and the last build was on 22-May-2014 16:13:23). I can't remember the last time it failed. You should be able to just check out the repo and type mvn clean install from the top
> From Tom: I said that we might not run exec:exec in CI as some of the QS are quite intricate and difficult to script.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months
[JBoss JIRA] (JBTM-2182) [quickstart] NoClassDefFoundError on ArjunaJTA/maven
by Tom Jenkinson (JIRA)
Tom Jenkinson created JBTM-2182:
-----------------------------------
Summary: [quickstart] NoClassDefFoundError on ArjunaJTA/maven
Key: JBTM-2182
URL: https://issues.jboss.org/browse/JBTM-2182
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Demonstrator
Reporter: Tom Jenkinson
Assignee: Tom Jenkinson
Fix For: 5.0.3
[INFO] --- exec-maven-plugin:1.2:exec (default-cli) @ maven ---
Exception in thread "main" java.lang.RuntimeException: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager;
at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:81)
at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:49)
at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42)
at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:71)
at TransactionManagerExample.main(TransactionManagerExample.java:39)
Caused by: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager;
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Class.java:2570)
at java.lang.Class.getDeclaredFields(Class.java:1903)
at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:135)
at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:78)
... 4 more
Caused by: java.lang.ClassNotFoundException: javax.transaction.TransactionManager
at java.net.URLClassLoader$1.run(URLClassLoader.java:372)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:360)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 9 more
Probably due to Tx API being in provided scope, not included in exec:exec under src/java/main?
[INFO] +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.0.Final:provided
Also: NCDFE in javax_transaction/TransactionExample:
Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger
Probably wanna audit the whole module; is this not tested in CI? Would suggest re-implementing perhaps as unit tests instead of Main classes.
>From Mike: It gets run under CI regularly (and the last build was on 22-May-2014 16:13:23). I can't remember the last time it failed. You should be able to just check out the repo and type mvn clean install from the top
>From Tom: I said that we might not run exec:exec in CI as some of the QS are quite intricate and difficult to script.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months
[JBoss JIRA] (JBTM-2180) Determine whether or not we should use a specific collections framework
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-2180?page=com.atlassian.jira.plugin.... ]
Mark Little commented on JBTM-2180:
-----------------------------------
Yes. I know BasicAction uses Hashtable for maintaining child thread and actions, but since concurrent threads in the same transaction or nested transactions aren't used much, this may not be a problem there. StateManager's use of Hashtable may be a different matter though, since StateManager is used everywhere.
However, having a good analysis of the overhead is definitely the right first step. Then at least if we make no changes we can do so based on facts and not supposition. Also precisely which collections framework we might use were it to be necessary, is a job in its own right :-)
> Determine whether or not we should use a specific collections framework
> -----------------------------------------------------------------------
>
> Key: JBTM-2180
> URL: https://issues.jboss.org/browse/JBTM-2180
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JTA, JTS, Performance Testing, REST, Transaction Core
> Affects Versions: 5.0.1
> Reporter: Mark Little
> Assignee: Michael Musgrove
>
> We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should we use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections
> There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months
[JBoss JIRA] (JBTM-2180) Determine whether or not we should use a specific collections framework
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-2180?page=com.atlassian.jira.plugin.... ]
Mark Little updated JBTM-2180:
------------------------------
Description:
We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should we use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections
There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective.
was:
We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should be use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections
There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective.
> Determine whether or not we should use a specific collections framework
> -----------------------------------------------------------------------
>
> Key: JBTM-2180
> URL: https://issues.jboss.org/browse/JBTM-2180
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JTA, JTS, Performance Testing, REST, Transaction Core
> Affects Versions: 5.0.1
> Reporter: Mark Little
> Assignee: Michael Musgrove
>
> We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should we use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections
> There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months
[JBoss JIRA] (JBTM-2180) Determine whether or not we should use a specific collections framework
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2180?page=com.atlassian.jira.plugin.... ]
Michael Musgrove commented on JBTM-2180:
----------------------------------------
Initially we should profile which collections are suitable candidates to be replaced. My guess is that _transactions ConcurrentHashMap in TransactionImple could benefit from such a change.
> Determine whether or not we should use a specific collections framework
> -----------------------------------------------------------------------
>
> Key: JBTM-2180
> URL: https://issues.jboss.org/browse/JBTM-2180
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JTA, JTS, Performance Testing, REST, Transaction Core
> Affects Versions: 5.0.1
> Reporter: Mark Little
> Assignee: Michael Musgrove
>
> We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should be use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections
> There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
9 years, 11 months