August 2017 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-599) Update maven-assembly-plugin goal to 'single'

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-599?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-599: -------------------------------------- Component/s: Documentation & Demos (was: CI & Packaging) > Update maven-assembly-plugin goal to 'single' > --------------------------------------------- > > Key: MODCLUSTER-599 > URL: https://issues.jboss.org/browse/MODCLUSTER-599 > Project: mod_cluster > Issue Type: Task > Components: Documentation & Demos > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.7.Final, 1.4.0.Alpha1, 2.0.0.Alpha1 > > > {noformat} > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 2.305 s > [INFO] Finished at: 2017-06-29T00:16:15+02:00 > [INFO] Final Memory: 14M/245M > [INFO] ------------------------------------------------------------------------ > [ERROR] Could not find goal 'attached' in plugin org.apache.maven.plugins:maven-assembly-plugin:3.0.0 among available goals help, single -> [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/MojoNotFoundException > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-599) Update maven-assembly-plugin goal to 'single'

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-599?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-599: -------------------------------------- Issue Type: Task (was: Component Upgrade) > Update maven-assembly-plugin goal to 'single' > --------------------------------------------- > > Key: MODCLUSTER-599 > URL: https://issues.jboss.org/browse/MODCLUSTER-599 > Project: mod_cluster > Issue Type: Task > Components: CI & Packaging > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.7.Final, 1.4.0.Alpha1, 2.0.0.Alpha1 > > > {noformat} > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 2.305 s > [INFO] Finished at: 2017-06-29T00:16:15+02:00 > [INFO] Final Memory: 14M/245M > [INFO] ------------------------------------------------------------------------ > [ERROR] Could not find goal 'attached' in plugin org.apache.maven.plugins:maven-assembly-plugin:3.0.0 among available goals help, single -> [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/MojoNotFoundException > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-599) Update maven-assembly-plugin goal to 'single'

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-599?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-599: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > Update maven-assembly-plugin goal to 'single' > --------------------------------------------- > > Key: MODCLUSTER-599 > URL: https://issues.jboss.org/browse/MODCLUSTER-599 > Project: mod_cluster > Issue Type: Component Upgrade > Components: CI & Packaging > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.7.Final, 1.4.0.Alpha1, 2.0.0.Alpha1 > > > {noformat} > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 2.305 s > [INFO] Finished at: 2017-06-29T00:16:15+02:00 > [INFO] Final Memory: 14M/245M > [INFO] ------------------------------------------------------------------------ > [ERROR] Could not find goal 'attached' in plugin org.apache.maven.plugins:maven-assembly-plugin:3.0.0 among available goals help, single -> [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/MojoNotFoundException > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-598) Include building the distribution profile in CI

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-598?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-598: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > Include building the distribution profile in CI > ----------------------------------------------- > > Key: MODCLUSTER-598 > URL: https://issues.jboss.org/browse/MODCLUSTER-598 > Project: mod_cluster > Issue Type: Component Upgrade > Components: CI & Packaging > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.7.Final, 1.4.0.Alpha1, 2.0.0.Alpha1 > > > Prevents issues such as MODCLUSTER-599. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-597) Upgrade jboss-parent to 24 (to support jdk-9+175)

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-597?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-597: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > Upgrade jboss-parent to 24 (to support jdk-9+175) > ------------------------------------------------- > > Key: MODCLUSTER-597 > URL: https://issues.jboss.org/browse/MODCLUSTER-597 > Project: mod_cluster > Issue Type: Component Upgrade > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.7.Final, 1.4.0.Alpha1, 2.0.0.Alpha1 > > > {noformat} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce (enforce-java-version) on project mod_cluster-parent: Execution enforce-java-version of goal org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce: java.lang.ExceptionInInitializerError: null > [ERROR] ----------------------------------------------------- > [ERROR] realm = plugin>org.apache.maven.plugins:maven-enforcer-plugin:1.3.1 > [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy > [ERROR] urls[0] = file:/Users/rhusar/.m2/repository/org/apache/maven/plugins/maven-enforcer-plugin/1.3.1/maven-enforcer-plugin-1.3.1.jar > [ERROR] urls[1] = file:/Users/rhusar/.m2/repository/org/apache/maven/reporting/maven-reporting-api/2.0.9/maven-reporting-api-2.0.9.jar > [ERROR] urls[2] = file:/Users/rhusar/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-10/doxia-sink-api-1.0-alpha-10.jar > [ERROR] urls[3] = file:/Users/rhusar/.m2/repository/commons-cli/commons-cli/1.0/commons-cli-1.0.jar > [ERROR] urls[4] = file:/Users/rhusar/.m2/repository/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-4/plexus-interactivity-api-1.0-alpha-4.jar > [ERROR] urls[5] = file:/Users/rhusar/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.8/plexus-utils-1.5.8.jar > [ERROR] urls[6] = file:/Users/rhusar/.m2/repository/commons-lang/commons-lang/2.3/commons-lang-2.3.jar > [ERROR] urls[7] = file:/Users/rhusar/.m2/repository/org/apache/maven/enforcer/enforcer-api/1.3.1/enforcer-api-1.3.1.jar > [ERROR] urls[8] = file:/Users/rhusar/.m2/repository/org/apache/maven/enforcer/enforcer-rules/1.3.1/enforcer-rules-1.3.1.jar > [ERROR] urls[9] = file:/Users/rhusar/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/1.4/maven-common-artifact-filters-1.4.jar > [ERROR] urls[10] = file:/Users/rhusar/.m2/repository/org/beanshell/bsh/2.0b4/bsh-2.0b4.jar > [ERROR] urls[11] = file:/Users/rhusar/.m2/repository/org/apache/maven/shared/maven-dependency-tree/2.1/maven-dependency-tree-2.1.jar > [ERROR] urls[12] = file:/Users/rhusar/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar > [ERROR] urls[13] = file:/Users/rhusar/.m2/repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar > [ERROR] urls[14] = file:/Users/rhusar/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-6/plexus-i18n-1.0-beta-6.jar > [ERROR] Number of foreign imports: 1 > [ERROR] import: Entry[import from realm ClassRealm[maven.api, parent: null]] > [ERROR] > [ERROR] ----------------------------------------------------- > [ERROR] : begin 0, end 3, length 1 > [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/PluginContainerException > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-581) Session draining with non-positive timeout may wait indefinitely

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-581?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-581: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > Session draining with non-positive timeout may wait indefinitely > ---------------------------------------------------------------- > > Key: MODCLUSTER-581 > URL: https://issues.jboss.org/browse/MODCLUSTER-581 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.6.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.7.Final, 1.4.0.Alpha1, 2.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-586) Upgrade jboss-parent to 22

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-586?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-586: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > Upgrade jboss-parent to 22 > -------------------------- > > Key: MODCLUSTER-586 > URL: https://issues.jboss.org/browse/MODCLUSTER-586 > Project: mod_cluster > Issue Type: Component Upgrade > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.4.0.Alpha1, 2.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-596) mod_cluster stop/stop-context operations do not send STOP-* in when session draining was unsuccessful

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-596?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-596: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > mod_cluster stop/stop-context operations do not send STOP-* in when session draining was unsuccessful > ----------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-596 > URL: https://issues.jboss.org/browse/MODCLUSTER-596 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.6.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.7.Final, 1.4.0.Alpha1, 2.0.0.Alpha1 > > > CLI operation description > {noformat} > [standalone@localhost:9990 /] /subsystem=modcluster/:read-operation-description(name=stop > { > "outcome" => "success", > "result" => { > "operation-name" => "stop", > "description" => "Tell reverse proxies that all contexts on the node can't process requests.", > "request-properties" => {"waittime" => { > "type" => INT, > "description" => "Timeout to wait for all contexts to stop.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "default" => 10, > "unit" => "SECONDS" > }}, > "reply-properties" => {}, > "read-only" => false, > "runtime-only" => true > } > } > {noformat} > With default and non-distributable context or draining strategy set to ALWAYS. > * stop() or stop-context is called > * Disable creating any new session by sending DISABLE-APP command to balancer > {noformat} > "context" => {"/clusterbench" => { > "requests" => 0, > "status" => "disabled" > }} > {noformat} > * Session drain > {noformat} > 2017-05-10 09:19:09,956 INFO [org.jboss.modcluster] (management-handler-thread - 1) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/clusterbench in 10 seconds. > {noformat} > * Session timeout is 5 minutes so it fails > {noformat} > 2017-05-10 09:26:05,081 WARN [org.jboss.modcluster] (management-handler-thread - 1) MODCLUSTER000025: Failed to drain 1 remaining active sessions from default-host:/clusterbench within 10.0 seconds > {noformat} > *_+{color:red}Issue{color}+_* > * Stop-app should be sent to balancer to stop context/node, but node/context stays disabled. This happens even if session drain is successful. > {noformat} > "context" => {"/clusterbench" => { > "requests" => 0, > "status" => "disabled" > }} > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-572) Normalize hostnames in MCMP messages

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-572?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-572: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > Normalize hostnames in MCMP messages > ------------------------------------ > > Key: MODCLUSTER-572 > URL: https://issues.jboss.org/browse/MODCLUSTER-572 > Project: mod_cluster > Issue Type: Enhancement > Components: Core & Container Integration (Java) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.6.CR2, 1.4.0.Alpha1, 2.0.0.Alpha1 > > > Sort of container aspect of MODCLUSTER-463. Moreover, to mitigate MODCLUSTER-568 for versions <1.2.14.Final we should normalize the hostnames to lowercase we send out in MCMP messages. > As per RFC 1035 Section 2.3.3 hostnames have to be treated case insensitive. > The downside to this is that the manager page/logs will display lowercased hostnames. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-575) Create a Load SPI module

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-575?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-575: -------------------------------------- Fix Version/s: 1.4.0.Alpha1 > Create a Load SPI module > ------------------------ > > Key: MODCLUSTER-575 > URL: https://issues.jboss.org/browse/MODCLUSTER-575 > Project: mod_cluster > Issue Type: Feature Request > Components: Core & Container Integration (Java) > Affects Versions: 1.3.6.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.4.0.Alpha1, 2.0.0.Alpha1 > > > Currently, implementers of a custom LoadMetric need to pull in entire core module. A load spi module could be created, which then along with the container spi module is sufficient for metric implementers to import. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues August 2017