May 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2897) Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2897?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2897: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2897 > URL: https://issues.jboss.org/browse/JBTM-2897 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.next > > > If trace logging is enabled then call on {{com.arjuna.ats.internal.jta.transaction.jts.TransactionImple#registerSynchronization}} is done with {{null}} in parameter then {{NullPointerException}} is thrown but {{SystemException}} should be thrown in such case. > https://github.com/jbosstm/narayana/blob/930bd7f17f1b0cc2b8529eaa2ae1fcac... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2889) Include a vertx with STM quickstart

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2889?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2889: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Include a vertx with STM quickstart > ----------------------------------- > > Key: JBTM-2889 > URL: https://issues.jboss.org/browse/JBTM-2889 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, STM > Affects Versions: 5.5.24.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > It would be useful to include a quickstart that shows how to use STM with vertx -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2885) Orphan detection may attempt to rollback orphan if resource fails to return values

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2885?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2885: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Orphan detection may attempt to rollback orphan if resource fails to return values > ---------------------------------------------------------------------------------- > > Key: JBTM-2885 > URL: https://issues.jboss.org/browse/JBTM-2885 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Optional > Fix For: 5.next > > > If the XAR returns a Xid from recover(FIRST_PASS) to XARM but then goes offline for a cycle we may attempt to rollback the Xid thinking it is stale. If the XAR returns an XAE at that point we should clear the _xidScans so we pick it up next time. > However, there is a filter that checks for transaction state (JTATransactionLogXAResourceOrphanFilter) which would detect a transaction log and ignore this Xid so adding this protection would only be considered belt-and-braces. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2865) Cache store can get an NPE as work is written to outside of _workList lock

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2865?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2865: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Cache store can get an NPE as work is written to outside of _workList lock > -------------------------------------------------------------------------- > > Key: JBTM-2865 > URL: https://issues.jboss.org/browse/JBTM-2865 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > {code} > java.lang.NullPointerException > at com.arjuna.ats.internal.arjuna.objectstore.AsyncStore.getState(CacheStore.java:579) > at com.arjuna.ats.internal.arjuna.objectstore.CacheStore.read_state(CacheStore.java:130) > at com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.read_state_internal(FileSystemStore.java:331) > at com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.read_committed(FileSystemStore.java:103) > at com.hp.mwtests.ts.arjuna.objectstore.ThreadWriter.run(CachedTest.java:69) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2896) Invalid warning when committing STM optimistic records

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2896?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2896: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Invalid warning when committing STM optimistic records > ------------------------------------------------------ > > Key: JBTM-2896 > URL: https://issues.jboss.org/browse/JBTM-2896 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.5.24.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > There is some code in OptimisticLockRecord#topLevelCommit that generates an invalid warning > bq. WARN: ARJUNA015051: OptimisticLockRecord.topLevelCommit state check failed for org.jboss.stm.internal.proxy.OptimisticLockManagerProxy@7f058cfa will force rollback. > when in fact there is no rollback. The offending code is: > {code} > public int topLevelCommit () > { > boolean stateOK = checkState(); > > if (stateOK) > { > txojLogger.i18NLogger.warn_OptimisticLockRecord_2((LockManager) value()); > } > {code} > The condition was intended to be if (!stateOK) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2766) Allow Transactional Driver to be used with commons-dbcp in Tomcat

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2766?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2766: -------------------------------- Fix Version/s: 5.next > Allow Transactional Driver to be used with commons-dbcp in Tomcat > ----------------------------------------------------------------- > > Key: JBTM-2766 > URL: https://issues.jboss.org/browse/JBTM-2766 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.next > > > Transactional driver does not provide connection pooling but commons-dbcp (as used in Tomcat) does. We should test it and provide a demonstration and blog post of its usage. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2900) Byteman fails to start on IBM JDK (quickstart)

by Anonymous (JIRA)

