October 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1473) Update "wsat-jta-multi_hop" quickstart to use new APIs

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1473?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1473: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/100 > Update "wsat-jta-multi_hop" quickstart to use new APIs > ------------------------------------------------------ > > Key: JBTM-1473 > URL: https://issues.jboss.org/browse/JBTM-1473 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator, TxBridge, TXFramework, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.Final > > > And move out of the legacy-api folder as they are no longer legacy. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1474) Update "wsat-jta-multi_service" quickstart to use new APIs

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1474?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1474: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/99 > Update "wsat-jta-multi_service" quickstart to use new APIs > ---------------------------------------------------------- > > Key: JBTM-1474 > URL: https://issues.jboss.org/browse/JBTM-1474 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator, TxBridge, TXFramework, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.Final > > > And move out of the legacy-api folder as they are no longer legacy. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1925) Enable remote debugger in JBossAS/WildFly for all tests

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1925?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1925: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Enable remote debugger in JBossAS/WildFly for all tests > ------------------------------------------------------- > > Key: JBTM-1925 > URL: https://issues.jboss.org/browse/JBTM-1925 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 4.17.13, 5.0.0.Final > > > We need to enable the debugger in all arquillian.xml files. To do this: > 1. Add this to each arquillian.xml: > {code} > <configuration> > <property name="javaVmArguments">${server.jvm.args}</property> > .... > </configuration> > {code} > 2. Update the server.jvm.args in each maven profile for running the Arquillian tests: > {code} > <server.jvm.args>..... ${jvm.args.debug}</server.jvm.args> > {code} > Look at the XTS/localjunit/pom.xml for an example. You will notice that not all Arquillian profiles configure the server.jvm.args. In which case you will need to add the config to match the others. > 3. Add this property to the root pom,xml: > {code} > <jvm.args.debug>-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n</jvm.args.debug> > {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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1968) Add possibility to parametrize qa jts tests running with JDBC Object Store

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-1968?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka updated JBTM-1968: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/493, https://github.com/jbosstm/narayana/pull/486 > Add possibility to parametrize qa jts tests running with JDBC Object Store > -------------------------------------------------------------------------- > > Key: JBTM-1968 > URL: https://issues.jboss.org/browse/JBTM-1968 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 4.17.10 > Reporter: Ondřej Chaloupka > Assignee: Ondřej Chaloupka > Fix For: 4.17.13, 5.0.0.Final > > > Current ant configuration is hardcoded and there is no possibility to parametrize db properties to get test running against different databases. > Rework the qa/run-tests.xml file to add such functionality. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1972) JBAS014134: EJB Invocation failed

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1972?page=com.atlassian.jira.plugin.... ] Michael Musgrove closed JBTM-1972. ---------------------------------- Resolution: Rejected JIRA is not the appropriate place to ask this question. Please can you raise it via the forums at http://www.jboss.org/ejb3 > JBAS014134: EJB Invocation failed > --------------------------------- > > Key: JBTM-1972 > URL: https://issues.jboss.org/browse/JBTM-1972 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: THIRUPATHIREDDY VAJJALA > Assignee: Tom Jenkinson > > i'm trying to call the method of stateful session bean , proxy bean i'm saving on session for to maintain state and to get same instance . > and i have given @StatefulTimeout as 30 sec . after that i'm trying to call proxy from session. i can able to catch error but console it is printing error how to stop this. > ERROR [org.jboss.as.ejb3.invocation] (http-localhost/127.0.0.1:8080-5) JBAS014134: EJB Invocation failed on component OrderServiceBean for method public abstract void com.triabeauty.enterprise.service.endpoint.local.OrderService.placeOrder(): javax.ejb.NoSuchEJBException: JBAS014300: Could not find EJB with id {[-125, -35, -121, 33, -97, -28, 75, -14, -89, -37, -50, -41, 90, 124, 77, -17]} > at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:63) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:315) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:214) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] > at org.jboss.as.ee -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1963) Automatically added TXBridge handler should be optional

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1963?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1963: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Automatically added TXBridge handler should be optional > ------------------------------------------------------- > > Key: JBTM-1963 > URL: https://issues.jboss.org/browse/JBTM-1963 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Application Server Integration, TxBridge > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.Final > > > XTS subsystem automatically adds XTS and TXBridge handlers if the deployment has a class annotated with @WebService and @Transactional. However, TXBridge handler required the WS-AT transaction to be available for every request. If the transaction is not present, it fails to handle the message with com.arjuna.wst.UnknownTransactionException. > The problem arises when @Transactional annotation has a type such as SUPPORTED, in which case WS-AT transaction should not be mandatory. > We could write a wrapper for the current handler, which will delegate the call only if the transaction is available. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1444) Review the logging in XTS when participants throw Exceptions in phase 2 methods

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1444?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1444: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Review the logging in XTS when participants throw Exceptions in phase 2 methods > ------------------------------------------------------------------------------- > > Key: JBTM-1444 > URL: https://issues.jboss.org/browse/JBTM-1444 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Labels: assign > Fix For: 5.0.0.Final > > Original Estimate: 1 day > Time Spent: 1 day > Remaining Estimate: 0 minutes > > To experiment: > 1. Take the JDF WS-AT and WS-BA quickstarts. > 2. Update the server logging to TRACE for the 'arjuna' catagory. > 3. Observe what happens when the declared exceptions (and RuntimeException) are thrown from each of the phase two methods on the participants (close, compensate, commit, rollback). > 3.1 We are interested in what logging is produced (and at what log level) and what behaviour it has on the application (does it hang, is an exception returned to the client, or something else). -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1972) JBAS014134: EJB Invocation failed

