From issues at jboss.org  Fri Jan  4 04:06:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:06:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2496) Investigate using of
 camel for content based routing in the Blacktie
In-Reply-To: <JIRA.12581931.1440050467000@Atlassian.JIRA>
References: <JIRA.12581931.1440050467000@Atlassian.JIRA>
	<JIRA.12581931.1440050467000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12581931.1440050467000.17096.1546592760367@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-2496:
-----------------------------------

    Assignee:     (was: Amos Feng)


> Investigate using of camel for content based routing in the Blacktie
> --------------------------------------------------------------------
>
>                 Key: JBTM-2496
>                 URL: https://issues.jboss.org/browse/JBTM-2496
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>          Components: BlackTie, Demonstrator
>            Reporter: Amos Feng
>            Priority: Minor
>
> The current cbr quickstart is out-of-date by using the jboss-esb and it needs to investigate the camel 



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:06:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:06:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3075) Segment fault failure
 with tpacall when running the blacktie with centos7
In-Reply-To: <JIRA.12778829.1542005168000@Atlassian.JIRA>
References: <JIRA.12778829.1542005168000@Atlassian.JIRA>
	<JIRA.12778829.1542005168000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12778829.1542005168000.17099.1546592760430@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-3075:
-----------------------------------

    Assignee:     (was: Amos Feng)


> Segment fault failure with tpacall when running the blacktie with centos7
> -------------------------------------------------------------------------
>
>                 Key: JBTM-3075
>                 URL: https://issues.jboss.org/browse/JBTM-3075
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: BlackTie
>    Affects Versions: 5.9.0.Final
>         Environment: > you may get it by "uname -a" ?
> Linux localhost.localdomain 3.10.0-693.el7.x86_64 #1 SMP Thu Jul 6 19:56:57 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux
> >what is the version of the gcc, you could get by "gcc --version"
> gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16)
> rpm -qa | grep -i apr
> apr-1.4.8-3.el7.x86_64
> apr-util-1.5.2-6.el7.x86_64
>            Reporter: Amos Feng
>            Priority: Major
>             Fix For: 5.later
>
>
> The call stack is 
> {code}
> #0  0x00007ffff607d9f6 in _int_malloc () from /usr/lib64/libc.so.6
> #1  0x00007ffff608010c in malloc () from /usr/lib64/libc.so.6
> #2  0x00007ffff5bc3263 in allocator_alloc (in_size=<optimized out>,
>     allocator=<optimized out>) at memory/unix/apr_pools.c:349
> #3  apr_pool_create_ex (newpool=0x7fffffff9cf0, parent=0x640b18, abort_fn=0x0,
>     allocator=0x63ca00) at memory/unix/apr_pools.c:891
> #4  0x00007ffff7ae9c6d in log4cxx::helpers::Pool::Pool (this=0x7fffffff9cf0)
>     at /home/hudson/blacktie/utils/apache-log4cxx/src/main/cpp/pool.cpp:34
> #5  0x00007ffff7b35eb0 in log4cxx::Logger::forcedLog (this=0x652bc0,
>     level1=..., message="HttpTxManager:57:ENTER HttpTxManager constructor",
>     location=...)
>     at /home/hudson/blacktie/utils/apache-log4cxx/src/main/cpp/logger.cpp:121
> #6  0x00007ffff74b655c in atmibroker::tx::HttpTxManager::HttpTxManager (
>     this=0x6853a0,
>     txmUrl=0x714a60 "http://127.0.0.1:8080/rest-at-coordinator/tx/transaction-manager", resUrl=0x6ef560 "127.0.0.1:8888", __in_chrg=<optimized out>,
>     __vtt_parm=<optimized out>)
>     at /home/jenkins/workspace/release-narayana/blacktie/tx/src/main/cpp/HttpTxManager.cxx:57
> #7  0x00007ffff74b71ea in atmibroker::tx::HttpTxManager::create (txmUrl=0x714a60 "http://127.0.0.1:8080/rest-at-coordinator/tx/transaction-ma                                                                                        nager", resUrl=0x6ef560 "127.0.0.1:8888")
>     at /home/jenkins/workspace/release-narayana/blacktie/tx/src/main/cpp/HttpTxM---Type <return> to continue, or q <return> to quit---
> anager.cxx:87
> #8  0x00007ffff74a2c3e in atmibroker::tx::TxManager::get_instance ()  at /home/jenkins/workspace/release-narayana/blacktie/tx/src/main/cpp/TxManager.cxx:49
> #9  0x00007ffff74b5255 in txx_get_control ()    at /home/jenkins/workspace/release-narayana/blacktie/tx/src/main/cpp/TxManagerc.cxx:56
> #10 0x00007ffff72424c0 in tpacall (svc=0x42eb8c "some service",   idata=0x69ab20 "N", ilen=0, flags=34)
> {code}
> The failure looks like related to the log4xx.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:06:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:06:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2495) Installing Blacktie 5.2.2
 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or
 appropriate)
In-Reply-To: <JIRA.12581866.1439996721000@Atlassian.JIRA>
References: <JIRA.12581866.1439996721000@Atlassian.JIRA>
	<JIRA.12581866.1439996721000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12581866.1439996721000.17102.1546592760529@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-2495:
-----------------------------------

    Assignee:     (was: Amos Feng)


> Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate)
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: JBTM-2495
>                 URL: https://issues.jboss.org/browse/JBTM-2495
>             Project: JBoss Transaction Manager
>          Issue Type: Sub-task
>          Components: BlackTie, Documentation
>    Affects Versions: 5.0.0.M2
>         Environment: RHEL 6.3
>            Reporter: Joice Joy
>            Priority: Minor
>
> I am installing Blacktie 5.2.2 Final with Wildfly 9.0.1 but the Wildfly server fails to start the Blacktie service
> But the server does not start the blacktie service:
> This is from quickstart quickstart/blacktie
>  
>  
>  
> =========================================================================
>  
>  
>   JBoss Bootstrap Environment
>  
>  
>   JBOSS_HOME: /fxtest/trep/wildfly/wildfly-9.0.1.Final
>  
>  
>   JAVA: /fxtest/trep/java/jdk1.8.0_51/bin/java
>  
>  
>   JAVA_OPTS:  -server -XX:+UseCompressedOops  -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE
>  
>  
> =========================================================================
>  
>  
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
> 07:35:52,490 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final
> 07:35:52,892 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
> 07:35:53,007 INFO  [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting
> 07:35:55,053 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 07:35:55,055 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 07:35:55,121 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment blacktie-admin-services-ear-5.2.2.Final.ear
> 07:35:55,361 INFO  [org.jboss.as.repository] (ServerService Thread Pool -- 24) WFLYDR0001: Content added at location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content
> 07:35:55,390 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
> 07:35:55,422 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final
> 07:35:55,438 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final
> 07:35:55,482 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final
> 07:35:55,548 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem.
> 07:35:55,554 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
> 07:35:55,557 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem
> 07:35:55,602 INFO  [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final)
> 07:35:55,615 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main]
> 07:35:55,652 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> 07:35:55,661 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem
> 07:35:55,670 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2
> 07:35:55,827 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem
> 07:35:55,829 INFO  [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final
> 07:35:55,849 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
> 07:35:55,849 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension
> 07:35:55,998 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.9.Final starting
> 07:35:56,034 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting
> 07:35:56,095 INFO  [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
> 07:35:56,119 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
> 07:35:56,352 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path /fxtest/trep/wildfly/wildfly-9.0.1.Final/welcome-content
> 07:35:56,417 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server.
> 07:35:56,437 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
> 07:35:56,589 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080
> 07:35:56,945 INFO  [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started
> 07:35:56,969 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
> 07:35:57,030 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/deployments
> 07:35:57,059 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear")
> 07:35:57,187 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingpaging)
> 07:35:57,193 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock
> 07:35:57,287 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221012: Using AIO Journal
> 07:35:57,387 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE
> 07:35:57,414 INFO  [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final
> 07:35:57,439 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP
> 07:35:57,443 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP
> 07:35:57,502 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock
> 07:35:57,504 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock
> 07:35:58,108 INFO  [org.jboss.messaging] (MSC service thread 1-3) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor
> 07:35:58,112 INFO  [org.jboss.messaging] (MSC service thread 1-1) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor
> 07:35:58,206 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live
> 07:35:58,207 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [9d12c6a3-4666-11e5-8632-95a54ac84561]
> 07:35:58,210 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue
> 07:35:58,514 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 66) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory
> 07:35:58,519 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 67) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
> 07:35:58,519 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ
> 07:35:58,623 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA
> 07:35:58,721 INFO  [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started
> 07:35:58,721 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra
> 07:35:58,733 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
> 07:35:58,733 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
> 07:35:58,762 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar  does not point to a valid jar for a Class-Path reference.
> 07:35:58,762 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar  does not point to a valid jar for a Class-Path reference.
> 07:35:58,762 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar  does not point to a valid jar for a Class-Path reference.
> 07:35:58,763 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar  does not point to a valid jar for a Class-Path reference.
> 07:35:58,780 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "blacktie-admin-services-5.2.2.Final.jar")
> 07:35:58,885 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear"
>         at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
>         at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
>         at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>         at java.lang.Thread.run(Thread.java:745)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml
>         at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98)
>         at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
>         ... 5 more
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml
>         at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95)
>         ... 6 more
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1]
> Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'
>         at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108)
>         at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
>         at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89)
>         ... 6 more
>  
>  
> 07:35:58,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "blacktie-admin-services-ear-5.2.2.Final.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment \"blacktie-admin-services-5.2.2.Final.jar\" of deployment \"blacktie-admin-services-ear-5.2.2.Final.ear\"
>     Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml
>     Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml
>     Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1]
> Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}}
> 07:35:58,980 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.2.2.Final.ear")
> 07:35:58,982 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0186:   Services which failed to start:      service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear"
>  
>  
> 07:35:59,202 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> 07:35:59,202 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> 07:35:59,202 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 7156ms - Started 247 of 423 services (2 services failed or missing dependencies, 222 services are lazy, passive or on-demand)
> 07:35:59,243 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: blacktie-admin-services-5.2.2.Final.jar) in 9ms
> 07:35:59,332 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment blacktie-admin-services-ear-5.2.2.Final.ear (runtime-name: blacktie-admin-services-ear-5.2.2.Final.ear) in 98ms
> 07:35:59,413 INFO  [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content
> 07:35:59,414 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear")
> 07:35:59,414 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report
> WFLYCTL0186:   Services which failed to start:      service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:06:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:06:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2527) Update to check the
 buffer size in btgetattribute
In-Reply-To: <JIRA.12586535.1443582257000@Atlassian.JIRA>
References: <JIRA.12586535.1443582257000@Atlassian.JIRA>
	<JIRA.12586535.1443582257000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12586535.1443582257000.17104.1546592760589@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-2527:
-----------------------------------

    Assignee:     (was: Amos Feng)


> Update to check the buffer size in btgetattribute
> -------------------------------------------------
>
>                 Key: JBTM-2527
>                 URL: https://issues.jboss.org/browse/JBTM-2527
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>          Components: BlackTie
>            Reporter: Amos Feng
>            Priority: Minor
>
> currently the nbf btgetattribute does not check the buffer size is big enough for copying the value.
> So it should return error if the pass buffer size is not enough.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:06:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:06:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2998) Blacktie TestTPGetRply
 failed with unknown session
In-Reply-To: <JIRA.12737348.1520232570000@Atlassian.JIRA>
References: <JIRA.12737348.1520232570000@Atlassian.JIRA>
	<JIRA.12737348.1520232570000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12737348.1520232570000.17106.1546592760645@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-2998:
-----------------------------------

    Assignee:     (was: Amos Feng)


> Blacktie TestTPGetRply failed with unknown session
> --------------------------------------------------
>
>                 Key: JBTM-2998
>                 URL: https://issues.jboss.org/browse/JBTM-2998
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: BlackTie
>            Reporter: Amos Feng
>            Priority: Minor
>             Fix For: 5.later
>
>         Attachments: archive(1).zip, archive.zip
>
>
> {noformat}
> 2018-01-09 02:24:48,064 [0x00001db8] DEBUG (AtmiBrokerClient         :200 ) - get session: 3
> 2018-01-09 02:24:48,064 [0x00001db8] DEBUG (AtmiBrokerClient         :209 ) - did not get session: 3
> 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc                   :411 ) - _get_tperrno
> 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc                   :415 ) - found _get_tperrno2
> 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc                   :418 ) - returning _get_tperrno2
> 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc                   :924 ) - tpgetrply return: -1 tperrno: 2
> 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc                   :411 ) - _get_tperrno
> 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc                   :415 ) - found _get_tperrno2
> 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc                   :418 ) - returning _get_tperrno2
> 2018-01-09 02:24:48,064 [0x00001db8] DEBUG (AtmiBrokerLogc           :72  ) - CHKCOND ASSERT FAILED C:\hudson\workspace\narayana-catelyn\blacktie\xatmi\src\test\cpp\TestTPGetRply.cxx:272
> {noformat}
> It looks like that the sessionIds have the prev id in the other tests which has not been removed.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:06:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:06:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2832) Blacktie
 TestTPGetRely::test_tpgetrply_with_TPGETANY fail
In-Reply-To: <JIRA.12668922.1483060535000@Atlassian.JIRA>
References: <JIRA.12668922.1483060535000@Atlassian.JIRA>
	<JIRA.12668922.1483060535000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12668922.1483060535000.17108.1546592760694@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-2832:
-----------------------------------

    Assignee:     (was: Amos Feng)


> Blacktie TestTPGetRely::test_tpgetrply_with_TPGETANY fail
> ---------------------------------------------------------
>
>                 Key: JBTM-2832
>                 URL: https://issues.jboss.org/browse/JBTM-2832
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: BlackTie
>            Reporter: Amos Feng
>            Priority: Minor
>             Fix For: 5.later
>
>         Attachments: CIfailure.zip
>
>
> [exec] 1) test: TestTPGetRply::test_tpgetrply_with_TPGETANY (F) line: 272 C:\hudson\workspace\narayana-catelyn\blacktie\xatmi\src\test\cpp\TestTPGetRply.cxx
>      [exec] assertion failed
>      [exec] - Expression: _w12pq_u
>      [exec] 



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:06:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:06:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2877) Linkage errors whilst
 building BlackTie Admin CLI tool on Fedora 25
In-Reply-To: <JIRA.12685144.1490867517000@Atlassian.JIRA>
References: <JIRA.12685144.1490867517000@Atlassian.JIRA>
	<JIRA.12685144.1490867517000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12685144.1490867517000.17111.1546592760759@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-2877:
-----------------------------------

    Assignee:     (was: Amos Feng)


