August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3139) Optimize ValidateModelStepHandler

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3139: ---------------------------------------- Summary: Optimize ValidateModelStepHandler Key: WFCORE-3139 URL: https://issues.jboss.org/browse/WFCORE-3139 Project: WildFly Core Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.0.0.CR1 ValidateModelStepHandler is taking about 100ms during boot. We should optimize this. Some thoughts: 1) Just add 1 step for it with all needed addresses, rather than 1 step per address. 2) Doing 1) makes it possible to cache looked up resources and MRRs throughout execution so we don't need to do context.readResource[Registration]FromRoot multiple times for the same address. 3) Add a Map<String, AttributeAccess> getAttributeAccesses() to MRR so we can get all of them for an address in one go and avoid having to continually cycle through the MRR tree. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9167) mod_cluster stop status is not updated in balancer/node resource

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9167?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved UNDERTOW-1141 to WFLY-9167: ------------------------------------------------ Project: WildFly (was: Undertow) Key: WFLY-9167 (was: UNDERTOW-1141) Affects Version/s: (was: 1.4.18.Final) > mod_cluster stop status is not updated in balancer/node resource > ---------------------------------------------------------------- > > Key: WFLY-9167 > URL: https://issues.jboss.org/browse/WFLY-9167 > Project: WildFly > Issue Type: Bug > Reporter: Bogdan Sikora > Assignee: Stuart Douglas > > Operation stop on mod_cluster worker disable all contexts (send disable status to balancer) for the duration of session draining. After the session is drained ( successfully or not ), worker stops all contexts ( send stop status to balancer ). > {noformat} > [standalone@192.168.122.206:9990 /] /subsystem=modcluster:stop(waittime=-1) > { > "outcome" => "success", > "result" => {"session-draining-complete" => true} > } > {noformat} > However, status stays disabled, but functionallity is of a stopped one > {noformat} > "/karel" => { > "requests" => 0, > "status" => "disabled" > } > {noformat} > Apache httpd server as balancer correctly recognize stop status and stops contexts > {noformat} > /karel, Status: STOPPED Request: 0 Enable Disable > {noformat} > *Reproducing:* > # Set up undertow balancer with one worker > # Deploy an app to the worker > # Chech that app is correctly registered with balancer and that is enabled > # Stop the worker {noformat} /subsystem=modcluster:stop(){noformat} > # Watch if the context (deployed app) is moved to the stoped status {noformat}/subsystem=undertow/configuration=filter/mod-cluster=modcluster:read-resource(include-runtime=true, recursive=true, recursive-depth=100){noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3138) Upgrade VDX from 1.1.5 to 1.1.6

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3138?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-3138: ---------------------------------- Fix Version/s: 3.0.0.CR1 > Upgrade VDX from 1.1.5 to 1.1.6 > ------------------------------- > > Key: WFCORE-3138 > URL: https://issues.jboss.org/browse/WFCORE-3138 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Domain Management > Reporter: James Perkins > Assignee: James Perkins > Priority: Blocker > Fix For: 3.0.0.CR1 > > > Upgrade VDX from 1.1.5 to 1.1.6. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3138) Upgrade VDX from 1.1.5 to 1.1.6

by James Perkins (JIRA)

