[JBoss JIRA] (JBTM-1700) Server startup is delayed if recovery starts before all resource plugins register
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1700?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1700:
--------------------------------
Fix Version/s: 5.0.0.M4
> Server startup is delayed if recovery starts before all resource plugins register
> ---------------------------------------------------------------------------------
>
> Key: JBTM-1700
> URL: https://issues.jboss.org/browse/JBTM-1700
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: James Livingston
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.M4
>
>
> If the startup of JBoss is sufficiently slow, it is possible for a recovery run to already be in progress when a resource plugin is added. When this occurs, the startup will block until the recovery run has finished.
> It would be much better if starting a recovery run did not block AS startup.
> An example of this occurring on EAP 5 is:
> "main" prio=10 tid=0x00002aac680cc000 nid=0x5e67 waiting for monitor entry [0x00000000412cb000]
> java.lang.Thread.State: BLOCKED (on object monitor)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.addXAResourceRecoveryHelper(XARecoveryModule.java:85)
> - waiting to lock <0x00002aab3e8b9d68> (a java.util.LinkedList)
> at com.arjuna.ats.jbossatx.jta.TransactionManagerService.addXAResourceRecovery(TransactionManagerService.java:695)
> at org.jboss.resource.connectionmanager.ManagedConnectionFactoryDeployment.startService(ManagedConnectionFactoryDeployment.java:500)
> at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)
> at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322)
> at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:124)
> at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
> at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> at org.jboss.system.server.jmx.LazyMBeanServer.invoke(LazyMBeanServer.java:283)
> at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:189)
> at $Proxy43.start(Unknown Source)
> at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
> at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
> ...
> "Thread-21" prio=10 tid=0x00002aacdd1f7000 nid=0x5ee3 runnable [0x000000004416a000]
> java.lang.Thread.State: RUNNABLE
> ...
> at org.jboss.resource.adapter.jdbc.xa.XAManagedConnection.recover(XAManagedConnection.java:294)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecovery(XARecoveryModule.java:773)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecoveryForRecoveryHelpers(XARecoveryModule.java:712)
> - locked <0x00002aab3e8b9d68> (a java.util.LinkedList)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:201)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:799)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:412)
--
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-1558) Prune redundant code from jboss-transaction-spi
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1558?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1558:
--------------------------------
Assignee: Michael Musgrove (was: Tom Jenkinson)
> Prune redundant code from jboss-transaction-spi
> -----------------------------------------------
>
> Key: JBTM-1558
> URL: https://issues.jboss.org/browse/JBTM-1558
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Application Server Integration
> Reporter: Tom Jenkinson
> Assignee: Michael Musgrove
> Fix For: 5.0.0.Final
>
> Attachments: as8.zip, ij-tx-spi.txt
>
>
> We can use jboss-transaction-spi to get started
> There is much old code in jboss-transaction-spi that does not get used in AS7 and does not apply to Narayana.
> Run tattletale over AS8, identify redundant methods and add new SPI functions if necessary
--
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 Paul Gier (JIRA)
[ https://issues.jboss.org/browse/JBTM-1754?page=com.atlassian.jira.plugin.... ]
Paul Gier commented on JBTM-1754:
---------------------------------
Yes, it's a bit redundant, but I think ok because it doesn't really make the name too long, and it makes it more clear that each module is part of the Narayana project vs. an external submodule or something like that. It's also the same convention that the JBossAS/Wildfly poms use.
> 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-1670) Add a community profile to enable none-EAP features: was Remove jfreechart dependency from EAP6 profile
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1670?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1670:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 5.0.0.M4
Resolution: Done
> Add a community profile to enable none-EAP features: was Remove jfreechart dependency from EAP6 profile
> -------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1670
> URL: https://issues.jboss.org/browse/JBTM-1670
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Build System
> Affects Versions: 4.17.4
> Reporter: Weinan Li
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.M4
>
>
> Currently in EAP6 there is no jfreechart library so we need to remove the relative components from JBossTS:
> {code}
> ArjunaCore/arjuna/pom.xml
> pom.xml
> {code}
> And we need to remove these two classes which depend on jfreechart:
> {code}
> ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/stats/TxPerfPlugin.java
> ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/stats/TxPerfGraph.java
> {code}
--
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-1755) Spurious warning messages?
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1755?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1755:
--------------------------------
Fix Version/s: 5.0.0.M4
> Spurious warning messages?
> --------------------------
>
> Key: JBTM-1755
> URL: https://issues.jboss.org/browse/JBTM-1755
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System
> Affects Versions: 5.0.0.M3
> Reporter: Mark Little
> Assignee: Tom Jenkinson
> Priority: Minor
> Fix For: 5.0.0.M4
>
>
> [WARNING] The following patterns were never triggered in this artifact inclusion filter:
> o 'org.jboss.narayana.jts:narayana-jts-idlj'
> [WARNING] The following patterns were never triggered in this artifact exclusion filter:
> o '*:javadoc'
> o '**'
> [WARNING] The following patterns were never triggered in this artifact inclusion filter:
> o 'org.jboss.narayana.arjunacore:arjunacore-services'
--
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-1607) Hardcoded path in qa run.sh
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1607?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1607:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 5.0.0.M4
Resolution: Done
> Hardcoded path in qa run.sh
> ---------------------------
>
> Key: JBTM-1607
> URL: https://issues.jboss.org/browse/JBTM-1607
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Configuration, Testing
> Affects Versions: 5.0.0.M2
> Reporter: Mark Little
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.M4
>
>
> qa/run.sh
> #!/bin/bash
> sed -i TaskImpl.properties -e "s#^COMMAND_LINE_0=.*#COMMAND_LINE_0=java#"
> ant -Ddriver.url=file:///home/tom/narayana/dbdrivers get.drivers dist
> ant -f run-tests.xml ci-tests
--
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-1669) Remove tanukisoftware wrapper dependency from EAP6 profile
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1669?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1669:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 5.0.0.M4
Resolution: Done
> Remove tanukisoftware wrapper dependency from EAP6 profile
> ----------------------------------------------------------
>
> Key: JBTM-1669
> URL: https://issues.jboss.org/browse/JBTM-1669
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Build System
> Affects Versions: 4.17.4
> Reporter: Weinan Li
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.M4
>
>
> Currently we have tanuki in these components:
> {code}
> ArjunaCore/arjuna/services/pom.xml
> ArjunaJTS/narayana-jts-idlj/pom.xml
> ArjunaJTS/narayana-jts-jacorb/pom.xml
> pom.xml
> {code}
> {code}
> <dependency>
> <groupId>tanukisoft</groupId>
> <artifactId>wrapper</artifactId>
> <version>${version.tanukisoft}</version>
> </dependency>
> {code}
> We need to remove these dependencies from eap6 profile according to comments from Fernando:
> {quote}
> We do not ship tanukiwrapper with the AS (the windows on is an exceptional case and for different reasons).
> It is not in the AS7 dependencies, and it will be hard for Support to
> properly rebuild TS in the field.
> {quote}
> btw, there are two classes we need to remove from eap6 profile which depends on tanuki wrapper:
> {code}
> ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/services/recovery/RecoveryManagerService.java
> ArjunaJTS/jts/services/classes/com/arjuna/ats/jts/services/transactionserver/TransactionServerService.java
> {code}
--
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-1689) "jta" vs. "jts" profile seems duplicate
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1689?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1689:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 5.0.0.M4
Resolution: Done
> "jta" vs. "jts" profile seems duplicate
> ---------------------------------------
>
> Key: JBTM-1689
> URL: https://issues.jboss.org/browse/JBTM-1689
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Build System
> Affects Versions: 4.17.4
> Reporter: Weinan Li
> Assignee: Tom Jenkinson
> Priority: Minor
> Fix For: 5.0.0.M4
>
>
> "jta" vs. "jts" profile, they seem to build the same modules except for ArjunaJTS.
> As maven has some built in options for selecting which modules/directories to build, would it be better to just use those options? Instead of defining profiles, it might look something like "mvn install -pl common,ArjunaCore" instead of the build profile "mvn install -Pcore"
--
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