> Linkage errors whilst building BlackTie Admin CLI tool on Fedora 25
> -------------------------------------------------------------------
>
>                 Key: JBTM-2877
>                 URL: https://issues.jboss.org/browse/JBTM-2877
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: BlackTie
>    Affects Versions: 5.5.5.Final
>            Reporter: Michael Musgrove
>            Priority: Major
>
> I get linkage errors when building the admin tool on Fedora 25. Note that I have log4cxx-902683-fc18x64.jar in my local repo. The linker errors are:
>        [cc] Starting link
>        [cc] cxx/test/lib/libblacktie-codec.so: undefined reference to `log4cxx::helpers::MessageBuffer::str[abi:cxx11](log4cxx::helpers::CharMessageBuffer&)'
>        [cc] cxx/test/lib/libblacktie-core.so: undefined reference to `log4cxx::helpers::CharMessageBuffer::str[abi:cxx11](log4cxx::helpers::CharMessageBuffer&)'
>        [cc] cxx/test/lib/libblacktie-codec.so: undefined reference to `log4cxx::helpers::MessageBuffer::str[abi:cxx11](std::ostream&)'
>        [cc] cxx/test/lib/libblacktie-hybrid.so: undefined reference to `log4cxx::helpers::CharMessageBuffer::operator<<(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
>        [cc] cxx/test/lib/libblacktie-codec.so: undefined reference to `log4cxx::Logger::forcedLog(log4cxx::helpers::ObjectPtrT<log4cxx::Level> const&, std::__cxx11::basic_string<char, std::char_traits<char>, std
> ::allocator<char> > const&, log4cxx::spi::LocationInfo const&) const'
>        [cc] collect2: error: ld returned 1 exit status



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:06:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:06:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2841)
 HybridSocketEndpointQueue::_send() needs wrapper around apr_socket_send()
In-Reply-To: <JIRA.12671589.1484662875000@Atlassian.JIRA>
References: <JIRA.12671589.1484662875000@Atlassian.JIRA>
	<JIRA.12671589.1484662875000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12671589.1484662875000.17113.1546592760801@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-2841:
-----------------------------------

    Assignee:     (was: Amos Feng)


> HybridSocketEndpointQueue::_send() needs wrapper around apr_socket_send()
> -------------------------------------------------------------------------
>
>                 Key: JBTM-2841
>                 URL: https://issues.jboss.org/browse/JBTM-2841
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: BlackTie
>            Reporter: Amos Feng
>            Priority: Major
>
> tpreturn() seems to non-block send without checking tranfer length.
> It needs a wrapper of looping apr_socket_send() until all of the data write to the socket.
> similar like [stomp_write_buffer|https://github.com/jbosstm/narayana/blob/c035f66960d189a5b96d1940c9d251a4e2d7b113/blacktie/hybrid/src/main/cpp/stomp.c]



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:10:01 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:10:01 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2598) Merge in BlackTie
 Javadocs to main Narayana javadocs
In-Reply-To: <JIRA.12598016.1451900178000@Atlassian.JIRA>
References: <JIRA.12598016.1451900178000@Atlassian.JIRA>
	<JIRA.12598016.1451900178000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12598016.1451900178000.17123.1546593001236@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-2598:
-----------------------------------

    Assignee:     (was: Amos Feng)


> Merge in BlackTie Javadocs to main Narayana javadocs
> ----------------------------------------------------
>
>                 Key: JBTM-2598
>                 URL: https://issues.jboss.org/browse/JBTM-2598
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>          Components: Build System, Documentation
>            Reporter: Tom Jenkinson
>            Priority: Minor
>             Fix For: 6.later
>
>
> The BlackTie javadocs are still separate http://narayana.io/documentation/index.html - it would be useful to ensure that they are in the same place as the rest of the Narayana javadocs.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:10:01 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:10:01 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2598) Merge in BlackTie
 Javadocs to main Narayana javadocs
In-Reply-To: <JIRA.12598016.1451900178000@Atlassian.JIRA>
References: <JIRA.12598016.1451900178000@Atlassian.JIRA>
	<JIRA.12598016.1451900178000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12598016.1451900178000.17126.1546593001301@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2598:
--------------------------------
    Component/s: BlackTie


> Merge in BlackTie Javadocs to main Narayana javadocs
> ----------------------------------------------------
>
>                 Key: JBTM-2598
>                 URL: https://issues.jboss.org/browse/JBTM-2598
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>          Components: BlackTie, Build System, Documentation
>            Reporter: Tom Jenkinson
>            Priority: Minor
>             Fix For: 6.later
>
>
> The BlackTie javadocs are still separate http://narayana.io/documentation/index.html - it would be useful to ensure that they are in the same place as the rest of the Narayana javadocs.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:10:01 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:10:01 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2827) No easy way to acquire
 node name from JBoss Transaction SPI
In-Reply-To: <JIRA.12668622.1482351971000@Atlassian.JIRA>
References: <JIRA.12668622.1482351971000@Atlassian.JIRA>
	<JIRA.12668622.1482351971000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12668622.1482351971000.17129.1546593001380@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-2827:
-----------------------------------

    Assignee:     (was: Amos Feng)


> No easy way to acquire node name from JBoss Transaction SPI
> -----------------------------------------------------------
>
>                 Key: JBTM-2827
>                 URL: https://issues.jboss.org/browse/JBTM-2827
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>          Components: Application Server Integration
>            Reporter: David Lloyd
>            Priority: Minor
>
> There's no good way to get the node identifier string for the local transaction environment using the integration SPIs.  I have to use {{com.arjuna.ats.arjuna.common.CoreEnvironmentBean#getNodeIdentifier}} which brings in narayana-jta to make this work.
> It would be nice if this could be gotten from the TransactionManager or perhaps the ExtendedJBossXATerminator.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:10:01 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:10:01 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2856) Add a way to register an
 interposed synchronization without associating the txn
In-Reply-To: <JIRA.12678586.1487868418000@Atlassian.JIRA>
References: <JIRA.12678586.1487868418000@Atlassian.JIRA>
	<JIRA.12678586.1487868418000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12678586.1487868418000.17132.1546593001471@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-2856:
-----------------------------------

    Assignee:     (was: Amos Feng)


> Add a way to register an interposed synchronization without associating the txn
> -------------------------------------------------------------------------------
>
>                 Key: JBTM-2856
>                 URL: https://issues.jboss.org/browse/JBTM-2856
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>          Components: Application Server Integration
>            Reporter: David Lloyd
>            Priority: Major
>
> It would be very useful to the application server if there were an API method to register an interposed synchronization on a transaction that was not currently associated with the calling thread, the same way that non-interposed synchronizations can be.  Right now the only two options are to use TransactionSynchronizationRegistry, which requires that the existing transaction be suspended and a new one associated, or to use reflection to directly call the registerSynchronizationImple method of the transaction.  Neither one is optimal.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:10:02 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:10:02 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2839) Add ability to retrieve
 suppressed exceptions from org.jboss.tm.ImportedTransaction
In-Reply-To: <JIRA.12671055.1484315151000@Atlassian.JIRA>
References: <JIRA.12671055.1484315151000@Atlassian.JIRA>
	<JIRA.12671055.1484315151000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12671055.1484315151000.17135.1546593002274@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-2839:
-----------------------------------

    Assignee:     (was: Amos Feng)


> Add ability to retrieve suppressed exceptions from org.jboss.tm.ImportedTransaction
> -----------------------------------------------------------------------------------
>
>                 Key: JBTM-2839
>                 URL: https://issues.jboss.org/browse/JBTM-2839
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>          Components: Application Server Integration
>            Reporter: David Lloyd
>            Priority: Major
>
> In order to propagate complete failure information from subordinate to parent, we need a method on {{org.jboss.tm.ImportedTransaction}} which allows us to get the suppressed exceptions which occurred as a result of doPrepare and possibly also doOnePhaseCommit so we can attach the cause to the message returned to the master.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:12:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:12:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3057) build javadoc failure
In-Reply-To: <JIRA.12768419.1536219121000@Atlassian.JIRA>
References: <JIRA.12768419.1536219121000@Atlassian.JIRA>
	<JIRA.12768419.1536219121000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12768419.1536219121000.17144.1546593120179@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-3057:
-----------------------------------

    Assignee: Tom Jenkinson  (was: Amos Feng)


> build javadoc failure
> ---------------------
>
>                 Key: JBTM-3057
>                 URL: https://issues.jboss.org/browse/JBTM-3057
>             Project: JBoss Transaction Manager
>          Issue Type: Sub-task
>          Components: Build System
>            Reporter: Amos Feng
>            Assignee: Tom Jenkinson
>            Priority: Major
>
> I have to disable the maven-javadoc-plugin on the JDK9 and it needs more investigation.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:13:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:13:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2697) Add a test to check
 @Transactional work with the narayana osgi bundle
In-Reply-To: <JIRA.12635820.1467187439000@Atlassian.JIRA>
References: <JIRA.12635820.1467187439000@Atlassian.JIRA>
	<JIRA.12635820.1467187439000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12635820.1467187439000.17146.1546593180116@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2697:
--------------------------------
    Component/s: OSGi
                 Testing


> Add a test to check @Transactional work with the narayana osgi bundle
> ---------------------------------------------------------------------
>
>                 Key: JBTM-2697
>                 URL: https://issues.jboss.org/browse/JBTM-2697
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>          Components: OSGi, Testing
>            Reporter: Amos Feng
>            Assignee: Amos Feng
>            Priority: Major
>
> It needs to add a test to check if the annotation works



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:14:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:14:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2659) narayana-osgi-jta build
	bundle warings
In-Reply-To: <JIRA.12617016.1461728759000@Atlassian.JIRA>
References: <JIRA.12617016.1461728759000@Atlassian.JIRA>
	<JIRA.12617016.1461728759000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12617016.1461728759000.17158.1546593240931@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2659:
--------------------------------
    Component/s: OSGi


> narayana-osgi-jta build bundle warings
> --------------------------------------
>
>                 Key: JBTM-2659
>                 URL: https://issues.jboss.org/browse/JBTM-2659
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: OSGi
>            Reporter: Amos Feng
>            Assignee: Amos Feng
>            Priority: Minor
>
> There are three warning when building the bundle.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:15:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:15:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2541) Even ActiveMQ Artemis
 object store is used the Narayana log contains notion of HornetQ store
In-Reply-To: <JIRA.12590221.1445596284000@Atlassian.JIRA>
References: <JIRA.12590221.1445596284000@Atlassian.JIRA>
	<JIRA.12590221.1445596284000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12590221.1445596284000.17166.1546593300295@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-2541:
-----------------------------------

    Assignee:     (was: Amos Feng)


> Even ActiveMQ Artemis object store is used the Narayana log contains notion of HornetQ store
> --------------------------------------------------------------------------------------------
>
>                 Key: JBTM-2541
>                 URL: https://issues.jboss.org/browse/JBTM-2541
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>    Affects Versions: 5.2.5.Final
>            Reporter: Ondra Chaloupka
>            Priority: Minor
>             Fix For: 6.later
>
>
> Currently the Narayna could use journal store which is implemented by ActiveMQ journaling. But after activation the narayana trace log contains messages like 
> {{2015-10-23 12:24:40,735 TRACE [com.arjuna.ats.arjuna] HornetqObjectStore.start()}}.
> If HornetQ object store is not really used the log messages should be changed to correspond to the state.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:15:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:15:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2662) Export org.jboss.tm, has 1,
 private references [org.jboss.logging]
In-Reply-To: <JIRA.12617019.1461728973000@Atlassian.JIRA>
References: <JIRA.12617019.1461728973000@Atlassian.JIRA>
	<JIRA.12617019.1461728973000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12617019.1461728973000.17168.1546593300336@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2662:
--------------------------------
    Component/s: Build System


> Export org.jboss.tm,  has 1,  private references [org.jboss.logging]
> --------------------------------------------------------------------
>
>                 Key: JBTM-2662
>                 URL: https://issues.jboss.org/browse/JBTM-2662
>             Project: JBoss Transaction Manager
>          Issue Type: Sub-task
>          Components: Build System
>            Reporter: Amos Feng
>            Assignee: Amos Feng
>            Priority: Minor
>




--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:15:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:15:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2661) Unknown directive
 cardinality: in Require-Capability
In-Reply-To: <JIRA.12617018.1461728939000@Atlassian.JIRA>
References: <JIRA.12617018.1461728939000@Atlassian.JIRA>
	<JIRA.12617018.1461728939000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12617018.1461728939000.17170.1546593300386@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2661:
--------------------------------
    Component/s: Build System


> Unknown directive cardinality: in Require-Capability
> ----------------------------------------------------
>
>                 Key: JBTM-2661
>                 URL: https://issues.jboss.org/browse/JBTM-2661
>             Project: JBoss Transaction Manager
>          Issue Type: Sub-task
>          Components: Build System
>            Reporter: Amos Feng
>            Assignee: Amos Feng
>            Priority: Minor
>
> [WARNING] Bundle org.jboss.narayana.osgi:narayana-osgi-jta:bundle:5.3.3.Final-SNAPSHOT : Unknown directive cardinality: in Require-Capability, allowed directives are effective:,resolution:,filter:, and 'x-*'.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:16:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:16:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2372) Create integration test
	for JBTM-2356
In-Reply-To: <JIRA.12568848.1429535321000@Atlassian.JIRA>
References: <JIRA.12568848.1429535321000@Atlassian.JIRA>
	<JIRA.12568848.1429535321000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12568848.1429535321000.17176.1546593360170@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-2372:
-----------------------------------

    Assignee: Michael Musgrove  (was: Amos Feng)


> Create integration test for JBTM-2356
> -------------------------------------
>
>                 Key: JBTM-2372
>                 URL: https://issues.jboss.org/browse/JBTM-2372
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>          Components: REST
>            Reporter: Gytis Trikleris
>            Assignee: Michael Musgrove
>            Priority: Minor
>             Fix For: 5.later
>
>
> There was an integration test for it: https://github.com/jbosstm/narayana/commit/5b278de35b9095a27e27514cca4eea51d8e231cf.
> However, it was failing on CI intermittently and had to be reverted. 



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:20:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:20:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2571) Enable code coverage for
 XTS crash recovery tests
In-Reply-To: <JIRA.12594412.1448633013000@Atlassian.JIRA>
References: <JIRA.12594412.1448633013000@Atlassian.JIRA>
	<JIRA.12594412.1448633013000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12594412.1448633013000.17189.1546593600151@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-2571:
-----------------------------------

    Assignee: Ondra Chaloupka  (was: Amos Feng)


> Enable code coverage for XTS crash recovery tests
> -------------------------------------------------
>
>                 Key: JBTM-2571
>                 URL: https://issues.jboss.org/browse/JBTM-2571
>             Project: JBoss Transaction Manager
>          Issue Type: Sub-task
>          Components: XTS
>            Reporter: Gytis Trikleris
>            Assignee: Ondra Chaloupka
>            Priority: Minor
>
> Code coverage data is not collected during the XTS crash recovery tests execution. Currently this seems to be blocked by [1], [2], and [3].
> [1] https://community.jboss.org/message/817252
> [2] https://issues.jboss.org/browse/ARQ-1014
> [3] https://issues.jboss.org/browse/ARQ-918



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:21:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:21:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2580) Create a Narayana
	troubleshooting guide
In-Reply-To: <JIRA.12595716.1449576818000@Atlassian.JIRA>
References: <JIRA.12595716.1449576818000@Atlassian.JIRA>
	<JIRA.12595716.1449576818000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12595716.1449576818000.17196.1546593660403@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson closed JBTM-2580.
-------------------------------
    Fix Version/s:     (was: 5.later)
       Resolution: Migrated to another ITS


> Create a Narayana troubleshooting guide
> ---------------------------------------
>
>                 Key: JBTM-2580
>                 URL: https://issues.jboss.org/browse/JBTM-2580
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>          Components: Documentation
>            Reporter: Tom Jenkinson
>            Assignee: Amos Feng
>            Priority: Minor
>
> This information may already exist but is possibly fragmented. This issue is to record the fact that we need to collate this.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:25:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:25:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2805) Karaf fails to build in CI
In-Reply-To: <JIRA.12664503.1480515112000@Atlassian.JIRA>
References: <JIRA.12664503.1480515112000@Atlassian.JIRA>
	<JIRA.12664503.1480515112000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12664503.1480515112000.17211.1546593900109@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2805:
--------------------------------
    Component/s: OSGi


> Karaf fails to build in CI
> --------------------------
>
>                 Key: JBTM-2805
>                 URL: https://issues.jboss.org/browse/JBTM-2805
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>          Components: Build System, OSGi
>            Reporter: Tom Jenkinson
>            Assignee: Amos Feng
>            Priority: Major
>
> We should try to avoid building Karaf in CI.
> At this point it fails to build.
> {code}
> [INFO] --- maven-resources-plugin:2.7:resources (process-resources) @ apache-karaf-minimal ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 4 resources
> [INFO] 
> [INFO] --- karaf-maven-plugin:4.1.0-SNAPSHOT:assembly (process-resources) @ apache-karaf-minimal ---
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Karaf ....................................... SUCCESS [  4.795 s]
> [INFO] Apache Karaf :: JAAS ............................... SUCCESS [  0.017 s]
> [INFO] Apache Karaf :: JAAS :: Boot ....................... SUCCESS [  2.413 s]
> [INFO] Apache Karaf :: Util ............................... SUCCESS [  4.843 s]
> [INFO] Apache Karaf :: Main ............................... SUCCESS [ 11.143 s]
> [INFO] Apache Karaf :: Features ........................... SUCCESS [  0.012 s]
> [INFO] Apache Karaf :: Features :: Extension .............. SUCCESS [  0.157 s]
> [INFO] Apache Karaf :: Service ............................ SUCCESS [  0.012 s]
> [INFO] Apache Karaf :: Service :: Guard ................... SUCCESS [  8.831 s]
> [INFO] Apache Karaf :: Shell .............................. SUCCESS [  0.010 s]
> [INFO] Apache Karaf :: Shell :: Core ...................... SUCCESS [  6.523 s]
> [INFO] Apache Karaf :: Tooling ............................ SUCCESS [  0.013 s]
> [INFO] Apache Karaf :: Tooling :: Maven Karaf Plugin for Services Metadata SUCCESS [ 58.898 s]
> [INFO] Apache Karaf :: Features :: Core ................... SUCCESS [  5.522 s]
> [INFO] Apache Karaf :: Features :: Command ................ SUCCESS [  0.845 s]
> [INFO] Apache Karaf :: KAR :: Core ........................ SUCCESS [  0.869 s]
> [INFO] Apache Karaf :: JAAS :: Config ..................... SUCCESS [  7.906 s]
> [INFO] Apache Karaf :: JAAS :: Modules .................... SUCCESS [ 18.313 s]
> [INFO] Apache Karaf :: Bundle ............................. SUCCESS [  0.009 s]
> [INFO] Apache Karaf :: Bundle :: Core ..................... SUCCESS [  1.076 s]
> [INFO] Apache Karaf :: Bundle :: BlueprintStateService .... SUCCESS [  0.095 s]
> [INFO] Apache Karaf :: Bundle :: SpringStateService ....... SUCCESS [  8.690 s]
> [INFO] Apache Karaf :: ConfigAdmin :: Core ................ SUCCESS [  0.454 s]
> [INFO] Apache Karaf :: Tooling :: Utils ................... SUCCESS [  2.911 s]
> [INFO] Apache Karaf :: Deployer ........................... SUCCESS [  0.007 s]
> [INFO] Apache Karaf :: Deployer :: Blueprint .............. SUCCESS [  2.328 s]
> [INFO] Apache Karaf :: Deployer :: Spring ................. SUCCESS [  0.166 s]
> [INFO] Apache Karaf :: Demos :: Profiles :: Registry ...... SUCCESS [  0.031 s]
> [INFO] Apache Karaf :: Profile :: Core .................... SUCCESS [  9.123 s]
> [INFO] Apache Karaf :: Instance :: Core ................... SUCCESS [  1.096 s]
> [INFO] Apache Karaf :: Package :: Core .................... SUCCESS [  0.316 s]
> [INFO] Apache Karaf :: HTTP :: Core ....................... SUCCESS [  3.623 s]
> [INFO] Apache Karaf :: Service :: Core .................... SUCCESS [  0.323 s]
> [INFO] Apache Karaf :: Log :: Core ........................ SUCCESS [  4.122 s]
> [INFO] Apache Karaf :: Deployer :: Features ............... SUCCESS [  0.568 s]
> [INFO] Apache Karaf :: Deployer :: Karaf Archive (.kar) ... SUCCESS [  0.491 s]
> [INFO] Apache Karaf :: Deployer :: Wrap Non OSGi Jar ...... SUCCESS [  0.100 s]
> [INFO] Apache Karaf :: Shell :: Various Commands .......... SUCCESS [  0.471 s]
> [INFO] Apache Karaf :: Shell :: Console ................... SUCCESS [  3.362 s]
> [INFO] Apache Karaf :: Shell :: Table ..................... SUCCESS [  0.111 s]
> [INFO] Apache Karaf :: Shell :: SSH ....................... SUCCESS [  2.032 s]
> [INFO] Apache Karaf :: JAAS :: Jasypt Encryption .......... SUCCESS [  2.921 s]
> [INFO] Apache Karaf :: JAAS :: Command .................... SUCCESS [  0.492 s]
> [INFO] Apache Karaf :: JAAS :: Blueprint .................. SUCCESS [  0.007 s]
> [INFO] Apache Karaf :: JAAS :: Blueprint :: Config ........ SUCCESS [  0.081 s]
> [INFO] Apache Karaf :: JAAS :: Blueprint :: Jasypt ........ SUCCESS [  1.509 s]
> [INFO] Apache Karaf :: Client ............................. SUCCESS [  0.164 s]
> [INFO] Apache Karaf :: Management ......................... SUCCESS [  0.008 s]
> [INFO] Apache Karaf :: Management ......................... SUCCESS [  0.212 s]
> [INFO] Apache Karaf :: System :: Core ..................... SUCCESS [  0.329 s]
> [INFO] Apache Karaf :: Web :: Core ........................ SUCCESS [  0.328 s]
> [INFO] Apache Karaf :: Wrapper :: Core .................... SUCCESS [  0.667 s]
> [INFO] Apache Karaf :: Web Console ........................ SUCCESS [  0.007 s]
> [INFO] Apache Karaf :: Web Console :: Console ............. SUCCESS [  3.205 s]
> [INFO] Apache Karaf :: Web Console :: Features Plugin ..... SUCCESS [  0.559 s]
> [INFO] Apache Karaf :: Web Console :: Gogo Plugin ......... SUCCESS [  0.617 s]
> [INFO] Apache Karaf :: Web Console :: HTTP Plugin ......... SUCCESS [  0.567 s]
> [INFO] Apache Karaf :: Web Console :: Instance Plugin ..... SUCCESS [  0.224 s]
> [INFO] Apache Karaf :: Exception .......................... SUCCESS [  0.031 s]
> [INFO] Apache Karaf :: Scheduler :: Core .................. SUCCESS [  3.628 s]
> [INFO] Apache Karaf :: Declarative Services (DS) .......... SUCCESS [  0.007 s]
> [INFO] Apache Karaf :: SCR :: Shell Commands .............. SUCCESS [  3.391 s]
> [INFO] Apache Karaf :: SCR :: Management MBeans ........... SUCCESS [  1.491 s]
> [INFO] Apache Karaf :: SCR :: Bundle State ................ SUCCESS [  0.176 s]
> [INFO] Apache Karaf :: SCR :: Examples .................... SUCCESS [  0.006 s]
> [INFO] Apache Karaf :: SCR :: Examples :: Basic Service ... SUCCESS [  0.060 s]
> [INFO] Apache Karaf :: SCR :: Examples :: Managed Services  SUCCESS [  0.076 s]
> [INFO] Apache Karaf :: SCR :: Examples :: Component Factories SUCCESS [  0.063 s]
> [INFO] Apache Karaf :: Diagnostic ......................... SUCCESS [  0.007 s]
> [INFO] Apache Karaf :: Diagnostic :: Boot ................. SUCCESS [  0.096 s]
> [INFO] Apache Karaf :: Diagnostic :: Core ................. SUCCESS [  0.748 s]
> [INFO] Apache Karaf :: OBR :: Core ........................ SUCCESS [  1.771 s]
> [INFO] Apache Karaf :: JNDI :: Core ....................... SUCCESS [  1.765 s]
> [INFO] Apache Karaf :: JDBC :: Core ....................... SUCCESS [  0.410 s]
> [INFO] Apache Karaf :: JMS :: Core ........................ SUCCESS [  6.591 s]
> [INFO] Apache Karaf :: Features ........................... SUCCESS [  0.006 s]
> [INFO] Apache Karaf :: JPA :: Parent ...................... SUCCESS [  0.006 s]
> [INFO] Apache Karaf :: JPA :: Hibernate ................... SUCCESS [  8.436 s]
> [INFO] Apache Karaf :: OSGi Services :: Coordinator ....... SUCCESS [  1.763 s]
> [INFO] Apache Karaf :: OSGi Services :: EventAdmin ........ SUCCESS [  1.511 s]
> [INFO] Apache Karaf :: OSGi Services :: Static ConfigAdmin  SUCCESS [  0.087 s]
> [INFO] Apache Karaf :: OSGi Services ...................... SUCCESS [  0.006 s]
> [INFO] Apache Karaf :: Subsystem :: Core .................. SUCCESS [  5.008 s]
> [INFO] Apache Karaf :: OSGi Services :: Event ............. SUCCESS [  1.709 s]
> [INFO] Apache Karaf :: Tooling :: Maven Karaf Plugin ...... SUCCESS [  7.875 s]
> [INFO] Apache Karaf :: Assemblies ......................... SUCCESS [  0.008 s]
> [INFO] Apache Karaf :: Assemblies :: Features ............. SUCCESS [  0.006 s]
> [INFO] Apache Karaf :: Assemblies :: Features :: Base ..... SUCCESS [  3.828 s]
> [INFO] Apache Karaf :: Assemblies :: Features :: Framework  SUCCESS [  2.555 s]
> [INFO] Apache Karaf :: Assemblies :: Features :: Static ... SUCCESS [  1.836 s]
> [INFO] Apache Karaf :: Assemblies :: Features :: Standard . SUCCESS [01:12 min]
> [INFO] Apache Karaf :: Assemblies :: Features :: Spring ... SUCCESS [01:19 min]
> [INFO] Apache Karaf :: Assemblies :: Features :: Enterprise SUCCESS [ 42.574 s]
> [INFO] Apache Karaf :: Assemblies :: Demos ................ SUCCESS [  0.075 s]
> [INFO] Apache Karaf :: Assemblies :: Minimal Distribution . FAILURE [  0.097 s]
> [INFO] Apache Karaf :: Assemblies :: Default Distribution . SKIPPED
> [INFO] Apache Karaf :: Demos .............................. SKIPPED
> [INFO] Apache Karaf :: Demos :: Web ....................... SKIPPED
> [INFO] Apache Karaf :: Demos :: Branding :: Shell ......... SKIPPED
> [INFO] Apache Karaf :: Demos :: Command :: Extend Console . SKIPPED
> [INFO] Apache Karaf :: Demos :: Demo Dump provider ........ SKIPPED
> [INFO] Apache Karaf :: Demos :: Deployer .................. SKIPPED
> [INFO] Apache Karaf :: Demos :: Deployer :: Kar ........... SKIPPED
> [INFO] Apache Karaf :: Demos :: Deployer :: Bundle ........ SKIPPED
> [INFO] Apache Karaf :: Demos :: Profiles :: Dynamic Assembly SKIPPED
> [INFO] Apache Karaf :: Demos :: Profiles :: Static Assembly SKIPPED
> [INFO] Apache Karaf :: Demos :: Profiles .................. SKIPPED
> [INFO] Apache Karaf :: Archetypes ......................... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Assembly Archetype ... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Command Archetype .... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Feature Archetype .... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Kar Archetype ........ SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Bundle Archetype ..... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Blueprint Archetype .. SKIPPED
> [INFO] Apache Karaf :: Integration Tests .................. SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 07:17 min
> [INFO] Finished at: 2016-11-29T00:19:34+00:00
> [INFO] Final Memory: 165M/1003M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:assembly (process-resources) on project apache-karaf-minimal: Unable to parse configuration of mojo org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:assembly for parameter pidsToExtract: Cannot assign configuration entry 'pidsToExtract' with value '!jmx.acl.*,
> [ERROR] !org.apache.karaf.command.acl.*,
> [ERROR] *' of type java.lang.String to property of type java.util.List
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginConfigurationException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR]   mvn <goals> -rf :apache-karaf-minimal
> {code}



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:25:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:25:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2659) narayana-osgi-jta build
	bundle warings
In-Reply-To: <JIRA.12617016.1461728759000@Atlassian.JIRA>
References: <JIRA.12617016.1461728759000@Atlassian.JIRA>
	<JIRA.12617016.1461728759000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12617016.1461728759000.17213.1546593900153@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2659:
--------------------------------
    Priority: Major  (was: Minor)


> narayana-osgi-jta build bundle warings
> --------------------------------------
>
>                 Key: JBTM-2659
>                 URL: https://issues.jboss.org/browse/JBTM-2659
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: OSGi
>            Reporter: Amos Feng
>            Assignee: Amos Feng
>            Priority: Major
>
> There are three warning when building the bundle.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:29:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:29:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2661) Unknown directive
 cardinality: in Require-Capability
In-Reply-To: <JIRA.12617018.1461728939000@Atlassian.JIRA>
References: <JIRA.12617018.1461728939000@Atlassian.JIRA>
	<JIRA.12617018.1461728939000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12617018.1461728939000.17240.1546594140294@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2661:
--------------------------------
    Component/s: OSGi


> Unknown directive cardinality: in Require-Capability
> ----------------------------------------------------
>
>                 Key: JBTM-2661
>                 URL: https://issues.jboss.org/browse/JBTM-2661
>             Project: JBoss Transaction Manager
>          Issue Type: Sub-task
>          Components: Build System, OSGi
>            Reporter: Amos Feng
>            Assignee: Amos Feng
>            Priority: Minor
>
> [WARNING] Bundle org.jboss.narayana.osgi:narayana-osgi-jta:bundle:5.3.3.Final-SNAPSHOT : Unknown directive cardinality: in Require-Capability, allowed directives are effective:,resolution:,filter:, and 'x-*'.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan  4 04:29:00 2019
From: issues at jboss.org (Tom Jenkinson (Jira))
Date: Fri, 4 Jan 2019 04:29:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2662) Export org.jboss.tm, has 1,
 private references [org.jboss.logging]
In-Reply-To: <JIRA.12617019.1461728973000@Atlassian.JIRA>
References: <JIRA.12617019.1461728973000@Atlassian.JIRA>
	<JIRA.12617019.1461728973000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12617019.1461728973000.17242.1546594140329@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-2662:
--------------------------------
    Component/s: OSGi


> Export org.jboss.tm,  has 1,  private references [org.jboss.logging]
> --------------------------------------------------------------------
>
>                 Key: JBTM-2662
>                 URL: https://issues.jboss.org/browse/JBTM-2662
>             Project: JBoss Transaction Manager
>          Issue Type: Sub-task
>          Components: Build System, OSGi
>            Reporter: Amos Feng
>            Assignee: Amos Feng
>            Priority: Minor
>




--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Sun Jan  6 20:22:00 2019
From: issues at jboss.org (Amos Feng (Jira))
Date: Sun, 6 Jan 2019 20:22:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2805) Karaf fails to build in CI
In-Reply-To: <JIRA.12664503.1480515112000@Atlassian.JIRA>
References: <JIRA.12664503.1480515112000@Atlassian.JIRA>
	<JIRA.12664503.1480515112000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12664503.1480515112000.20231.1546824120176@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amos Feng closed JBTM-2805.
---------------------------
    Resolution: Done


no need to build the karaf now

> Karaf fails to build in CI
> --------------------------
>
>                 Key: JBTM-2805
>                 URL: https://issues.jboss.org/browse/JBTM-2805
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>          Components: Build System, OSGi
>            Reporter: Tom Jenkinson
>            Assignee: Amos Feng
>            Priority: Major
>
> We should try to avoid building Karaf in CI.
> At this point it fails to build.
> {code}
> [INFO] --- maven-resources-plugin:2.7:resources (process-resources) @ apache-karaf-minimal ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 4 resources
> [INFO] 
> [INFO] --- karaf-maven-plugin:4.1.0-SNAPSHOT:assembly (process-resources) @ apache-karaf-minimal ---
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Karaf ....................................... SUCCESS [  4.795 s]
> [INFO] Apache Karaf :: JAAS ............................... SUCCESS [  0.017 s]
> [INFO] Apache Karaf :: JAAS :: Boot ....................... SUCCESS [  2.413 s]
> [INFO] Apache Karaf :: Util ............................... SUCCESS [  4.843 s]
> [INFO] Apache Karaf :: Main ............................... SUCCESS [ 11.143 s]
> [INFO] Apache Karaf :: Features ........................... SUCCESS [  0.012 s]
> [INFO] Apache Karaf :: Features :: Extension .............. SUCCESS [  0.157 s]
> [INFO] Apache Karaf :: Service ............................ SUCCESS [  0.012 s]
> [INFO] Apache Karaf :: Service :: Guard ................... SUCCESS [  8.831 s]
> [INFO] Apache Karaf :: Shell .............................. SUCCESS [  0.010 s]
> [INFO] Apache Karaf :: Shell :: Core ...................... SUCCESS [  6.523 s]
> [INFO] Apache Karaf :: Tooling ............................ SUCCESS [  0.013 s]
> [INFO] Apache Karaf :: Tooling :: Maven Karaf Plugin for Services Metadata SUCCESS [ 58.898 s]
> [INFO] Apache Karaf :: Features :: Core ................... SUCCESS [  5.522 s]
> [INFO] Apache Karaf :: Features :: Command ................ SUCCESS [  0.845 s]
> [INFO] Apache Karaf :: KAR :: Core ........................ SUCCESS [  0.869 s]
> [INFO] Apache Karaf :: JAAS :: Config ..................... SUCCESS [  7.906 s]
> [INFO] Apache Karaf :: JAAS :: Modules .................... SUCCESS [ 18.313 s]
> [INFO] Apache Karaf :: Bundle ............................. SUCCESS [  0.009 s]
> [INFO] Apache Karaf :: Bundle :: Core ..................... SUCCESS [  1.076 s]
> [INFO] Apache Karaf :: Bundle :: BlueprintStateService .... SUCCESS [  0.095 s]
> [INFO] Apache Karaf :: Bundle :: SpringStateService ....... SUCCESS [  8.690 s]
> [INFO] Apache Karaf :: ConfigAdmin :: Core ................ SUCCESS [  0.454 s]
> [INFO] Apache Karaf :: Tooling :: Utils ................... SUCCESS [  2.911 s]
> [INFO] Apache Karaf :: Deployer ........................... SUCCESS [  0.007 s]
> [INFO] Apache Karaf :: Deployer :: Blueprint .............. SUCCESS [  2.328 s]
> [INFO] Apache Karaf :: Deployer :: Spring ................. SUCCESS [  0.166 s]
> [INFO] Apache Karaf :: Demos :: Profiles :: Registry ...... SUCCESS [  0.031 s]
> [INFO] Apache Karaf :: Profile :: Core .................... SUCCESS [  9.123 s]
> [INFO] Apache Karaf :: Instance :: Core ................... SUCCESS [  1.096 s]
> [INFO] Apache Karaf :: Package :: Core .................... SUCCESS [  0.316 s]
> [INFO] Apache Karaf :: HTTP :: Core ....................... SUCCESS [  3.623 s]
> [INFO] Apache Karaf :: Service :: Core .................... SUCCESS [  0.323 s]
> [INFO] Apache Karaf :: Log :: Core ........................ SUCCESS [  4.122 s]
> [INFO] Apache Karaf :: Deployer :: Features ............... SUCCESS [  0.568 s]
> [INFO] Apache Karaf :: Deployer :: Karaf Archive (.kar) ... SUCCESS [  0.491 s]
> [INFO] Apache Karaf :: Deployer :: Wrap Non OSGi Jar ...... SUCCESS [  0.100 s]
> [INFO] Apache Karaf :: Shell :: Various Commands .......... SUCCESS [  0.471 s]
> [INFO] Apache Karaf :: Shell :: Console ................... SUCCESS [  3.362 s]
> [INFO] Apache Karaf :: Shell :: Table ..................... SUCCESS [  0.111 s]
> [INFO] Apache Karaf :: Shell :: SSH ....................... SUCCESS [  2.032 s]
> [INFO] Apache Karaf :: JAAS :: Jasypt Encryption .......... SUCCESS [  2.921 s]
> [INFO] Apache Karaf :: JAAS :: Command .................... SUCCESS [  0.492 s]
> [INFO] Apache Karaf :: JAAS :: Blueprint .................. SUCCESS [  0.007 s]
> [INFO] Apache Karaf :: JAAS :: Blueprint :: Config ........ SUCCESS [  0.081 s]
> [INFO] Apache Karaf :: JAAS :: Blueprint :: Jasypt ........ SUCCESS [  1.509 s]
> [INFO] Apache Karaf :: Client ............................. SUCCESS [  0.164 s]
> [INFO] Apache Karaf :: Management ......................... SUCCESS [  0.008 s]
> [INFO] Apache Karaf :: Management ......................... SUCCESS [  0.212 s]
> [INFO] Apache Karaf :: System :: Core ..................... SUCCESS [  0.329 s]
> [INFO] Apache Karaf :: Web :: Core ........................ SUCCESS [  0.328 s]
> [INFO] Apache Karaf :: Wrapper :: Core .................... SUCCESS [  0.667 s]
> [INFO] Apache Karaf :: Web Console ........................ SUCCESS [  0.007 s]
> [INFO] Apache Karaf :: Web Console :: Console ............. SUCCESS [  3.205 s]
> [INFO] Apache Karaf :: Web Console :: Features Plugin ..... SUCCESS [  0.559 s]
> [INFO] Apache Karaf :: Web Console :: Gogo Plugin ......... SUCCESS [  0.617 s]
> [INFO] Apache Karaf :: Web Console :: HTTP Plugin ......... SUCCESS [  0.567 s]
> [INFO] Apache Karaf :: Web Console :: Instance Plugin ..... SUCCESS [  0.224 s]
> [INFO] Apache Karaf :: Exception .......................... SUCCESS [  0.031 s]
> [INFO] Apache Karaf :: Scheduler :: Core .................. SUCCESS [  3.628 s]
> [INFO] Apache Karaf :: Declarative Services (DS) .......... SUCCESS [  0.007 s]
> [INFO] Apache Karaf :: SCR :: Shell Commands .............. SUCCESS [  3.391 s]
> [INFO] Apache Karaf :: SCR :: Management MBeans ........... SUCCESS [  1.491 s]
> [INFO] Apache Karaf :: SCR :: Bundle State ................ SUCCESS [  0.176 s]
> [INFO] Apache Karaf :: SCR :: Examples .................... SUCCESS [  0.006 s]
> [INFO] Apache Karaf :: SCR :: Examples :: Basic Service ... SUCCESS [  0.060 s]
> [INFO] Apache Karaf :: SCR :: Examples :: Managed Services  SUCCESS [  0.076 s]
> [INFO] Apache Karaf :: SCR :: Examples :: Component Factories SUCCESS [  0.063 s]
> [INFO] Apache Karaf :: Diagnostic ......................... SUCCESS [  0.007 s]
> [INFO] Apache Karaf :: Diagnostic :: Boot ................. SUCCESS [  0.096 s]
> [INFO] Apache Karaf :: Diagnostic :: Core ................. SUCCESS [  0.748 s]
> [INFO] Apache Karaf :: OBR :: Core ........................ SUCCESS [  1.771 s]
> [INFO] Apache Karaf :: JNDI :: Core ....................... SUCCESS [  1.765 s]
> [INFO] Apache Karaf :: JDBC :: Core ....................... SUCCESS [  0.410 s]
> [INFO] Apache Karaf :: JMS :: Core ........................ SUCCESS [  6.591 s]
> [INFO] Apache Karaf :: Features ........................... SUCCESS [  0.006 s]
> [INFO] Apache Karaf :: JPA :: Parent ...................... SUCCESS [  0.006 s]
> [INFO] Apache Karaf :: JPA :: Hibernate ................... SUCCESS [  8.436 s]
> [INFO] Apache Karaf :: OSGi Services :: Coordinator ....... SUCCESS [  1.763 s]
> [INFO] Apache Karaf :: OSGi Services :: EventAdmin ........ SUCCESS [  1.511 s]
> [INFO] Apache Karaf :: OSGi Services :: Static ConfigAdmin  SUCCESS [  0.087 s]
> [INFO] Apache Karaf :: OSGi Services ...................... SUCCESS [  0.006 s]
> [INFO] Apache Karaf :: Subsystem :: Core .................. SUCCESS [  5.008 s]
> [INFO] Apache Karaf :: OSGi Services :: Event ............. SUCCESS [  1.709 s]
> [INFO] Apache Karaf :: Tooling :: Maven Karaf Plugin ...... SUCCESS [  7.875 s]
> [INFO] Apache Karaf :: Assemblies ......................... SUCCESS [  0.008 s]
> [INFO] Apache Karaf :: Assemblies :: Features ............. SUCCESS [  0.006 s]
> [INFO] Apache Karaf :: Assemblies :: Features :: Base ..... SUCCESS [  3.828 s]
> [INFO] Apache Karaf :: Assemblies :: Features :: Framework  SUCCESS [  2.555 s]
> [INFO] Apache Karaf :: Assemblies :: Features :: Static ... SUCCESS [  1.836 s]
> [INFO] Apache Karaf :: Assemblies :: Features :: Standard . SUCCESS [01:12 min]
> [INFO] Apache Karaf :: Assemblies :: Features :: Spring ... SUCCESS [01:19 min]
> [INFO] Apache Karaf :: Assemblies :: Features :: Enterprise SUCCESS [ 42.574 s]
> [INFO] Apache Karaf :: Assemblies :: Demos ................ SUCCESS [  0.075 s]
> [INFO] Apache Karaf :: Assemblies :: Minimal Distribution . FAILURE [  0.097 s]
> [INFO] Apache Karaf :: Assemblies :: Default Distribution . SKIPPED
> [INFO] Apache Karaf :: Demos .............................. SKIPPED
> [INFO] Apache Karaf :: Demos :: Web ....................... SKIPPED
> [INFO] Apache Karaf :: Demos :: Branding :: Shell ......... SKIPPED
> [INFO] Apache Karaf :: Demos :: Command :: Extend Console . SKIPPED
> [INFO] Apache Karaf :: Demos :: Demo Dump provider ........ SKIPPED
> [INFO] Apache Karaf :: Demos :: Deployer .................. SKIPPED
> [INFO] Apache Karaf :: Demos :: Deployer :: Kar ........... SKIPPED
> [INFO] Apache Karaf :: Demos :: Deployer :: Bundle ........ SKIPPED
> [INFO] Apache Karaf :: Demos :: Profiles :: Dynamic Assembly SKIPPED
> [INFO] Apache Karaf :: Demos :: Profiles :: Static Assembly SKIPPED
> [INFO] Apache Karaf :: Demos :: Profiles .................. SKIPPED
> [INFO] Apache Karaf :: Archetypes ......................... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Assembly Archetype ... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Command Archetype .... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Feature Archetype .... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Kar Archetype ........ SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Bundle Archetype ..... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Blueprint Archetype .. SKIPPED
> [INFO] Apache Karaf :: Integration Tests .................. SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 07:17 min
> [INFO] Finished at: 2016-11-29T00:19:34+00:00
> [INFO] Final Memory: 165M/1003M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:assembly (process-resources) on project apache-karaf-minimal: Unable to parse configuration of mojo org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:assembly for parameter pidsToExtract: Cannot assign configuration entry 'pidsToExtract' with value '!jmx.acl.*,
> [ERROR] !org.apache.karaf.command.acl.*,
> [ERROR] *' of type java.lang.String to property of type java.util.List
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginConfigurationException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR]   mvn <goals> -rf :apache-karaf-minimal
> {code}



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Sun Jan  6 20:22:00 2019
From: issues at jboss.org (Amos Feng (Jira))
Date: Sun, 6 Jan 2019 20:22:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2816) Quickstart can not find
 the mvn.bat after upgrade to maven 3.3.9
In-Reply-To: <JIRA.12667175.1481602016000@Atlassian.JIRA>
References: <JIRA.12667175.1481602016000@Atlassian.JIRA>
	<JIRA.12667175.1481602016000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12667175.1481602016000.20234.1546824120233@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amos Feng closed JBTM-2816.
---------------------------
    Resolution: Done


> Quickstart can not find the mvn.bat after upgrade to maven 3.3.9
> ----------------------------------------------------------------
>
>                 Key: JBTM-2816
>                 URL: https://issues.jboss.org/browse/JBTM-2816
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: Build System, Demonstrator
>            Reporter: Amos Feng
>            Assignee: Amos Feng
>            Priority: Major
>
> The maven 3.3.9 rename the mvn.bat to mvn



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Sun Jan  6 20:29:00 2019
From: issues at jboss.org (Amos Feng (Jira))
Date: Sun, 6 Jan 2019 20:29:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3054) Postgres test failure on
	Narayana Tomcat
In-Reply-To: <JIRA.12767042.1535447389000@Atlassian.JIRA>
References: <JIRA.12767042.1535447389000@Atlassian.JIRA>
	<JIRA.12767042.1535447389000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12767042.1535447389000.20255.1546824540110@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amos Feng closed JBTM-3054.
---------------------------
    Resolution: Done


> Postgres test failure on Narayana Tomcat
> ----------------------------------------
>
>                 Key: JBTM-3054
>                 URL: https://issues.jboss.org/browse/JBTM-3054
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: Testing, Tomcat
>            Reporter: Tom Jenkinson
>            Assignee: Amos Feng
>            Priority: Major
>
> Log contains:
> {code}
> BaseITCase>AbstractCase.init:65 ? IllegalArgument version.postgresql must not
> {code}
> In http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/247/, http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/246/, http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/245/



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Sun Jan  6 20:30:00 2019
From: issues at jboss.org (Amos Feng (Jira))
Date: Sun, 6 Jan 2019 20:30:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2402) Karaf Integration
In-Reply-To: <JIRA.12571281.1431348726000@Atlassian.JIRA>
References: <JIRA.12571281.1431348726000@Atlassian.JIRA>
	<JIRA.12571281.1431348726000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12571281.1431348726000.20258.1546824600175@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amos Feng closed JBTM-2402.
---------------------------
    Fix Version/s: 5.3.5.Final
                       (was: 5.later)
       Resolution: Done


> Karaf Integration
> -----------------
>
>                 Key: JBTM-2402
>                 URL: https://issues.jboss.org/browse/JBTM-2402
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>          Components: Application Server Integration, Demonstrator, Documentation
>            Reporter: Tom Jenkinson
>            Assignee: Amos Feng
>            Priority: Major
>             Fix For: 5.3.5.Final
>
>
> We should create a quickstart to demonstrate how to install and use our bundle. It should also be described in our project (community) manual.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Sun Jan  6 20:31:00 2019
From: issues at jboss.org (Amos Feng (Jira))
Date: Sun, 6 Jan 2019 20:31:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2697) Add a test to check
 @Transactional work with the narayana osgi bundle
In-Reply-To: <JIRA.12635820.1467187439000@Atlassian.JIRA>
References: <JIRA.12635820.1467187439000@Atlassian.JIRA>
	<JIRA.12635820.1467187439000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12635820.1467187439000.20261.1546824660111@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amos Feng updated JBTM-2697:
----------------------------
    Priority: Minor  (was: Major)


> Add a test to check @Transactional work with the narayana osgi bundle
> ---------------------------------------------------------------------
>
>                 Key: JBTM-2697
>                 URL: https://issues.jboss.org/browse/JBTM-2697
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>          Components: OSGi, Testing
>            Reporter: Amos Feng
>            Assignee: Amos Feng
>            Priority: Minor
>
> It needs to add a test to check if the annotation works



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Sun Jan  6 20:32:00 2019
From: issues at jboss.org (Amos Feng (Jira))
Date: Sun, 6 Jan 2019 20:32:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2659) narayana-osgi-jta build
	bundle warings
In-Reply-To: <JIRA.12617016.1461728759000@Atlassian.JIRA>
References: <JIRA.12617016.1461728759000@Atlassian.JIRA>
	<JIRA.12617016.1461728759000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12617016.1461728759000.20264.1546824720114@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amos Feng updated JBTM-2659:
----------------------------
    Priority: Minor  (was: Major)


> narayana-osgi-jta build bundle warings
> --------------------------------------
>
>                 Key: JBTM-2659
>                 URL: https://issues.jboss.org/browse/JBTM-2659
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: OSGi
>            Reporter: Amos Feng
>            Assignee: Amos Feng
>            Priority: Minor
>
> There are three warning when building the bundle.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Mon Jan  7 12:49:00 2019
From: issues at jboss.org (Michael Musgrove (Jira))
Date: Mon, 7 Jan 2019 12:49:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3091) LRA module should depend
 on a specific snapshot build
In-Reply-To: <JIRA.12786390.1546883290000@Atlassian.JIRA>
References: <JIRA.12786390.1546883290000@Atlassian.JIRA>
	<JIRA.12786390.1546883290188@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12786390.1546883290000.27342.1546883340070@Atlassian.JIRA>

Michael Musgrove created JBTM-3091:
--------------------------------------

             Summary: LRA module should depend on a specific snapshot build
                 Key: JBTM-3091
                 URL: https://issues.jboss.org/browse/JBTM-3091
             Project: JBoss Transaction Manager
          Issue Type: Bug
          Components: LRA
    Affects Versions: 5.9.2.Final
            Reporter: Michael Musgrove
            Assignee: Michael Musgrove
             Fix For: 5.next


The Narayana implementation of the LRA spec should depend on specific LRA API snapshot builds (since the LRA API is a moving target).

The current implementation was coded against the following maven snapshot:

org.eclipse.microprofile.lra:microprofile-lra-api:1.0-20181217.132756-202



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Mon Jan  7 12:54:00 2019
From: issues at jboss.org (Michael Musgrove (Jira))
Date: Mon, 7 Jan 2019 12:54:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3091) LRA module should depend
 on a specific snapshot build
In-Reply-To: <JIRA.12786390.1546883290000@Atlassian.JIRA>
References: <JIRA.12786390.1546883290000@Atlassian.JIRA>
	<JIRA.12786390.1546883290000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12786390.1546883290000.27351.1546883640162@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Issue was automatically transitioned when Michael Musgrove created pull request #1398 in GitHub
-----------------------------------------------------------------------------------------------
    Status: Pull Request Sent  (was: Open)


> LRA module should depend on a specific snapshot build
> -----------------------------------------------------
>
>                 Key: JBTM-3091
>                 URL: https://issues.jboss.org/browse/JBTM-3091
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: LRA
>    Affects Versions: 5.9.2.Final
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>            Priority: Major
>             Fix For: 5.next
>
>
> The Narayana implementation of the LRA spec should depend on specific LRA API snapshot builds (since the LRA API is a moving target).
> The current implementation was coded against the following maven snapshot:
> org.eclipse.microprofile.lra:microprofile-lra-api:1.0-20181217.132756-202



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Tue Jan  8 05:17:01 2019
From: issues at jboss.org (Michael Musgrove (Jira))
Date: Tue, 8 Jan 2019 05:17:01 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3091) LRA module should depend
 on a specific snapshot build
In-Reply-To: <JIRA.12786390.1546883290000@Atlassian.JIRA>
References: <JIRA.12786390.1546883290000@Atlassian.JIRA>
	<JIRA.12786390.1546883290000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12786390.1546883290000.30441.1546942621063@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679340#comment-13679340 ] 

Michael Musgrove commented on JBTM-3091:
----------------------------------------

The same fix should be applied to the quickstart repo too.

> LRA module should depend on a specific snapshot build
> -----------------------------------------------------
>
>                 Key: JBTM-3091
>                 URL: https://issues.jboss.org/browse/JBTM-3091
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: LRA
>    Affects Versions: 5.9.2.Final
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>            Priority: Major
>             Fix For: 5.next
>
>
> The Narayana implementation of the LRA spec should depend on specific LRA API snapshot builds (since the LRA API is a moving target).
> The current implementation was coded against the following maven snapshot:
> org.eclipse.microprofile.lra:microprofile-lra-api:1.0-20181217.132756-202



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Tue Jan  8 11:55:00 2019
From: issues at jboss.org (Michael Musgrove (Jira))
Date: Tue, 8 Jan 2019 11:55:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3091) LRA module should depend
 on a specific snapshot build
In-Reply-To: <JIRA.12786390.1546883290000@Atlassian.JIRA>
References: <JIRA.12786390.1546883290000@Atlassian.JIRA>
	<JIRA.12786390.1546883290000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12786390.1546883290000.34662.1546966500193@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679584#comment-13679584 ] 

Michael Musgrove commented on JBTM-3091:
----------------------------------------

The quickstart PR is https://github.com/jbosstm/quickstart/pull/243

> LRA module should depend on a specific snapshot build
> -----------------------------------------------------
>
>                 Key: JBTM-3091
>                 URL: https://issues.jboss.org/browse/JBTM-3091
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: LRA
>    Affects Versions: 5.9.2.Final
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>            Priority: Major
>             Fix For: 5.next
>
>
> The Narayana implementation of the LRA spec should depend on specific LRA API snapshot builds (since the LRA API is a moving target).
> The current implementation was coded against the following maven snapshot:
> org.eclipse.microprofile.lra:microprofile-lra-api:1.0-20181217.132756-202



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan 11 03:31:00 2019
From: issues at jboss.org (Michael Musgrove (Jira))
Date: Fri, 11 Jan 2019 03:31:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3091) LRA module should depend
 on a specific snapshot build
In-Reply-To: <JIRA.12786390.1546883290000@Atlassian.JIRA>
References: <JIRA.12786390.1546883290000@Atlassian.JIRA>
	<JIRA.12786390.1546883290000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12786390.1546883290000.48871.1547195460096@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-3091:
-----------------------------------
        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


> LRA module should depend on a specific snapshot build
> -----------------------------------------------------
>
>                 Key: JBTM-3091
>                 URL: https://issues.jboss.org/browse/JBTM-3091
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: LRA
>    Affects Versions: 5.9.2.Final
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>            Priority: Major
>             Fix For: 5.next
>
>
> The Narayana implementation of the LRA spec should depend on specific LRA API snapshot builds (since the LRA API is a moving target).
> The current implementation was coded against the following maven snapshot:
> org.eclipse.microprofile.lra:microprofile-lra-api:1.0-20181217.132756-202



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan 11 07:03:03 2019
From: issues at jboss.org (Ondra Chaloupka (Jira))
Date: Fri, 11 Jan 2019 07:03:03 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3092) Performance TxnTest is
 processed with ServiceUnavailableException
In-Reply-To: <JIRA.12787098.1547208176000@Atlassian.JIRA>
References: <JIRA.12787098.1547208176000@Atlassian.JIRA>
	<JIRA.12787098.1547208176723@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787098.1547208176000.49984.1547208183659@Atlassian.JIRA>

Ondra Chaloupka created JBTM-3092:
-------------------------------------

             Summary: Performance TxnTest is processed with ServiceUnavailableException 
                 Key: JBTM-3092
                 URL: https://issues.jboss.org/browse/JBTM-3092
             Project: JBoss Transaction Manager
          Issue Type: Bug
          Components: Performance Testing
            Reporter: Ondra Chaloupka
            Assignee: Michael Musgrove
         Attachments: perf-failure-rts.log, undertow-log.zip

The performance test `org.jboss.narayana.rts.TxnTest` runs with errors `javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable`. It seems the Undertow is not accepting requests for some reason. 

At first I thought it could be an issue of the Undertow that fully stopped the endpoint from some reason. But on generating the Undertow logs (attached) it kind of seems there are some request dropped and some are processed. Maybe there is only need to tune Undertow about dropping requests.

But it seems that even some requests are dropped the test passes.

The log contains errors
```
javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable
	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.handleErrorStatus(ClientInvocation.java:191)
	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.extractResult(ClientInvocation.java:154)
	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.invoke(ClientInvocation.java:444)
	at org.jboss.narayana.rts.TxnHelper.sendRequest(TxnHelper.java:87)
	at org.jboss.narayana.rts.TxnTest.testTxn(TxnTest.java:66)
	at org.jboss.narayana.rts.generated.TxnTest_testTxn_jmhTest.testTxn_thrpt_jmhStub(TxnTest_testTxn_jmhTest.java:143)
	at org.jboss.narayana.rts.generated.TxnTest_testTxn_jmhTest.testTxn_Throughput(TxnTest_testTxn_jmhTest.java:83)
	at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.openjdk.jmh.runner.BenchmarkHandler$BenchmarkTask.call(BenchmarkHandler.java:453)
	at org.openjdk.jmh.runner.BenchmarkHandler$BenchmarkTask.call(BenchmarkHandler.java:437)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

javax.ws.rs.ProcessingException: Unable to invoke request
	at org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.invoke(ApacheHttpClient4Engine.java:287)
	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.invoke(ClientInvocation.java:407)
	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocationBuilder.post(ClientInvocationBuilder.java:195)
	at org.jboss.narayana.rts.TxnHelper.beginTxn(TxnHelper.java:50)
	at org.jboss.narayana.rts.TxnTest.testTxn(TxnTest.java:59)
	at org.jboss.narayana.rts.generated.TxnTest_testTxn_jmhTest.testTxn_Throughput(TxnTest_testTxn_jmhTest.java:78)
	at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.openjdk.jmh.runner.BenchmarkHandler$BenchmarkTask.call(BenchmarkHandler.java:453)
	at org.openjdk.jmh.runner.BenchmarkHandler$BenchmarkTask.call(BenchmarkHandler.java:437)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.http.conn.HttpHostConnectException: Connect to localhost:8090 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused (Connection refused)
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
	at org.apache.http.impl.execchain.MinimalClientExec.execute(MinimalClientExec.java:183)
	at org.apache.http.impl.client.MinimalHttpClient.doExecute(MinimalHttpClient.java:107)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:84)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
	at org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.invoke(ApacheHttpClient4Engine.java:283)
	... 16 more