James Perkins created WFCORE-3138: ------------------------------------- Summary: Upgrade VDX from 1.1.5 to 1.1.6 Key: WFCORE-3138 URL: https://issues.jboss.org/browse/WFCORE-3138 Project: WildFly Core Issue Type: Component Upgrade Components: Domain Management Reporter: James Perkins Assignee: James Perkins Priority: Blocker Upgrade VDX from 1.1.5 to 1.1.6. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1689) maven-checkstyle-plugin does not have a version specified, so the build is non-reproducible

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1689?page=com.atlassian.jira.plugi... ] Geoffrey De Smet resolved DROOLS-1689. -------------------------------------- Resolution: Rejected > maven-checkstyle-plugin does not have a version specified, so the build is non-reproducible > ------------------------------------------------------------------------------------------- > > Key: DROOLS-1689 > URL: https://issues.jboss.org/browse/DROOLS-1689 > Project: Drools > Issue Type: Task > Components: build > Reporter: Geoffrey De Smet > Assignee: Karel Suta > Priority: Minor > > {code} > $ mvn versions:display-plugin-updates > ... > [INFO] ------------------------------------------------------------------------ > [INFO] Building OptaPlanner multiproject parent 8.0.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- versions-maven-plugin:2.1:display-plugin-updates (default-cli) @ optaplanner --- > [INFO] artifact org.apache.maven.plugins:maven-checkstyle-plugin: checking for updates from central > [INFO] artifact org.apache.maven.plugins:maven-checkstyle-plugin: checking for updates from jboss-public-repository-group > [INFO] > [INFO] All plugins with a version specified are using the latest versions. > [INFO] > [WARNING] The following plugins do not have their version specified: > [WARNING] maven-checkstyle-plugin ..................................... 2.17 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1689) maven-checkstyle-plugin does not have a version specified, so the build is non-reproducible

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1689?page=com.atlassian.jira.plugi... ] Geoffrey De Smet edited comment on DROOLS-1689 at 8/2/17 3:36 PM: ------------------------------------------------------------------ Agreed, I see it in jboss-parent on line 276. I also see the version in "mvn help:effective-pom" of optaplanner. Must be a bug in the versions plugin? It should be reporting it. was (Author: ge0ffrey): Agreed, I see it in jboss-parent on line 276. Must be a bug in the versions plugin? > maven-checkstyle-plugin does not have a version specified, so the build is non-reproducible > ------------------------------------------------------------------------------------------- > > Key: DROOLS-1689 > URL: https://issues.jboss.org/browse/DROOLS-1689 > Project: Drools > Issue Type: Task > Components: build > Reporter: Geoffrey De Smet > Assignee: Karel Suta > Priority: Minor > > {code} > $ mvn versions:display-plugin-updates > ... > [INFO] ------------------------------------------------------------------------ > [INFO] Building OptaPlanner multiproject parent 8.0.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- versions-maven-plugin:2.1:display-plugin-updates (default-cli) @ optaplanner --- > [INFO] artifact org.apache.maven.plugins:maven-checkstyle-plugin: checking for updates from central > [INFO] artifact org.apache.maven.plugins:maven-checkstyle-plugin: checking for updates from jboss-public-repository-group > [INFO] > [INFO] All plugins with a version specified are using the latest versions. > [INFO] > [WARNING] The following plugins do not have their version specified: > [WARNING] maven-checkstyle-plugin ..................................... 2.17 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1689) maven-checkstyle-plugin does not have a version specified, so the build is non-reproducible

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1689?page=com.atlassian.jira.plugi... ] Geoffrey De Smet commented on DROOLS-1689: ------------------------------------------ Agreed, I see it in jboss-parent on line 276. Must be a bug in the versions plugin? > maven-checkstyle-plugin does not have a version specified, so the build is non-reproducible > ------------------------------------------------------------------------------------------- > > Key: DROOLS-1689 > URL: https://issues.jboss.org/browse/DROOLS-1689 > Project: Drools > Issue Type: Task > Components: build > Reporter: Geoffrey De Smet > Assignee: Karel Suta > Priority: Minor > > {code} > $ mvn versions:display-plugin-updates > ... > [INFO] ------------------------------------------------------------------------ > [INFO] Building OptaPlanner multiproject parent 8.0.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- versions-maven-plugin:2.1:display-plugin-updates (default-cli) @ optaplanner --- > [INFO] artifact org.apache.maven.plugins:maven-checkstyle-plugin: checking for updates from central > [INFO] artifact org.apache.maven.plugins:maven-checkstyle-plugin: checking for updates from jboss-public-repository-group > [INFO] > [INFO] All plugins with a version specified are using the latest versions. > [INFO] > [WARNING] The following plugins do not have their version specified: > [WARNING] maven-checkstyle-plugin ..................................... 2.17 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1689) maven-checkstyle-plugin does not have a version specified, so the build is non-reproducible

