[JBoss JIRA] (JBTM-1757) Tests fail when building with emma
by Mark Little (JIRA)
Mark Little created JBTM-1757:
---------------------------------
Summary: Tests fail when building with emma
Key: JBTM-1757
URL: https://issues.jboss.org/browse/JBTM-1757
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Build System, Testing
Affects Versions: 5.0.0.M3
Environment: Mac OS 10.7.5
JDK 7
Reporter: Mark Little
Assignee: Tom Jenkinson
The following tests fail or hang when building with emma (command used is ./build.sh clean install -PcodeCoverage emma:emma):
test(com.hp.mwtests.ts.arjuna.atomicaction.CheckedActionTest) Time elapsed: 0.005 sec <<< FAILURE!
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:92)
at org.junit.Assert.assertTrue(Assert.java:43)
at org.junit.Assert.assertTrue(Assert.java:54)
at com.hp.mwtests.ts.arjuna.atomicaction.CheckedActionTest.test(CheckedActionTest.java:49)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
testCheckedAction(com.hp.mwtests.ts.arjuna.atomicaction.CheckedActionTest) Time elapsed: 0.001 sec <<< FAILURE!
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:92)
at org.junit.Assert.assertTrue(Assert.java:43)
at org.junit.Assert.assertTrue(Assert.java:54)
at com.hp.mwtests.ts.arjuna.atomicaction.CheckedActionTest.testCheckedAction(CheckedActionTest.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
testGetSet(com.hp.mwtests.ts.arjuna.atomicaction.TxControlUnitTest) Time elapsed: 0.001 sec <<< FAILURE!
java.lang.AssertionError: expected:<false> but was:<true>
at org.junit.Assert.fail(Assert.java:93)
at org.junit.Assert.failNotEquals(Assert.java:647)
at org.junit.Assert.assertEquals(Assert.java:128)
at org.junit.Assert.assertEquals(Assert.java:147)
at com.hp.mwtests.ts.arjuna.atomicaction.TxControlUnitTest.testGetSet(TxControlUnitTest.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
test(com.hp.mwtests.ts.arjuna.objectstore.AltStoreTest) Time elapsed: 0.119 sec <<< FAILURE!
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:92)
at org.junit.Assert.assertTrue(Assert.java:43)
at org.junit.Assert.assertFalse(Assert.java:68)
at org.junit.Assert.assertFalse(Assert.java:79)
at com.hp.mwtests.ts.arjuna.objectstore.AltStoreTest.test(AltStoreTest.java:72)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
testStateMachine(com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest) Time elapsed: 0.001 sec <<< ERROR!
com.arjuna.ats.arjuna.exceptions.ObjectStoreException: ARJUNA012263: No JDBCAccess implementation provided!
at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.<init>(JDBCStore.java:200)
at com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest.testStateMachine(JDBCStoreTest.java:69)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running com.hp.mwtests.ts.arjuna.objectstore.LogStoreRecoveryTest
^C
Results :
Failed tests: test(com.hp.mwtests.ts.arjuna.atomicaction.CheckedActionTest)
testCheckedAction(com.hp.mwtests.ts.arjuna.atomicaction.CheckedActionTest)
testGetSet(com.hp.mwtests.ts.arjuna.atomicaction.TxControlUnitTest): expected:<false> but was:<true>
test(com.hp.mwtests.ts.arjuna.objectstore.AltStoreTest)
Tests in error:
testStateMachine(com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest): ARJUNA012263: No JDBCAccess implementation provided!
LogStoreRecoveryTest hung and I killed the build.
It's worth noting that the build does not stop when a test fails. Furthermore, a quick look at some of the tests (e.g., CheckedActionTest) seems to indicate that perhaps the environment from previous tests has not been cleaned up before the next tests run.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month
[JBoss JIRA] (JBTM-1754) Make project names consistent in poms
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1754?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1754:
-------------------------------------
Great, feel free to raise a PR with those changes then - thanks
> Make project names consistent in poms
> -------------------------------------
>
> Key: JBTM-1754
> URL: https://issues.jboss.org/browse/JBTM-1754
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Paul Gier
> Assignee: Paul Gier
>
> The project names used in the build are not consistent which makes it difficult for someone unfamiliar with the project to debug build issues.
> Some examples are provided:
> ||Dir Name||Artifact ID||Project Name||Proposed Name||
> |/ArjunaJTA|narayana-jta-all|JBoss JTA everything|Narayana: ArjunaJTA|
> |/ArjunaJTS/narayana-jts-idlj|narayana-jts-idlj|JBossJTS packaged module with idlj stubs|Narayana: ArjunaJTS idlj|
> |/ArjunaJTS/orbportability|orbportability|JBossJTS orb portability|Narayana: ArjunaJTS orbportability|
> The project names can be changed without disrupting the way the build works, so these should be changed to match the dir and artifactId as much as possible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month
[JBoss JIRA] (JBTM-1756) JDK ORB.idl does not include Current yet rt.jar does
by Mark Little (JIRA)
Mark Little created JBTM-1756:
---------------------------------
Summary: JDK ORB.idl does not include Current yet rt.jar does
Key: JBTM-1756
URL: https://issues.jboss.org/browse/JBTM-1756
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Build System, JTS
Affects Versions: 5.0.0.M3
Reporter: Mark Little
Assignee: Mark Little
OTS Current should inherit from CORBA::Current but the definition of that isn't in the JDK orb.idl.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month
[JBoss JIRA] (JBTM-860) use XAResourceWrapper metadata for assume complete
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-860?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson updated JBTM-860:
-------------------------------
Fix Version/s: 5.0.0.M4
(was: 5.0.0.Final)
> use XAResourceWrapper metadata for assume complete
> --------------------------------------------------
>
> Key: JBTM-860
> URL: https://issues.jboss.org/browse/JBTM-860
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Resource Manager
> Affects Versions: 4.15.0
> Reporter: Jonathan Halliday
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.M4
>
>
> In the XA protocol a time window exists wherein the RM has committed and thus forgotten a tx branch but the TM has not yet deleted its log. A crash during this window currently results in an unrecoverable situation, as the TM assumes the branch belongs to an RM that is uncontactable and will retry recovery indefinitely. This stems from an inability to relate the Xid to a specific RM. It can be overridden globally with JTAEnvironmentBean.xaAssumeRecoveryComplete, but we would prefer more fine-grained control. With the availability of RM id information from XAResourceWrapper this becomes feasible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month
[JBoss JIRA] (JBTM-1340) BeanPopulator overhead needs looking into
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1340?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1340:
--------------------------------
Fix Version/s: 5.0.0.M4
(was: 5.0.0.Final)
> BeanPopulator overhead needs looking into
> -----------------------------------------
>
> Key: JBTM-1340
> URL: https://issues.jboss.org/browse/JBTM-1340
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Common
> Affects Versions: 4.17.2
> Environment: Mac OS 10.7
> Reporter: Mark Little
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.M4
>
>
> During profiling, BeanPopulator can represent a 7% overhead. It may not seem like a lot, but for something as relatively simple as what BeanPopulator should be doing, it seems to be quite a bit.
> 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.coordinator.TxStats.enabled
> 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.common.arjPropertyManager.getCoordinatorEnvironmentBean
> 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance
> 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance
> 2.5% - 1,587 ms - 10,000 inv. java.lang.StringBuilder.<init>
> 2.3% - 1,507 ms - 10,000 inv. java.lang.StringBuilder.toString
> 0.0% - 320 µs - 10,000 inv. java.util.concurrent.ConcurrentMap.containsKey
> 0.0% - 61 µs - 10,000 inv. java.lang.Class.getName
> 0.0% - 25 µs - 10,000 inv. java.util.concurrent.ConcurrentMap.get
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month
[JBoss JIRA] (JBTM-1742) Tidy up the JTS IDL
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-1742?page=com.atlassian.jira.plugin.... ]
Mark Little commented on JBTM-1742:
-----------------------------------
OK, so the orb.idl that ships with the JDK is from 1995, which means it's at least 10 years out of date! However, rt.jar does include Current:
1020 Thu May 17 19:25:14 BST 2012 com/sun/corba/se/impl/interceptors/PICurrent$1.class
2433 Thu May 17 19:25:14 BST 2012 com/sun/corba/se/impl/interceptors/PICurrent.class
2972 Thu May 17 19:27:44 BST 2012 com/sun/corba/se/impl/oa/poa/POACurrent.class
1417 Thu May 17 19:28:26 BST 2012 com/sun/org/apache/xalan/internal/xsltc/compiler/CurrentCall.class
311 Thu May 17 19:28:28 BST 2012 com/sun/org/apache/xalan/internal/xsltc/dom/CurrentNodeListFilter.class
4612 Thu May 17 19:28:28 BST 2012 com/sun/org/apache/xalan/internal/xsltc/dom/CurrentNodeListIterator.class
2224 Thu May 17 19:28:48 BST 2012 com/sun/org/apache/xpath/internal/functions/FuncCurrent.class
1706 Thu May 17 19:47:24 BST 2012 java/util/concurrent/Executors$PrivilegedCallableUsingCurrentClassLoader$1.class
2465 Thu May 17 19:47:24 BST 2012 java/util/concurrent/Executors$PrivilegedCallableUsingCurrentClassLoader.class
216 Thu May 17 19:27:22 BST 2012 org/omg/CORBA/Current.class
1485 Thu May 17 19:22:14 BST 2012 org/omg/CORBA/CurrentHelper.class
912 Thu May 17 19:22:14 BST 2012 org/omg/CORBA/CurrentHolder.class
129 Thu May 17 19:27:22 BST 2012 org/omg/CORBA/CurrentOperations.class
245 Thu May 17 19:27:22 BST 2012 org/omg/PortableInterceptor/Current.class
2119 Thu May 17 19:22:38 BST 2012 org/omg/PortableInterceptor/CurrentHelper.class
349 Thu May 17 19:27:22 BST 2012 org/omg/PortableInterceptor/CurrentOperations.class
235 Thu May 17 19:27:44 BST 2012 org/omg/PortableServer/Current.class
2061 Thu May 17 19:22:00 BST 2012 org/omg/PortableServer/CurrentHelper.class
345 Thu May 17 19:27:44 BST 2012 org/omg/PortableServer/CurrentOperations.class
576 Thu May 17 19:27:44 BST 2012 org/omg/PortableServer/CurrentPackage/NoContext.class
2365 Thu May 17 19:27:44 BST 2012 org/omg/PortableServer/CurrentPackage/NoContextHelper.class
I need to figure out the best way around this problem, so will create a separate issue.
> Tidy up the JTS IDL
> -------------------
>
> Key: JBTM-1742
> URL: https://issues.jboss.org/browse/JBTM-1742
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JTS
> Affects Versions: 5.0.0.M3
> Reporter: Mark Little
> Assignee: Mark Little
> Fix For: 5.0.0.M4
>
>
> The IDL hasn't been updated for over a decade and has preprocessor directives in there that are probably no longer needed, unless we want to be backwardly compatible for ORBs that are no longer produced.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month