[JBoss JIRA] (JGRP-2501) Jgroup view not stabilized after upgrading from 3.4.3 to 4.01.0
by Ajay Sharma (Jira)
Ajay Sharma created JGRP-2501:
---------------------------------
Summary: Jgroup view not stabilized after upgrading from 3.4.3 to 4.01.0
Key: JGRP-2501
URL: https://issues.redhat.com/browse/JGRP-2501
Project: JGroups
Issue Type: Bug
Affects Versions: 4.0.10
Reporter: Ajay Sharma
Assignee: Bela Ban
Hi
we have 15 node cluster after upgrading Jgroup from 3.4.3 to 4.0.10, system is unstable and keep getting below logs
2020-09-03 11:47:30.317 WARN org.jgroups.protocols.pbcast.GMS - vmc0198-27827: not member of view [vmc0208-48939|123]; discarding it
2020-09-03 11:47:32.316 WARN org.jgroups.protocols.pbcast.GMS - vmc0198-27827: failed to create view from delta-view; dropping view: java.lang.IllegalStateException: the view-id of the delta view ([vmc0208-48939|123]) doesn't match the current view-id ([vmc0208-48939|122]); discarding delta view [vmc0208-48939|124], ref-view=[vmc0208-48939|123], joined=[vmc0198-5504]
2020-09-03 11:47:32.323 WARN org.jgroups.protocols.pbcast.GMS - vmc0198-27827: not member of view [vmc0208-48939|124]; discarding it.
2020-09-03 11:49:07.160 WARN org.jgroups.protocols.pbcast.NAKACK2 - JGRP000011: vmc0198-63871: dropped message batch from non-member vmc0201-28703 (view=MergeView::[vmc0208-48939|140] (24) [ ***REMOVING MACHINE NAME AND PORT ***] ])
2020-09-03 11:49:07.160 WARN org.jgroups.protocols.pbcast.NAKACK2 - JGRP000011: vmc0198-23411: dropped message batch from non-member vmc0201-28703 (view=[***REMOVING MACHINE NAME AND PORT FOR CLEAR VIEW ***] .])
2020-09-05 16:16:07.380 DEBUG org.jgroups.protocols.FD_ALL - haven't received a heartbeat from vmc0201-55458 for 12541 ms, adding it to suspect list
2020-09-05 16:16:07.535 DEBUG org.jgroups.protocols.FD_SOCK - vmc0198-24881: failed connecting to vmc0204-45403: connect timed out
2020-09-05 16:16:07.536 DEBUG org.jgroups.protocols.FD_SOCK - vmc0198-24881: broadcasting suspect(vmc0204-45403)
2020-09-05 16:16:07.536 DEBUG org.jgroups.protocols.FD_SOCK - vmc0198-24881: pingable_mbrs=[***REMOVING MACHINE NAME AND PORT ***], ping_dest=vmc0204-54485
2020-09-05 16:16:08.513 DEBUG org.jgroups.protocols.pbcast.GMS - vmc0198-52842: installing view [ ***REMOVING MACHINE NAME AND PORT FOR CLEAR VIEW *** ]
2020-09-05 16:16:08.513 DEBUG org.jgroups.protocols.pbcast.GMS - vmc0198-24881: installing view [vmc0200-30543|2672] (184) [ ***REMOVING MACHINE NAME AND PORT FOR CLEAR VIEW *** ]
===================================
To isolate the issue we have created a small program both in Jgroup 3.4.3 and Jgroups 4.0.10
Both applications take IP addresses and the number of channels as arguments. We have run both applications in the following matrix and collected view data and timings.
Below are the stats:
Number of members (number of nodes x number of channels) Jgroups 3.4.3 Jgroup 4.0.10
225 (15x15) Simultaneous start 25 - 30 seconds* 15 minutes**
225 (15x15) Rolling start (view after 15th node start) 20 seconds* 10 minutes**
196 (14x14) Simultaneous start 25 seconds* 4 minutes**
169 (13x13) Simultaneous start 30 - 31 seconds* 7 minutes**
144 (12x12) Simultaneous start 27 seconds* 5 minutes**
121 (11x11) Simultaneous start 22 seconds* 2 minutes**
100 (10x10) Simultaneous start 20 seconds* 5 minutes**
...
...
9 to 49 channels (3x3) to (7x7) almost immediate* almost immediate*
Note: Even after taking 15 minutes, views are not stable its keeps fluctuating.
=======
Below are my protocols used with properties:
Protocol[] protocolStack={
new UDP().setValue("bind_addr",InetAddress.getByName(myBindAddress)).setValue("mcast_port", 10600).setValue("bind_port", 10601)
.setValue("port_range", 100).setValue("diagnostics_bind_interfaces", parInterfaceList).setValue("diagnostics_port", 10599),
new PING(),
new MERGE3(),
new FD_SOCK().setValue("bind_addr", InetAddress.getByName(myBindAddress)),
new FD_ALL().setValue("timeout", 12000).setValue("interval", 3000),
new VERIFY_SUSPECT().setValue("bind_addr", InetAddress.getByName(myBindAddress)),
new BARRIER(),
new NAKACK2(),
new UNICAST3(),
new STABLE(),
new GMS().setValue("print_local_addr", true),
new UFC(),
new MFC(),
new FRAG2()};
However, we tried to update below few properties value but no luck
thread_pool_max_threads = 200 in UDP()
Default values of FD_ALL()
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFLY-13692) Anything in jboss-all.xml after <weld/> element is ignored
by Sudeshna Sur (Jira)
[ https://issues.redhat.com/browse/WFLY-13692?page=com.atlassian.jira.plugi... ]
Sudeshna Sur reassigned WFLY-13692:
-----------------------------------
Assignee: Sudeshna Sur (was: Matěj Novotný)
> Anything in jboss-all.xml after <weld/> element is ignored
> ----------------------------------------------------------
>
> Key: WFLY-13692
> URL: https://issues.redhat.com/browse/WFLY-13692
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 20.0.1.Final
> Reporter: L K
> Assignee: Sudeshna Sur
> Priority: Major
>
> Classes org.jboss.as.weld.WeldJBossAll10Parser and org.jboss.as.weld.WeldJBossAll11Parser are incorrect. They do not parse <weld> element as XML, they just check attributes.
> As a result, everything that comes after </weld> is ignored.
> This jboss-all.xml fails, as expected:
> {code:java}
> <jboss xmlns="urn:jboss:1.0">
> <some-stupid-element/>
> <weld xmlns="urn:jboss:weld:1.1"/>
> </jboss>
> {code}
> This one is successfully parsed (but must also fail):
> {code:java}
> <jboss xmlns="urn:jboss:1.0">
> <weld xmlns="urn:jboss:weld:1.1"/>
> <some-stupid-element/>
> </jboss>
> {code}
>
> Now imagine that "some-stupid-element" is in fact "jboss-deployment-structure" which gets ignored...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFWIP-354) Bootable JAR - jboss-maven-dist plugin param doesn't work as expected
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFWIP-354?page=com.atlassian.jira.plugin... ]
Jean Francois Denise commented on WFWIP-354:
--------------------------------------------
[~tommaso-borgato], in addition, the chapter "11.1. Provisioning a slim bootable jar' in [https://github.com/wildfly-extras/wildfly-jar-maven-plugin/releases/downl... it.
> Bootable JAR - jboss-maven-dist plugin param doesn't work as expected
> ----------------------------------------------------------------------
>
> Key: WFWIP-354
> URL: https://issues.redhat.com/browse/WFWIP-354
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Marek Kopecky
> Assignee: Jean Francois Denise
> Priority: Blocker
>
> Related RFE: EAP7-1385
> This usage of jboss-maven-dist plugin param doesn't work as expected:
> [<jboss-maven-dist>/home/mkopecky/jboss-eap-custom-maven-repository/maven-repository</jboss-maven-dist>|https://github.com/marekkopecky/Resteasy/commit/fb29381a9ef9a709f33481af8020a649db002980#diff-8c7ea03eb619e46657b96e8fe8d4f09eR248]
> Steps to reproduce:
> # clone resteasy 3.12 with this commit: https://github.com/marekkopecky/Resteasy/commit/fb29381a9ef9a709f33481af8...
> # update jboss-maven-dist plugin param to your custom repo path
> # rm -rf ~/.m2/repository/xerces/xercesImpl/2.12.0.SP03
> # set REPO variable (eg. "REPO=/home/mkopecky/jboss-eap-custom-maven-repository/maven-repository")
> # build start tests {code}mvn install -DskipTests -Dmaven.repo.local=$REPO
> cd testsuite
> mvn install:install-file -Dpackaging=pom -Dfile=pom.xml -DpomFile=pom.xml -Dmaven.repo.local=$REPO
> cd integration-tests
> mvn clean install -Dts.bootable -Ddefault=false -Ddisable.microprofile.tests -Dserver.version=21.0.0.Beta1-SNAPSHOT -Dserver.home=placeholder -Dmaven.repo.local=$REPO -Dmaven.test.redirectTestOutputToFile=false{code}
> # see the results: org.jboss.modules.ModuleLoadException, because xercesImpl 2.12.0.SP03 is downloaded in custom repo, but not present in .m2
> cc [~fburzigo], [~yersan]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFWIP-354) Bootable JAR - jboss-maven-dist plugin param doesn't work as expected
by Fabio Burzigotti (Jira)
[ https://issues.redhat.com/browse/WFWIP-354?page=com.atlassian.jira.plugin... ]
Fabio Burzigotti commented on WFWIP-354:
----------------------------------------
Hi [~mkopecky] - what [~jdenise] replied in first comment seems like what I have summed up here: https://github.com/marekkopecky/Resteasy/commit/fb29381a9ef9a709f33481af8...
Is the RESTEasy TS case configuration satisfying those requirements?
BTW CC [~tommaso-borgato] for he's checking whether what Marek reported can be reproduced by using the slim example: https://github.com/wildfly-extras/wildfly-jar-maven-plugin/tree/master/ex...
> Bootable JAR - jboss-maven-dist plugin param doesn't work as expected
> ----------------------------------------------------------------------
>
> Key: WFWIP-354
> URL: https://issues.redhat.com/browse/WFWIP-354
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Marek Kopecky
> Assignee: Jean Francois Denise
> Priority: Blocker
>
> Related RFE: EAP7-1385
> This usage of jboss-maven-dist plugin param doesn't work as expected:
> [<jboss-maven-dist>/home/mkopecky/jboss-eap-custom-maven-repository/maven-repository</jboss-maven-dist>|https://github.com/marekkopecky/Resteasy/commit/fb29381a9ef9a709f33481af8020a649db002980#diff-8c7ea03eb619e46657b96e8fe8d4f09eR248]
> Steps to reproduce:
> # clone resteasy 3.12 with this commit: https://github.com/marekkopecky/Resteasy/commit/fb29381a9ef9a709f33481af8...
> # update jboss-maven-dist plugin param to your custom repo path
> # rm -rf ~/.m2/repository/xerces/xercesImpl/2.12.0.SP03
> # set REPO variable (eg. "REPO=/home/mkopecky/jboss-eap-custom-maven-repository/maven-repository")
> # build start tests {code}mvn install -DskipTests -Dmaven.repo.local=$REPO
> cd testsuite
> mvn install:install-file -Dpackaging=pom -Dfile=pom.xml -DpomFile=pom.xml -Dmaven.repo.local=$REPO
> cd integration-tests
> mvn clean install -Dts.bootable -Ddefault=false -Ddisable.microprofile.tests -Dserver.version=21.0.0.Beta1-SNAPSHOT -Dserver.home=placeholder -Dmaven.repo.local=$REPO -Dmaven.test.redirectTestOutputToFile=false{code}
> # see the results: org.jboss.modules.ModuleLoadException, because xercesImpl 2.12.0.SP03 is downloaded in custom repo, but not present in .m2
> cc [~fburzigo], [~yersan]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFLY-13502) UT000010: Session is invalid
by Bartosz Baranowski (Jira)
[ https://issues.redhat.com/browse/WFLY-13502?page=com.atlassian.jira.plugi... ]
Bartosz Baranowski commented on WFLY-13502:
-------------------------------------------
[~cveli] - can you cook some sort of reproducer?
> UT000010: Session is invalid
> -----------------------------
>
> Key: WFLY-13502
> URL: https://issues.redhat.com/browse/WFLY-13502
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 14.0.0.Final, 16.0.0.Final
> Reporter: Cristian VL
> Assignee: Flavia Rainone
> Priority: Critical
>
> {code}
> 2020-05-21 06:00:22,239 ERROR [org.jboss.threads.errors] (default task-1145) Thread Thread[default task-1145,5,main] threw an uncaught exception: java.lang.RuntimeException: java.lang.IllegalStateException: UT000010: Session is invalid X0SZbaIu078s8ChCz8YIJON59sTmY7gV2bopjwlm
> at io.undertow.servlet.spec.ServletContextImpl.invokeRunnable(ServletContextImpl.java:1029)
> at io.undertow.servlet.spec.AsyncContextImpl.onAsyncComplete(AsyncContextImpl.java:614)
> at io.undertow.servlet.spec.AsyncContextImpl.access$100(AsyncContextImpl.java:73)
> at io.undertow.servlet.spec.AsyncContextImpl$3.run(AsyncContextImpl.java:316)
> at io.undertow.servlet.spec.AsyncContextImpl$6.run(AsyncContextImpl.java:485)
> at io.undertow.servlet.spec.AsyncContextImpl$TaskDispatchRunnable.run(AsyncContextImpl.java:604)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException: UT000010: Session is invalid X0SZbaIu078s8ChCz8YIJON59sTmY7gV2bopjwlm
> at io.undertow.server.session.InMemorySessionManager$SessionImpl.getAttribute(InMemorySessionManager.java:512)
> at io.undertow.servlet.spec.HttpSessionImpl.getAttribute(HttpSessionImpl.java:122)
> at org.jboss.weld.module.web.context.http.HttpConversationContextImpl.getSessionAttribute(HttpConversationContextImpl.java:37)
> at org.jboss.weld.module.web.context.http.HttpConversationContextImpl.getSessionAttribute(HttpConversationContextImpl.java:18)
> at org.jboss.weld.contexts.AbstractConversationContext.copyConversationIdGeneratorAndConversationsToSession(AbstractConversationContext.java:179)
> at org.jboss.weld.contexts.AbstractConversationContext.dissociate(AbstractConversationContext.java:157)
> at org.jboss.weld.module.web.servlet.ConversationContextActivator.activateConversationContext(ConversationContextActivator.java:116)
> at org.jboss.weld.module.web.servlet.HttpContextLifecycle.requestInitialized(HttpContextLifecycle.java:254)
> at org.jboss.weld.module.web.servlet.WeldInitialListener.requestInitialized(WeldInitialListener.java:152)
> at io.undertow.servlet.core.ApplicationListeners.requestInitialized(ApplicationListeners.java:246)
> at io.undertow.servlet.spec.AsyncContextImpl.setupRequestContext(AsyncContextImpl.java:706)
> at io.undertow.servlet.spec.AsyncContextImpl.access$700(AsyncContextImpl.java:73)
> at io.undertow.servlet.spec.AsyncContextImpl$7.run(AsyncContextImpl.java:619)
> at io.undertow.servlet.spec.ServletContextImpl$2.call(ServletContextImpl.java:181)
> at io.undertow.servlet.spec.ServletContextImpl$2.call(ServletContextImpl.java:178)
> at io.undertow.servlet.spec.ServletContextImpl.invokeRunnable(ServletContextImpl.java:1027)
> ... 10 more
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFWIP-355) Bootable JAR - scripts in bin folder of the server installation directory are not executable
by Fabio Burzigotti (Jira)
[ https://issues.redhat.com/browse/WFWIP-355?page=com.atlassian.jira.plugin... ]
Fabio Burzigotti reassigned WFWIP-355:
--------------------------------------
Assignee: Jean Francois Denise (was: Kabir Khan)
> Bootable JAR - scripts in bin folder of the server installation directory are not executable
> --------------------------------------------------------------------------------------------
>
> Key: WFWIP-355
> URL: https://issues.redhat.com/browse/WFWIP-355
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Tommaso Borgato
> Assignee: Jean Francois Denise
> Priority: Major
>
> Related RFE: EAP7-1385
> Scripts in the bin folder of the server's installation directory are not executable;
> If you start the server like the following:
> {noformat}
> java -jar target/default-hollow-jar-bootable.jar --install-dir=/tmp/wildfly-bootable-server-hollow-jar
> {noformat}
> and the look into the bin folder:
> {noformat}
> $ ls -ltr /tmp/wildfly-bootable-server-hollow-jar/bin
> total 1520
> -rw-rw-r--. 1 hudson hudson 2362 Sep 11 10:11 vault.sh
> -rw-rw-r--. 1 hudson hudson 709 Sep 11 10:11 vault.ps1
> -rw-rw-r--. 1 hudson hudson 2269 Sep 11 10:11 vault.bat
> -rw-rw-r--. 1 hudson hudson 823 Sep 11 10:11 common.bat
> -rw-rw-r--. 1 hudson hudson 1933 Sep 11 10:11 jboss-cli-logging.properties
> -rw-rw-r--. 1 hudson hudson 3271 Sep 11 10:11 jboss-cli.bat
> -rw-rw-r--. 1 hudson hudson 792 Sep 11 10:11 common.sh
> -rw-rw-r--. 1 hudson hudson 11549 Sep 11 10:11 common.ps1
> -rw-rw-r--. 1 hudson hudson 893 Sep 11 10:11 jboss-cli.ps1
> -rw-rw-r--. 1 hudson hudson 1793 Sep 11 10:11 elytron-tool.sh
> -rw-rw-r--. 1 hudson hudson 1079 Sep 11 10:11 elytron-tool.ps1
> -rw-rw-r--. 1 hudson hudson 1710 Sep 11 10:11 elytron-tool.bat
> -rw-rw-r--. 1 hudson hudson 2392 Sep 11 10:11 add-user.sh
> -rw-rw-r--. 1 hudson hudson 3035 Sep 11 10:11 jboss-cli.xml
> -rw-rw-r--. 1 hudson hudson 2635 Sep 11 10:11 jboss-cli.sh
> -rw-rw-r--. 1 hudson hudson 1069 Sep 11 10:11 add-user.ps1
> -rw-rw-r--. 1 hudson hudson 2444 Sep 11 10:11 add-user.properties
> -rw-rw-r--. 1 hudson hudson 2417 Sep 11 10:11 add-user.bat
> -rw-rw-r--. 1 hudson hudson 12843 Sep 11 10:11 standalone.sh
> -rw-rw-r--. 1 hudson hudson 1624 Sep 11 10:11 standalone.ps1
> -rw-rw-r--. 1 hudson hudson 3226 Sep 11 10:11 standalone.conf.ps1
> -rw-rw-r--. 1 hudson hudson 3402 Sep 11 10:11 standalone.conf.bat
> -rw-rw-r--. 1 hudson hudson 2965 Sep 11 10:11 standalone.conf
> -rw-rw-r--. 1 hudson hudson 9576 Sep 11 10:11 standalone.bat
> -rw-rw-r--. 1 hudson hudson 49 Sep 11 10:11 product.conf
> -rw-rw-r--. 1 hudson hudson 49721 Sep 11 10:11 launcher.jar
> -rw-rw-r--. 1 hudson hudson 1369074 Sep 11 10:11 wildfly-elytron-tool.jar
> {noformat}
> you can see e.g. jboss-cli.sh is not executable
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFWIP-355) Bootable JAR - scripts in bin folder of the server installation directory are not executable
by Tommaso Borgato (Jira)
[ https://issues.redhat.com/browse/WFWIP-355?page=com.atlassian.jira.plugin... ]
Tommaso Borgato updated WFWIP-355:
----------------------------------
Summary: Bootable JAR - scripts in bin folder of the server installation directory are not executable (was: Bootable JAR - bin folder of the server installation directory are not executable)
> Bootable JAR - scripts in bin folder of the server installation directory are not executable
> --------------------------------------------------------------------------------------------
>
> Key: WFWIP-355
> URL: https://issues.redhat.com/browse/WFWIP-355
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Tommaso Borgato
> Assignee: Kabir Khan
> Priority: Major
>
> Related RFE: EAP7-1385
> Scripts in the bin folder of the server's installation directory are not executable;
> If you start the server like the following:
> {noformat}
> java -jar target/default-hollow-jar-bootable.jar --install-dir=/tmp/wildfly-bootable-server-hollow-jar
> {noformat}
> and the look into the bin folder:
> {noformat}
> $ ls -ltr /tmp/wildfly-bootable-server-hollow-jar/bin
> total 1520
> -rw-rw-r--. 1 hudson hudson 2362 Sep 11 10:11 vault.sh
> -rw-rw-r--. 1 hudson hudson 709 Sep 11 10:11 vault.ps1
> -rw-rw-r--. 1 hudson hudson 2269 Sep 11 10:11 vault.bat
> -rw-rw-r--. 1 hudson hudson 823 Sep 11 10:11 common.bat
> -rw-rw-r--. 1 hudson hudson 1933 Sep 11 10:11 jboss-cli-logging.properties
> -rw-rw-r--. 1 hudson hudson 3271 Sep 11 10:11 jboss-cli.bat
> -rw-rw-r--. 1 hudson hudson 792 Sep 11 10:11 common.sh
> -rw-rw-r--. 1 hudson hudson 11549 Sep 11 10:11 common.ps1
> -rw-rw-r--. 1 hudson hudson 893 Sep 11 10:11 jboss-cli.ps1
> -rw-rw-r--. 1 hudson hudson 1793 Sep 11 10:11 elytron-tool.sh
> -rw-rw-r--. 1 hudson hudson 1079 Sep 11 10:11 elytron-tool.ps1
> -rw-rw-r--. 1 hudson hudson 1710 Sep 11 10:11 elytron-tool.bat
> -rw-rw-r--. 1 hudson hudson 2392 Sep 11 10:11 add-user.sh
> -rw-rw-r--. 1 hudson hudson 3035 Sep 11 10:11 jboss-cli.xml
> -rw-rw-r--. 1 hudson hudson 2635 Sep 11 10:11 jboss-cli.sh
> -rw-rw-r--. 1 hudson hudson 1069 Sep 11 10:11 add-user.ps1
> -rw-rw-r--. 1 hudson hudson 2444 Sep 11 10:11 add-user.properties
> -rw-rw-r--. 1 hudson hudson 2417 Sep 11 10:11 add-user.bat
> -rw-rw-r--. 1 hudson hudson 12843 Sep 11 10:11 standalone.sh
> -rw-rw-r--. 1 hudson hudson 1624 Sep 11 10:11 standalone.ps1
> -rw-rw-r--. 1 hudson hudson 3226 Sep 11 10:11 standalone.conf.ps1
> -rw-rw-r--. 1 hudson hudson 3402 Sep 11 10:11 standalone.conf.bat
> -rw-rw-r--. 1 hudson hudson 2965 Sep 11 10:11 standalone.conf
> -rw-rw-r--. 1 hudson hudson 9576 Sep 11 10:11 standalone.bat
> -rw-rw-r--. 1 hudson hudson 49 Sep 11 10:11 product.conf
> -rw-rw-r--. 1 hudson hudson 49721 Sep 11 10:11 launcher.jar
> -rw-rw-r--. 1 hudson hudson 1369074 Sep 11 10:11 wildfly-elytron-tool.jar
> {noformat}
> you can see e.g. jboss-cli.sh is not executable
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months