April 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1623) jboss-as is killed by Out of Memeory

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1623?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1623: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/blacktie/pull/40 > jboss-as is killed by Out of Memeory > ------------------------------------ > > Key: JBTM-1623 > URL: https://issues.jboss.org/browse/JBTM-1623 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > Attachments: consoleText.txt > > > See: http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1466 -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1643) Need a qa test suite ant target to skip jts tests

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1643?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1643: ----------------------------------- Why focus solely on JTS? Why not support something like this for each component? > Need a qa test suite ant target to skip jts tests > ------------------------------------------------- > > Key: JBTM-1643 > URL: https://issues.jboss.org/browse/JBTM-1643 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Trivial > Fix For: 5.0.0.M3 > > > Useful for testing everything apart from JTS -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1556) provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1556?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1556: ----------------------------------- Each transaction instance (subordinate or coordinator) has its own reaper and they work autonomously. > provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling > ---------------------------------------------------------------------------------------------- > > Key: JBTM-1556 > URL: https://issues.jboss.org/browse/JBTM-1556 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.17.3 > Reporter: Scott Marlow > Assignee: Tom Jenkinson > Fix For: 4.17.5, 5.0.0.M3 > > > When the Synchronization.afterCompletion is invoked for EE JPA containers, knowledge of whether the current thread is the Reaper thread (cancelling the transaction from a background thread). > The fix to this jira will help with handling the [JPA 2.1 container concurrency requirements|http://java.net/projects/jpa-spec/lists/jsr338-experts/archi...]. > Please implement the solution makes the most sense to you, as this will introduce an additional dependency between other systems and JBossTM/JBossTS that depend on the solution, that will likely be around for a long time. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS subsystem and module

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?focusedWorklogId=12429104&page=... ] Gytis Trikleris logged work on JBTM-1365: ----------------------------------------- Author: Gytis Trikleris Created on: 22/Apr/13 3:31 PM Start Date: 22/Apr/13 3:30 PM Worklog Time Spent: 2 hours, 30 minutes Issue Time Tracking ------------------- Remaining Estimate: 2 weeks, 2 days, 1 hour, 30 minutes (was: 2 weeks, 2 days, 4 hours) Time Spent: 2 days, 6 hours, 30 minutes (was: 2 days, 4 hours) Worklog Id: (was: 12429104) > Deploy REST-AT support as a JBossAS subsystem and module > -------------------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Original Estimate: 3 weeks > Time Spent: 2 days, 6 hours, 30 minutes > Remaining Estimate: 2 weeks, 2 days, 1 hour, 30 minutes > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > The subsystem would need to: > * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. > * Deploy the coordinator endpoint. > The module would need to contain the REST-AT coordinator code and the client libraries. > h3. Open Issues > Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1623) jboss-as is killed by Out of Memeory

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1623?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1623: -------------------------------- Priority: Critical (was: Minor) > jboss-as is killed by Out of Memeory > ------------------------------------ > > Key: JBTM-1623 > URL: https://issues.jboss.org/browse/JBTM-1623 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > Attachments: consoleText.txt > > > See: http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1466 -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1634) TX tests failed with "Unable to start a new txn on URI"

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1634?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1634: ------------------------------------- Looks like the pull failed due to JBTM-1623 > TX tests failed with "Unable to start a new txn on URI" > ------------------------------------------------------- > > Key: JBTM-1634 > URL: https://issues.jboss.org/browse/JBTM-1634 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/246/ > http://172.17.131.2/job/blacktie-linux32/915/ > http://172.17.131.2/job/blacktie-linux64/1472/ > {code} > 2013-04-16 06:12:25,324 [0x57fb3f0] DEBUG (HttpClient :114 ) - connected to TM on localhost:8080 URI=http://localhost:8080/rest-tx/tx/transaction-manager > 2013-04-16 06:12:25,484 [0x57fb3f0] DEBUG (HttpClient :74 ) - connect to localhost:8080 ok > 2013-04-16 06:12:25,491 [0x57fb3f0] DEBUG (HttpClient :99 ) - POST http://localhost:8080/rest-tx/tx/transaction-manager HTTP/1.1 > 2013-04-16 06:12:25,495 [0x57fb3f0] DEBUG (HttpClient :99 ) - Host: localhost > 2013-04-16 06:12:25,498 [0x57fb3f0] DEBUG (HttpClient :99 ) - Content-Length: 13 > 2013-04-16 06:12:25,500 [0x57fb3f0] DEBUG (HttpClient :99 ) - Content-Type: application/x-www-form-urlencoded > 2013-04-16 06:12:25,505 [0x57fb3f0] DEBUG (HttpClient :148 ) - timeout=-1000 > 2013-04-16 06:12:25,508 [0x57fb3f0] DEBUG (HttpClient :158 ) - buf size is 4096 > 2013-04-16 06:12:27,023 [0x57fb3f0] DEBUG (HttpClient :162 ) - receive 241 bytes > 2013-04-16 06:12:27,028 [0x57fb3f0] DEBUG (HttpClient :165 ) - HTTP/1.1 404 Not Found > Content-Length: 145 > Connection: keep-alive > Content-Type: text/html > Could not find resource for relative : /rest-tx/tx/transaction-manager of full path: http://localhosthttp/rest-tx/rest-tx/tx/transaction-manager? > 2013-04-16 06:12:27,049 [0x57fb3f0] DEBUG (HttpClient :194 ) - HTTP/1.1 404 Not Found > {code} > It looks like restat-web.war has not regiter as /rest-tx -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1647) narayana.sh expects DB drivers to be available locally

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1647: ----------------------------------- Summary: narayana.sh expects DB drivers to be available locally Key: JBTM-1647 URL: https://issues.jboss.org/browse/JBTM-1647 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Reporter: Paul Robinson Assignee: Tom Jenkinson Fix For: 5.0.0.M3 >From talking to Jonathan and Mike, my understanding is that narayana.sh should wget the DB drivers from albany. Instead it relies on them being available in /home/hudson/dbdrivers. The problem with this approach is that it requires setting up every time we add a new machine in the pool, or add new drivers. Here's what happens when you run the Oracle JDBC job on a machine with no /home/hudson/dbdrivers: {code} Started by upstream project "jbossts-EAP61-jdbcobjectstore-haverstraw-oracle" build number 1 originally caused by: Started by user anonymous Building remotely on haverstraw in workspace /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw Checkout:haverstraw / /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw - hudson.remoting.Channel@4376502f:haverstraw Using strategy: Default Cloning the remote Git repository Cloning repository git://github.com/jbosstm/narayana.git git --version git version 1.7.1 Fetching upstream changes from origin Commencing build of Revision dc53acf1f5faffeb92ecabba85a6877bc699ada0 (origin/4.17) Checking out Revision dc53acf1f5faffeb92ecabba85a6877bc699ada0 (origin/4.17) No change to record in branch origin/4.17 [haverstraw] $ /bin/bash -xe /tmp/hudson5928481526507148318.sh + export ANT_HOME=/home/hudson/apache-ant-1.8.2 + ANT_HOME=/home/hudson/apache-ant-1.8.2 + export PATH=/home/hudson/apache-ant-1.8.2/bin:/usr/local/jdk1.6.0_37/bin:/usr/local/jdk1.6.0_37/bin:/usr/local/jdk1.7.0_09/bin:/usr/local/bin:/bin:/usr/bin + PATH=/home/hudson/apache-ant-1.8.2/bin:/usr/local/jdk1.6.0_37/bin:/usr/local/jdk1.6.0_37/bin:/usr/local/jdk1.7.0_09/bin:/usr/local/bin:/bin:/usr/bin + export MFACTOR=2 + MFACTOR=2 + rm -rf /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw/ext/../qa/dbdrivers/ + cd /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw/qa/ + ant get.drivers -Ddriver.url=file:///home/hudson/dbdrivers Buildfile: /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw/qa/build.xml clean-dbdrivers: get.drivers: [mkdir] Created dir: /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw/qa/dbdrivers/oracle_10_2_0_4 [get] Getting: file:/home/hudson/dbdrivers/ojdbc14.jar [get] To: /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw/qa/dbdrivers/oracle_10_2_0_4/ojdbc14.jar [get] Error getting file:/home/hudson/dbdrivers/ojdbc14.jar to /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw/qa/dbdrivers/oracle_10_2_0_4/ojdbc14.jar BUILD FAILED /home/hudson/workspace/jbossts-EAP61-jdbcobjectstore-haverstraw-oracle/DB_TYPE/oracle/jdk/jdk6.latest/slave/haverstraw/qa/build.xml:66: java.io.FileNotFoundException: /home/hudson/dbdrivers/ojdbc14.jar (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:120) at java.io.FileInputStream.<init>(FileInputStream.java:79) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70) at org.apache.tools.ant.taskdefs.Get$GetThread.openConnection(Get.java:660) at org.apache.tools.ant.taskdefs.Get$GetThread.get(Get.java:579) at org.apache.tools.ant.taskdefs.Get$GetThread.run(Get.java:569) Total time: 0 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Sending e-mails to: gtrikler(a)redhat.com Finished: FAILURE {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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1609) Certain XAResourceRecord constructors don't take into account configured SerializableXAResourceDeserializer(s)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1609?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1609: -------------------------------- Fix Version/s: 5.0.0.M3 4.17.4 > Certain XAResourceRecord constructors don't take into account configured SerializableXAResourceDeserializer(s) > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1609 > URL: https://issues.jboss.org/browse/JBTM-1609 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.3, 5.0.0.M2 > Reporter: jaikiran pai > Assignee: Tom Jenkinson > Fix For: 4.17.4, 5.0.0.M3 > > > Certain XAResourceRecord constructors don't initialize the list of SerializableXAResourceDeserializer that's maintained in the XAResourceRecord. As a result, during restoring the state of the record, the XAResourceRecord will not be aware of the configured SerializableXAResourceDeserializer(s) and can end up not being able to deserialize the XAResource within that record. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1609) Certain XAResourceRecord constructors don't take into account configured SerializableXAResourceDeserializer(s)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1609?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1609: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Certain XAResourceRecord constructors don't take into account configured SerializableXAResourceDeserializer(s) > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1609 > URL: https://issues.jboss.org/browse/JBTM-1609 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.3, 5.0.0.M2 > Reporter: jaikiran pai > Assignee: Tom Jenkinson > Fix For: 5.0.0.M3, 4.17.4 > > > Certain XAResourceRecord constructors don't initialize the list of SerializableXAResourceDeserializer that's maintained in the XAResourceRecord. As a result, during restoring the state of the record, the XAResourceRecord will not be aware of the configured SerializableXAResourceDeserializer(s) and can end up not being able to deserialize the XAResource within that record. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1646) IndirectTXManagementTest failed. rest-tx.realm is already registered

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-1646: ------------------------------------- Summary: IndirectTXManagementTest failed. rest-tx.realm is already registered Key: JBTM-1646 URL: https://issues.jboss.org/browse/JBTM-1646 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Demonstrator, REST Reporter: Gytis Trikleris Assignee: Michael Musgrove Fix For: 5.0.0.M3 http://172.17.131.2/job/btny-pulls-quickstarts/227 http://172.17.131.2/job/btny-pulls-quickstarts/226 http://172.17.131.2/job/btny-pulls-quickstarts/225 -- 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

11 years, 5 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 April 2013