November 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2483) Investigate ways to test Docker quickstarts

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2483?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2483: ----------------------------------- Assignee: (was: Amos Feng) > Investigate ways to test Docker quickstarts > ------------------------------------------- > > Key: JBTM-2483 > URL: https://issues.jboss.org/browse/JBTM-2483 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud > Reporter: Gytis Trikleris > Priority: Major > Fix For: 5.later > > > Currently there is only one quickstart for docker (https://github.com/jbosstm/quickstart/tree/master/jts-docker), but its tests are disabled by default. However, it would be good to run them in our CI. > We'll have the same problem in the future with Kubernetes quickstarts. > Maybe Arquillian Cube is something what could help? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3056) Remove the xts-test-servlet dependency in narayana-full

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3056?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-3056: ----------------------------------- Assignee: (was: Amos Feng) > Remove the xts-test-servlet dependency in narayana-full > ------------------------------------------------------- > > Key: JBTM-3056 > URL: https://issues.jboss.org/browse/JBTM-3056 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Amos Feng > Priority: Major > > this dependency is generated by the module XTS/WSAS/xts-test-servlet but does not produce any files. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2968) Some JTS quickstarts run with JacORB

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2968?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2968: -------------------------------- Priority: Optional (was: Major) > Some JTS quickstarts run with JacORB > ------------------------------------ > > Key: JBTM-2968 > URL: https://issues.jboss.org/browse/JBTM-2968 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Affects Versions: 5.7.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Some of the JTS quickstarts are using JacORB. The narayana project has since changed the default ORB (OpenJDK ORB) so we should change the quickstarts to use the new default. The affected poms are: > ArjunaJTS/pom.xml > ArjunaJTS/standalone/pom.xml > ArjunaJTS/trailmap/pom.xml -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1105) Setup client side interceptors based on WS-Policy in WSDL

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-1105?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1105: -------------------------------- Priority: Optional (was: Major) > Setup client side interceptors based on WS-Policy in WSDL > --------------------------------------------------------- > > Key: JBTM-1105 > URL: https://issues.jboss.org/browse/JBTM-1105 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Paul Robinson > Priority: Optional > Original Estimate: 3 days > Remaining Estimate: 3 days > > If the Service WSDL specifies a WS-Policy assertion, we know that WS-AT or WS-BA is required/supported and we should be able to setup this handler chain automatically. Another benefit is that we can catch, on the client side, the situation where no WS-AT or WS-BA transaction context is present. Currently we leave it up to the service to detect and as a result we have no control over how this fault will be propagated back to the client. For example, a WrongStateException could be thrown when the service tries to enlist a participant and a transaction is not present. The Client may receive a generic fault message back or, in this case some or all of the WrongStateException. In either case, the developer of the Client is unlikely to realise that this is due to there not being a transaction present when the service was invoked. If the service mandates a WS-AT or WS-BA transaction, but none is present, then the client handler throws a suitable exception explaining what went wrong. If the service supports (i.e. it is optional) a WS-AT or WS-BA transaction, then the interceptor ignores the situation where non exists. > CXF seems to have a plugin point for adding WS-Policy assertion handlers. This could be the right integration point for this feature. This is to be investigated. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2899) Consider independently versioning the quickstarts

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2899?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2899. ------------------------------- Resolution: Won't Do > Consider independently versioning the quickstarts > ------------------------------------------------- > > Key: JBTM-2899 > URL: https://issues.jboss.org/browse/JBTM-2899 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Priority: Major > > It would be clearer to know when an individual quickstart has changed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-870) Add more XTS quickstarts

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-870?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-870: ------------------------------- Priority: Optional (was: Major) > Add more XTS quickstarts > ------------------------ > > Key: JBTM-870 > URL: https://issues.jboss.org/browse/JBTM-870 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, XTS > Reporter: Paul Robinson > Priority: Optional > > See the individual sub tasks for more information. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2765) Document Narayana Tomcat module

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2765?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2765. ------------------------------- Resolution: Won't Do This is moved to the webservers github org so they should determine the required documentation /cc [~mbabacek] > Document Narayana Tomcat module > ------------------------------- > > Key: JBTM-2765 > URL: https://issues.jboss.org/browse/JBTM-2765 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Major > > Tomcat module is not documented in http://narayana.io//docs/project/index.html. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1577) Create a quickstart that shows a transaction created in EJB being propagated to an XATMI service

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-1577?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1577: -------------------------------- Priority: Optional (was: Major) > Create a quickstart that shows a transaction created in EJB being propagated to an XATMI service > ------------------------------------------------------------------------------------------------ > > Key: JBTM-1577 > URL: https://issues.jboss.org/browse/JBTM-1577 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Priority: Optional > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1515) Investigate the overhead of bridging JTA to WS-AT when not needed

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-1515?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1515: -------------------------------- Priority: Optional (was: Major) > Investigate the overhead of bridging JTA to WS-AT when not needed > ----------------------------------------------------------------- > > Key: JBTM-1515 > URL: https://issues.jboss.org/browse/JBTM-1515 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Paul Robinson > Priority: Optional > > When using default context propagation, a subordinate WS-AT transaction will be created for Web service calls made within a JTA transaction. This is wasteful if the target service does not enlist any participants in this transaction. > We should measure the overhead that this imposes and take steps to reduce/remove it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1666) Investigate "still reachable" valgrind memory errors

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-1666?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1666: -------------------------------- Priority: Minor (was: Major) > Investigate "still reachable" valgrind memory errors > ---------------------------------------------------- > > Key: JBTM-1666 > URL: https://issues.jboss.org/browse/JBTM-1666 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Reporter: Tom Jenkinson > Priority: Minor > > Most of the valgrind logs are full of: > ==9548== 4 bytes in 1 blocks are still reachable in loss record 1 of 51 > ==9548== at 0x4027D17: operator new(unsigned int) (vg_replace_malloc.c:292) > ==9548== by 0x4E633A8: google::protobuf::DescriptorPool::DescriptorPool(google::protobuf::DescriptorDatabase*, google::protobuf::DescriptorPool::ErrorCollector*) (descriptor.cc:770) > ==9548== by 0x4E6346D: google::protobuf::(anonymous namespace)::InitGeneratedPool() (descriptor.cc:816) > ==9548== by 0x546E8DF: pthread_once (in /lib/libpthread-2.12.so) > ==9548== by 0x4E86E3F: google::protobuf::protobuf_AddDesc_google_2fprotobuf_2fdescriptor_2eproto() (descriptor.pb.cc:656) > ==9548== by 0x4E8790C: __static_initialization_and_destruction_0(int, int) (descriptor.pb.cc:705) > ==9548== by 0x4ED2495: ??? (in /home/hudson/workspace/blacktie-linux32/nbf/target/cxx/runtime/lib/libprotobuf.so.7) > ==9548== by 0x4E4538C: ??? (in /home/hudson/workspace/blacktie-linux32/nbf/target/cxx/runtime/lib/libprotobuf.so.7) > ==9548== by 0x400EFCE: _dl_init (in /lib/ld-2.12.so) > ==9548== by 0x400088E: ??? (in /lib/ld-2.12.so) > Please can you explain what this is and whether it is a leak and if so, try to resolve it? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 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 November 2018