[JBoss JIRA] (JBTM-2206) Use synchronized HashMaps
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2206?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson edited comment on JBTM-2206 at 12/12/14 7:59 AM:
---------------------------------------------------------------
Mike, using our performance toolkit please can you provide some details on here about the performance improvement that we see with the commits applied? I am trying to make a decision on whether its worth having to inconvenience users by deprecating the checked action API and replacing it with the updated one.
was (Author: tomjenkinson):
Mike, using our performance toolkit please can you provide some details on here about the performance improvement that we see with this commit applied? I am trying to make a decision on whether its worth having to inconvenience users by deprecating the checked action API and replacing it with the updated one.
> Use synchronized HashMaps
> -------------------------
>
> Key: JBTM-2206
> URL: https://issues.jboss.org/browse/JBTM-2206
> Project: JBoss Transaction Manager
> Issue Type: Sub-task
> Components: Transaction Core
> Reporter: Jesper Pedersen
> Assignee: Michael Musgrove
>
> Change usage of Hashtable into synchronized HashMap's instead.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (JBTM-2203) Remove ReentrantLock from StateManager
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2203?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson edited comment on JBTM-2203 at 12/12/14 7:52 AM:
---------------------------------------------------------------
I have pulled the changes to the hashmap into a separate commit and raised a PR for it over on JBTM-2206 (note it does have an effect on the API of StateManager).
was (Author: tomjenkinson):
I have pulled the changes to the hashmap into a separate commit and raised a PR for it over on JBTM-2206.
> Remove ReentrantLock from StateManager
> --------------------------------------
>
> Key: JBTM-2203
> URL: https://issues.jboss.org/browse/JBTM-2203
> Project: JBoss Transaction Manager
> Issue Type: Sub-task
> Components: JTA
> Affects Versions: 5.0.2
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.x.y
>
>
> Remove unused lock from StateManager, and add the access methods to LockManager instead
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (JBTM-2203) Remove ReentrantLock from StateManager
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2203?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson edited comment on JBTM-2203 at 12/12/14 7:50 AM:
---------------------------------------------------------------
I have pulled the changes to the hashmap into a separate commit and raised a PR for it over on JBTM-2206.
was (Author: tomjenkinson):
I have pulled the changes to the hashmap into a separate commit and raised a PR for it over on JBTM-2203.
> Remove ReentrantLock from StateManager
> --------------------------------------
>
> Key: JBTM-2203
> URL: https://issues.jboss.org/browse/JBTM-2203
> Project: JBoss Transaction Manager
> Issue Type: Sub-task
> Components: JTA
> Affects Versions: 5.0.2
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.x.y
>
>
> Remove unused lock from StateManager, and add the access methods to LockManager instead
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (JBTM-2206) Use synchronized HashMaps
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2206?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-2206:
-------------------------------------
Mike, using our performance toolkit please can you provide some details on here about the performance improvement that we see with this commit applied? I am trying to make a decision on whether its worth having to inconvenience users by deprecating the checked action API and replacing it with the updated one.
> Use synchronized HashMaps
> -------------------------
>
> Key: JBTM-2206
> URL: https://issues.jboss.org/browse/JBTM-2206
> Project: JBoss Transaction Manager
> Issue Type: Sub-task
> Components: Transaction Core
> Reporter: Jesper Pedersen
> Assignee: Michael Musgrove
>
> Change usage of Hashtable into synchronized HashMap's instead.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (JBTM-2158) btadmin ListServiceStatusTest::testListServiceStatusWithRunningServer failed with starting up the server
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2158?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2158.
-------------------------------
> btadmin ListServiceStatusTest::testListServiceStatusWithRunningServer failed with starting up the server
> --------------------------------------------------------------------------------------------------------
>
> Key: JBTM-2158
> URL: https://issues.jboss.org/browse/JBTM-2158
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: BlackTie
> Reporter: Amos Feng
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.4
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon...
> {noformat}
> 2014-04-22 19:03:12,740 [main] INFO (min.ListServiceStatusTest:86 ) - ListServiceStatusTest::testListServiceStatusWithRunningServer
> 2014-04-22 19:03:12,746 [main] INFO (conf.Server :51 ) - Checking for host: WIN-5GKPEREVUOO or ip: 172.17.131.21
> 2014-04-22 19:04:04,486 [main] INFO (commands.Startup :123 ) - 2014-04-22 19:04:04,455 [0x00000f34] WARN (HybridSocketEndpointQueue:224 ) - no message receive session 0 for 50 seconds
> 2014-04-22 19:04:04,486 [main] INFO (commands.Startup :123 ) -
> 2014-04-22 19:04:04,487 [main] INFO (commands.Startup :123 ) - 2014-04-22 19:04:04,473 [0x00000f34] ERROR (AtmiBrokerServer :1113) - Could not advertise service with command: tpadvertise,testsui,.testsui1,0,queue,5.0.2.Final-SNAPSHOT,
> 2014-04-22 19:04:04,487 [main] INFO (commands.Startup :123 ) -
> 2014-04-22 19:04:04,487 [main] INFO (commands.Startup :123 ) - 2014-04-22 19:04:04,481 [0x00000f34] FATAL (AtmiBrokerServer :473 ) - advertise admin service failed
> 2014-04-22 19:04:04,488 [main] INFO (commands.Startup :123 ) -
> 2014-04-22 19:04:04,629 [main] INFO (commands.Startup :123 ) - 2014-04-22 19:04:04,616 [0x00000f34] FATAL (AtmiBrokerServer :254 ) - serverinit failed
> 2014-04-22 19:04:04,630 [main] INFO (min.ListServiceStatusTest:42 ) - ListServiceStatusTest::tearDown
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (JBTM-2288) Deploy/Undeploy BlacktieAdminService MBean throws javax.naming.NameNotFoundException: java:comp/BeanManager
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2288?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2288.
-------------------------------
> Deploy/Undeploy BlacktieAdminService MBean throws javax.naming.NameNotFoundException: java:comp/BeanManager
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBTM-2288
> URL: https://issues.jboss.org/browse/JBTM-2288
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Application Server Integration, BlackTie
> Reporter: Amos Feng
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.4
>
>
> When deploy the balcktie admin ear, the wildfly throws NameNotFound Exception when deploying the BlacktiAdminService MBean
> {code}
> 11:39:30,059 INFO [org.jboss.narayana.blacktie.administration.BlacktieAdminService] (MSC service thread 1-8) Admin Server Started
> 11:39:30,060 ERROR [org.jboss.as.weld] (MSC service thread 1-8) WFLYWELD0002: Failed to tear down Weld contexts: javax.naming.NameNotFoundException: java:comp/BeanManager
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187) [wildfly-naming-9.0.0.Alpha2-SNAPSHOT.jar:9.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:231) [wildfly-naming-9.0.0.Alpha2-SNAPSHOT.jar:9.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188) [wildfly-naming-9.0.0.Alpha2-SNAPSHOT.jar:9.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) [wildfly-naming-9.0.0.Alpha2-SNAPSHOT.jar:9.0.0.Alpha2-SNAPSHOT]
> at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21]
> at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21]
> at org.jboss.as.weld.arquillian.WeldContextSetup.teardown(WeldContextSetup.java:108)
> at org.jboss.as.service.AbstractService.invokeLifecycleMethod(AbstractService.java:77) [wildfly-sar-9.0.0.Alpha2-SNAPSHOT.jar:9.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.service.StartStopService.start(StartStopService.java:57) [wildfly-sar-9.0.0.Alpha2-SNAPSHOT.jar:9.0.0.Alpha2-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> 11:39:30,064 ERROR [org.jboss.as.weld] (MSC service thread 1-8) WFLYWELD0002: Failed to tear down Weld contexts: javax.naming.NameNotFoundException: java:comp/BeanManager
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187)
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:231)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)
> at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21]
> at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_21]
> at org.jboss.as.weld.arquillian.WeldContextSetup.teardown(WeldContextSetup.java:108)
> at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistrationService.java:106) [wildfly-jmx-1.0.0.Alpha9.jar:1.0.0.Alpha9]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (JBTM-2264) Error enlisting second xa resource on the same oracle instance but other schema
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2264?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2264.
-------------------------------
> Error enlisting second xa resource on the same oracle instance but other schema
> -------------------------------------------------------------------------------
>
> Key: JBTM-2264
> URL: https://issues.jboss.org/browse/JBTM-2264
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: JTA
> Affects Versions: 5.0.3
> Reporter: Evgeniy Smelik
> Assignee: Tom Jenkinson
> Fix For: 5.0.4
>
> Attachments: sscce.zip, sscce.zip, test.log
>
>
> I've got an exception {{java.sql.SQLException: ConnectionImple.registerDatabase - ARJUNA017017: enlist of resource failed}} while preparing statement in the second connection within the same oracle instance but other schema.
> Whole stack trace:
> {noformat}
> oracle.jdbc.xa.OracleXAException
> at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1110)
> at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:240)
> at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:741)
> at com.arjuna.ats.internal.jdbc.ConnectionImple.registerDatabase(ConnectionImple.java:983)
> at com.arjuna.ats.internal.jdbc.ConnectionImple.prepareStatement(ConnectionImple.java:179)
> at SimpleJdbcTest.insert(SimpleJdbcTest.java:46)
> at SimpleJdbcTest.main(SimpleJdbcTest.java:36)
> 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:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> java.sql.SQLException: ConnectionImple.registerDatabase - ARJUNA017017: enlist of resource failed
> at com.arjuna.ats.internal.jdbc.ConnectionImple.registerDatabase(ConnectionImple.java:1003)
> at com.arjuna.ats.internal.jdbc.ConnectionImple.prepareStatement(ConnectionImple.java:179)
> at SimpleJdbcTest.insert(SimpleJdbcTest.java:46)
> at SimpleJdbcTest.main(SimpleJdbcTest.java:36)
> {noformat}
> (Detail log and SSCCE are attached).
> I use jboss transaction manager in standaloine application just to test jboss JTA implementation. The same code works well if one and second data sources use own (different) database instances.
> I note that atomikos and bitronix JTA implementation works correctly in the same environment irrespectively single oracle instance is used or not.
> I found similar problem [here|http://stackoverflow.com/questions/23617179/jboss-6-1-unable-to-get-...].
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months