by THIRUPATHIREDDY VAJJALA (JIRA)

THIRUPATHIREDDY VAJJALA created JBTM-1972: --------------------------------------------- Summary: JBAS014134: EJB Invocation failed Key: JBTM-1972 URL: https://issues.jboss.org/browse/JBTM-1972 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: THIRUPATHIREDDY VAJJALA Assignee: Tom Jenkinson i'm trying to call the method of stateful session bean , proxy bean i'm saving on session for to maintain state and to get same instance . and i have given @StatefulTimeout as 30 sec . after that i'm trying to call proxy from session. i can able to catch error but console it is printing error how to stop this. ERROR [org.jboss.as.ejb3.invocation] (http-localhost/127.0.0.1:8080-5) JBAS014134: EJB Invocation failed on component OrderServiceBean for method public abstract void com.triabeauty.enterprise.service.endpoint.local.OrderService.placeOrder(): javax.ejb.NoSuchEJBException: JBAS014300: Could not find EJB with id {[-125, -35, -121, 33, -97, -28, 75, -14, -89, -37, -50, -41, 90, 124, 77, -17]} at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:63) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:315) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:214) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2] at org.jboss.as.ee -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1961) Exception while converting string to object: java.lang.IllegalArgumentException: Invalid or unreadable URL/IOR: txstatus=TransactionActive

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1961?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1961: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/491 (was: https://github.com/jbosstm/narayana/pull/487) > Exception while converting string to object: java.lang.IllegalArgumentException: Invalid or unreadable URL/IOR: txstatus=TransactionActive > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-1961 > URL: https://issues.jboss.org/browse/JBTM-1961 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.0.M6 > > > http://172.17.131.2/job/narayana-quickstarts-windows2008-taconic/472/console > CI failure after adding JBTM-1958 (required update) > I suspect that there are multiple RTS participants launching on the same URL from the different servers in this quickstart -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1925) Enable remote debugger in JBossAS/WildFly for all tests

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1925?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1925: ---------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/narayana/pull/489, https://github.com/jbosstm/narayana/pull/490 (was: https://github.com/jbosstm/narayana/pull/438, https://github.com/jbosstm/narayana/pull/437) > Enable remote debugger in JBossAS/WildFly for all tests > ------------------------------------------------------- > > Key: JBTM-1925 > URL: https://issues.jboss.org/browse/JBTM-1925 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 4.17.13, 5.0.0.Final > > > We need to enable the debugger in all arquillian.xml files. To do this: > 1. Add this to each arquillian.xml: > {code} > <configuration> > <property name="javaVmArguments">${server.jvm.args}</property> > .... > </configuration> > {code} > 2. Update the server.jvm.args in each maven profile for running the Arquillian tests: > {code} > <server.jvm.args>..... ${jvm.args.debug}</server.jvm.args> > {code} > Look at the XTS/localjunit/pom.xml for an example. You will notice that not all Arquillian profiles configure the server.jvm.args. In which case you will need to add the config to match the others. > 3. Add this property to the root pom,xml: > {code} > <jvm.args.debug>-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n</jvm.args.debug> > {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

10 years, 11 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 October 2013