Caused by: java.net.ConnectException: Connection refused (Connection refused)
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:74)
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)
	... 22 more
```



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan 11 07:05:00 2019
From: issues at jboss.org (Ondra Chaloupka (Jira))
Date: Fri, 11 Jan 2019 07:05:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3092) Performance TxnTest is
 processed with ServiceUnavailableException
In-Reply-To: <JIRA.12787098.1547208177000@Atlassian.JIRA>
References: <JIRA.12787098.1547208177000@Atlassian.JIRA>
	<JIRA.12787098.1547208177000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787098.1547208177000.49993.1547208300805@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondra Chaloupka updated JBTM-3092:
----------------------------------
    Description: 
The performance test `org.jboss.narayana.rts.TxnTest` runs with errors `javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable`. It seems the Undertow is not accepting requests for some reason. 

At first I thought it could be an issue of the Undertow that fully stopped the endpoint from some reason. But on generating the Undertow logs (attached) it kind of seems there are some request dropped and some are processed. Maybe there is only need to tune Undertow about dropping requests.

But it seems that even some requests are dropped the test passes.

The log contains errors
{code}
javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable
	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.handleErrorStatus(ClientInvocation.java:191)
	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.extractResult(ClientInvocation.java:154)
	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.invoke(ClientInvocation.java:444)
	at org.jboss.narayana.rts.TxnHelper.sendRequest(TxnHelper.java:87)
	at org.jboss.narayana.rts.TxnTest.testTxn(TxnTest.java:66)
	at org.jboss.narayana.rts.generated.TxnTest_testTxn_jmhTest.testTxn_thrpt_jmhStub(TxnTest_testTxn_jmhTest.java:143)
	at org.jboss.narayana.rts.generated.TxnTest_testTxn_jmhTest.testTxn_Throughput(TxnTest_testTxn_jmhTest.java:83)
	at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.openjdk.jmh.runner.BenchmarkHandler$BenchmarkTask.call(BenchmarkHandler.java:453)
	at org.openjdk.jmh.runner.BenchmarkHandler$BenchmarkTask.call(BenchmarkHandler.java:437)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

javax.ws.rs.ProcessingException: Unable to invoke request
	at org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.invoke(ApacheHttpClient4Engine.java:287)
	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.invoke(ClientInvocation.java:407)
	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocationBuilder.post(ClientInvocationBuilder.java:195)
	at org.jboss.narayana.rts.TxnHelper.beginTxn(TxnHelper.java:50)
	at org.jboss.narayana.rts.TxnTest.testTxn(TxnTest.java:59)
	at org.jboss.narayana.rts.generated.TxnTest_testTxn_jmhTest.testTxn_Throughput(TxnTest_testTxn_jmhTest.java:78)
	at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.openjdk.jmh.runner.BenchmarkHandler$BenchmarkTask.call(BenchmarkHandler.java:453)
	at org.openjdk.jmh.runner.BenchmarkHandler$BenchmarkTask.call(BenchmarkHandler.java:437)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.http.conn.HttpHostConnectException: Connect to localhost:8090 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused (Connection refused)
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
	at org.apache.http.impl.execchain.MinimalClientExec.execute(MinimalClientExec.java:183)
	at org.apache.http.impl.client.MinimalHttpClient.doExecute(MinimalHttpClient.java:107)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:84)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
	at org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.invoke(ApacheHttpClient4Engine.java:283)
	... 16 more
Caused by: java.net.ConnectException: Connection refused (Connection refused)
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:74)
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)
	... 22 more
{code}

  was:
The performance test `org.jboss.narayana.rts.TxnTest` runs with errors `javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable`. It seems the Undertow is not accepting requests for some reason. 

At first I thought it could be an issue of the Undertow that fully stopped the endpoint from some reason. But on generating the Undertow logs (attached) it kind of seems there are some request dropped and some are processed. Maybe there is only need to tune Undertow about dropping requests.

But it seems that even some requests are dropped the test passes.

The log contains errors
```
javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable
	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.handleErrorStatus(ClientInvocation.java:191)
	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.extractResult(ClientInvocation.java:154)
	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.invoke(ClientInvocation.java:444)
	at org.jboss.narayana.rts.TxnHelper.sendRequest(TxnHelper.java:87)
	at org.jboss.narayana.rts.TxnTest.testTxn(TxnTest.java:66)
	at org.jboss.narayana.rts.generated.TxnTest_testTxn_jmhTest.testTxn_thrpt_jmhStub(TxnTest_testTxn_jmhTest.java:143)
	at org.jboss.narayana.rts.generated.TxnTest_testTxn_jmhTest.testTxn_Throughput(TxnTest_testTxn_jmhTest.java:83)
	at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.openjdk.jmh.runner.BenchmarkHandler$BenchmarkTask.call(BenchmarkHandler.java:453)
	at org.openjdk.jmh.runner.BenchmarkHandler$BenchmarkTask.call(BenchmarkHandler.java:437)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

