[JBoss JIRA] (JBTM-2596) TxCore or ArjunaCore in docs?
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-2596?page=com.atlassian.jira.plugin.... ]
Mark Little closed JBTM-2596.
-----------------------------
Resolution: Done
> TxCore or ArjunaCore in docs?
> -----------------------------
>
> Key: JBTM-2596
> URL: https://issues.jboss.org/browse/JBTM-2596
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Documentation
> Affects Versions: 5.2.11.Final
> Reporter: Mark Little
> Assignee: Mark Little
>
> The original core transaction module was called Arjuna. Then years ago we changed it to ArjunaCore. Then we changed it to TxCore, though didn't change the docs consistently or the Java package structure. Then TxCore became confusing and conflicted with other uses elsewhere (e.g., Microsoft) so we reverted to ArjunaCore (blogs, docs etc.) But once again, not consistently. Fix the docs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBTM-2596) TxCore or ArjunaCore in docs?
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-2596?page=com.atlassian.jira.plugin.... ]
Mark Little commented on JBTM-2596:
-----------------------------------
Changed TxCore to ArjunaCore in the docs. Haven't changed the names of various xml files or file names for images, which still refer to txcore, but those are probably not so important since most people don't see them.
> TxCore or ArjunaCore in docs?
> -----------------------------
>
> Key: JBTM-2596
> URL: https://issues.jboss.org/browse/JBTM-2596
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Documentation
> Affects Versions: 5.2.11.Final
> Reporter: Mark Little
> Assignee: Mark Little
>
> The original core transaction module was called Arjuna. Then years ago we changed it to ArjunaCore. Then we changed it to TxCore, though didn't change the docs consistently or the Java package structure. Then TxCore became confusing and conflicted with other uses elsewhere (e.g., Microsoft) so we reverted to ArjunaCore (blogs, docs etc.) But once again, not consistently. Fix the docs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBTM-2596) TxCore or ArjunaCore in docs?
by Mark Little (JIRA)
Mark Little created JBTM-2596:
---------------------------------
Summary: TxCore or ArjunaCore in docs?
Key: JBTM-2596
URL: https://issues.jboss.org/browse/JBTM-2596
Project: JBoss Transaction Manager
Issue Type: Task
Components: Documentation
Affects Versions: 5.2.11.Final
Reporter: Mark Little
Assignee: Mark Little
The original core transaction module was called Arjuna. Then years ago we changed it to ArjunaCore. Then we changed it to TxCore, though didn't change the docs consistently or the Java package structure. Then TxCore became confusing and conflicted with other uses elsewhere (e.g., Microsoft) so we reverted to ArjunaCore (blogs, docs etc.) But once again, not consistently. Fix the docs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBTM-2596) TxCore or ArjunaCore in docs?
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-2596?page=com.atlassian.jira.plugin.... ]
Work on JBTM-2596 started by Mark Little.
-----------------------------------------
> TxCore or ArjunaCore in docs?
> -----------------------------
>
> Key: JBTM-2596
> URL: https://issues.jboss.org/browse/JBTM-2596
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Documentation
> Affects Versions: 5.2.11.Final
> Reporter: Mark Little
> Assignee: Mark Little
>
> The original core transaction module was called Arjuna. Then years ago we changed it to ArjunaCore. Then we changed it to TxCore, though didn't change the docs consistently or the Java package structure. Then TxCore became confusing and conflicted with other uses elsewhere (e.g., Microsoft) so we reverted to ArjunaCore (blogs, docs etc.) But once again, not consistently. Fix the docs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBTM-2595) TransactionalDriver consuming all database connections
by Karsten Ohme (JIRA)
Karsten Ohme created JBTM-2595:
----------------------------------
Summary: TransactionalDriver consuming all database connections
Key: JBTM-2595
URL: https://issues.jboss.org/browse/JBTM-2595
Project: JBoss Transaction Manager
Issue Type: Bug
Components: JTA
Affects Versions: 5.2.11.Final
Environment: Windows 7, Java 8, Spring 4.1.7, Hibernate 5.0.1, PostgreSQL
Reporter: Karsten Ohme
I'm using Narayana in a Spring / Hibernate Set Up for running a distributed Infinispan cache. During the start up of the application Spring Security is fetching several access control entries from the database. These are several hundred requests. The TransactionManager is creating always a new connection and I can see in the PostgreSQL console that all connections are used up until PostgreSQL is not allowing any connections anymore.
What is needed is a blocking feature. I think Apache DBCP has something like this and is blocking calls until connections are available again.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBTM-2591) WildFly quick start example fails to build
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-2591?page=com.atlassian.jira.plugin.... ]
Mark Little commented on JBTM-2591:
-----------------------------------
Except it works fine with 5.2.9.Final and the pom.xml references 5.2.12.Final-SNAPSHOT
<dependency>
<groupId>org.jboss.narayana.jta</groupId>
<artifactId>jta</artifactId>
<version>5.2.12.Final-SNAPSHOT</version>
<scope>provided</scope>
</dependency>
I think the README.md does need updating somehow though, because it says "You will need a WildFly server" and then just says to do a maven build, presumably with the pom.xml that's in the example. Which doesn't work. So something needs changing :)
> WildFly quick start example fails to build
> ------------------------------------------
>
> Key: JBTM-2591
> URL: https://issues.jboss.org/browse/JBTM-2591
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Application Server Integration, Demonstrator
> Affects Versions: 5.2.11.Final
> Reporter: Mark Little
> Assignee: Amos Feng
>
> Trying to build the example here ...
> https://github.com/jbosstm/quickstart/tree/master/wildfly/setCheckedActio...
> The pom refers to a version of JTA that isn't in the repo, so it fails.
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 19.553 s
> [INFO] Finished at: 2015-12-24T15:30:31+00:00
> [INFO] Final Memory: 8M/149M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal on project setCheckedActionFactoryExample: Could not resolve dependencies for project org.jboss.narayana:setCheckedActionFactoryExample:war:0.0.1-SNAPSHOT: Could not find artifact org.jboss.narayana.jta:jta:jar:5.2.12.Final-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) -> [Help 1]
> Changing to 5.2.9.Final at least lets the example build (and hopefully run).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBTM-2591) WildFly quick start example fails to build
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-2591?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-2591:
---------------------------------
I think it needs to build the narayana 5.2.12.Final-SNAPSHOT at first. We maybe emphasis this in the README.md.
> WildFly quick start example fails to build
> ------------------------------------------
>
> Key: JBTM-2591
> URL: https://issues.jboss.org/browse/JBTM-2591
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Application Server Integration, Demonstrator
> Affects Versions: 5.2.11.Final
> Reporter: Mark Little
> Assignee: Amos Feng
>
> Trying to build the example here ...
> https://github.com/jbosstm/quickstart/tree/master/wildfly/setCheckedActio...
> The pom refers to a version of JTA that isn't in the repo, so it fails.
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 19.553 s
> [INFO] Finished at: 2015-12-24T15:30:31+00:00
> [INFO] Final Memory: 8M/149M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal on project setCheckedActionFactoryExample: Could not resolve dependencies for project org.jboss.narayana:setCheckedActionFactoryExample:war:0.0.1-SNAPSHOT: Could not find artifact org.jboss.narayana.jta:jta:jar:5.2.12.Final-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) -> [Help 1]
> Changing to 5.2.9.Final at least lets the example build (and hopefully run).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBTM-2593) Suggest making this read_state INFO not WARN
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-2593?page=com.atlassian.jira.plugin.... ]
Mark Little commented on JBTM-2593:
-----------------------------------
OK, so rather than remove this and revert back to what we had for 20+ years, I've made it a trace. There may have been a reason why it was needed, e.g., debugging? Would be good for someone to link any related issues here for the future.
> Suggest making this read_state INFO not WARN
> --------------------------------------------
>
> Key: JBTM-2593
> URL: https://issues.jboss.org/browse/JBTM-2593
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Transaction Core
> Affects Versions: 5.2.11.Final
> Reporter: Mark Little
> Assignee: Mark Little
> Priority: Minor
>
> I'm not sure why it was added or why it's a warning. Maybe should be info or debug?
> read_state operation, ShadowingStore_6
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months