by Karel Suta (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1689?page=com.atlassian.jira.plugi... ] Karel Suta commented on DROOLS-1689: ------------------------------------ [~ge0ffrey] I have tried to check it in droolsjbpm-integration pom and I found out that maven-checkstyle-plugin has already defined its version. It is defined in org.jboss:jboss-parent:22, which is parent of org.jboss.integration-platform:jboss-integration-platform-parent:7.0.0.CR9. That one is a parent of org.jboss.integration-platform:jboss-integration-platform-bom. > maven-checkstyle-plugin does not have a version specified, so the build is non-reproducible > ------------------------------------------------------------------------------------------- > > Key: DROOLS-1689 > URL: https://issues.jboss.org/browse/DROOLS-1689 > Project: Drools > Issue Type: Task > Components: build > Reporter: Geoffrey De Smet > Assignee: Karel Suta > Priority: Minor > > {code} > $ mvn versions:display-plugin-updates > ... > [INFO] ------------------------------------------------------------------------ > [INFO] Building OptaPlanner multiproject parent 8.0.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- versions-maven-plugin:2.1:display-plugin-updates (default-cli) @ optaplanner --- > [INFO] artifact org.apache.maven.plugins:maven-checkstyle-plugin: checking for updates from central > [INFO] artifact org.apache.maven.plugins:maven-checkstyle-plugin: checking for updates from jboss-public-repository-group > [INFO] > [INFO] All plugins with a version specified are using the latest versions. > [INFO] > [WARNING] The following plugins do not have their version specified: > [WARNING] maven-checkstyle-plugin ..................................... 2.17 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9160) ChunkPartitionTestCase fails with security manager

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9160?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-9160: ------------------------------------- Any test that uses a {{ModelControllerClient}} is going to have this issue. > ChunkPartitionTestCase fails with security manager > -------------------------------------------------- > > Key: WFLY-9160 > URL: https://issues.jboss.org/browse/WFLY-9160 > Project: WildFly > Issue Type: Bug > Components: Batch, Test Suite > Reporter: Hynek Švábek > Assignee: James Perkins > > ChunkPartitionTestCase fails with security manager > {code} > Suppressed: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "/home/hsvabek/securityworkspace/VERIFICATION/2017_08_02_BEAP-7584/jboss-eap-7.1.0.ER3-src/testsuite/integration/basic/target/jbossas/standalone/tmp/auth/local1937539592015998438.challenge" "read")" in code source "(vfs:/content/batch-chunk-partition.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.batch-chunk-partition.war" from Service Module Loader") > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:278) > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175) > at java.lang.SecurityManager.checkRead(SecurityManager.java:888) > at org.wildfly.security.manager.WildFlySecurityManager.checkRead(WildFlySecurityManager.java:350) > at java.io.FileInputStream.<init>(FileInputStream.java:127) > at org.wildfly.security.sasl.localuser.LocalUserClient.evaluateMessage(LocalUserClient.java:93) > at org.wildfly.security.sasl.util.AbstractSaslParticipant.evaluateMessage(AbstractSaslParticipant.java:180) > at org.wildfly.security.sasl.util.AbstractSaslClient.evaluateChallenge(AbstractSaslClient.java:59) > at org.wildfly.security.sasl.util.AbstractDelegatingSaslClient.evaluateChallenge(AbstractDelegatingSaslClient.java:54) > at org.wildfly.security.sasl.util.PrivilegedSaslClient.lambda$evaluateChallenge$0(PrivilegedSaslClient.java:55) > at java.security.AccessController.doPrivileged(Native Method) > at org.wildfly.security.sasl.util.PrivilegedSaslClient.evaluateChallenge(PrivilegedSaslClient.java:55) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.lambda$handleEvent$0(ClientConnectionOpenListener.java:644) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:898) > ... 3 more > Suppressed: javax.security.sasl.SaslException: DIGEST-MD5: Server rejected authentication > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:730) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:572) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:571) > ... > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9166) Fix OtpSaslTestCase to reflect OTP related changes in model

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-9166?page=com.atlassian.jira.plugin.... ] Josef Cacek reassigned WFLY-9166: --------------------------------- Assignee: Josef Cacek > Fix OtpSaslTestCase to reflect OTP related changes in model > ----------------------------------------------------------- > > Key: WFLY-9166 > URL: https://issues.jboss.org/browse/WFLY-9166 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > > Follow up to JBEAP-12140. > The {{OtpSaslTestCase}} has to be updated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2017