January 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3094) Redesign Narayana.io page to follow modern trends

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3094?page=com.atlassian.jira.plugin.... ] 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-B3bN2j5GHen0a7By2R23...] and [summarized at F2F 19 presentation|https://docs.google.com/presentation/d/1N6La-75ImuRYYwTS5nbc...]. There were some ideas about enhancements [in jira issues|https://issues.jboss.org/issues/?jql=summary%20~%20%22narayana.io%...]. 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-B3bN2j5GHen0a7By2R23...] and [summarized at F2F 19 presentation|https://docs.google.com/presentation/d/1N6La-75ImuRYYwTS5nbc...]. There were some ideas about enhancements [in jira issues|https://issues.jboss.org/issues/?jql=summary%20~%20%22narayana.io%...]. > 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-B3bN2j5GHen0a7By2R23...] and [summarized at F2F 19 presentation|https://docs.google.com/presentation/d/1N6La-75ImuRYYwTS5nbc...]. > There were some ideas about enhancements [in jira issues|https://issues.jboss.org/issues/?jql=summary%20~%20%22narayana.io%...]. > 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)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3094) Redesign Narayana.io page to follow more modern trends

by Ondra Chaloupka (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-B3bN2j5GHen0a7By2R23...] and [summarized at F2F 19 presentation|https://docs.google.com/presentation/d/1N6La-75ImuRYYwTS5nbc...]. There were some ideas about enhancements [in jira issues|https://issues.jboss.org/issues/?jql=summary%20~%20%22narayana.io%...]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3093) Disable the maven site plugin for the LRA module

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3093?page=com.atlassian.jira.plugin.... ] 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)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3093) disable the maven site plugin for the LRA module

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3093?page=com.atlassian.jira.plugin.... ] 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)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3093) maven site plugin fails on the LRA client module

by Michael Musgrove (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)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2805) Karaf fails to build in CI

by Amos Feng (Jira)

[ https://issues.jboss.org/browse/JBTM-2805?page=com.atlassian.jira.plugin.... ] 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/resourc... [2] https://github.com/jbosstm/narayana/blob/master/osgi/jta/pom.xml#L350 [3] https://github.com/apache/karaf/commit/658a2bda0791ed6ff7aa965a8db3904273... > 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/PluginConfigurationExcep... > [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)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3092) Performance TxnTest is processed with ServiceUnavailableException

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3092?page=com.atlassian.jira.plugin.... ] 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)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3092) Performance TxnTest is processed with ServiceUnavailableException

by Ondra Chaloupka (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)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3091) LRA module should depend on a specific snapshot build

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3091?page=com.atlassian.jira.plugin.... ] 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)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3091) LRA module should depend on a specific snapshot build

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3091?page=com.atlassian.jira.plugin.... ] 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)

5 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues January 2019