December 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2010) Scalability Enhancements for BlackTie

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2010?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2010: ------------------------------------- This may help: https://github.com/tomjenkinson/narayana/commits/JBTM-2010-nio > Scalability Enhancements for BlackTie > ------------------------------------- > > Key: JBTM-2010 > URL: https://issues.jboss.org/browse/JBTM-2010 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 6.0.0.Final > > > At the moment we are using traditional IO techniques which means there is a single thread and connection per service on the C++ side and a single thread per server per service on the WildFly side. > For example: > 10 servers with 10 services = 10 threads on the client side, 100 threads on the wildfly side > We should look to use AIO on the Java side and apr pollset on the C++ side to reduce the number of threads. This will not reduce the physical number of connections but should allow the server to scale much higher. > 1. use AIO for StompConnect, > 2. add a configurably sized connection polling pool to BlackTie C++, > 3. use a common pool for servicedispatchers, so for example if 10 services with a size of 10 would normally mean 100 threads, we can say 10 services, size of 10, share 10 threads. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2010) Scalability Enhancements for BlackTie

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2010?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2010: -------------------------------- Assignee: Amos Feng (was: Tom Jenkinson) > Scalability Enhancements for BlackTie > ------------------------------------- > > Key: JBTM-2010 > URL: https://issues.jboss.org/browse/JBTM-2010 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 6.0.0.Final > > > At the moment we are using traditional IO techniques which means there is a single thread and connection per service on the C++ side and a single thread per server per service on the WildFly side. > For example: > 10 servers with 10 services = 10 threads on the client side, 100 threads on the wildfly side > We should look to use AIO on the Java side and apr pollset on the C++ side to reduce the number of threads. This will not reduce the physical number of connections but should allow the server to scale much higher. > 1. use AIO for StompConnect, > 2. add a configurably sized connection polling pool to BlackTie C++, > 3. use a common pool for servicedispatchers, so for example if 10 services with a size of 10 would normally mean 100 threads, we can say 10 services, size of 10, share 10 threads. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2060) STM not compiling

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2060?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2060: ------------------------------------- Fails on Windows too: http://172.17.131.2/view/Narayana+BlackTie/job/narayana-windows2008-tacon... > STM not compiling > ----------------- > > Key: JBTM-2060 > URL: https://issues.jboss.org/browse/JBTM-2060 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > Priority: Blocker > Fix For: 5.0.0.CR3 > > > CI is failing to build past STM so marking as a blocker. > This is the line that if I comment out the build succeeds: > https://github.com/jbosstm/narayana/blob/master/STM/src/main/java/org/jbo... > It could be a JDK bug if it works for you? Here is what I am using: > Fedora 18 > [tom@dhcppc1 narayana]((26ce143...)) (08:11:47) $ env | grep JAVA > JAVA_HOME=/usr/lib/jvm/java-1.7.0 > [tom@dhcppc1 narayana]((26ce143...)) (08:11:47) $ which java > /usr/lib/jvm/java-1.7.0/bin/java > [tom@dhcppc1 narayana]((26ce143...)) (08:11:47) $ java -version > java version "1.7.0_45" > OpenJDK Runtime Environment (fedora-2.4.3.0.fc18-x86_64 u45-b15) > OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode) > Can we git revert https://github.com/jbosstm/narayana/commit/d1e5c1adb175104e95db578d8b3001... till we know what the issue is? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2061) blacktie-all pom was not uploaded to nexus for CR2? - strange!

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2061?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2061: ------------------------------------- Nexus has been running really slow since I released CR2, maybe it is in a queue?? Its been 48 hours so far. > blacktie-all pom was not uploaded to nexus for CR2? - strange! > -------------------------------------------------------------- > > Key: JBTM-2061 > URL: https://issues.jboss.org/browse/JBTM-2061 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Affects Versions: 5.0.0.CR2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.0.CR3 > > > For some reason the blacktie-all pom.xml was not uploaded with CR2. I don't think anything should have changed so I think it could be an issue with Nexus. > First thing is to verify if there were any changes to that pom (or its parent between CR1 and CR2)? Maybe the NRP instructions don't include the exact steps that would get that pom into Nexus? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2061) blacktie-all pom was not uploaded to nexus for CR2? - strange!

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2061?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2061: ------------------------------------- http://172.17.131.2/job/release-btny-narayana-quickstarts-taconic/27/ > blacktie-all pom was not uploaded to nexus for CR2? - strange! > -------------------------------------------------------------- > > Key: JBTM-2061 > URL: https://issues.jboss.org/browse/JBTM-2061 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Affects Versions: 5.0.0.CR2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.0.CR3 > > > For some reason the blacktie-all pom.xml was not uploaded with CR2. I don't think anything should have changed so I think it could be an issue with Nexus. > First thing is to verify if there were any changes to that pom (or its parent between CR1 and CR2)? Maybe the NRP instructions don't include the exact steps that would get that pom into Nexus? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2061) blacktie-all pom was not uploaded to nexus for CR2? - strange!

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2061?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2061: ------------------------------------- A temporary workaround would be to try to upload that pom to nexus directly. If you do ./build.sh clean install deploy -f blacktie/pom.xml it will try to re-release everything so that doesn't work. Maybe we can do mvn deploy:deploy-file ...? > blacktie-all pom was not uploaded to nexus for CR2? - strange! > -------------------------------------------------------------- > > Key: JBTM-2061 > URL: https://issues.jboss.org/browse/JBTM-2061 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Affects Versions: 5.0.0.CR2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.0.CR3 > > > For some reason the blacktie-all pom.xml was not uploaded with CR2. I don't think anything should have changed so I think it could be an issue with Nexus. > First thing is to verify if there were any changes to that pom (or its parent between CR1 and CR2)? Maybe the NRP instructions don't include the exact steps that would get that pom into Nexus? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2061) blacktie-all pom was not uploaded to nexus for CR2? - strange!

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2061: ----------------------------------- Summary: blacktie-all pom was not uploaded to nexus for CR2? - strange! Key: JBTM-2061 URL: https://issues.jboss.org/browse/JBTM-2061 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: BlackTie, Build System Affects Versions: 5.0.0.CR2 Reporter: Tom Jenkinson Assignee: Gytis Trikleris Priority: Blocker Fix For: 5.0.0.CR3 For some reason the blacktie-all pom.xml was not uploaded with CR2. I don't think anything should have changed so I think it could be an issue with Nexus. First thing is to verify if there were any changes to that pom (or its parent between CR1 and CR2)? Maybe the NRP instructions don't include the exact steps that would get that pom into Nexus? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2060) STM not compiling

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2060: ----------------------------------- Summary: STM not compiling Key: JBTM-2060 URL: https://issues.jboss.org/browse/JBTM-2060 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: STM Reporter: Tom Jenkinson Assignee: Mark Little Priority: Blocker Fix For: 5.0.0.CR3 CI is failing to build past STM so marking as a blocker. This is the line that if I comment out the build succeeds: https://github.com/jbosstm/narayana/blob/master/STM/src/main/java/org/jbo... It could be a JDK bug if it works for you? Here is what I am using: Fedora 18 [tom@dhcppc1 narayana]((26ce143...)) (08:11:47) $ env | grep JAVA JAVA_HOME=/usr/lib/jvm/java-1.7.0 [tom@dhcppc1 narayana]((26ce143...)) (08:11:47) $ which java /usr/lib/jvm/java-1.7.0/bin/java [tom@dhcppc1 narayana]((26ce143...)) (08:11:47) $ java -version java version "1.7.0_45" OpenJDK Runtime Environment (fedora-2.4.3.0.fc18-x86_64 u45-b15) OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode) Can we git revert https://github.com/jbosstm/narayana/commit/d1e5c1adb175104e95db578d8b3001... till we know what the issue is? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2060) STM not compiling

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2060?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2060: ------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana/368/ > STM not compiling > ----------------- > > Key: JBTM-2060 > URL: https://issues.jboss.org/browse/JBTM-2060 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > Priority: Blocker > Fix For: 5.0.0.CR3 > > > CI is failing to build past STM so marking as a blocker. > This is the line that if I comment out the build succeeds: > https://github.com/jbosstm/narayana/blob/master/STM/src/main/java/org/jbo... > It could be a JDK bug if it works for you? Here is what I am using: > Fedora 18 > [tom@dhcppc1 narayana]((26ce143...)) (08:11:47) $ env | grep JAVA > JAVA_HOME=/usr/lib/jvm/java-1.7.0 > [tom@dhcppc1 narayana]((26ce143...)) (08:11:47) $ which java > /usr/lib/jvm/java-1.7.0/bin/java > [tom@dhcppc1 narayana]((26ce143...)) (08:11:47) $ java -version > java version "1.7.0_45" > OpenJDK Runtime Environment (fedora-2.4.3.0.fc18-x86_64 u45-b15) > OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode) > Can we git revert https://github.com/jbosstm/narayana/commit/d1e5c1adb175104e95db578d8b3001... till we know what the issue is? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1593) Most top level subsystem folders in the quickstart repo are missing README.md files

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1593?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1593: -------------------------------- Priority: Major (was: Minor) > Most top level subsystem folders in the quickstart repo are missing README.md files > ----------------------------------------------------------------------------------- > > Key: JBTM-1593 > URL: https://issues.jboss.org/browse/JBTM-1593 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator > Affects Versions: 5.0.0.M2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.0.CR3 > > > Top level subsystem folders in the quickstart repo are missing README.md files (except XTS). > Use the XTS README.md as an example of what they should look like. I suggest the workload assignments for completing this task as follows: > ArjunaCore - Mike > ArjunaJTA - Mike > ArjunaJTS - Mike > atsintegration - Mike > ObjectStore - Mike > blacktie Amos > rest-tx - Mike -- 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, 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 December 2013