javax.ws.rs.ProcessingException: Unable to invoke request
	at org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.invoke(ApacheHttpClient4Engine.java:287)
	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.invoke(ClientInvocation.java:407)
	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocationBuilder.post(ClientInvocationBuilder.java:195)
	at org.jboss.narayana.rts.TxnHelper.beginTxn(TxnHelper.java:50)
	at org.jboss.narayana.rts.TxnTest.testTxn(TxnTest.java:59)
	at org.jboss.narayana.rts.generated.TxnTest_testTxn_jmhTest.testTxn_Throughput(TxnTest_testTxn_jmhTest.java:78)
	at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.openjdk.jmh.runner.BenchmarkHandler$BenchmarkTask.call(BenchmarkHandler.java:453)
	at org.openjdk.jmh.runner.BenchmarkHandler$BenchmarkTask.call(BenchmarkHandler.java:437)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.http.conn.HttpHostConnectException: Connect to localhost:8090 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused (Connection refused)
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
	at org.apache.http.impl.execchain.MinimalClientExec.execute(MinimalClientExec.java:183)
	at org.apache.http.impl.client.MinimalHttpClient.doExecute(MinimalHttpClient.java:107)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:84)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
	at org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.invoke(ApacheHttpClient4Engine.java:283)
	... 16 more
