April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5529) Clustering Quickstarts Tracker

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5529?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5529: --------------------------------- Component/s: Quickstarts > Clustering Quickstarts Tracker > ------------------------------ > > Key: WFLY-5529 > URL: https://issues.jboss.org/browse/WFLY-5529 > Project: WildFly > Issue Type: Task > Components: Clustering, Quickstarts > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Tracker for clustering quickstarts. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8523) Create Clustering Command Dispatcher Quickstart

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-8523: ------------------------------------ Summary: Create Clustering Command Dispatcher Quickstart Key: WFLY-8523 URL: https://issues.jboss.org/browse/WFLY-8523 Project: WildFly Issue Type: Task Reporter: Radoslav Husar Assignee: Jason Greene -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5529) Revisit clustering quickstarts

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5529?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5529: --------------------------------- Affects Version/s: (was: 10.0.0.CR2) > Revisit clustering quickstarts > ------------------------------ > > Key: WFLY-5529 > URL: https://issues.jboss.org/browse/WFLY-5529 > Project: WildFly > Issue Type: Task > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Tracker for clustering quickstarts. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5529) Revisit clustering quickstarts

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5529?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5529: --------------------------------- Description: Tracker for clustering quickstarts. (was: * ha/failover simulation quickstart * group membership * command dispatcher * singleton deployer * JGroups channel injection * Infinispan cache injection) > Revisit clustering quickstarts > ------------------------------ > > Key: WFLY-5529 > URL: https://issues.jboss.org/browse/WFLY-5529 > Project: WildFly > Issue Type: Task > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Tracker for clustering quickstarts. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5529) Clustering Quickstarts Tracker

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5529?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5529: --------------------------------- Summary: Clustering Quickstarts Tracker (was: Revisit clustering quickstarts) > Clustering Quickstarts Tracker > ------------------------------ > > Key: WFLY-5529 > URL: https://issues.jboss.org/browse/WFLY-5529 > Project: WildFly > Issue Type: Task > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Tracker for clustering quickstarts. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4260) Schema validation errors against jboss-service_7_0.xsd

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4260?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4260: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1183165|https://bugzilla.redhat.com/show_bug.cgi?id=1183165] from MODIFIED to ON_QA > Schema validation errors against jboss-service_7_0.xsd > ------------------------------------------------------- > > Key: WFLY-4260 > URL: https://issues.jboss.org/browse/WFLY-4260 > Project: WildFly > Issue Type: Bug > Reporter: Sande Gilda > Assignee: Tomas Hofman > > When you import a quickstart containing a jboss-service.xml file, you get the following XML: > cvc-complex-type.2.3: Element 'attribute' cannot have character [children], because the type's content type is element-only. > The quickstart source is located here: > https://github.com/jboss-developer/jboss-eap-quickstarts/tree/6.4.x/hello... > I searched the https://github.com/jbossas/jboss-eap/ source code for other jboss-service.xml examples, and found a few with syntax similar to what the quickstarts use: > * sar/src/test/resources/test/serviceXmlDeployment.jar/META-INF/jboss-service.xml > * testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/sar/injection/jboss-service.xml > * testsuite/integration/smoke/src/test/java/org/jboss/as/test/smoke/sar/jboss-service.xml > * arquillian/container-managed/src/test/resources/sar-example.sar/META-INF/jboss-service.xml > * arquillian/container-remote/src/test/resources/sar-example.sar/META-INF/jboss-service.xml > There seems to be an error in the schema: > http://www.jboss.org/schema/jbossas/jboss-service_7_0.xsd > The quickstart bug is located here: https://bugzilla.redhat.com/show_bug.cgi?id=1178782 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-411) Syntax error when applying patch and exiting jboss-cli

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-411?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-411: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1408961|https://bugzilla.redhat.com/show_bug.cgi?id=1408961] from MODIFIED to ON_QA > Syntax error when applying patch and exiting jboss-cli > ------------------------------------------------------ > > Key: WFCORE-411 > URL: https://issues.jboss.org/browse/WFCORE-411 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Patching > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > > [disconnected /] patch apply > ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch > { > "outcome" : "success", > "result" : {} > } > [disconnected /] > [disconnected /] > [disconnected /] > [disconnected /] exit > logging.configuration already set in JAVA_OPTS > ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi' > ./bin/jboss-cli.sh: line 81: `fi' -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1536) NPE thrown during application redeployment, slaves taken offline

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1536?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1536: ------------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1406562|https://bugzilla.redhat.com/show_bug.cgi?id=1406562] from MODIFIED to ON_QA > NPE thrown during application redeployment, slaves taken offline > ---------------------------------------------------------------- > > Key: WFCORE-1536 > URL: https://issues.jboss.org/browse/WFCORE-1536 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Matthew Casperson > Assignee: ehsavoie Hugonnet > Fix For: 3.0.0.Alpha2 > > > We have some development Wildfly 10.0.0 servers running as slaves in a domain that frequently have WAR files redeployed. We have noticed that these slaves will often go offline after a redeployment of WAR files with the following stack trace: > {code} > 2016-05-06 05:05:51,306 ERROR [org.jboss.as.controller.management-operation] (Host Controller Service Threads - 1012) WFLYCTL0190: Step handler org.jboss.as.domain.controller.operations.deployment.DeploymentFullReplaceHandler@3f68226b for operation {"operation" => "full-replace-deployment","name" => "whatever.war","enabled" => true,"content" => [{"hash" => bytes { 0x5d, 0x12, 0x18, 0x2b, 0x1c, 0x86, 0x71, 0x27, 0x08, 0x3d, 0xf1, 0x75, 0x08, 0x29, 0xa6, 0x49, 0x1f, 0x16, 0xe8, 0x22 }}],"operation-headers" => {"access-mechanism" => "NATIVE","domain-uuid" => "802ab616-dd2c-4081-a79c-c4d54e14c384","push-to-servers" => undefined},"address" => [],"runtime-name" => undefined} at address [] failed handling operation rollback -- java.lang.NullPointerException: java.lang.NullPointerException > at org.jboss.as.repository.LocalDeploymentFileRepository.deleteDeployment(LocalDeploymentFileRepository.java:59) > at org.jboss.as.host.controller.RemoteDomainConnectionService$RemoteFileRepository.deleteDeployment(RemoteDomainConnectionService.java:756) > at org.jboss.as.domain.controller.operations.deployment.DeploymentFullReplaceHandler$1.handleResult(DeploymentFullReplaceHandler.java:181) > at org.jboss.as.controller.AbstractOperationContext$Step.invokeResultHandler(AbstractOperationContext.java:1384) > at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1366) > at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1328) > at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1311) > at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1185) > at org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase(AbstractOperationContext.java:767) > at org.jboss.as.controller.AbstractOperationContext.executeDoneStage(AbstractOperationContext.java:753) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:680) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1344) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217) > at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler.internalExecute(TransactionalProtocolOperationHandler.java:247) > at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler.doExecute(TransactionalProtocolOperationHandler.java:185) > at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$1.run(TransactionalProtocolOperationHandler.java:138) > at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$1.run(TransactionalProtocolOperationHandler.java:134) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:360) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:81) > at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$2$1.run(TransactionalProtocolOperationHandler.java:157) > at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$2$1.run(TransactionalProtocolOperationHandler.java:153) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$2.execute(TransactionalProtocolOperationHandler.java:153) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:472) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {code} > This error will usually only happen for 2 out of the 4 identically configured slaves, and seems to happen randomly, although frequently enough. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-562) Wrong order of elements in jboss-cli.xml

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-562?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-562: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1195132|https://bugzilla.redhat.com/show_bug.cgi?id=1195132] from MODIFIED to ON_QA > Wrong order of elements in jboss-cli.xml > ---------------------------------------- > > Key: WFCORE-562 > URL: https://issues.jboss.org/browse/WFCORE-562 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 1.0.0.Alpha19 > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > Fix For: 1.0.0.Beta1 > > > File bin/jboss-cli.xml has an incorrect order of elements. <history> tag should be before <resolve-parameter-values> tag. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2157) Full-replace rollback is failing with java.util.NoSuchElementException: No child 'name' exists: java.util.NoSuchElementException: No child > 'name' exists

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2157?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-2157: ------------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1434597|https://bugzilla.redhat.com/show_bug.cgi?id=1434597] from MODIFIED to ON_QA > Full-replace rollback is failing with java.util.NoSuchElementException: No child 'name' exists: java.util.NoSuchElementException: No child > 'name' exists > ---------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2157 > URL: https://issues.jboss.org/browse/WFCORE-2157 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Alpha16 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Labels: downstream_dependency > Fix For: 3.0.0.Alpha18 > > > 21:24:18,013 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 56) WFLYCTL0190: Step > > handler org.jboss.as.server.deployment.DeploymentHandlerUtil$4@6f678cd for operation {"operation" => "full-replace-deployment","name" => > > "drmk22.ear","enabled" => true,"content" => [{"hash" => bytes { 0x40, 0xde, 0xe4, 0x1d, 0xdd, 0xd0, 0xa7, 0x9f, 0xa9, 0x7a, 0x92, 0x84, > > 0xee, 0x92, 0x81, 0xea, 0x5d, 0x7b, 0xa3, 0x2a }}],"operation-headers" => {"access-mechanism" => "NATIVE","domain-uuid" => > > "cf11aeb2-70b8-4f64-aa64-67fffd9c8080"},"address" => [],"runtime-name" => undefined,"persistent" => true,"owner" => undefined} at address [] > > failed handling operation rollback -- java.util.NoSuchElementException: No child 'name' exists: java.util.NoSuchElementException: No child > > 'name' exists > > at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:387) > > at org.jboss.dmr.ObjectModelValue.requireChild(ObjectModelValue.java:302) > > at org.jboss.dmr.ModelNode.require(ModelNode.java:875) > > at org.jboss.as.server.deployment.DeploymentHandlerUtil$4$1.handleResult(DeploymentHandlerUtil.java:331) > > at org.jboss.as.controller.AbstractOperationContext$Step.invokeResultHandler(AbstractOperationContext.java:1435) > > at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1417) > > at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1379) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2017