[JBoss JIRA] (SWSQE-489) Setup role based access for Jenkins2
by Jeeva Kandasamy (Jira)
Jeeva Kandasamy created SWSQE-489:
-------------------------------------
Summary: Setup role based access for Jenkins2
Key: SWSQE-489
URL: https://issues.jboss.org/browse/SWSQE-489
Project: Kiali QE
Issue Type: QE Task
Reporter: Jeeva Kandasamy
Assignee: Jeeva Kandasamy
Jenkins2 using user-based access for authorization. We are going to support Jaeger developers Jenkins pipeline jobs with our jenkins2. It is too complex to manage permissions with the user.
It is a right time to switch our jenkins2 from user-based authorization to role-based authorization.
https://plugins.jenkins.io/role-strategy
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFCORE-3825) Unify "-server" option in windows scripts (ps1, bat) for domain mode (and its servers) on all JDKs
by R Searls (Jira)
[ https://issues.jboss.org/browse/WFCORE-3825?page=com.atlassian.jira.plugi... ]
R Searls commented on WFCORE-3825:
----------------------------------
I have withdrawn from this jira. I no longer have access to a Windows machine.
Perhaps James Perkins can take it. He is working on similar Windows scripts.
> Unify "-server" option in windows scripts (ps1, bat) for domain mode (and its servers) on all JDKs
> --------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3825
> URL: https://issues.jboss.org/browse/WFCORE-3825
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Reporter: Marek Kopecký
> Priority: Major
>
> Unify "-server" option in windows scripts (ps1, bat) for domain mode (and its servers) on all JDKs
> Domain use "-server" option in unix, windows bat. Domain doesn't use "-server" option in windows ps1 scripts. Same for JVMs of domain servers.
> I prefer to add "-server" option to ps1 scripts.
> {noformat:title=domain.ps1 - "-server" option is missing}
> PS C:\Users\Administrator\playground\wfly.15\wildfly\bin> .\domain.ps1
> =================================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: C:\Users\Administrator\playground\wfly.15\wildfly
> JAVA: C:\Program Files\Java\jdk1.8.0_121\bin\java.exe
> MODULE_OPTS:
> JAVA_OPTS: -Xms64M -Xmx512M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman
> =================================================================================
> ...
> {noformat}
> {noformat:title=domain.bat - "-server" option is listed in JAVA_OPTS}
> C:\Users\Administrator\playground\wfly.15\wildfly\bin>domain.bat
> Calling "C:\Users\Administrator\playground\wfly.15\wildfly\bin\domain.conf.bat"
> Setting JAVA property to "C:\Program Files\Java\jdk1.8.0_121\bin\java"
> ===============================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: "C:\Users\Administrator\playground\wfly.15\wildfly"
> JAVA: "C:\Program Files\Java\jdk1.8.0_121\bin\java"
> JAVA_OPTS: "-Xms64M -Xmx512M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -server"
> ===============================================================================
> ...
> {noformat}
> cc: [~jamezp]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFCORE-3825) Unify "-server" option in windows scripts (ps1, bat) for domain mode (and its servers) on all JDKs
by R Searls (Jira)
[ https://issues.jboss.org/browse/WFCORE-3825?page=com.atlassian.jira.plugi... ]
R Searls reassigned WFCORE-3825:
--------------------------------
Assignee: (was: R Searls)
> Unify "-server" option in windows scripts (ps1, bat) for domain mode (and its servers) on all JDKs
> --------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3825
> URL: https://issues.jboss.org/browse/WFCORE-3825
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Reporter: Marek Kopecký
> Priority: Major
>
> Unify "-server" option in windows scripts (ps1, bat) for domain mode (and its servers) on all JDKs
> Domain use "-server" option in unix, windows bat. Domain doesn't use "-server" option in windows ps1 scripts. Same for JVMs of domain servers.
> I prefer to add "-server" option to ps1 scripts.
> {noformat:title=domain.ps1 - "-server" option is missing}
> PS C:\Users\Administrator\playground\wfly.15\wildfly\bin> .\domain.ps1
> =================================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: C:\Users\Administrator\playground\wfly.15\wildfly
> JAVA: C:\Program Files\Java\jdk1.8.0_121\bin\java.exe
> MODULE_OPTS:
> JAVA_OPTS: -Xms64M -Xmx512M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman
> =================================================================================
> ...
> {noformat}
> {noformat:title=domain.bat - "-server" option is listed in JAVA_OPTS}
> C:\Users\Administrator\playground\wfly.15\wildfly\bin>domain.bat
> Calling "C:\Users\Administrator\playground\wfly.15\wildfly\bin\domain.conf.bat"
> Setting JAVA property to "C:\Program Files\Java\jdk1.8.0_121\bin\java"
> ===============================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: "C:\Users\Administrator\playground\wfly.15\wildfly"
> JAVA: "C:\Program Files\Java\jdk1.8.0_121\bin\java"
> JAVA_OPTS: "-Xms64M -Xmx512M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -server"
> ===============================================================================
> ...
> {noformat}
> cc: [~jamezp]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-10817) Incorrect data check when clearing body of large compressed message after failover
by Miroslav Novak (Jira)
[ https://issues.jboss.org/browse/WFLY-10817?page=com.atlassian.jira.plugin... ]
Miroslav Novak commented on WFLY-10817:
---------------------------------------
I cannot reproduce it with Artemis 2.6.3 in WF14. Setting as resolved.
> Incorrect data check when clearing body of large compressed message after failover
> ----------------------------------------------------------------------------------
>
> Key: WFLY-10817
> URL: https://issues.jboss.org/browse/WFLY-10817
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 13.0.0.Final
> Reporter: Erich Duda
> Assignee: Jeff Mesnil
> Priority: Critical
>
> *Scenario*
> * There are two WildFly (Artemis) servers in dedicated shared store HA topology
> * Connection factory is configured to compress large messages
> * Live server is killed
> * Clients do failover to backup
> After the clients do failover to backup, I can see following exceptions in the log when a receiver tries to clear body of large message. The test fails because of lost messages.
> I can see this issue with Artemis 1.5.5.jbossorg-012.
> I am not able to reproduce it locally but I hit it on Jenkins every time.
> {code}
> javax.jms.JMSException: AMQ119029: Error writing body of message
> at org.apache.activemq.artemis.jms.client.ActiveMQBytesMessage.clearBody(ActiveMQBytesMessage.java:337)
> at org.jboss.qa.hornetq.apps.clients.Client.cleanMessage(Client.java:144)
> at org.jboss.qa.hornetq.apps.clients.Receiver11.receiveMessage(Receiver11.java:153)
> at org.jboss.qa.hornetq.apps.clients.ReceiverTransAck.run(ReceiverTransAck.java:89)
> Caused by: java.lang.RuntimeException: AMQ119029: Error writing body of message
> at org.apache.activemq.artemis.core.client.impl.ClientLargeMessageImpl.getBodyBuffer(ClientLargeMessageImpl.java:93)
> at org.apache.activemq.artemis.jms.client.ActiveMQBytesMessage.getBuffer(ActiveMQBytesMessage.java:363)
> at org.apache.activemq.artemis.jms.client.ActiveMQBytesMessage.clearBody(ActiveMQBytesMessage.java:335)
> ... 3 more
> Caused by: ActiveMQLargeMessageException[errorType=LARGE_MESSAGE_ERROR_BODY message=AMQ119029: Error writing body of message]
> at org.apache.activemq.artemis.core.client.impl.LargeMessageControllerImpl.sendPacketToOutput(LargeMessageControllerImpl.java:1077)
> at org.apache.activemq.artemis.core.client.impl.LargeMessageControllerImpl.setOutputStream(LargeMessageControllerImpl.java:258)
> at org.apache.activemq.artemis.core.client.impl.CompressedLargeMessageControllerImpl.setOutputStream(CompressedLargeMessageControllerImpl.java:75)
> at org.apache.activemq.artemis.core.client.impl.CompressedLargeMessageControllerImpl.saveBuffer(CompressedLargeMessageControllerImpl.java:80)
> at org.apache.activemq.artemis.core.client.impl.ClientLargeMessageImpl.checkBuffer(ClientLargeMessageImpl.java:159)
> at org.apache.activemq.artemis.core.client.impl.ClientLargeMessageImpl.getBodyBuffer(ClientLargeMessageImpl.java:91)
> ... 5 more
> Caused by: java.io.IOException: incorrect data check
> at org.apache.activemq.artemis.utils.InflaterWriter.close(InflaterWriter.java:81)
> at org.apache.activemq.artemis.core.client.impl.LargeMessageControllerImpl.sendPacketToOutput(LargeMessageControllerImpl.java:1074)
> ... 10 more
> Caused by: java.util.zip.DataFormatException: incorrect data check
> at java.util.zip.Inflater.inflateBytes(Native Method)
> at java.util.zip.Inflater.inflate(Inflater.java:259)
> at java.util.zip.Inflater.inflate(Inflater.java:280)
> at org.apache.activemq.artemis.utils.InflaterWriter.close(InflaterWriter.java:77)
> ... 11 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-10817) Incorrect data check when clearing body of large compressed message after failover
by Miroslav Novak (Jira)
[ https://issues.jboss.org/browse/WFLY-10817?page=com.atlassian.jira.plugin... ]
Miroslav Novak resolved WFLY-10817.
-----------------------------------
Resolution: Done
> Incorrect data check when clearing body of large compressed message after failover
> ----------------------------------------------------------------------------------
>
> Key: WFLY-10817
> URL: https://issues.jboss.org/browse/WFLY-10817
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 13.0.0.Final
> Reporter: Erich Duda
> Assignee: Jeff Mesnil
> Priority: Critical
>
> *Scenario*
> * There are two WildFly (Artemis) servers in dedicated shared store HA topology
> * Connection factory is configured to compress large messages
> * Live server is killed
> * Clients do failover to backup
> After the clients do failover to backup, I can see following exceptions in the log when a receiver tries to clear body of large message. The test fails because of lost messages.
> I can see this issue with Artemis 1.5.5.jbossorg-012.
> I am not able to reproduce it locally but I hit it on Jenkins every time.
> {code}
> javax.jms.JMSException: AMQ119029: Error writing body of message
> at org.apache.activemq.artemis.jms.client.ActiveMQBytesMessage.clearBody(ActiveMQBytesMessage.java:337)
> at org.jboss.qa.hornetq.apps.clients.Client.cleanMessage(Client.java:144)
> at org.jboss.qa.hornetq.apps.clients.Receiver11.receiveMessage(Receiver11.java:153)
> at org.jboss.qa.hornetq.apps.clients.ReceiverTransAck.run(ReceiverTransAck.java:89)
> Caused by: java.lang.RuntimeException: AMQ119029: Error writing body of message
> at org.apache.activemq.artemis.core.client.impl.ClientLargeMessageImpl.getBodyBuffer(ClientLargeMessageImpl.java:93)
> at org.apache.activemq.artemis.jms.client.ActiveMQBytesMessage.getBuffer(ActiveMQBytesMessage.java:363)
> at org.apache.activemq.artemis.jms.client.ActiveMQBytesMessage.clearBody(ActiveMQBytesMessage.java:335)
> ... 3 more
> Caused by: ActiveMQLargeMessageException[errorType=LARGE_MESSAGE_ERROR_BODY message=AMQ119029: Error writing body of message]
> at org.apache.activemq.artemis.core.client.impl.LargeMessageControllerImpl.sendPacketToOutput(LargeMessageControllerImpl.java:1077)
> at org.apache.activemq.artemis.core.client.impl.LargeMessageControllerImpl.setOutputStream(LargeMessageControllerImpl.java:258)
> at org.apache.activemq.artemis.core.client.impl.CompressedLargeMessageControllerImpl.setOutputStream(CompressedLargeMessageControllerImpl.java:75)
> at org.apache.activemq.artemis.core.client.impl.CompressedLargeMessageControllerImpl.saveBuffer(CompressedLargeMessageControllerImpl.java:80)
> at org.apache.activemq.artemis.core.client.impl.ClientLargeMessageImpl.checkBuffer(ClientLargeMessageImpl.java:159)
> at org.apache.activemq.artemis.core.client.impl.ClientLargeMessageImpl.getBodyBuffer(ClientLargeMessageImpl.java:91)
> ... 5 more
> Caused by: java.io.IOException: incorrect data check
> at org.apache.activemq.artemis.utils.InflaterWriter.close(InflaterWriter.java:81)
> at org.apache.activemq.artemis.core.client.impl.LargeMessageControllerImpl.sendPacketToOutput(LargeMessageControllerImpl.java:1074)
> ... 10 more
> Caused by: java.util.zip.DataFormatException: incorrect data check
> at java.util.zip.Inflater.inflateBytes(Native Method)
> at java.util.zip.Inflater.inflate(Inflater.java:259)
> at java.util.zip.Inflater.inflate(Inflater.java:280)
> at org.apache.activemq.artemis.utils.InflaterWriter.close(InflaterWriter.java:77)
> ... 11 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months