Caused by: java.net.ConnectException: Connection refused (Connection refused)
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:74)
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)
	... 22 more
```



> Performance TxnTest is processed with ServiceUnavailableException 
> ------------------------------------------------------------------
>
>                 Key: JBTM-3092
>                 URL: https://issues.jboss.org/browse/JBTM-3092
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: Performance Testing
>            Reporter: Ondra Chaloupka
>            Assignee: Michael Musgrove
>            Priority: Major
>         Attachments: perf-failure-rts.log, undertow-log.zip
>
>
> The performance test `org.jboss.narayana.rts.TxnTest` runs with errors `javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable`. It seems the Undertow is not accepting requests for some reason. 
> At first I thought it could be an issue of the Undertow that fully stopped the endpoint from some reason. But on generating the Undertow logs (attached) it kind of seems there are some request dropped and some are processed. Maybe there is only need to tune Undertow about dropping requests.
> But it seems that even some requests are dropped the test passes.
> The log contains errors
> {code}
> javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable
> 	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.handleErrorStatus(ClientInvocation.java:191)
> 	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.extractResult(ClientInvocation.java:154)
> 	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.invoke(ClientInvocation.java:444)
> 	at org.jboss.narayana.rts.TxnHelper.sendRequest(TxnHelper.java:87)
> 	at org.jboss.narayana.rts.TxnTest.testTxn(TxnTest.java:66)
> 	at org.jboss.narayana.rts.generated.TxnTest_testTxn_jmhTest.testTxn_thrpt_jmhStub(TxnTest_testTxn_jmhTest.java:143)
> 	at org.jboss.narayana.rts.generated.TxnTest_testTxn_jmhTest.testTxn_Throughput(TxnTest_testTxn_jmhTest.java:83)
> 	at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:498)
> 	at org.openjdk.jmh.runner.BenchmarkHandler$BenchmarkTask.call(BenchmarkHandler.java:453)
> 	at org.openjdk.jmh.runner.BenchmarkHandler$BenchmarkTask.call(BenchmarkHandler.java:437)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 	at java.lang.Thread.run(Thread.java:748)
> javax.ws.rs.ProcessingException: Unable to invoke request
> 	at org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.invoke(ApacheHttpClient4Engine.java:287)
> 	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.invoke(ClientInvocation.java:407)
> 	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocationBuilder.post(ClientInvocationBuilder.java:195)
> 	at org.jboss.narayana.rts.TxnHelper.beginTxn(TxnHelper.java:50)
> 	at org.jboss.narayana.rts.TxnTest.testTxn(TxnTest.java:59)
> 	at org.jboss.narayana.rts.generated.TxnTest_testTxn_jmhTest.testTxn_Throughput(TxnTest_testTxn_jmhTest.java:78)
> 	at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:498)
> 	at org.openjdk.jmh.runner.BenchmarkHandler$BenchmarkTask.call(BenchmarkHandler.java:453)
> 	at org.openjdk.jmh.runner.BenchmarkHandler$BenchmarkTask.call(BenchmarkHandler.java:437)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 	at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.http.conn.HttpHostConnectException: Connect to localhost:8090 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused (Connection refused)
> 	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
> 	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
> 	at org.apache.http.impl.execchain.MinimalClientExec.execute(MinimalClientExec.java:183)
> 	at org.apache.http.impl.client.MinimalHttpClient.doExecute(MinimalHttpClient.java:107)
> 	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:84)
> 	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
> 	at org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.invoke(ApacheHttpClient4Engine.java:283)
> 	... 16 more
> Caused by: java.net.ConnectException: Connection refused (Connection refused)
> 	at java.net.PlainSocketImpl.socketConnect(Native Method)
> 	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> 	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> 	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> 	at java.net.Socket.connect(Socket.java:589)
> 	at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:74)
> 	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)
> 	... 22 more
> {code}



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Tue Jan 15 05:19:04 2019
From: issues at jboss.org (Amos Feng (Jira))
Date: Tue, 15 Jan 2019 05:19:04 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2805) Karaf fails to build in CI
In-Reply-To: <JIRA.12664503.1480515112000@Atlassian.JIRA>
References: <JIRA.12664503.1480515112000@Atlassian.JIRA>
	<JIRA.12664503.1480515112000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12664503.1480515112000.73515.1547547544684@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682194#comment-13682194 ] 

Amos Feng commented on JBTM-2805:
---------------------------------

When running the osgi integration tests, it copies the configuration files [1] to the karaf/etc/ [2]. So we just need to build the OSGi bundle now.
Also the features.xml of karaf was added with the narayana osgi bundle configuration in the commit [3]

[1] https://github.com/jbosstm/narayana/tree/master/osgi/jta/src/test/resources/etc
[2] https://github.com/jbosstm/narayana/blob/master/osgi/jta/pom.xml#L350
[3] https://github.com/apache/karaf/commit/658a2bda0791ed6ff7aa965a8db39042738c26cc#diff-59845b1c772d324b5d5834b2724c7350

> Karaf fails to build in CI
> --------------------------
>
>                 Key: JBTM-2805
>                 URL: https://issues.jboss.org/browse/JBTM-2805
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>          Components: Build System, OSGi
>            Reporter: Tom Jenkinson
>            Assignee: Amos Feng
>            Priority: Major
>
> We should try to avoid building Karaf in CI.
> At this point it fails to build.
> {code}
> [INFO] --- maven-resources-plugin:2.7:resources (process-resources) @ apache-karaf-minimal ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 4 resources
> [INFO] 
> [INFO] --- karaf-maven-plugin:4.1.0-SNAPSHOT:assembly (process-resources) @ apache-karaf-minimal ---
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Karaf ....................................... SUCCESS [  4.795 s]
> [INFO] Apache Karaf :: JAAS ............................... SUCCESS [  0.017 s]
> [INFO] Apache Karaf :: JAAS :: Boot ....................... SUCCESS [  2.413 s]
> [INFO] Apache Karaf :: Util ............................... SUCCESS [  4.843 s]
> [INFO] Apache Karaf :: Main ............................... SUCCESS [ 11.143 s]
> [INFO] Apache Karaf :: Features ........................... SUCCESS [  0.012 s]
> [INFO] Apache Karaf :: Features :: Extension .............. SUCCESS [  0.157 s]
> [INFO] Apache Karaf :: Service ............................ SUCCESS [  0.012 s]
> [INFO] Apache Karaf :: Service :: Guard ................... SUCCESS [  8.831 s]
> [INFO] Apache Karaf :: Shell .............................. SUCCESS [  0.010 s]
> [INFO] Apache Karaf :: Shell :: Core ...................... SUCCESS [  6.523 s]
> [INFO] Apache Karaf :: Tooling ............................ SUCCESS [  0.013 s]
> [INFO] Apache Karaf :: Tooling :: Maven Karaf Plugin for Services Metadata SUCCESS [ 58.898 s]
> [INFO] Apache Karaf :: Features :: Core ................... SUCCESS [  5.522 s]
> [INFO] Apache Karaf :: Features :: Command ................ SUCCESS [  0.845 s]
> [INFO] Apache Karaf :: KAR :: Core ........................ SUCCESS [  0.869 s]
> [INFO] Apache Karaf :: JAAS :: Config ..................... SUCCESS [  7.906 s]
> [INFO] Apache Karaf :: JAAS :: Modules .................... SUCCESS [ 18.313 s]
> [INFO] Apache Karaf :: Bundle ............................. SUCCESS [  0.009 s]
> [INFO] Apache Karaf :: Bundle :: Core ..................... SUCCESS [  1.076 s]
> [INFO] Apache Karaf :: Bundle :: BlueprintStateService .... SUCCESS [  0.095 s]
> [INFO] Apache Karaf :: Bundle :: SpringStateService ....... SUCCESS [  8.690 s]
> [INFO] Apache Karaf :: ConfigAdmin :: Core ................ SUCCESS [  0.454 s]
> [INFO] Apache Karaf :: Tooling :: Utils ................... SUCCESS [  2.911 s]
> [INFO] Apache Karaf :: Deployer ........................... SUCCESS [  0.007 s]
> [INFO] Apache Karaf :: Deployer :: Blueprint .............. SUCCESS [  2.328 s]
> [INFO] Apache Karaf :: Deployer :: Spring ................. SUCCESS [  0.166 s]
> [INFO] Apache Karaf :: Demos :: Profiles :: Registry ...... SUCCESS [  0.031 s]
> [INFO] Apache Karaf :: Profile :: Core .................... SUCCESS [  9.123 s]
> [INFO] Apache Karaf :: Instance :: Core ................... SUCCESS [  1.096 s]
> [INFO] Apache Karaf :: Package :: Core .................... SUCCESS [  0.316 s]
> [INFO] Apache Karaf :: HTTP :: Core ....................... SUCCESS [  3.623 s]
> [INFO] Apache Karaf :: Service :: Core .................... SUCCESS [  0.323 s]
> [INFO] Apache Karaf :: Log :: Core ........................ SUCCESS [  4.122 s]
> [INFO] Apache Karaf :: Deployer :: Features ............... SUCCESS [  0.568 s]
> [INFO] Apache Karaf :: Deployer :: Karaf Archive (.kar) ... SUCCESS [  0.491 s]
> [INFO] Apache Karaf :: Deployer :: Wrap Non OSGi Jar ...... SUCCESS [  0.100 s]
> [INFO] Apache Karaf :: Shell :: Various Commands .......... SUCCESS [  0.471 s]
> [INFO] Apache Karaf :: Shell :: Console ................... SUCCESS [  3.362 s]
> [INFO] Apache Karaf :: Shell :: Table ..................... SUCCESS [  0.111 s]
> [INFO] Apache Karaf :: Shell :: SSH ....................... SUCCESS [  2.032 s]
> [INFO] Apache Karaf :: JAAS :: Jasypt Encryption .......... SUCCESS [  2.921 s]
> [INFO] Apache Karaf :: JAAS :: Command .................... SUCCESS [  0.492 s]
> [INFO] Apache Karaf :: JAAS :: Blueprint .................. SUCCESS [  0.007 s]
> [INFO] Apache Karaf :: JAAS :: Blueprint :: Config ........ SUCCESS [  0.081 s]
> [INFO] Apache Karaf :: JAAS :: Blueprint :: Jasypt ........ SUCCESS [  1.509 s]
> [INFO] Apache Karaf :: Client ............................. SUCCESS [  0.164 s]
> [INFO] Apache Karaf :: Management ......................... SUCCESS [  0.008 s]
> [INFO] Apache Karaf :: Management ......................... SUCCESS [  0.212 s]
> [INFO] Apache Karaf :: System :: Core ..................... SUCCESS [  0.329 s]
> [INFO] Apache Karaf :: Web :: Core ........................ SUCCESS [  0.328 s]
> [INFO] Apache Karaf :: Wrapper :: Core .................... SUCCESS [  0.667 s]
> [INFO] Apache Karaf :: Web Console ........................ SUCCESS [  0.007 s]
> [INFO] Apache Karaf :: Web Console :: Console ............. SUCCESS [  3.205 s]
> [INFO] Apache Karaf :: Web Console :: Features Plugin ..... SUCCESS [  0.559 s]
> [INFO] Apache Karaf :: Web Console :: Gogo Plugin ......... SUCCESS [  0.617 s]
> [INFO] Apache Karaf :: Web Console :: HTTP Plugin ......... SUCCESS [  0.567 s]
> [INFO] Apache Karaf :: Web Console :: Instance Plugin ..... SUCCESS [  0.224 s]
> [INFO] Apache Karaf :: Exception .......................... SUCCESS [  0.031 s]
> [INFO] Apache Karaf :: Scheduler :: Core .................. SUCCESS [  3.628 s]
> [INFO] Apache Karaf :: Declarative Services (DS) .......... SUCCESS [  0.007 s]
> [INFO] Apache Karaf :: SCR :: Shell Commands .............. SUCCESS [  3.391 s]
> [INFO] Apache Karaf :: SCR :: Management MBeans ........... SUCCESS [  1.491 s]
> [INFO] Apache Karaf :: SCR :: Bundle State ................ SUCCESS [  0.176 s]
> [INFO] Apache Karaf :: SCR :: Examples .................... SUCCESS [  0.006 s]
> [INFO] Apache Karaf :: SCR :: Examples :: Basic Service ... SUCCESS [  0.060 s]
> [INFO] Apache Karaf :: SCR :: Examples :: Managed Services  SUCCESS [  0.076 s]
> [INFO] Apache Karaf :: SCR :: Examples :: Component Factories SUCCESS [  0.063 s]
> [INFO] Apache Karaf :: Diagnostic ......................... SUCCESS [  0.007 s]
> [INFO] Apache Karaf :: Diagnostic :: Boot ................. SUCCESS [  0.096 s]
> [INFO] Apache Karaf :: Diagnostic :: Core ................. SUCCESS [  0.748 s]
> [INFO] Apache Karaf :: OBR :: Core ........................ SUCCESS [  1.771 s]
> [INFO] Apache Karaf :: JNDI :: Core ....................... SUCCESS [  1.765 s]
> [INFO] Apache Karaf :: JDBC :: Core ....................... SUCCESS [  0.410 s]
> [INFO] Apache Karaf :: JMS :: Core ........................ SUCCESS [  6.591 s]
> [INFO] Apache Karaf :: Features ........................... SUCCESS [  0.006 s]
> [INFO] Apache Karaf :: JPA :: Parent ...................... SUCCESS [  0.006 s]
> [INFO] Apache Karaf :: JPA :: Hibernate ................... SUCCESS [  8.436 s]
> [INFO] Apache Karaf :: OSGi Services :: Coordinator ....... SUCCESS [  1.763 s]
> [INFO] Apache Karaf :: OSGi Services :: EventAdmin ........ SUCCESS [  1.511 s]
> [INFO] Apache Karaf :: OSGi Services :: Static ConfigAdmin  SUCCESS [  0.087 s]
> [INFO] Apache Karaf :: OSGi Services ...................... SUCCESS [  0.006 s]
> [INFO] Apache Karaf :: Subsystem :: Core .................. SUCCESS [  5.008 s]
> [INFO] Apache Karaf :: OSGi Services :: Event ............. SUCCESS [  1.709 s]
> [INFO] Apache Karaf :: Tooling :: Maven Karaf Plugin ...... SUCCESS [  7.875 s]
> [INFO] Apache Karaf :: Assemblies ......................... SUCCESS [  0.008 s]
> [INFO] Apache Karaf :: Assemblies :: Features ............. SUCCESS [  0.006 s]
> [INFO] Apache Karaf :: Assemblies :: Features :: Base ..... SUCCESS [  3.828 s]
> [INFO] Apache Karaf :: Assemblies :: Features :: Framework  SUCCESS [  2.555 s]
> [INFO] Apache Karaf :: Assemblies :: Features :: Static ... SUCCESS [  1.836 s]
> [INFO] Apache Karaf :: Assemblies :: Features :: Standard . SUCCESS [01:12 min]
> [INFO] Apache Karaf :: Assemblies :: Features :: Spring ... SUCCESS [01:19 min]
> [INFO] Apache Karaf :: Assemblies :: Features :: Enterprise SUCCESS [ 42.574 s]
> [INFO] Apache Karaf :: Assemblies :: Demos ................ SUCCESS [  0.075 s]
> [INFO] Apache Karaf :: Assemblies :: Minimal Distribution . FAILURE [  0.097 s]
> [INFO] Apache Karaf :: Assemblies :: Default Distribution . SKIPPED
> [INFO] Apache Karaf :: Demos .............................. SKIPPED
> [INFO] Apache Karaf :: Demos :: Web ....................... SKIPPED
> [INFO] Apache Karaf :: Demos :: Branding :: Shell ......... SKIPPED
> [INFO] Apache Karaf :: Demos :: Command :: Extend Console . SKIPPED
> [INFO] Apache Karaf :: Demos :: Demo Dump provider ........ SKIPPED
> [INFO] Apache Karaf :: Demos :: Deployer .................. SKIPPED
> [INFO] Apache Karaf :: Demos :: Deployer :: Kar ........... SKIPPED
> [INFO] Apache Karaf :: Demos :: Deployer :: Bundle ........ SKIPPED
> [INFO] Apache Karaf :: Demos :: Profiles :: Dynamic Assembly SKIPPED
> [INFO] Apache Karaf :: Demos :: Profiles :: Static Assembly SKIPPED
> [INFO] Apache Karaf :: Demos :: Profiles .................. SKIPPED
> [INFO] Apache Karaf :: Archetypes ......................... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Assembly Archetype ... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Command Archetype .... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Feature Archetype .... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Kar Archetype ........ SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Bundle Archetype ..... SKIPPED
> [INFO] Apache Karaf :: Archetypes :: Blueprint Archetype .. SKIPPED
> [INFO] Apache Karaf :: Integration Tests .................. SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 07:17 min
> [INFO] Finished at: 2016-11-29T00:19:34+00:00
> [INFO] Final Memory: 165M/1003M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:assembly (process-resources) on project apache-karaf-minimal: Unable to parse configuration of mojo org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:assembly for parameter pidsToExtract: Cannot assign configuration entry 'pidsToExtract' with value '!jmx.acl.*,
> [ERROR] !org.apache.karaf.command.acl.*,
> [ERROR] *' of type java.lang.String to property of type java.util.List
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginConfigurationException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR]   mvn <goals> -rf :apache-karaf-minimal
> {code}



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Wed Jan 16 12:40:01 2019
From: issues at jboss.org (Michael Musgrove (Jira))
Date: Wed, 16 Jan 2019 12:40:01 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3093) maven site plugin fails
 on the LRA client module
In-Reply-To: <JIRA.12787777.1547660006000@Atlassian.JIRA>
References: <JIRA.12787777.1547660006000@Atlassian.JIRA>
	<JIRA.12787777.1547660006469@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787777.1547660006000.119929.1547660401254@Atlassian.JIRA>

Michael Musgrove created JBTM-3093:
--------------------------------------

             Summary: maven site plugin fails on the LRA client module
                 Key: JBTM-3093
                 URL: https://issues.jboss.org/browse/JBTM-3093
             Project: JBoss Transaction Manager
          Issue Type: Bug
          Components: LRA
    Affects Versions: 5.9.2.Final
            Reporter: Michael Musgrove
            Assignee: Michael Musgrove
             Fix For: 5.next



LRA relies on microprofile-lra-api snapshot builds but the site module appears to resolve to the latest snapshot (rather than a particular snapshot build) and since microprofile-lra-api regularly undergoes changes there is a compilation failure:

```
[ERROR] COMPILATION ERROR : 
[INFO] -------------------------------------------------------------
[ERROR] /home/jenkins/workspace/narayana-codeCoverage/rts/lra/lra-client/src/main/java/io/narayana/lra/client/NarayanaLRAClient.java:[89,8] io.narayana.lra.client.NarayanaLRAClient is not abstract and does not override abstract method joinLRA(java.net.URL,java.lang.Class<?>,java.net.URI,java.lang.String) in org.eclipse.microprofile.lra.client.LRAClient
[ERROR] /home/jenkins/workspace/narayana-codeCoverage/rts/lra/lra-client/src/main/java/io/narayana/lra/client/NarayanaLRAClient.java:[545,19] joinLRA(java.net.URL,java.lang.Class<?>,java.net.URI,java.lang.String) in io.narayana.lra.client.NarayanaLRAClient cannot implement joinLRA(java.net.URL,java.lang.Class<?>,java.net.URI,java.lang.String) in org.eclipse.microprofile.lra.client.LRAClient
  return type java.lang.String is not compatible with java.net.URL