[ https://issues.jboss.org/browse/JBTM-2900?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when istraka created pull request #197 in GitHub ------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Byteman fails to start on IBM JDK (quickstart) > ---------------------------------------------- > > Key: JBTM-2900 > URL: https://issues.jboss.org/browse/JBTM-2900 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.5.24.Final > Reporter: Ivan Straka > Assignee: Ivan Straka > Priority: Minor > > Byteman fails to start on IBM JDK for jta-and-hibernate-standalone quickstart. > output: > {code:java} > Running org.jboss.narayana.quickstart.jta.TestCase > byteman jar is /home/hudson/.m2/repository/org/jboss/byteman/byteman/3.0.3/byteman-3.0.3.jar > *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 > Setting org.jboss.byteman.allow.config.update=true > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:508) > at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:408) > at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(InstrumentationImpl.java:433) > at com.ibm.tools.attach.javaSE.Attachment.loadAgentLibraryImpl(Native Method) > at com.ibm.tools.attach.javaSE.Attachment.loadAgentLibrary(Attachment.java:309) > at com.ibm.tools.attach.javaSE.Attachment.parseLoadAgent(Attachment.java:287) > at com.ibm.tools.attach.javaSE.Attachment.doCommand(Attachment.java:168) > at com.ibm.tools.attach.javaSE.Attachment.run(Attachment.java:128) > Caused by: java.lang.UnsupportedOperationException: adding retransformable transformers is not supported in this environment > at sun.instrument.InstrumentationImpl.addTransformer(InstrumentationImpl.java:100) > Exception in thread "Attachment 45368" Agent failed to start! > at org.jboss.byteman.agent.Main.premain(Main.java:275) > at org.jboss.byteman.agent.Main.agentmain(Main.java:305) > ... 11 more > JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2900) Byteman fails to start on IBM JDK (quickstart)

by Ivan Straka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2900?page=com.atlassian.jira.plugin.... ] Work on JBTM-2900 started by Ivan Straka. ----------------------------------------- > Byteman fails to start on IBM JDK (quickstart) > ---------------------------------------------- > > Key: JBTM-2900 > URL: https://issues.jboss.org/browse/JBTM-2900 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.5.24.Final > Reporter: Ivan Straka > Assignee: Ivan Straka > Priority: Minor > > Byteman fails to start on IBM JDK for jta-and-hibernate-standalone quickstart. > output: > {code:java} > Running org.jboss.narayana.quickstart.jta.TestCase > byteman jar is /home/hudson/.m2/repository/org/jboss/byteman/byteman/3.0.3/byteman-3.0.3.jar > *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 > Setting org.jboss.byteman.allow.config.update=true > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:508) > at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:408) > at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(InstrumentationImpl.java:433) > at com.ibm.tools.attach.javaSE.Attachment.loadAgentLibraryImpl(Native Method) > at com.ibm.tools.attach.javaSE.Attachment.loadAgentLibrary(Attachment.java:309) > at com.ibm.tools.attach.javaSE.Attachment.parseLoadAgent(Attachment.java:287) > at com.ibm.tools.attach.javaSE.Attachment.doCommand(Attachment.java:168) > at com.ibm.tools.attach.javaSE.Attachment.run(Attachment.java:128) > Caused by: java.lang.UnsupportedOperationException: adding retransformable transformers is not supported in this environment > at sun.instrument.InstrumentationImpl.addTransformer(InstrumentationImpl.java:100) > Exception in thread "Attachment 45368" Agent failed to start! > at org.jboss.byteman.agent.Main.premain(Main.java:275) > at org.jboss.byteman.agent.Main.agentmain(Main.java:305) > ... 11 more > JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2900) Byteman fails to start on IBM JDK (quickstart)

by Ivan Straka (JIRA)

Ivan Straka created JBTM-2900: --------------------------------- Summary: Byteman fails to start on IBM JDK (quickstart) Key: JBTM-2900 URL: https://issues.jboss.org/browse/JBTM-2900 Project: JBoss Transaction Manager Issue Type: Bug Affects Versions: 5.5.24.Final Reporter: Ivan Straka Assignee: Ivan Straka Priority: Minor Byteman fails to start on IBM JDK for jta-and-hibernate-standalone quickstart. output: {code:java} Running org.jboss.narayana.quickstart.jta.TestCase byteman jar is /home/hudson/.m2/repository/org/jboss/byteman/byteman/3.0.3/byteman-3.0.3.jar *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 Setting org.jboss.byteman.allow.config.update=true java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:508) at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:408) at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(InstrumentationImpl.java:433) at com.ibm.tools.attach.javaSE.Attachment.loadAgentLibraryImpl(Native Method) at com.ibm.tools.attach.javaSE.Attachment.loadAgentLibrary(Attachment.java:309) at com.ibm.tools.attach.javaSE.Attachment.parseLoadAgent(Attachment.java:287) at com.ibm.tools.attach.javaSE.Attachment.doCommand(Attachment.java:168) at com.ibm.tools.attach.javaSE.Attachment.run(Attachment.java:128) Caused by: java.lang.UnsupportedOperationException: adding retransformable transformers is not supported in this environment at sun.instrument.InstrumentationImpl.addTransformer(InstrumentationImpl.java:100) Exception in thread "Attachment 45368" Agent failed to start! at org.jboss.byteman.agent.Main.premain(Main.java:275) at org.jboss.byteman.agent.Main.agentmain(Main.java:305) ... 11 more JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2893) JTS subordinate transaction could check Xid format during enlistment to allow it being edited

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2893?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2893: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > JTS subordinate transaction could check Xid format during enlistment to allow it being edited > --------------------------------------------------------------------------------------------- > > Key: JBTM-2893 > URL: https://issues.jboss.org/browse/JBTM-2893 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > When a subordinate transaction created by Narayana is imported in JTS it's capable to correctly handle only one XAResource being enlisted. When two or more resources are enlisted they all contain the same Xid. That Xid came from what {{TransactionImple}} defines (here is call which is never reached by such txn code: https://github.com/jbosstm/narayana/blob/a8f8df24d6531e6ba83cc3746ce05fc3...) > That behavior is fine when txn is imported from EIS but when is managed by Narayana it should not be problem to generate Xids for each XAResource unique. > That behavior makes the issue when recovery should be part of handling. All the resources are "merged" under one record in object log store. That way can't be recovered correctly. > This handling is "fixed" in JTA (see https://github.com/jbosstm/narayana/blob/a8f8df24d6531e6ba83cc3746ce05fc3...) where format of xid is checked when enlistment happens. Such thing could be passed to JTS mode too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues May 2017