February 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1490) Track JBossWS 4.2.0.Alpha1

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1490?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1490: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbossas/jboss-as/pull/4144 > Track JBossWS 4.2.0.Alpha1 > -------------------------- > > Key: JBTM-1490 > URL: https://issues.jboss.org/browse/JBTM-1490 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Blocker > Fix For: 5.0.0.M2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Waiting for Alessio to release JBossWS 4.2.0.Alpha1 and have the component upgrade merged into AS master. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1490) Track JBossWS 4.2.0.Alpha1

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1490?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1490: -------------------------------- Priority: Blocker (was: Critical) > Track JBossWS 4.2.0.Alpha1 > -------------------------- > > Key: JBTM-1490 > URL: https://issues.jboss.org/browse/JBTM-1490 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Blocker > Fix For: 5.0.0.M2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Waiting for Alessio to release JBossWS 4.2.0.Alpha1 and have the component upgrade merged into AS master. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1479) Create a quickstart to show how to use IronJacamar and JBTM inside tomcat

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1479?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1479: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M2) > Create a quickstart to show how to use IronJacamar and JBTM inside tomcat > ------------------------------------------------------------------------- > > Key: JBTM-1479 > URL: https://issues.jboss.org/browse/JBTM-1479 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.Final > > Attachments: test-ds.xml, transaction.xml > > Original Estimate: 3 days > Time Spent: 6 hours > Remaining Estimate: 2 days, 2 hours > > See JBTM-809 for the algorithm > You might want to put the startup in the context listener: > public class MyServletContextListener implements ServletContextListener { > public void contextInitialized(ServletContextEvent sce) { > // Initialize RecoveryManager > // Initialize TransactionManager > // Initialize IronJacamar > } > > @Override > public void contextDestroyed(ServletContextEvent sce) { > // Clean IronJacamar > // Clean TransactionManager > // Clean RecoveryManager > } > } > Quickstart application should connect to the database (say PostgreSQL), dummy XA resource and coordinate the transaction. The PostgreSQL data source needs to be accessed via IronJacamar. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1490) Track JBossWS 4.2.0.Alpha1

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1490?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1490: ------------------------------------- Elevated to critical, please do downgrade (optional?) if not required. > Track JBossWS 4.2.0.Alpha1 > -------------------------- > > Key: JBTM-1490 > URL: https://issues.jboss.org/browse/JBTM-1490 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Critical > Fix For: 5.0.0.M2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Waiting for Alessio to release JBossWS 4.2.0.Alpha1 and have the component upgrade merged into AS master. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1490) Track JBossWS 4.2.0.Alpha1

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1490?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1490: -------------------------------- Priority: Critical (was: Major) > Track JBossWS 4.2.0.Alpha1 > -------------------------- > > Key: JBTM-1490 > URL: https://issues.jboss.org/browse/JBTM-1490 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Critical > Fix For: 5.0.0.M2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Waiting for Alessio to release JBossWS 4.2.0.Alpha1 and have the component upgrade merged into AS master. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1454) Compare performance of REST-AT with JTS

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1454?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1454: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M2) > Compare performance of REST-AT with JTS > --------------------------------------- > > Key: JBTM-1454 > URL: https://issues.jboss.org/browse/JBTM-1454 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.Final > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1453) Reinstate/review the numbers to detect performance regressions

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1453?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1453: -------------------------------- Fix Version/s: 5.0.0.M3 (was: 5.0.0.M2) > Reinstate/review the numbers to detect performance regressions > -------------------------------------------------------------- > > Key: JBTM-1453 > URL: https://issues.jboss.org/browse/JBTM-1453 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M3 > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1369) Benchmark performance difference between JacORB and JDK ORB

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1369?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1369: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M2) > Benchmark performance difference between JacORB and JDK ORB > ----------------------------------------------------------- > > Key: JBTM-1369 > URL: https://issues.jboss.org/browse/JBTM-1369 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS, Performance Testing > Affects Versions: 4.17.0 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.0.0.Final > > > JBTM-934 added support for the JDK orb to JTS. IOR sizes can range in size from 512 bytes to entirely unbounded, with the ORB being able to add arbitrary data within specific portions. Since the IOR is packed into transaction logs and if the IOR sizes are significantly different we may find that transaction throughput has been improved or degraded. We should run some benchmarks to see what the impact 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-985) Add WS-TX WS-Policy assertions to generated WSDL

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-985?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-985: ------------------------------- Fix Version/s: 6.0.0.Final > Add WS-TX WS-Policy assertions to generated WSDL > ------------------------------------------------- > > Key: JBTM-985 > URL: https://issues.jboss.org/browse/JBTM-985 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Fix For: 6.0.0.Final > > > See the "Policy Assertions" section of the WS-BA and WS-AT specification for what this should implement. Ideally this feature would be turned on/off via an annotation, however we should take a look to see if WS-Policy mandates a particular method. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1104) XTS support for load-balanced scenarios

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1104?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1104: -------------------------------- Fix Version/s: 6.0.0.Final > XTS support for load-balanced scenarios > --------------------------------------- > > Key: JBTM-1104 > URL: https://issues.jboss.org/browse/JBTM-1104 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Fix For: 6.0.0.Final > > > Enabling session affinity on the load balancer should ensure that all requests for a particular application endpoint, within a particular session, go to the same instance of the web service. > However, XTS advertises a number of endpoint addresses that will not make sense in a load balanced cluster. This is because it would be the internal endpoint address of the particular server that is advertised, rather than the load balancer's external address. > Even if we configured XTS (not yet possible) to offer the address of the LB, we would still have a problem as XTS will use a different session to the application to send protocol messages and thus they will go to a different server that is not aware of this transaction. > h4. Potential Solution > For each web service that is deployed by XTS, we advertises a modified version of the load balancer's address. The modification to the url provides a unique identifier for the particular node in the cluster. The load balancer would then be configured to route messages based on the modification in the url. The LB would also re-write the URL to match that expected by the particular server that receives the message. > This should be configurable per group of services provided by XTS (Client, Coordinator, Participant) as not all of these will, necessarily, be exposed via the LB. > Each Service offered by XTS is deployed via JBossWS. XTS also maintains metadata about the endpoint which it advertises to other participants in the protocol. This metadata is currently kept in sync with the service, but it doesn't have to be. In this situation, the metadata could be configured to advertise the LB address, rather than the actual address of the service. This is also where the URL re-writing would occur to identify the individual node. An example of a class that creates the endpoint metadata is "RegistrationCoordinatorInitialisation". > I don't know what support popular load balancers have for the type of URL re-writing that I mention here. This should be investigated. -- 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, 9 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 February 2013