```



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Wed Jan 16 12:46:03 2019
From: issues at jboss.org (Michael Musgrove (Jira))
Date: Wed, 16 Jan 2019 12:46:03 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3093) disable the maven site
 plugin for the LRA module
In-Reply-To: <JIRA.12787777.1547660006000@Atlassian.JIRA>
References: <JIRA.12787777.1547660006000@Atlassian.JIRA>
	<JIRA.12787777.1547660006000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787777.1547660006000.119969.1547660763894@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-3093:
-----------------------------------
    Summary: disable the maven site plugin for the LRA module  (was: maven site plugin fails on the LRA client module)


> disable the maven site plugin for the LRA module
> ------------------------------------------------
>
>                 Key: JBTM-3093
>                 URL: https://issues.jboss.org/browse/JBTM-3093
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: LRA
>    Affects Versions: 5.9.2.Final
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>            Priority: Major
>             Fix For: 5.next
>
>
> LRA relies on microprofile-lra-api snapshot builds but the site module appears to resolve to the latest snapshot (rather than a particular snapshot build) and since microprofile-lra-api regularly undergoes changes there is a compilation failure:
> ```
> [ERROR] COMPILATION ERROR : 
> [INFO] -------------------------------------------------------------
> [ERROR] /home/jenkins/workspace/narayana-codeCoverage/rts/lra/lra-client/src/main/java/io/narayana/lra/client/NarayanaLRAClient.java:[89,8] io.narayana.lra.client.NarayanaLRAClient is not abstract and does not override abstract method joinLRA(java.net.URL,java.lang.Class<?>,java.net.URI,java.lang.String) in org.eclipse.microprofile.lra.client.LRAClient
> [ERROR] /home/jenkins/workspace/narayana-codeCoverage/rts/lra/lra-client/src/main/java/io/narayana/lra/client/NarayanaLRAClient.java:[545,19] joinLRA(java.net.URL,java.lang.Class<?>,java.net.URI,java.lang.String) in io.narayana.lra.client.NarayanaLRAClient cannot implement joinLRA(java.net.URL,java.lang.Class<?>,java.net.URI,java.lang.String) in org.eclipse.microprofile.lra.client.LRAClient
>   return type java.lang.String is not compatible with java.net.URL
> ```



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Wed Jan 16 13:02:03 2019
From: issues at jboss.org (Michael Musgrove (Jira))
Date: Wed, 16 Jan 2019 13:02:03 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3093) Disable the maven site
 plugin for the LRA module
In-Reply-To: <JIRA.12787777.1547660006000@Atlassian.JIRA>
References: <JIRA.12787777.1547660006000@Atlassian.JIRA>
	<JIRA.12787777.1547660006000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787777.1547660006000.120163.1547661723253@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Issue was automatically transitioned when Michael Musgrove created pull request #1399 in GitHub
-----------------------------------------------------------------------------------------------
    Status: Pull Request Sent  (was: Open)


> Disable the maven site plugin for the LRA module
> ------------------------------------------------
>
>                 Key: JBTM-3093
>                 URL: https://issues.jboss.org/browse/JBTM-3093
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: LRA
>    Affects Versions: 5.9.2.Final
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>            Priority: Major
>             Fix For: 5.next
>
>
> The narayana code coverage profile invokes the maven site goal so that the output can be viewed easily.
>  
> Now LRA relies on microprofile-lra-api snapshot builds but the site plugin appears to resolve to the latest snapshot (rather than a particular snapshot build) and since microprofile-lra-api regularly undergoes changes there are compilation failures.
> This JIRA proposes that we disable the site plugin for the LRA module.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Thu Jan 17 13:32:03 2019
From: issues at jboss.org (Ondra Chaloupka (Jira))
Date: Thu, 17 Jan 2019 13:32:03 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3094) Redesign Narayana.io page
 to follow more modern trends
In-Reply-To: <JIRA.12787955.1547749915000@Atlassian.JIRA>
References: <JIRA.12787955.1547749915000@Atlassian.JIRA>
	<JIRA.12787955.1547749915013@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787955.1547749915000.162491.1547749923531@Atlassian.JIRA>

Ondra Chaloupka created JBTM-3094:
-------------------------------------

             Summary: Redesign Narayana.io page to follow more modern trends
                 Key: JBTM-3094
                 URL: https://issues.jboss.org/browse/JBTM-3094
             Project: JBoss Transaction Manager
          Issue Type: Enhancement
            Reporter: Ondra Chaloupka


The current Narayana project page at [http://narayana.io|http://narayana.io] is a little old fashioned. It would be good to create a newer looking page which would provide better information for developers about the Narayana capabilities.

This idea came from my attendance on design clinic. That was an informal session with an UX specialist. The idea was to help project to come up with better design if it's a webpage or a logo. The main point I took from the session was "make a small survey" what people thinks. I talked with few people and up to that I summarized their ideas [under document|https://docs.google.com/document/d/1yq0CuhD-B3bN2j5GHen0a7By2R23TFCnBxx3vP1nnyg/edit?usp=sharing] and [summarized at F2F 19 presentation|https://docs.google.com/presentation/d/1N6La-75ImuRYYwTS5nbcOqczQLv0AGS_1Hya4V0u7L4/edit?usp=sharing].
There were some ideas about enhancements [in jira issues|https://issues.jboss.org/issues/?jql=summary%20~%20%22narayana.io%22%20and%20status%20in%20(Open%2C%20New)].



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Thu Jan 17 13:37:03 2019
From: issues at jboss.org (Ondra Chaloupka (Jira))
Date: Thu, 17 Jan 2019 13:37:03 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3094) Redesign Narayana.io page
 to follow modern trends
In-Reply-To: <JIRA.12787955.1547749915000@Atlassian.JIRA>
References: <JIRA.12787955.1547749915000@Atlassian.JIRA>
	<JIRA.12787955.1547749915000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787955.1547749915000.162565.1547750223357@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondra Chaloupka updated JBTM-3094:
----------------------------------
    Description: 
The current Narayana project page at [http://narayana.io|http://narayana.io] is a little old fashioned. It would be good to create a newer looking page which would provide better information for developers about the Narayana capabilities.

This idea came from my attendance on design clinic. That was an informal session with an UX specialist. The idea was to help project to come up with better design if it's a webpage or a logo. The main point I took from the session was "make a small survey" what people thinks. I talked with few people and up to that I summarized their ideas [under document|https://docs.google.com/document/d/1yq0CuhD-B3bN2j5GHen0a7By2R23TFCnBxx3vP1nnyg/edit?usp=sharing] and [summarized at F2F 19 presentation|https://docs.google.com/presentation/d/1N6La-75ImuRYYwTS5nbcOqczQLv0AGS_1Hya4V0u7L4/edit?usp=sharing].
There were some ideas about enhancements [in jira issues|https://issues.jboss.org/issues/?jql=summary%20~%20%22narayana.io%22%20and%20status%20in%20(Open%2C%20New)].

Idea would be to talk to developers in better way and use nicer visual style. The examples would be project like https://antora.org, https://thorntail.io, https://vertx.io or https://debezium.io 

  was:
The current Narayana project page at [http://narayana.io|http://narayana.io] is a little old fashioned. It would be good to create a newer looking page which would provide better information for developers about the Narayana capabilities.

This idea came from my attendance on design clinic. That was an informal session with an UX specialist. The idea was to help project to come up with better design if it's a webpage or a logo. The main point I took from the session was "make a small survey" what people thinks. I talked with few people and up to that I summarized their ideas [under document|https://docs.google.com/document/d/1yq0CuhD-B3bN2j5GHen0a7By2R23TFCnBxx3vP1nnyg/edit?usp=sharing] and [summarized at F2F 19 presentation|https://docs.google.com/presentation/d/1N6La-75ImuRYYwTS5nbcOqczQLv0AGS_1Hya4V0u7L4/edit?usp=sharing].
There were some ideas about enhancements [in jira issues|https://issues.jboss.org/issues/?jql=summary%20~%20%22narayana.io%22%20and%20status%20in%20(Open%2C%20New)].



> Redesign Narayana.io page to follow modern trends
> -------------------------------------------------
>
>                 Key: JBTM-3094
>                 URL: https://issues.jboss.org/browse/JBTM-3094
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>            Reporter: Ondra Chaloupka
>            Priority: Major
>              Labels: narayana.io
>
> The current Narayana project page at [http://narayana.io|http://narayana.io] is a little old fashioned. It would be good to create a newer looking page which would provide better information for developers about the Narayana capabilities.
> This idea came from my attendance on design clinic. That was an informal session with an UX specialist. The idea was to help project to come up with better design if it's a webpage or a logo. The main point I took from the session was "make a small survey" what people thinks. I talked with few people and up to that I summarized their ideas [under document|https://docs.google.com/document/d/1yq0CuhD-B3bN2j5GHen0a7By2R23TFCnBxx3vP1nnyg/edit?usp=sharing] and [summarized at F2F 19 presentation|https://docs.google.com/presentation/d/1N6La-75ImuRYYwTS5nbcOqczQLv0AGS_1Hya4V0u7L4/edit?usp=sharing].
> There were some ideas about enhancements [in jira issues|https://issues.jboss.org/issues/?jql=summary%20~%20%22narayana.io%22%20and%20status%20in%20(Open%2C%20New)].
> Idea would be to talk to developers in better way and use nicer visual style. The examples would be project like https://antora.org, https://thorntail.io, https://vertx.io or https://debezium.io 



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Thu Jan 17 13:37:04 2019
From: issues at jboss.org (Ondra Chaloupka (Jira))
Date: Thu, 17 Jan 2019 13:37:04 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3094) Redesign Narayana.io page
 to follow modern trends
In-Reply-To: <JIRA.12787955.1547749915000@Atlassian.JIRA>
References: <JIRA.12787955.1547749915000@Atlassian.JIRA>
	<JIRA.12787955.1547749915000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787955.1547749915000.162569.1547750224786@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondra Chaloupka updated JBTM-3094:
----------------------------------
    Summary: Redesign Narayana.io page to follow modern trends  (was: Redesign Narayana.io page to follow more modern trends)


> Redesign Narayana.io page to follow modern trends
> -------------------------------------------------
>
>                 Key: JBTM-3094
>                 URL: https://issues.jboss.org/browse/JBTM-3094
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>            Reporter: Ondra Chaloupka
>            Priority: Major
>              Labels: narayana.io
>
> The current Narayana project page at [http://narayana.io|http://narayana.io] is a little old fashioned. It would be good to create a newer looking page which would provide better information for developers about the Narayana capabilities.
> This idea came from my attendance on design clinic. That was an informal session with an UX specialist. The idea was to help project to come up with better design if it's a webpage or a logo. The main point I took from the session was "make a small survey" what people thinks. I talked with few people and up to that I summarized their ideas [under document|https://docs.google.com/document/d/1yq0CuhD-B3bN2j5GHen0a7By2R23TFCnBxx3vP1nnyg/edit?usp=sharing] and [summarized at F2F 19 presentation|https://docs.google.com/presentation/d/1N6La-75ImuRYYwTS5nbcOqczQLv0AGS_1Hya4V0u7L4/edit?usp=sharing].
> There were some ideas about enhancements [in jira issues|https://issues.jboss.org/issues/?jql=summary%20~%20%22narayana.io%22%20and%20status%20in%20(Open%2C%20New)].



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Thu Jan 17 13:41:01 2019
From: issues at jboss.org (Ondra Chaloupka (Jira))
Date: Thu, 17 Jan 2019 13:41:01 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3094) Redesign Narayana.io page
 to follow modern trends
In-Reply-To: <JIRA.12787955.1547749915000@Atlassian.JIRA>
References: <JIRA.12787955.1547749915000@Atlassian.JIRA>
	<JIRA.12787955.1547749915000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787955.1547749915000.162644.1547750461242@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondra Chaloupka reassigned JBTM-3094:
-------------------------------------

    Assignee:     (was: Ondra Chaloupka)


> Redesign Narayana.io page to follow modern trends
> -------------------------------------------------
>
>                 Key: JBTM-3094
>                 URL: https://issues.jboss.org/browse/JBTM-3094
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>            Reporter: Ondra Chaloupka
>            Priority: Major
>              Labels: narayana.io
>
> The current Narayana project page at [http://narayana.io|http://narayana.io] is a little old fashioned. It would be good to create a newer looking page which would provide better information for developers about the Narayana capabilities.
> This idea came from my attendance on design clinic. That was an informal session with an UX specialist. The idea was to help project to come up with better design if it's a webpage or a logo. The main point I took from the session was "make a small survey" what people thinks. I talked with few people and up to that I summarized their ideas [under document|https://docs.google.com/document/d/1yq0CuhD-B3bN2j5GHen0a7By2R23TFCnBxx3vP1nnyg/edit?usp=sharing] and [summarized at F2F 19 presentation|https://docs.google.com/presentation/d/1N6La-75ImuRYYwTS5nbcOqczQLv0AGS_1Hya4V0u7L4/edit?usp=sharing].
> There were some ideas about enhancements [in jira issues|https://issues.jboss.org/issues/?jql=summary%20~%20%22narayana.io%22%20and%20status%20in%20(Open%2C%20New)].
> Idea would be to talk to developers in better way and use nicer visual style. The examples would be project like https://antora.org, https://thorntail.io, https://vertx.io or https://debezium.io 



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Thu Jan 17 13:41:06 2019
From: issues at jboss.org (Ondra Chaloupka (Jira))
Date: Thu, 17 Jan 2019 13:41:06 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3095) Copy write better the
 landing page of narayana.io page
In-Reply-To: <JIRA.12787957.1547750317000@Atlassian.JIRA>
References: <JIRA.12787957.1547750317000@Atlassian.JIRA>
	<JIRA.12787957.1547750317847@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787957.1547750317000.162668.1547750466414@Atlassian.JIRA>

Ondra Chaloupka created JBTM-3095:
-------------------------------------

             Summary: Copy write better the landing page of narayana.io page
                 Key: JBTM-3095
                 URL: https://issues.jboss.org/browse/JBTM-3095
             Project: JBoss Transaction Manager
          Issue Type: Sub-task
            Reporter: Ondra Chaloupka


The landing page of http://narayana.io is a bit too academic. It would be good to copy write the text to show features of Narayana in better consumable way. If you take a look at the page e.g. at the end there is multiple abbreviation which is not understood anybody else than a person working with transactions. The same is the diagram showing features. That can't be understood well by strangers. The table with set of qualities does not say much when anybody understand what's the project good for.

A side note: there should not be an annoucement at the top of the page. It's better to be aside. It's the first think a newcomer see and it possibly should not be.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Thu Jan 17 13:41:08 2019
From: issues at jboss.org (Ondra Chaloupka (Jira))
Date: Thu, 17 Jan 2019 13:41:08 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3094) Redesign Narayana.io page
 to follow modern trends
In-Reply-To: <JIRA.12787955.1547749915000@Atlassian.JIRA>
References: <JIRA.12787955.1547749915000@Atlassian.JIRA>
	<JIRA.12787955.1547749915000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787955.1547749915000.162676.1547750468531@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on JBTM-3094 started by Ondra Chaloupka.
---------------------------------------------
> Redesign Narayana.io page to follow modern trends
> -------------------------------------------------
>
>                 Key: JBTM-3094
>                 URL: https://issues.jboss.org/browse/JBTM-3094
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>            Reporter: Ondra Chaloupka
>            Assignee: Ondra Chaloupka
>            Priority: Major
>              Labels: narayana.io
>
> The current Narayana project page at [http://narayana.io|http://narayana.io] is a little old fashioned. It would be good to create a newer looking page which would provide better information for developers about the Narayana capabilities.
> This idea came from my attendance on design clinic. That was an informal session with an UX specialist. The idea was to help project to come up with better design if it's a webpage or a logo. The main point I took from the session was "make a small survey" what people thinks. I talked with few people and up to that I summarized their ideas [under document|https://docs.google.com/document/d/1yq0CuhD-B3bN2j5GHen0a7By2R23TFCnBxx3vP1nnyg/edit?usp=sharing] and [summarized at F2F 19 presentation|https://docs.google.com/presentation/d/1N6La-75ImuRYYwTS5nbcOqczQLv0AGS_1Hya4V0u7L4/edit?usp=sharing].
> There were some ideas about enhancements [in jira issues|https://issues.jboss.org/issues/?jql=summary%20~%20%22narayana.io%22%20and%20status%20in%20(Open%2C%20New)].
> Idea would be to talk to developers in better way and use nicer visual style. The examples would be project like https://antora.org, https://thorntail.io, https://vertx.io or https://debezium.io 



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Thu Jan 17 13:41:11 2019
From: issues at jboss.org (Ondra Chaloupka (Jira))
Date: Thu, 17 Jan 2019 13:41:11 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3094) Redesign Narayana.io page
 to follow modern trends
In-Reply-To: <JIRA.12787955.1547749915000@Atlassian.JIRA>
References: <JIRA.12787955.1547749915000@Atlassian.JIRA>
	<JIRA.12787955.1547749915000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787955.1547749915000.162688.1547750471578@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on JBTM-3094 stopped by Ondra Chaloupka.
---------------------------------------------
> Redesign Narayana.io page to follow modern trends
> -------------------------------------------------
>
>                 Key: JBTM-3094
>                 URL: https://issues.jboss.org/browse/JBTM-3094
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>            Reporter: Ondra Chaloupka
>            Assignee: Ondra Chaloupka
>            Priority: Major
>              Labels: narayana.io
>
> The current Narayana project page at [http://narayana.io|http://narayana.io] is a little old fashioned. It would be good to create a newer looking page which would provide better information for developers about the Narayana capabilities.
> This idea came from my attendance on design clinic. That was an informal session with an UX specialist. The idea was to help project to come up with better design if it's a webpage or a logo. The main point I took from the session was "make a small survey" what people thinks. I talked with few people and up to that I summarized their ideas [under document|https://docs.google.com/document/d/1yq0CuhD-B3bN2j5GHen0a7By2R23TFCnBxx3vP1nnyg/edit?usp=sharing] and [summarized at F2F 19 presentation|https://docs.google.com/presentation/d/1N6La-75ImuRYYwTS5nbcOqczQLv0AGS_1Hya4V0u7L4/edit?usp=sharing].
> There were some ideas about enhancements [in jira issues|https://issues.jboss.org/issues/?jql=summary%20~%20%22narayana.io%22%20and%20status%20in%20(Open%2C%20New)].
> Idea would be to talk to developers in better way and use nicer visual style. The examples would be project like https://antora.org, https://thorntail.io, https://vertx.io or https://debezium.io 



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Thu Jan 17 13:43:00 2019
From: issues at jboss.org (Ondra Chaloupka (Jira))
Date: Thu, 17 Jan 2019 13:43:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3096) Create a set of usecase
 for what Narayana is good for for narayana.io page
In-Reply-To: <JIRA.12787958.1547750561000@Atlassian.JIRA>
References: <JIRA.12787958.1547750561000@Atlassian.JIRA>
	<JIRA.12787958.1547750561640@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787958.1547750561000.162701.1547750580234@Atlassian.JIRA>

Ondra Chaloupka created JBTM-3096:
-------------------------------------

             Summary: Create a set of usecase for what Narayana is good for for narayana.io page
                 Key: JBTM-3096
                 URL: https://issues.jboss.org/browse/JBTM-3096
             Project: JBoss Transaction Manager
          Issue Type: Sub-task
            Reporter: Ondra Chaloupka


It would be good to provide the ways how Narayana could be used in use cases. It's what is modern now how the documentation is written (documentation is done in way of ?stories? in Red). We could provide set of examples what the Narayana is good for and how it could be used and implemented easily to the user's system.

It could be thinks like a bit of what our quickstarts are for but it's rather a paragraph of text where is said what and why is good for. How process goes and then e.g. link to quickstarts.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)


From issues at jboss.org  Thu Jan 17 13:44:01 2019
From: issues at jboss.org (Ondra Chaloupka (Jira))
Date: Thu, 17 Jan 2019 13:44:01 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3096) Create a set of usecase
 for what Narayana is good for narayana.io page
In-Reply-To: <JIRA.12787958.1547750562000@Atlassian.JIRA>
References: <JIRA.12787958.1547750562000@Atlassian.JIRA>
	<JIRA.12787958.1547750562000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787958.1547750562000.162703.1547750641055@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondra Chaloupka updated JBTM-3096:
----------------------------------
    Summary: Create a set of usecase for what Narayana is good for narayana.io page  (was: Create a set of usecase for what Narayana is good for for narayana.io page)


> Create a set of usecase for what Narayana is good for narayana.io page
> ----------------------------------------------------------------------
>
>                 Key: JBTM-3096
>                 URL: https://issues.jboss.org/browse/JBTM-3096
>             Project: JBoss Transaction Manager
>          Issue Type: Sub-task
>            Reporter: Ondra Chaloupka
>            Priority: Major
>
> It would be good to provide the ways how Narayana could be used in use cases. It's what is modern now how the documentation is written (documentation is done in way of ?stories? in Red). We could provide set of examples what the Narayana is good for and how it could be used and implemented easily to the user's system.
> It could be thinks like a bit of what our quickstarts are for but it's rather a paragraph of text where is said what and why is good for. How process goes and then e.g. link to quickstarts.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)


From issues at jboss.org  Thu Jan 17 13:44:01 2019
From: issues at jboss.org (Ondra Chaloupka (Jira))
Date: Thu, 17 Jan 2019 13:44:01 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3096) Create a set of usecase
 for what Narayana is good for narayana.io page
In-Reply-To: <JIRA.12787958.1547750562000@Atlassian.JIRA>
References: <JIRA.12787958.1547750562000@Atlassian.JIRA>
	<JIRA.12787958.1547750562000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787958.1547750562000.162705.1547750641541@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondra Chaloupka updated JBTM-3096:
----------------------------------
    Description: 
It would be good to provide the ways how Narayana could be used in use cases. It's what is modern now how the documentation is written (documentation is done in way of ?stories? in Red). We could provide set of examples what the Narayana is good for and how it could be used and implemented easily to the user's system.

It could be thinks like a bit of what our quickstarts are for but it's rather a paragraph of text where is said what and why is good for. How process goes and then e.g. link to quickstarts.
Talk about features but say why. Play a user story.

  was:
It would be good to provide the ways how Narayana could be used in use cases. It's what is modern now how the documentation is written (documentation is done in way of ?stories? in Red). We could provide set of examples what the Narayana is good for and how it could be used and implemented easily to the user's system.

It could be thinks like a bit of what our quickstarts are for but it's rather a paragraph of text where is said what and why is good for. How process goes and then e.g. link to quickstarts.



> Create a set of usecase for what Narayana is good for narayana.io page
> ----------------------------------------------------------------------
>
>                 Key: JBTM-3096
>                 URL: https://issues.jboss.org/browse/JBTM-3096
>             Project: JBoss Transaction Manager
>          Issue Type: Sub-task
>            Reporter: Ondra Chaloupka
>            Priority: Major
>
> It would be good to provide the ways how Narayana could be used in use cases. It's what is modern now how the documentation is written (documentation is done in way of ?stories? in Red). We could provide set of examples what the Narayana is good for and how it could be used and implemented easily to the user's system.
> It could be thinks like a bit of what our quickstarts are for but it's rather a paragraph of text where is said what and why is good for. How process goes and then e.g. link to quickstarts.
> Talk about features but say why. Play a user story.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)


From issues at jboss.org  Thu Jan 17 13:49:00 2019
From: issues at jboss.org (Ondra Chaloupka (Jira))
Date: Thu, 17 Jan 2019 13:49:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3097) Small enhancement of
 current look and feel of narayana.io
In-Reply-To: <JIRA.12787961.1547750905000@Atlassian.JIRA>
References: <JIRA.12787961.1547750905000@Atlassian.JIRA>
	<JIRA.12787961.1547750905057@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787961.1547750905000.162733.1547750940543@Atlassian.JIRA>

Ondra Chaloupka created JBTM-3097:
-------------------------------------

             Summary: Small enhancement of current look and feel of narayana.io
                 Key: JBTM-3097
                 URL: https://issues.jboss.org/browse/JBTM-3097
             Project: JBoss Transaction Manager
          Issue Type: Sub-task
            Reporter: Ondra Chaloupka


Some items from the survey

* announcement is pretty long - just link not 3 lines that talks the same
* support of Spring is not mentioned at the page
* it's hard to understand why the source code is at two places (source code goes to github and fisheye)
* link for release changes for particular release could be useful
* maybe a link to a logo when somebody wants to use for presentation could be added



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Thu Jan 17 13:54:00 2019
From: issues at jboss.org (Ondra Chaloupka (Jira))
Date: Thu, 17 Jan 2019 13:54:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3098) A page dedicated about
 integration to other project would be beneficial on narayana.io
In-Reply-To: <JIRA.12787962.1547750995000@Atlassian.JIRA>
References: <JIRA.12787962.1547750995000@Atlassian.JIRA>
	<JIRA.12787962.1547750995789@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787962.1547750995000.162782.1547751240757@Atlassian.JIRA>

Ondra Chaloupka created JBTM-3098:
-------------------------------------

             Summary: A page dedicated about integration to other project would be beneficial on narayana.io
                 Key: JBTM-3098
                 URL: https://issues.jboss.org/browse/JBTM-3098
             Project: JBoss Transaction Manager
          Issue Type: Sub-task
            Reporter: Ondra Chaloupka


It would be good to have a page dedicated to set of project the Narayana is capable being integrated to and showing how to do so (connected to JBTM-3096)



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Thu Jan 17 14:09:07 2019
From: issues at jboss.org (Ondra Chaloupka (Jira))
Date: Thu, 17 Jan 2019 14:09:07 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3101) Have a new visual design
	for narayana.io
In-Reply-To: <JIRA.12787965.1547751497000@Atlassian.JIRA>
References: <JIRA.12787965.1547751497000@Atlassian.JIRA>
	<JIRA.12787965.1547751497102@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787965.1547751497000.163135.1547752147482@Atlassian.JIRA>

Ondra Chaloupka created JBTM-3101:
-------------------------------------

             Summary: Have a new visual design for narayana.io
                 Key: JBTM-3101
                 URL: https://issues.jboss.org/browse/JBTM-3101
             Project: JBoss Transaction Manager
          Issue Type: Sub-task
            Reporter: Ondra Chaloupka


When copy-writing is done then it would be good to create a new look for the page.

See e.g.
* https://antora.org
* https://thorntail.io
* https://vertx.io
* https://debezium.io



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Thu Jan 17 14:09:07 2019
From: issues at jboss.org (Ondra Chaloupka (Jira))
Date: Thu, 17 Jan 2019 14:09:07 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3097) Small enhancement of
 current look and feel of narayana.io
In-Reply-To: <JIRA.12787961.1547750905000@Atlassian.JIRA>
References: <JIRA.12787961.1547750905000@Atlassian.JIRA>
	<JIRA.12787961.1547750905000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787961.1547750905000.163137.1547752147811@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondra Chaloupka updated JBTM-3097:
----------------------------------
    Description: 
Some items from the survey

* announcement is pretty long - just link not 3 lines that talks the same
* support of Spring is not mentioned at the page
* it's hard to understand why the source code is at two places (source code goes to github and fisheye)
* link for release changes for particular release could be useful
* maybe a link to a logo when somebody wants to use for presentation could be added
* sponsors at the page is not up-to-date

  was:
Some items from the survey

* announcement is pretty long - just link not 3 lines that talks the same
* support of Spring is not mentioned at the page
* it's hard to understand why the source code is at two places (source code goes to github and fisheye)
* link for release changes for particular release could be useful
* maybe a link to a logo when somebody wants to use for presentation could be added



> Small enhancement of current look and feel of narayana.io
> ---------------------------------------------------------
>
>                 Key: JBTM-3097
>                 URL: https://issues.jboss.org/browse/JBTM-3097
>             Project: JBoss Transaction Manager
>          Issue Type: Sub-task
>            Reporter: Ondra Chaloupka
>            Priority: Major
>              Labels: narayana.io
>
> Some items from the survey
> * announcement is pretty long - just link not 3 lines that talks the same
> * support of Spring is not mentioned at the page
> * it's hard to understand why the source code is at two places (source code goes to github and fisheye)
> * link for release changes for particular release could be useful
> * maybe a link to a logo when somebody wants to use for presentation could be added
> * sponsors at the page is not up-to-date



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Thu Jan 17 14:09:08 2019
From: issues at jboss.org (Ondra Chaloupka (Jira))
Date: Thu, 17 Jan 2019 14:09:08 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3097) Small enhancement of
 current look and feel of narayana.io
In-Reply-To: <JIRA.12787961.1547750905000@Atlassian.JIRA>
References: <JIRA.12787961.1547750905000@Atlassian.JIRA>
	<JIRA.12787961.1547750905000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12787961.1547750905000.163139.1547752148240@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondra Chaloupka updated JBTM-3097:
----------------------------------
    Description: 
Some items from the survey

* announcement is pretty long - just link not 3 lines that talks the same
* support of Spring is not mentioned at the page
* it's hard to understand why the source code is at two places (source code goes to github and fisheye)
* link for release changes for particular release could be useful
* maybe a link to a logo when somebody wants to use for presentation could be added
* sponsors links are not up-to-date

  was:
Some items from the survey

* announcement is pretty long - just link not 3 lines that talks the same
* support of Spring is not mentioned at the page
* it's hard to understand why the source code is at two places (source code goes to github and fisheye)
* link for release changes for particular release could be useful
* maybe a link to a logo when somebody wants to use for presentation could be added
* sponsors at the page is not up-to-date



> Small enhancement of current look and feel of narayana.io
> ---------------------------------------------------------
>
>                 Key: JBTM-3097
>                 URL: https://issues.jboss.org/browse/JBTM-3097
>             Project: JBoss Transaction Manager
>          Issue Type: Sub-task
>            Reporter: Ondra Chaloupka
>            Priority: Major
>              Labels: narayana.io
>
> Some items from the survey
> * announcement is pretty long - just link not 3 lines that talks the same
> * support of Spring is not mentioned at the page
> * it's hard to understand why the source code is at two places (source code goes to github and fisheye)
> * link for release changes for particular release could be useful
> * maybe a link to a logo when somebody wants to use for presentation could be added
> * sponsors links are not up-to-date



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Mon Jan 21 12:28:00 2019
From: issues at jboss.org (Michael Musgrove (Jira))
Date: Mon, 21 Jan 2019 12:28:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3102) Provide a gRPC service
 for accessing OTS funtionality
In-Reply-To: <JIRA.12788400.1548091636000@Atlassian.JIRA>
References: <JIRA.12788400.1548091636000@Atlassian.JIRA>
	<JIRA.12788400.1548091636696@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12788400.1548091636000.9238.1548091680174@Atlassian.JIRA>

Michael Musgrove created JBTM-3102:
--------------------------------------

             Summary: Provide a gRPC service for accessing OTS funtionality
                 Key: JBTM-3102
                 URL: https://issues.jboss.org/browse/JBTM-3102
             Project: JBoss Transaction Manager
          Issue Type: Feature Request
          Components: JTS
    Affects Versions: 5.9.2.Final
            Reporter: Michael Musgrove
            Assignee: Michael Musgrove
             Fix For: 5.later


JTS was the Java EE standard for different JTA implementations to interoperate. Since CORBA (and therefore JTS) is now an optional component of Jakarta EE there is a need for an alternative specification for how services can propagate a transaction context. A popular alternative to CORBA is gRPC which has the following nice features: 1) it is a good technology choice for service to service interactions; 2) is polyglot or, as stated in the documentation, "Automatically generates idiomatic client and server stubs for your service in a variety of languages and platforms"; and 3) provides excellent performance.

The reason JTS was chosen as the Java EE interop standard is that 1) it provides language level bindings that enable interoperability; and 2) it builds on a pre-existing industry standard, namely OTS.

Consequently, it is reasonable to conclude that a mapping from CosTransactions.idl (the IDL definition for OTS) to Protocol Buffers and gRPC services will:

- Enable existing OTS/JTS implementations to provide service in these new environments.
- Enable new and existing gRPC services to be able to access transactional functionality in an interoperable manner.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Wed Jan 23 08:24:00 2019
From: issues at jboss.org (Michael Musgrove (Jira))
Date: Wed, 23 Jan 2019 08:24:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3087) Ensure the LRA
 implementation is up to date
In-Reply-To: <JIRA.12783379.1544523365000@Atlassian.JIRA>
References: <JIRA.12783379.1544523365000@Atlassian.JIRA>
	<JIRA.12783379.1544523365000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12783379.1544523365000.10794.1548249840159@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-3087:
-----------------------------------
        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


> Ensure the LRA implementation is up to date
> -------------------------------------------
>
>                 Key: JBTM-3087
>                 URL: https://issues.jboss.org/browse/JBTM-3087
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>          Components: LRA
>    Affects Versions: 5.9.1.Final
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>            Priority: Major
>             Fix For: 5.next
>
>
> The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Wed Jan 23 08:25:00 2019
From: issues at jboss.org (Michael Musgrove (Jira))
Date: Wed, 23 Jan 2019 08:25:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3087) Ensure the LRA
 implementation is up to date
In-Reply-To: <JIRA.12783379.1544523365000@Atlassian.JIRA>
References: <JIRA.12783379.1544523365000@Atlassian.JIRA>
	<JIRA.12783379.1544523365000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12783379.1544523365000.10810.1548249900791@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove reopened JBTM-3087:
------------------------------------


The Narayana implementation of LRA depends on specific snapshot builds in the eclipse repo since the LRA spec is in flux. But snapshots are purged after a month so I am reopening to bring the implementation up to date.

> Ensure the LRA implementation is up to date
> -------------------------------------------
>
>                 Key: JBTM-3087
>                 URL: https://issues.jboss.org/browse/JBTM-3087
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>          Components: LRA
>    Affects Versions: 5.9.1.Final
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>            Priority: Major
>             Fix For: 5.next
>
>
> The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Wed Jan 23 08:28:00 2019
From: issues at jboss.org (Michael Musgrove (Jira))
Date: Wed, 23 Jan 2019 08:28:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3087) Ensure the LRA
 implementation is up to date
In-Reply-To: <JIRA.12783379.1544523365000@Atlassian.JIRA>
References: <JIRA.12783379.1544523365000@Atlassian.JIRA>
	<JIRA.12783379.1544523365000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12783379.1544523365000.10819.1548250080520@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Issue was automatically transitioned when Michael Musgrove created pull request #1401 in GitHub
-----------------------------------------------------------------------------------------------
    Status: Pull Request Sent  (was: Reopened)


> Ensure the LRA implementation is up to date
> -------------------------------------------
>
>                 Key: JBTM-3087
>                 URL: https://issues.jboss.org/browse/JBTM-3087
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>          Components: LRA
>    Affects Versions: 5.9.1.Final
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>            Priority: Major
>             Fix For: 5.next
>
>
> The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Thu Jan 24 12:47:00 2019
From: issues at jboss.org (Michael Musgrove (Jira))
Date: Thu, 24 Jan 2019 12:47:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3103) LRA api-particpant
 quickstart needs aligning with the latest MP LRA spec changes
In-Reply-To: <JIRA.12789141.1548351972000@Atlassian.JIRA>
References: <JIRA.12789141.1548351972000@Atlassian.JIRA>
	<JIRA.12789141.1548351972474@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12789141.1548351972000.18800.1548352020050@Atlassian.JIRA>

Michael Musgrove created JBTM-3103:
--------------------------------------

             Summary: LRA api-particpant quickstart needs aligning with the latest MP LRA spec changes
                 Key: JBTM-3103
                 URL: https://issues.jboss.org/browse/JBTM-3103
             Project: JBoss Transaction Manager
          Issue Type: Bug
            Reporter: Michael Musgrove


This quickstart depends on LRAParticipantDeserializer to recreate participants during crash recovery but [MP LRA issue #61|https://github.com/eclipse/microprofile-lra/issues/61] has removed this class. The alternative registration mechanism is still outstanding [see the comments on issue #35|https://github.com/eclipse/microprofile-lra/issues/35] for a discussion of the new way of registering participants.

Until a PR is raised for this issue I would like to disable the quickstarts that utilise LRAParticipantDeserializer.

Note that this has only just become an issue since previouslythe Narayana implementation of LRA depended on a specific snapshot build in the eclipse repo (since the LRA spec is in flux), but snapshots are purged after a month so the old way of registering participants is no longer available.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Thu Jan 24 13:00:00 2019
From: issues at jboss.org (Michael Musgrove (Jira))
Date: Thu, 24 Jan 2019 13:00:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3103) LRA api-particpant
 quickstart needs aligning with the latest MP LRA spec changes
In-Reply-To: <JIRA.12789141.1548351972000@Atlassian.JIRA>
References: <JIRA.12789141.1548351972000@Atlassian.JIRA>
	<JIRA.12789141.1548351972000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12789141.1548351972000.18836.1548352800475@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBTM-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Issue was automatically transitioned when Michael Musgrove created pull request #244 in GitHub
----------------------------------------------------------------------------------------------
    Status: Pull Request Sent  (was: Open)


> LRA api-particpant quickstart needs aligning with the latest MP LRA spec changes
> --------------------------------------------------------------------------------
>
>                 Key: JBTM-3103
>                 URL: https://issues.jboss.org/browse/JBTM-3103
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>            Reporter: Michael Musgrove
>            Priority: Major
>
> This quickstart depends on LRAParticipantDeserializer to recreate participants during crash recovery but [MP LRA issue #61|https://github.com/eclipse/microprofile-lra/issues/61] has removed this class. The alternative registration mechanism is still outstanding [see the comments on issue #35|https://github.com/eclipse/microprofile-lra/issues/35] for a discussion of the new way of registering participants.
> Until a PR is raised for this issue I would like to disable the quickstarts that utilise LRAParticipantDeserializer.
> Note that this has only just become an issue since previouslythe Narayana implementation of LRA depended on a specific snapshot build in the eclipse repo (since the LRA spec is in flux), but snapshots are purged after a month so the old way of registering participants is no longer available.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)

From issues at jboss.org  Fri Jan 25 13:09:00 2019
From: issues at jboss.org (Michael Musgrove (Jira))
Date: Fri, 25 Jan 2019 13:09:00 -0500 (EST)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3102) Provide a gRPC service
 for accessing OTS funtionality
In-Reply-To: <JIRA.12788400.1548091637000@Atlassian.JIRA>
References: <JIRA.12788400.1548091637000@Atlassian.JIRA>
	<JIRA.12788400.1548091637000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12788400.1548091637000.24351.1548439740136@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/JBTM-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687759#comment-13687759 ] 

Michael Musgrove commented on JBTM-3102:
----------------------------------------

The initial POC for this task is located at https://github.com/mmusgrov/narayana/tree/JBTM-3102/ArjunaJTS/grpc

> Provide a gRPC service for accessing OTS funtionality
> -----------------------------------------------------
>
>                 Key: JBTM-3102
>                 URL: https://issues.jboss.org/browse/JBTM-3102
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: JTS
>    Affects Versions: 5.9.2.Final
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>            Priority: Major
>             Fix For: 5.later
>
>
> JTS was the Java EE standard for different JTA implementations to interoperate. Since CORBA (and therefore JTS) is now an optional component of Jakarta EE there is a need for an alternative specification for how services can propagate a transaction context. A popular alternative to CORBA is gRPC which has the following nice features: 1) it is a good technology choice for service to service interactions; 2) is polyglot or, as stated in the documentation, "Automatically generates idiomatic client and server stubs for your service in a variety of languages and platforms"; and 3) provides excellent performance.
> The reason JTS was chosen as the Java EE interop standard is that 1) it provides language level bindings that enable interoperability; and 2) it builds on a pre-existing industry standard, namely OTS.
> Consequently, it is reasonable to conclude that a mapping from CosTransactions.idl (the IDL definition for OTS) to Protocol Buffers and gRPC services will:
> - Enable existing OTS/JTS implementations to provide service in these new environments.
> - Enable new and existing gRPC services to be able to access transactional functionality in an interoperable manner.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)