[JBoss JIRA] (JBTM-2819) Recover operation does not work for participant of JCA type transactions
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2819?page=com.atlassian.jira.plugin.... ]
Michael Musgrove commented on JBTM-2819:
----------------------------------------
I have clarified the semantics of clearing heuristics in the linked documentation issue.
QE are reworking the test to see if there is an issue with our handling of these types of transaction.
> Recover operation does not work for participant of JCA type transactions
> ------------------------------------------------------------------------
>
> Key: JBTM-2819
> URL: https://issues.jboss.org/browse/JBTM-2819
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Affects Versions: 5.4.0.Final
> Reporter: Ondra Chaloupka
> Assignee: Michael Musgrove
> Attachments: heuristic-rollback-objectstore.zip
>
>
> Jboss cli {{:recover}} operation does not work when having JCA type transaction. My test shows following
> {code}
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store:probe
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store:read-resource(recursive=true)
> {
> "outcome" => "success",
> "result" => {
> "expose-all-logs" => false,
> "type" => "default",
> "transactions" => {
> "0:ffff7f000001:-4cecb39b:585109e2:31" => {
> "age-in-seconds" => undefined,
> "id" => "0:ffff7f000001:-4cecb39b:585109e2:31",
> "jmx-name" => undefined,
> "type" => "CosTransactions/XAResourceRecord",
> "participants" => undefined
> },
> "0:ffff7f000001:-4cecb39b:585109e2:28" => {
> "age-in-seconds" => "1481798762",
> "id" => "0:ffff7f000001:-4cecb39b:585109e2:28",
> "jmx-name" => undefined,
> "type" => "StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple/ServerTransaction/JCA",
> "participants" => {"0:ffff7f000001:-4cecb39b:585109e2:31" => {
> "eis-product-name" => "unavailable",
> "eis-product-version" => "unavailable",
> "jmx-name" => undefined,
> "jndi-name" => "0:ffff7f000001:-4cecb39b:585109e2:31",
> "status" => "HEURISTIC_ROLLBACK",
> "type" => "/StateManager/AbstractRecord/ExtendedResourceRecord"
> }}
> }
> }
> }
> }
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-4cecb39b\:585109e2\:28/participants=0\:ffff7f000001\:-4cecb39b\:585109e2\:31:recover
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-4cecb39b\:585109e2\:28/participants=0\:ffff7f000001\:-4cecb39b\:585109e2\:31:read-resource
> {
> "outcome" => "success",
> "result" => {
> "eis-product-name" => "unavailable",
> "eis-product-version" => "unavailable",
> "jmx-name" => undefined,
> "jndi-name" => "0:ffff7f000001:-4cecb39b:585109e2:31",
> "status" => "HEURISTIC_ROLLBACK",
> "type" => "/StateManager/AbstractRecord/ExtendedResourceRecord"
> }
> }
> {code}
> I expect that {{:recover}} put the participant to {{PREPARED}} state and at that point RAR {{XATerminator.commit}} could commit such participant.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (JBTM-2819) Recover operation does not work for participant of JCA type transactions
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2819?page=com.atlassian.jira.plugin.... ]
Michael Musgrove reopened JBTM-2819:
------------------------------------
Reopening because it needs rejecting and not resolving.
> Recover operation does not work for participant of JCA type transactions
> ------------------------------------------------------------------------
>
> Key: JBTM-2819
> URL: https://issues.jboss.org/browse/JBTM-2819
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Affects Versions: 5.4.0.Final
> Reporter: Ondra Chaloupka
> Assignee: Michael Musgrove
> Attachments: heuristic-rollback-objectstore.zip
>
>
> Jboss cli {{:recover}} operation does not work when having JCA type transaction. My test shows following
> {code}
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store:probe
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store:read-resource(recursive=true)
> {
> "outcome" => "success",
> "result" => {
> "expose-all-logs" => false,
> "type" => "default",
> "transactions" => {
> "0:ffff7f000001:-4cecb39b:585109e2:31" => {
> "age-in-seconds" => undefined,
> "id" => "0:ffff7f000001:-4cecb39b:585109e2:31",
> "jmx-name" => undefined,
> "type" => "CosTransactions/XAResourceRecord",
> "participants" => undefined
> },
> "0:ffff7f000001:-4cecb39b:585109e2:28" => {
> "age-in-seconds" => "1481798762",
> "id" => "0:ffff7f000001:-4cecb39b:585109e2:28",
> "jmx-name" => undefined,
> "type" => "StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple/ServerTransaction/JCA",
> "participants" => {"0:ffff7f000001:-4cecb39b:585109e2:31" => {
> "eis-product-name" => "unavailable",
> "eis-product-version" => "unavailable",
> "jmx-name" => undefined,
> "jndi-name" => "0:ffff7f000001:-4cecb39b:585109e2:31",
> "status" => "HEURISTIC_ROLLBACK",
> "type" => "/StateManager/AbstractRecord/ExtendedResourceRecord"
> }}
> }
> }
> }
> }
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-4cecb39b\:585109e2\:28/participants=0\:ffff7f000001\:-4cecb39b\:585109e2\:31:recover
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-4cecb39b\:585109e2\:28/participants=0\:ffff7f000001\:-4cecb39b\:585109e2\:31:read-resource
> {
> "outcome" => "success",
> "result" => {
> "eis-product-name" => "unavailable",
> "eis-product-version" => "unavailable",
> "jmx-name" => undefined,
> "jndi-name" => "0:ffff7f000001:-4cecb39b:585109e2:31",
> "status" => "HEURISTIC_ROLLBACK",
> "type" => "/StateManager/AbstractRecord/ExtendedResourceRecord"
> }
> }
> {code}
> I expect that {{:recover}} put the participant to {{PREPARED}} state and at that point RAR {{XATerminator.commit}} could commit such participant.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (JBTM-2819) Recover operation does not work for participant of JCA type transactions
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2819?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-2819:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Recover operation does not work for participant of JCA type transactions
> ------------------------------------------------------------------------
>
> Key: JBTM-2819
> URL: https://issues.jboss.org/browse/JBTM-2819
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Affects Versions: 5.4.0.Final
> Reporter: Ondra Chaloupka
> Assignee: Michael Musgrove
> Attachments: heuristic-rollback-objectstore.zip
>
>
> Jboss cli {{:recover}} operation does not work when having JCA type transaction. My test shows following
> {code}
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store:probe
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store:read-resource(recursive=true)
> {
> "outcome" => "success",
> "result" => {
> "expose-all-logs" => false,
> "type" => "default",
> "transactions" => {
> "0:ffff7f000001:-4cecb39b:585109e2:31" => {
> "age-in-seconds" => undefined,
> "id" => "0:ffff7f000001:-4cecb39b:585109e2:31",
> "jmx-name" => undefined,
> "type" => "CosTransactions/XAResourceRecord",
> "participants" => undefined
> },
> "0:ffff7f000001:-4cecb39b:585109e2:28" => {
> "age-in-seconds" => "1481798762",
> "id" => "0:ffff7f000001:-4cecb39b:585109e2:28",
> "jmx-name" => undefined,
> "type" => "StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple/ServerTransaction/JCA",
> "participants" => {"0:ffff7f000001:-4cecb39b:585109e2:31" => {
> "eis-product-name" => "unavailable",
> "eis-product-version" => "unavailable",
> "jmx-name" => undefined,
> "jndi-name" => "0:ffff7f000001:-4cecb39b:585109e2:31",
> "status" => "HEURISTIC_ROLLBACK",
> "type" => "/StateManager/AbstractRecord/ExtendedResourceRecord"
> }}
> }
> }
> }
> }
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-4cecb39b\:585109e2\:28/participants=0\:ffff7f000001\:-4cecb39b\:585109e2\:31:recover
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-4cecb39b\:585109e2\:28/participants=0\:ffff7f000001\:-4cecb39b\:585109e2\:31:read-resource
> {
> "outcome" => "success",
> "result" => {
> "eis-product-name" => "unavailable",
> "eis-product-version" => "unavailable",
> "jmx-name" => undefined,
> "jndi-name" => "0:ffff7f000001:-4cecb39b:585109e2:31",
> "status" => "HEURISTIC_ROLLBACK",
> "type" => "/StateManager/AbstractRecord/ExtendedResourceRecord"
> }
> }
> {code}
> I expect that {{:recover}} put the participant to {{PREPARED}} state and at that point RAR {{XATerminator.commit}} could commit such participant.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (JBTM-2805) Karaf fails to build in CI
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2805?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson reopened JBTM-2805:
---------------------------------
I had to revert this so I could do a release sorry
> Karaf fails to build in CI
> --------------------------
>
> Key: JBTM-2805
> URL: https://issues.jboss.org/browse/JBTM-2805
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Build System
> Reporter: Tom Jenkinson
> Assignee: Amos Feng
>
> We should try to avoid building Karaf in CI.
> At this point it fails to build.
> {code}
> [INFO] --- maven-resources-plugin:2.7:resources (process-resources) @ apache-karaf-minimal ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 4 resources
> [INFO]
> [INFO] --- karaf-maven-plugin:4.1.0-SNAPSHOT:assembly (process-resources) @ apache-karaf-minimal ---
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Karaf ....................................... SUCCESS [ 4.795 s]
> [INFO] Apache Karaf :: JAAS ............................... SUCCESS [ 0.017 s]
> [INFO] Apache Karaf :: JAAS :: Boot ....................... SUCCESS [ 2.413 s]
> [INFO] Apache Karaf :: Util ............................... SUCCESS [ 4.843 s]
> [INFO] Apache Karaf :: Main ............................... SUCCESS [ 11.143 s]
> [INFO] Apache Karaf :: Features ........................... SUCCESS [ 0.012 s]
> [INFO] Apache Karaf :: Features :: Extension .............. SUCCESS [ 0.157 s]
> [INFO] Apache Karaf :: Service ............................ SUCCESS [ 0.012 s]
> [INFO] Apache Karaf :: Service :: Guard ................... SUCCESS [ 8.831 s]
> [INFO] Apache Karaf :: Shell .............................. SUCCESS [ 0.010 s]
> [INFO] Apache Karaf :: Shell :: Core ...................... SUCCESS [ 6.523 s]
> [INFO] Apache Karaf :: Tooling ............................ SUCCESS [ 0.013 s]
> [INFO] Apache Karaf :: Tooling :: Maven Karaf Plugin for Services Metadata SUCCESS [ 58.898 s]
> [INFO] Apache Karaf :: Features :: Core ................... SUCCESS [ 5.522 s]
> [INFO] Apache Karaf :: Features :: Command ................ SUCCESS [ 0.845 s]
> [INFO] Apache Karaf :: KAR :: Core ........................ SUCCESS [ 0.869 s]
> [INFO] Apache Karaf :: JAAS :: Config ..................... SUCCESS [ 7.906 s]
> [INFO] Apache Karaf :: JAAS :: Modules .................... SUCCESS [ 18.313 s]
> [INFO] Apache Karaf :: Bundle ............................. SUCCESS [ 0.009 s]
> [INFO] Apache Karaf :: Bundle :: Core ..................... SUCCESS [ 1.076 s]
> [INFO] Apache Karaf :: Bundle :: BlueprintStateService .... SUCCESS [ 0.095 s]
> [INFO] Apache Karaf :: Bundle :: SpringStateService ....... SUCCESS [ 8.690 s]
> [INFO] Apache Karaf :: ConfigAdmin :: Core ................ SUCCESS [ 0.454 s]
> [INFO] Apache Karaf :: Tooling :: Utils ................... SUCCESS [ 2.911 s]
> [INFO] Apache Karaf :: Deployer ........................... SUCCESS [ 0.007 s]
> [INFO] Apache Karaf :: Deployer :: Blueprint .............. SUCCESS [ 2.328 s]
> [INFO] Apache Karaf :: Deployer :: Spring ................. SUCCESS [ 0.166 s]
> [INFO] Apache Karaf :: Demos :: Profiles :: Registry ...... SUCCESS [ 0.031 s]
> [INFO] Apache Karaf :: Profile :: Core .................... SUCCESS [ 9.123 s]
> [INFO] Apache Karaf :: Instance :: Core ................... SUCCESS [ 1.096 s]
> [INFO] Apache Karaf :: Package :: Core .................... SUCCESS [ 0.316 s]
> [INFO] Apache Karaf :: HTTP :: Core ....................... SUCCESS [ 3.623 s]
> [INFO] Apache Karaf :: Service :: Core .................... SUCCESS [ 0.323 s]
> [INFO] Apache Karaf :: Log :: Core ........................ SUCCESS [ 4.122 s]
> [INFO] Apache Karaf :: Deployer :: Features ............... SUCCESS [ 0.568 s]
> [INFO] Apache Karaf :: Deployer :: Karaf Archive (.kar) ... SUCCESS [ 0.491 s]
> [INFO] Apache Karaf :: Deployer :: Wrap Non OSGi Jar ...... SUCCESS [ 0.100 s]
> [INFO] Apache Karaf :: Shell :: Various Commands .......... SUCCESS [ 0.471 s]
> [INFO] Apache Karaf :: Shell :: Console ................... SUCCESS [ 3.362 s]
> [INFO] Apache Karaf :: Shell :: Table ..................... SUCCESS [ 0.111 s]
> [INFO] Apache Karaf :: Shell :: SSH ....................... SUCCESS [ 2.032 s]
> [INFO] Apache Karaf :: JAAS :: Jasypt Encryption .......... SUCCESS [ 2.921 s]
> [INFO] Apache Karaf :: JAAS :: Command .................... SUCCESS [ 0.492 s]
> [INFO] Apache Karaf :: JAAS :: Blueprint .................. SUCCESS [ 0.007 s]
> [INFO] Apache Karaf :: JAAS :: Blueprint :: Config ........ SUCCESS [ 0.081 s]
> [INFO] Apache Karaf :: JAAS :: Blueprint :: Jasypt ........ SUCCESS [ 1.509 s]
> [INFO] Apache Karaf :: Client ............................. SUCCESS [ 0.164 s]
> [INFO] Apache Karaf :: Management ......................... SUCCESS [ 0.008 s]
> [INFO] Apache Karaf :: Management ......................... SUCCESS [ 0.212 s]
> [INFO] Apache Karaf :: System :: Core ..................... SUCCESS [ 0.329 s]
> [INFO] Apache Karaf :: Web :: Core ........................ SUCCESS [ 0.328 s]
> [INFO] Apache Karaf :: Wrapper :: Core .................... SUCCESS [ 0.667 s]
> [INFO] Apache Karaf :: Web Console ........................ SUCCESS [ 0.007 s]
> [INFO] Apache Karaf :: Web Console :: Console ............. SUCCESS [ 3.205 s]
> [INFO] Apache Karaf :: Web Console :: Features Plugin ..... SUCCESS [ 0.559 s]
> [INFO] Apache Karaf :: Web Console :: Gogo Plugin ......... SUCCESS [ 0.617 s]
> [INFO] Apache Karaf :: Web Console :: HTTP Plugin ......... SUCCESS [ 0.567 s]
> [INFO] Apache Karaf :: Web Console :: Instance Plugin ..... SUCCESS [ 0.224 s]
> [INFO] Apache Karaf :: Exception .......................... SUCCESS [ 0.031 s]
> [INFO] Apache Karaf :: Scheduler :: Core .................. SUCCESS [ 3.628 s]
> [INFO] Apache Karaf :: Declarative Services (DS) .......... SUCCESS [ 0.007 s]
> [INFO] Apache Karaf :: SCR :: Shell Commands .............. SUCCESS [ 3.391 s]
> [INFO] Apache Karaf :: SCR :: Management MBeans ........... SUCCESS [ 1.491 s]
> [INFO] Apache Karaf :: SCR :: Bundle State ................ SUCCESS [ 0.176 s]
> [INFO] Apache Karaf :: SCR :: Examples .................... SUCCESS [ 0.006 s]
> [INFO] Apache Karaf :: SCR :: Examples :: Basic Service ... SUCCESS [ 0.060 s]
> [INFO] Apache Karaf :: SCR :: Examples :: Managed Services SUCCESS [ 0.076 s]
> [INFO] Apache Karaf :: SCR :: Examples :: Component Factories SUCCESS [ 0.063 s]
> [INFO] Apache Karaf :: Diagnostic ......................... SUCCESS [ 0.007 s]
> [INFO] Apache Karaf :: Diagnostic :: Boot ................. SUCCESS [ 0.096 s]
> [INFO] Apache Karaf :: Diagnostic :: Core ................. SUCCESS [ 0.748 s]
> [INFO] Apache Karaf :: OBR :: Core ........................ SUCCESS [ 1.771 s]
> [INFO] Apache Karaf :: JNDI :: Core ....................... SUCCESS [ 1.765 s]
> [INFO] Apache Karaf :: JDBC :: Core ....................... SUCCESS [ 0.410 s]
> [INFO] Apache Karaf :: JMS :: Core ........................ SUCCESS [ 6.591 s]
> [INFO] Apache Karaf :: Features ........................... SUCCESS [ 0.006 s]
> [INFO] Apache Karaf :: JPA :: Parent ...................... SUCCESS [ 0.006 s]
> [INFO] Apache Karaf :: JPA :: Hibernate ................... SUCCESS [ 8.436 s]
> [INFO] Apache Karaf :: OSGi Services :: Coordinator ....... SUCCESS [ 1.763 s]
> [INFO] Apache Karaf :: OSGi Services :: EventAdmin ........ SUCCESS [ 1.511 s]
> [INFO] Apache Karaf :: OSGi Services :: Static ConfigAdmin SUCCESS [ 0.087 s]
> [INFO] Apache Karaf :: OSGi Services ...................... SUCCESS [ 0.006 s]
> [INFO] Apache Karaf :: Subsystem :: Core .................. SUCCESS [ 5.008 s]
> [INFO] Apache Karaf :: OSGi Services :: Event ............. SUCCESS [ 1.709 s]
> [INFO] Apache Karaf :: Tooling :: Maven Karaf Plugin ...... SUCCESS [ 7.875 s]
> [INFO] Apache Karaf :: Assemblies ......................... SUCCESS [ 0.008 s]
> [INFO] Apache Karaf :: Assemblies :: Features ............. SUCCESS [ 0.006 s]
> [INFO] Apache Karaf :: Assemblies :: Features :: Base ..... SUCCESS [ 3.828 s]
> [INFO] Apache Karaf :: Assemblies :: Features :: Framework SUCCESS [ 2.555 s]
> [INFO] Apache Karaf :: Assemblies :: Features :: Static ... SUCCESS [ 1.836 s]
> [INFO] Apache Karaf :: Assemblies :: Features :: Standard . SUCCESS [01:12 min]
> [INFO] Apache Karaf :: Assemblies :: Features :: Spring ... SUCCESS [01:19 min]
> [INFO] Apache Karaf :: Assemblies :: Features :: Enterprise SUCCESS [ 42.574 s]
> [INFO] Apache Karaf :: Assemblies :: Demos ................ SUCCESS [ 0.075 s]
> [INFO] Apache Karaf :: Assemblies :: Minimal Distribution . FAILURE [ 0.097 s]
> [INFO] Apache Karaf :: Assemblies :: Default Distribution . SKIPPED
> [INFO] Apache Karaf :: Demos .............................. SKIPPED
> [INFO] Apache Karaf :: Demos :: Web ....................... SKIPPED
> [INFO] Apache Karaf :: Demos :: Branding :: Shell ......... SKIPPED
> [INFO] Apache Karaf :: Demos :: Command :: Extend Console . SKIPPED
> [INFO] Apache Karaf :: Demos :: Demo Dump provider ........ SKIPPED
> [INFO] Apache Karaf :: Demos :: Deployer .................. SKIPPED
> [INFO] Apache Karaf :: Demos :: Deployer :: Kar ........... SKIPPED
> [INFO] Apache Karaf :: Demos :: Deployer :: Bundle ........ SKIPPED
> [INFO] Apache Karaf :: Demos :: Profiles :: Dynamic Assembly SKIPPED
> [INFO] Apache Karaf :: Demos :: Profiles :: Static Assembly SKIPPED
> [INFO] Apache Karaf :: Demos :: Profiles .................. SKIPPED
> [INFO] Apache Karaf :: Archetypes ......................... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Assembly Archetype ... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Command Archetype .... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Feature Archetype .... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Kar Archetype ........ SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Bundle Archetype ..... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Blueprint Archetype .. SKIPPED
> [INFO] Apache Karaf :: Integration Tests .................. SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 07:17 min
> [INFO] Finished at: 2016-11-29T00:19:34+00:00
> [INFO] Final Memory: 165M/1003M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:assembly (process-resources) on project apache-karaf-minimal: Unable to parse configuration of mojo org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:assembly for parameter pidsToExtract: Cannot assign configuration entry 'pidsToExtract' with value '!jmx.acl.*,
> [ERROR] !org.apache.karaf.command.acl.*,
> [ERROR] *' of type java.lang.String to property of type java.util.List
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginConfigurationExcep...
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :apache-karaf-minimal
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (JBTM-2821) Improve tooling documentation about clearing heuristics
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2821?page=com.atlassian.jira.plugin.... ]
Issue was automatically transitioned when Michael Musgrove created pull request #43 in GitHub
---------------------------------------------------------------------------------------------
Status: Pull Request Sent (was: Open)
> Improve tooling documentation about clearing heuristics
> -------------------------------------------------------
>
> Key: JBTM-2821
> URL: https://issues.jboss.org/browse/JBTM-2821
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: Documentation
> Affects Versions: 5.4.0.Final
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.next
>
>
> The tooling will only allow heuristics to be cleared if the are of type heuristic mixed or heuristic hazard. This is because for the other types (heuristic rollaback./commit) it is too late to reattempt commit. The documentation should clarify that this is the behaviour of the clearHeuristic operation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (JBTM-2819) Recover operation does not work for participant of JCA type transactions
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2819?page=com.atlassian.jira.plugin.... ]
Issue was automatically transitioned when Michael Musgrove created pull request #43 in GitHub
---------------------------------------------------------------------------------------------
Status: Pull Request Sent (was: Open)
> Recover operation does not work for participant of JCA type transactions
> ------------------------------------------------------------------------
>
> Key: JBTM-2819
> URL: https://issues.jboss.org/browse/JBTM-2819
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Affects Versions: 5.4.0.Final
> Reporter: Ondra Chaloupka
> Assignee: Michael Musgrove
> Attachments: heuristic-rollback-objectstore.zip
>
>
> Jboss cli {{:recover}} operation does not work when having JCA type transaction. My test shows following
> {code}
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store:probe
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store:read-resource(recursive=true)
> {
> "outcome" => "success",
> "result" => {
> "expose-all-logs" => false,
> "type" => "default",
> "transactions" => {
> "0:ffff7f000001:-4cecb39b:585109e2:31" => {
> "age-in-seconds" => undefined,
> "id" => "0:ffff7f000001:-4cecb39b:585109e2:31",
> "jmx-name" => undefined,
> "type" => "CosTransactions/XAResourceRecord",
> "participants" => undefined
> },
> "0:ffff7f000001:-4cecb39b:585109e2:28" => {
> "age-in-seconds" => "1481798762",
> "id" => "0:ffff7f000001:-4cecb39b:585109e2:28",
> "jmx-name" => undefined,
> "type" => "StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple/ServerTransaction/JCA",
> "participants" => {"0:ffff7f000001:-4cecb39b:585109e2:31" => {
> "eis-product-name" => "unavailable",
> "eis-product-version" => "unavailable",
> "jmx-name" => undefined,
> "jndi-name" => "0:ffff7f000001:-4cecb39b:585109e2:31",
> "status" => "HEURISTIC_ROLLBACK",
> "type" => "/StateManager/AbstractRecord/ExtendedResourceRecord"
> }}
> }
> }
> }
> }
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-4cecb39b\:585109e2\:28/participants=0\:ffff7f000001\:-4cecb39b\:585109e2\:31:recover
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-4cecb39b\:585109e2\:28/participants=0\:ffff7f000001\:-4cecb39b\:585109e2\:31:read-resource
> {
> "outcome" => "success",
> "result" => {
> "eis-product-name" => "unavailable",
> "eis-product-version" => "unavailable",
> "jmx-name" => undefined,
> "jndi-name" => "0:ffff7f000001:-4cecb39b:585109e2:31",
> "status" => "HEURISTIC_ROLLBACK",
> "type" => "/StateManager/AbstractRecord/ExtendedResourceRecord"
> }
> }
> {code}
> I expect that {{:recover}} put the participant to {{PREPARED}} state and at that point RAR {{XATerminator.commit}} could commit such participant.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (JBTM-2821) Improve tooling documentation about clearing heuristics
by Michael Musgrove (JIRA)
Michael Musgrove created JBTM-2821:
--------------------------------------
Summary: Improve tooling documentation about clearing heuristics
Key: JBTM-2821
URL: https://issues.jboss.org/browse/JBTM-2821
Project: JBoss Transaction Manager
Issue Type: Enhancement
Components: Documentation
Affects Versions: 5.4.0.Final
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Priority: Minor
Fix For: 5.next
The tooling will only allow heuristics to be cleared if the are of type heuristic mixed or heuristic hazard. This is because for the other types (heuristic rollaback./commit) it is too late to reattempt commit. The documentation should clarify that this is the behaviour of the clearHeuristic operation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (JBTM-2785) Provide a tooling operation to suspend/resume the recovery manager
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2785?page=com.atlassian.jira.plugin.... ]
Michael Musgrove closed JBTM-2785.
----------------------------------
Resolution: Rejected
Rejecting since we have not seen this as an issue and there is no test case that would highlight the problem.
> Provide a tooling operation to suspend/resume the recovery manager
> ------------------------------------------------------------------
>
> Key: JBTM-2785
> URL: https://issues.jboss.org/browse/JBTM-2785
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: Tooling
> Affects Versions: 5.3.5.Final
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
>
> Some tooling operations update the state of transaction log records and these updates could interfere with what the recovery manager is doing. Tooling updates should pause the recovery manager prior to performing such updates. Since tooling and recovery can run in different JVMs we need an MBean operation to suspend/resume the recovery manager to protect against this scenario.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (JBTM-2819) Recover operation does not work for participant of JCA type transactions
by Ondra Chaloupka (JIRA)
[ https://issues.jboss.org/browse/JBTM-2819?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka commented on JBTM-2819:
---------------------------------------
I see. Well, this is an issue of test. Nevertheless documenting behavior would be fine :) but you can reject this one.
I have to admit that I overlooked the consequences of the participant's heuristic rollback state. Part of the reason was that the JTA implementation works differently [1] - it ends with in heuristic mixed state. May I consider this as different behavior for "jta style" transactions and correct for jta and jts? It seems to me that transaction itself is with type heuristic mixed but the participant is with heuristic rollback. But jta does not save type directly to participant but its state is delivered from transaction type. Am I at lest partly right here?
Thank you
{code}
[standalone@localhost:42042 /] /subsystem=transactions/log-store=log-store:read-resource(recursive=true, include-runtime=true)
{
"outcome" => "success",
"result" => {
"expose-all-logs" => false,
"type" => "default",
"transactions" => {"0:ffff7f000001:9a556c9:5853b579:15" => {
"age-in-seconds" => "29",
"id" => "0:ffff7f000001:9a556c9:5853b579:15",
"jmx-name" => undefined,
"type" => "StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/SubordinateAtomicAction/JCA",
"participants" => {"java:/TestXAResource-48" => {
"eis-product-name" => "Crash Recovery Test",
"eis-product-version" => "EAP Test",
"jmx-name" => undefined,
"jndi-name" => "java:/TestXAResource-48",
"status" => "HEURISTIC",
"type" => "/StateManager/AbstractRecord/XAResourceRecord"
}}
}}
}
}
{code}
> Recover operation does not work for participant of JCA type transactions
> ------------------------------------------------------------------------
>
> Key: JBTM-2819
> URL: https://issues.jboss.org/browse/JBTM-2819
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Affects Versions: 5.4.0.Final
> Reporter: Ondra Chaloupka
> Assignee: Michael Musgrove
> Attachments: heuristic-rollback-objectstore.zip
>
>
> Jboss cli {{:recover}} operation does not work when having JCA type transaction. My test shows following
> {code}
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store:probe
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store:read-resource(recursive=true)
> {
> "outcome" => "success",
> "result" => {
> "expose-all-logs" => false,
> "type" => "default",
> "transactions" => {
> "0:ffff7f000001:-4cecb39b:585109e2:31" => {
> "age-in-seconds" => undefined,
> "id" => "0:ffff7f000001:-4cecb39b:585109e2:31",
> "jmx-name" => undefined,
> "type" => "CosTransactions/XAResourceRecord",
> "participants" => undefined
> },
> "0:ffff7f000001:-4cecb39b:585109e2:28" => {
> "age-in-seconds" => "1481798762",
> "id" => "0:ffff7f000001:-4cecb39b:585109e2:28",
> "jmx-name" => undefined,
> "type" => "StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple/ServerTransaction/JCA",
> "participants" => {"0:ffff7f000001:-4cecb39b:585109e2:31" => {
> "eis-product-name" => "unavailable",
> "eis-product-version" => "unavailable",
> "jmx-name" => undefined,
> "jndi-name" => "0:ffff7f000001:-4cecb39b:585109e2:31",
> "status" => "HEURISTIC_ROLLBACK",
> "type" => "/StateManager/AbstractRecord/ExtendedResourceRecord"
> }}
> }
> }
> }
> }
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-4cecb39b\:585109e2\:28/participants=0\:ffff7f000001\:-4cecb39b\:585109e2\:31:recover
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=transactions/log-store=log-store/transactions=0\:ffff7f000001\:-4cecb39b\:585109e2\:28/participants=0\:ffff7f000001\:-4cecb39b\:585109e2\:31:read-resource
> {
> "outcome" => "success",
> "result" => {
> "eis-product-name" => "unavailable",
> "eis-product-version" => "unavailable",
> "jmx-name" => undefined,
> "jndi-name" => "0:ffff7f000001:-4cecb39b:585109e2:31",
> "status" => "HEURISTIC_ROLLBACK",
> "type" => "/StateManager/AbstractRecord/ExtendedResourceRecord"
> }
> }
> {code}
> I expect that {{:recover}} put the participant to {{PREPARED}} state and at that point RAR {{XATerminator.commit}} could commit such participant.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months