[JBoss JIRA] (JBTM-2592) Incorrect warning messaging in ShadowingStore
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2592?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson reopened JBTM-2592:
---------------------------------
> Incorrect warning messaging in ShadowingStore
> ---------------------------------------------
>
> Key: JBTM-2592
> URL: https://issues.jboss.org/browse/JBTM-2592
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Transaction Core
> Affects Versions: 5.2.11.Final
> Reporter: Mark Little
> Assignee: Mark Little
> Priority: Minor
>
> warn_objectstore_ShadowingStore_6 currently says ...
> "ShadowingStore::read_state() - no type name given for object state"
> ... when in fact the else clause is triggered when the state isn't committed or uncommitted (typically when it's unknown and the state doesn't exist).
> I'm not sure when this warning message was added because it wasn't there in JBossTS 4.8 or 4.15.3.
> I'm going to fix this issue (the text). I'll create a separate issue because I think this should be info not warning.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 12 months
[JBoss JIRA] (JBTM-2592) Incorrect warning messaging in ShadowingStore
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2592?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2592:
--------------------------------
Fix Version/s: 5.next
> Incorrect warning messaging in ShadowingStore
> ---------------------------------------------
>
> Key: JBTM-2592
> URL: https://issues.jboss.org/browse/JBTM-2592
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Transaction Core
> Affects Versions: 5.2.11.Final
> Reporter: Mark Little
> Assignee: Mark Little
> Priority: Minor
> Fix For: 5.next
>
>
> warn_objectstore_ShadowingStore_6 currently says ...
> "ShadowingStore::read_state() - no type name given for object state"
> ... when in fact the else clause is triggered when the state isn't committed or uncommitted (typically when it's unknown and the state doesn't exist).
> I'm not sure when this warning message was added because it wasn't there in JBossTS 4.8 or 4.15.3.
> I'm going to fix this issue (the text). I'll create a separate issue because I think this should be info not warning.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 12 months
[JBoss JIRA] (JBTM-2592) Incorrect warning messaging in ShadowingStore
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2592?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2592.
-------------------------------
Resolution: Done
> Incorrect warning messaging in ShadowingStore
> ---------------------------------------------
>
> Key: JBTM-2592
> URL: https://issues.jboss.org/browse/JBTM-2592
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Transaction Core
> Affects Versions: 5.2.11.Final
> Reporter: Mark Little
> Assignee: Mark Little
> Priority: Minor
> Fix For: 5.next
>
>
> warn_objectstore_ShadowingStore_6 currently says ...
> "ShadowingStore::read_state() - no type name given for object state"
> ... when in fact the else clause is triggered when the state isn't committed or uncommitted (typically when it's unknown and the state doesn't exist).
> I'm not sure when this warning message was added because it wasn't there in JBossTS 4.8 or 4.15.3.
> I'm going to fix this issue (the text). I'll create a separate issue because I think this should be info not warning.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 12 months
[JBoss JIRA] (JBTM-2591) WildFly quick start example fails to build
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2591?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-2591:
-------------------------------------
I linked in a PR
> 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: 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, 12 months
[JBoss JIRA] (JBTM-2591) WildFly quick start example fails to build
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2591?page=com.atlassian.jira.plugin.... ]
Issue was automatically transitioned when Tom Jenkinson created pull request #157 in GitHub
-------------------------------------------------------------------------------------------
Status: Pull Request Sent (was: Open)
> 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: 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, 12 months
[JBoss JIRA] (JBTM-2591) WildFly quick start example fails to build
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2591?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2591:
--------------------------------
Component/s: (was: Application Server Integration)
> 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: 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, 12 months
[JBoss JIRA] (JBTM-2595) TransactionalDriver consuming all database connections
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2595?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2595:
--------------------------------
Component/s: Transactional Driver
> 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, Transactional Driver
> 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, 12 months